@salesforce/afv-skills 1.65.0 → 1.66.0

package/skills/fsc-pricing-salesforce-omnistudio-switch/SKILL.md

@@ -1,123 +0,0 @@
----
-name: fsc-pricing-salesforce-omnistudio-switch
-parent: "digital-origination-pricing-setup"
-purpose: "Repoint versioned Digital Lending OmniStudio components to Salesforce Pricing."
-description: "Switch Digital Lending OmniStudio components from the default Product Configurator path to the explicit Salesforce Pricing path. Creates new versions of DigitalLendingApplicantIntake and DigitalLendingApplicantIntakeSecured, replaces DigitalLendingOfferConfigurator with DigitalLendingViewOffer, and creates new DigitalLendingConfirmOffer and DigitalLendingConfirmOfferAAE card versions that replace DigitalLending_PricingEngineOfferConfiguratorFinalOffer with DigitalLending_PricingEngineFinalOffer. Reuses approved OmniStudio Phoenix and LiveCards operations, preserves existing active versions, and verifies every component tree or builder JSON before activation."
-metadata:
-  version: "1.0"
----
-
-# Switch Digital Origination OmniStudio components to Salesforce Pricing
-
-Use this sibling only when the admin explicitly selects **Salesforce Pricing**. Product Configurator
-is the Digital Lending default and requires no component repointing.
-
-## Preconditions
-
-- Target-org alias confirmed
-- Digital Lending sample/application components installed
-- OmniStudio Admin and Salesforce Pricing access verified
-- Source and target component names below resolve uniquely
-- Current active versions captured for rollback
-
-If any component is missing, do not create a look-alike component. Report the missing package artifact.
-
-## Required changes
-
-| Component | Type | Remove | Add |
-|---|---|---|---|
-| `DigitalLendingApplicantIntake` | OmniScript | `DigitalLendingOfferConfigurator` | `DigitalLendingViewOffer` |
-| `DigitalLendingApplicantIntakeSecured` | OmniScript | `DigitalLendingOfferConfigurator` | `DigitalLendingViewOffer` |
-| `DigitalLendingConfirmOffer` | FlexCard/LiveCard | `DigitalLending_PricingEngineOfferConfiguratorFinalOffer` | `DigitalLending_PricingEngineFinalOffer` |
-| `DigitalLendingConfirmOfferAAE` | FlexCard/LiveCard | `DigitalLending_PricingEngineOfferConfiguratorFinalOffer` | `DigitalLending_PricingEngineFinalOffer` |
-
-Never edit the current active version in place.
-
-## OmniScript operations
-
-Use approved SOR
-`connect-api/omni-studio-phoenix/omnistudio-connect-api__sfdc.omnistudio.connect.api_oas_67.0`:
-
-- `get-fetch-omni-process-list` (`getFetchOmniProcessList`) - find process/version IDs
-- `get-fetch-omni-process-data` (`getFetchOmniProcessData`) - read full process tree
-- `post-clone-omni-process` (`postCloneOmniProcess`) - clone OmniScript/Integration Procedure
-- `post-omniscript-delete-element` (`postOmniscriptDeleteElement`) - delete by element name and
-  OmniScript ID
-- `post-omniscript-insert-element` (`postOmniscriptInsertElement`) - insert element with
-  parent/order/type/designer name
-- `post-omniscript-build-json`, `save-bp` (`saveBP`), `lwc-prep` (`lwcPrep`) - build, persist, and
-  compile as supported
-- `post-upsert-omni-process` (`postUpsertOmniProcess`) - persist and explicitly set `isActive` after
-  the cloned version has been verified
-
-### Workflow for each intake OmniScript
-
-1. Find all versions and identify the active source version.
-2. Read the complete element tree. Locate `DigitalLendingOfferConfigurator` and capture parent ID,
-   order, type, properties, and neighboring elements.
-3. Verify `DigitalLendingViewOffer` exists and determine the correct insert contract.
-4. Clone the source process. Confirm the clone is a new, inactive working version.
-5. Delete `DigitalLendingOfferConfigurator` from the clone only.
-6. Insert `DigitalLendingViewOffer` at the captured parent and order; preserve branch/navigation data.
-7. Build, save, and compile. Re-read the clone and verify exactly one target element and no removed
-   element remain.
-8. Activate only after the new version validates, using `post-upsert-omni-process` with the complete
-   verified process definition and `isActive=true`; never send a partial upsert. Re-read `isActive`.
-   Preserve the former active version for rollback.
-
-`post-clone-omni-process` is the closest headless primitive to New Version; harness-verify version and
-activation semantics in the target org. If it cannot safely create a new version, use the OmniScript
-Designer New Version checkpoint.
-
-## FlexCard/LiveCard operations
-
-Use approved-but-draft SOR
-`connect-api/omni-studio-orion/industries-livecards-connect-api`:
-
-- `list-card-versions` (`listCardVersions`)
-- `get-card-version` (`getCardVersion`)
-- `create-card-version` (`createCardVersion`)
-- `update-card-version` (`updateCardVersion`)
-- `validate-card` (`validateCard`)
-- `compare-versions` (`compareVersions`)
-
-### Workflow for each confirmation card
-
-1. Resolve the card and active version. Confirm it is DynamicUiCard/LiveCard-backed; do not assume all
-   classic FlexCards use this API.
-2. Read complete builder JSON and locate the old Integration Procedure reference.
-3. Create a new version.
-4. Read-modify-write only the Integration Procedure reference; preserve all unrelated JSON, data
-   sources, actions, styling, and visibility rules.
-5. Validate the card and re-read it. Confirm old reference count is zero and new reference count is
-   exactly one at the intended location.
-6. Compare old/new versions and report the minimal diff.
-7. The current LiveCards input schemas expose builder JSON/version creation but no activation write,
-   even though reads expose `isActive`. Always use the FlexCard UI to activate the verified new version,
-   then re-run `list-card-versions` and require `isActive=true`.
-
-If the component is not compatible with LiveCards APIs or the draft SOR fails, use the full UI
-checkpoint: OmniStudio -> FlexCards -> card -> New Version -> Edit -> remove old IP -> add
-`DigitalLending_PricingEngineFinalOffer` -> validate/save. Whether created through API or UI, activation
-is a required UI checkpoint until a typed activation input is available. Resume with a read-back.
-
-## Idempotency and rollback
-
-- If an inactive version already contains the exact desired change, validate and reuse it.
-- Never create repeated new versions on every rerun.
-- OmniScript rollback uses the complete prior definition with `post-upsert-omni-process` and
-  `isActive=true` after verification. FlexCard rollback uses the UI to reactivate the captured previous
-  version, followed by `list-card-versions` read-back.
-- Do not modify source IPs or target OmniScripts; only update references in cloned consumers.
-
-## Output contract
-
-For each component, report component ID, old active version, new version, validation state, activation
-state, removed reference, new reference, and rollback version. Pass this evidence to
-nested `pricing-procedure` for the Salesforce Pricing branch.
-
-## Definition of done
-
-All four newly versioned components are valid and active with only the intended reference changes,
-and the prior active versions remain available for rollback. Any UI checkpoint not yet verified means
-partial completion.

package/skills/fsc-product-act2-catalog-categories-create/SKILL.md

@@ -1,82 +0,0 @@
----
-name: fsc-product-act2-catalog-categories-create
-description: "Sub-skill of digital-origination-product-setup. Act 2 — create the Digital Lending catalog (Sales type, unique code, effective start/end dates), then create catalog categories (e.g. Home Loans) and optionally subcategories under it."
-metadata:
-  version: "1.0"
----
-
-# Act 2 — Catalog + Categories/Subcategories
-
-Sources:
-- [Create a Catalog for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_create_catalog.htm&type=5)
-- [Create Catalog Categories and Subcategories for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_categories.htm&type=5)
-
-## Purpose
-
-Create the catalog that holds Digital Lending products, and the category hierarchy inside
-it so applicants can browse.
-
-## Prereq gate
-
-- Act 1 complete (PCM Designer perm set assigned).
-
-## Step 1 — Create the catalog
-
-Help-doc summary: A catalog is a collection of the products you sell, organized into
-categories for easier findability. Create a catalog before creating catalog categories +
-assigning products. Use Product Catalog Management.
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Catalogs**.
-2. From the catalogs list view page, click **New**.
-3. In the New Catalog window, enter the details:
-   - **Name** and **description** for the catalog.
-   - **Unique catalog code**.
-   - **Effective start date** — date/time the catalog becomes available to users.
-   - **Effective end date** — date/time after which the catalog is no longer available.
-   - **Type** — select **Sales**. (A Sales catalog is a catalog for products; a Service Process is a catalog for a suite of services.)
-4. Save.
-
-**Verify.** Query the created record; confirm all six fields populated as entered.
-
-## Step 2 — Create catalog categories
-
-Help-doc summary: To organize + group products, create catalog categories and
-subcategories. A product can be assigned to more than one category / subcategory. The
-Categories tab shows a hierarchical view — expandable/collapsible to show/hide
-subcategories.
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Catalogs**.
-2. From the catalogs list view, click the catalog created in Step 1.
-3. Click **Categories**.
-4. Click **Create Category**.
-5. In the New Catalog Category window, enter:
-   - **Name** and **description** for the category.
-   - **Catalog** — auto-populated with the parent catalog.
-   - **Parent category** — select if this category is a subcategory. If it's the first (top-level) category in the hierarchy, leave blank.
-   - **Sort order** — determines the order categories are shown to users in the purchase flow.
-   - **Category code**.
-6. Save.
-
-**Verify.** Re-open the Categories tab; confirm the new category appears in the hierarchy at
-the expected level.
-
-## Optional — subcategories
-
-Repeat Step 2 with **Parent category** set to a previously-created category. Help-doc Article
-5 notes: use subcategories to further group products. Article 14 considerations state:
-"When you use parent and child categories, categorize products by using subcategories."
-
-## End state
-
-- One catalog exists — name / description / unique code / effective start / effective end / type=Sales.
-- At least one top-level category exists under the catalog (e.g. Home Loans).
-- Optional subcategories exist as needed.
-
-## See also
-
-- Salesforce Help: Product Catalog Management
-- Salesforce Help: Create Catalog Categories and Subcategories

package/skills/fsc-product-act3-attributes-create/SKILL.md

@@ -1,249 +0,0 @@
----
-name: fsc-product-act3-attributes-create
-description: "Sub-skill of digital-origination-product-setup. Act 3 — create the Home Loan product, populate the LoanTerm attribute picklist (180/240/360 Months), and define the five product attributes: MinLoanAmount, LoanTerm, MaxLoanAmount, OfferValidPeriod, OmniScriptName."
-metadata:
-  version: "1.0"
-  cliTools:
-  - tool:
-    - "sf"
-    semver: ">=2.0.0"
----
-
-# Act 3 — Product + Attribute Picklist + Attribute Definitions
-
-Sources:
-- [Create a Product for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_product.htm&type=5)
-- [Create Loan Term Attribute Picklists for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_loan_term_picklist.htm&type=5)
-- [Define and Update Product Attributes for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_define_attributes.htm&type=5)
-- [Create Offer Validity Attribute for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_offer_attribute.htm&type=5)
-- [Create Omniscript Name Attribute for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_omniscipt_name_attribute.htm&type=5)
-
-## Purpose
-
-Create the Home Loan product record. Populate the loan-term picklist. Define the five
-product-attribute definitions needed by the Home Loans classification (Act 4).
-
-## Prereq gate
-
-- Acts 1 + 2 complete.
-
-## Ordering (within this act)
-
-1. Product record.
-2. LoanTerm picklist (parent `AttributePicklist`) + its picklist values (`AttributePicklistValue`) — MUST exist before the LoanTerm attribute definition (the attribute references the picklist by `PicklistId`).
-3. Attribute definitions: MinLoanAmount, LoanTerm, MaxLoanAmount, OfferValidPeriod, OmniScriptName.
-4. **Activate every attribute definition (`IsActive = true`) BEFORE proceeding to Act 4.** `ProductClassificationAttr` rejects inactive attributes with `INVALID_INPUT: You can associate only active attributes with a product classification.` (Org-verified 2026-07-29.)
-
-For the field-by-field attribute table, see
-[`../../references/attributes-and-defaults.md`](../../references/attributes-and-defaults.md).
-
-## Schema — required fields (org-verified 2026-07-29)
-
-| Object | Required fields (createable, non-defaulted, non-nillable) |
-|---|---|
-| `Product2` | `Name` |
-| `AttributePicklist` | `Name` (Status enum: Draft/Active/Inactive; DataType enum: Boolean/Date/Datetime/Number/Text/Currency/Percent) |
-| `AttributePicklistValue` | `Name`, `PicklistId`, `Code`, `Value` |
-| `AttributeDefinition` | `Name`, `Code`, `DataType`, `Label` (org-verified required set; `Code` is the unique API-name token the UI labels "API Name"). **Do NOT send `Status`** — this entity has no `Status` column (`400 INVALID_FIELD`). Activate separately via **`IsActive` (boolean)**, which defaults to `false` on create. |
-
-## Step 1 — Create the product
-
-Help-doc summary: Products are all the items and services you sell. Products can also be
-non-sellable. Two types: **simple** (no associated product hierarchy) and **bundled** (a
-group sold as one unit).
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Products**.
-2. From the product list view, click **New**.
-3. Create a product. For example, **Home Loan**.
-4. Save.
-
-**Verify.** Query the created record.
-
-Repeat for additional products as the admin requires.
-
-## Step 2 — Create LoanTerm picklist values
-
-Help-doc summary: Create loan term picklist values of 180 Months, 240 Months, 360 Months. A
-picklist represents all possible values for an attribute when the attribute has multiple
-values. **You must define picklists before creating picklist attributes.**
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Attribute Picklists**.
-2. On the Attribute Picklists list view, select **All Attribute Picklists**.
-3. Click **Loan Term**.
-4. Click the **Related** tab. In the Attribute Picklist Values section, click **New**.
-5. Create the 180 Months value:
-
-   | Field | Value |
-   |---|---|
-   | Picklist | LoanTerm |
-   | Name | 180 Months |
-   | Status | Active |
-   | Display Value | 180 Months |
-   | Sequence | 1 |
-
-   Click **Save & New**.
-6. Create the 240 Months value:
-
-   | Field | Value |
-   |---|---|
-   | Picklist | LoanTerm |
-   | Name | 240 Months |
-   | Status | Active |
-   | Display Value | 240 Months |
-   | Sequence | 1 |
-
-   Click **Save & New**.
-7. Create the 360 Months value:
-
-   | Field | Value |
-   |---|---|
-   | Picklist | LoanTerm |
-   | Name | 360 Months |
-   | Status | Active |
-   | Display Value | 360 Months |
-   | Sequence | 1 |
-
-   Click **Save**.
-
-**Verify.** Query picklist values under the LoanTerm picklist; confirm three active rows.
-
-## Step 3 — Define MinLoanAmount, LoanTerm, MaxLoanAmount attributes
-
-Help-doc summary: Attributes capture properties of products. Define name, label, and data
-type when creating.
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Attribute Definitions**.
-2. From the Attribute Definitions list view, click **New**.
-3. Create MinLoanAmount:
-
-   | Field | Value |
-   |---|---|
-   | Name | MinLoanAmount |
-   | Label | Minimum Loan Amount |
-   | API Name | MinLoanAmount |
-   | Data Type | Number |
-   | Description | Minimum loan amount. |
-
-   Click **Save & New**.
-4. Create LoanTerm:
-
-   | Field | Value |
-   |---|---|
-   | Name | LoanTerm |
-   | Label | Loan Term |
-   | API Name | LoanTerm |
-   | Data Type | Picklist |
-   | Picklist | LoanTerm |
-   | Description | Loan term. |
-   | Active | Select |
-
-   Click **Save & New**.
-5. Create MaxLoanAmount:
-
-   | Field | Value |
-   |---|---|
-   | Name | MaxLoanAmount |
-   | Label | Maximum Loan Amount |
-   | API Name | MaxLoanAmount |
-   | Data Type | Number |
-   | Description | Maximum loan amount. |
-   | Active | Select |
-
-   Click **Save**.
-
-**Note (Article 14 considerations).** MinLoanAmount and MaxLoanAmount are described as
-Type **currency** in the sample-data considerations. Help-doc Article 6 lists them as
-Data Type = Number. Follow the help-doc step above unless the admin's org uses the
-Agentforce Financial Services sample data, in which case use currency to match the
-sample-data expectations.
-
-## Step 4 — Create OfferValidPeriod attribute
-
-Help-doc summary: Use OfferValidPeriod to configure the validity in days for an offer
-generated for a product. When configured, the pricing engine uses OfferValidPeriod and
-populates the offer's valid start date and end date.
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Attribute Definitions**.
-2. Click **New**.
-3. Enter:
-
-   | Field | Value |
-   |---|---|
-   | Name | OfferValidPeriod |
-   | Label | Offer Valid Period |
-   | API Name | OfferValidPeriod |
-   | Data Type | Number |
-   | Description | Offer Valid Period |
-4. Save.
-
-## Step 5 — Create OmniScriptName attribute
-
-Help-doc summary: Use OmniScriptName to configure the loan intake process.
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Attribute Definitions**.
-2. Click **New**.
-3. Enter:
-
-   | Field | Value |
-   |---|---|
-   | Name | OmniScriptName |
-   | Label | OmniScript Name |
-   | API Name | OmniScriptName |
-   | Data Type | Text |
-   | Description | Stores the name of the Omniscript that launches the applicant intake experience. |
-4. Save.
-
-**⚠️ Do NOT set the attribute-level `DefaultValue` at create time (org-verified
-2026-07-29).** Help Article 8 lists
-`DigitalLending_DFApplicantIntakeSecured_English` as the attribute-level default, but the
-classification-level `ProductClassificationAttr.DefaultValue` set in Act 4 Step 3 is
-silently **overridden** by the attribute-level default at PCA-insert time — the stored PCA
-value becomes the AttributeDefinition-level value regardless of what the PCA insert
-passes. Skip the attribute-level default here and let Act 4 own the per-classification
-default (`ApplicantIntake` for unsecured, `ApplicantIntakeSecured` for secured). If a
-legacy org already has the attribute-level default set, either clear
-`AttributeDefinition.DefaultValue` before Act 4 or issue an explicit `UPDATE
-ProductClassificationAttr SET DefaultValue = <secured|unsecured value>` after each PCA
-insert.
-
-## Activation step (mandatory before Act 4)
-
-After all five attribute definitions are created, set `IsActive = true` on each:
-
-```text
-UPDATE AttributeDefinition
-   SET IsActive = true
- WHERE Id IN (<the five ids>)
-```
-
-Or via `sf data update record --sobject AttributeDefinition --record-id <id> --values "IsActive=true"`.
-
-**Verify** by re-querying: every attribute must show `IsActive = true` before Act 4
-begins. Skipping this step causes Act 4 Step 2 (`ProductClassificationAttr` insert) to
-fail with `INVALID_INPUT: You can associate only active attributes with a product
-classification.`
-
-## End state
-
-- Home Loan product record exists (or the admin's chosen product name).
-- LoanTerm `AttributePicklist` exists (parent record) with three active `AttributePicklistValue` rows: 180 Months / 240 Months / 360 Months. Each value carries `Code`, `Value`, `DisplayValue`.
-- Five attribute definitions exist: MinLoanAmount, LoanTerm, MaxLoanAmount, OfferValidPeriod, OmniScriptName — with the field values above.
-- **All five attribute definitions have `IsActive = true`.** This is the Act 4 prereq.
-
-## See also
-
-- Salesforce Help: Product
-- Salesforce Help: Picklists; Create Picklists
-- Salesforce Help: Dynamic Attributes; Create Attributes
-- Salesforce Help: OmniScripts
-- [`../../references/attributes-and-defaults.md`](../../references/attributes-and-defaults.md) — consolidated attribute field/default table

package/skills/fsc-product-act4-classification-assignment-create/SKILL.md

@@ -1,196 +0,0 @@
----
-name: fsc-product-act4-classification-assignment-create
-description: "Sub-skill of digital-origination-product-setup. Act 4 — create the Home Loans product classification, assign the five attributes to it, set default values (MinLoanAmount=1000, MaxLoanAmount=100000, OmniScriptName=ApplicantIntake or ApplicantIntakeSecured, OfferValidPeriod=30), point the Home Loan product's Based On field to the classification, and assign the product to the Home Loans category."
-metadata:
-  version: "1.0"
----
-
-# Act 4 — Classification + Assignment
-
-Sources:
-- [Create Personal Loans Product Classification for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_classifications.htm&type=5)
-- [Assign and Edit Attributes in the Personal Loans Product Classification for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_edit_attributes.htm&type=5)
-- [Add Product Classification to Personal Loan Product for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_classification_loan.htm&type=5)
-- [Assign Products to Catalog Categories for Digital Lending](https://help.salesforce.com/s/articleView?id=ind.fsc_lending_catalogs_products_assign_categories.htm&type=5)
-
-## Purpose
-
-Tie together the pieces built in Acts 2 + 3: create the classification, attach the
-attributes with defaults, point the product at the classification, and assign the product
-to a category.
-
-## Prereq gate
-
-- Acts 1, 2, 3 complete.
-- Five attribute definitions exist (Act 3): MinLoanAmount, LoanTerm, MaxLoanAmount, OfferValidPeriod, OmniScriptName.
-- **All five attribute definitions have `IsActive = true`.** `ProductClassificationAttr` inserts fail with `INVALID_INPUT: You can associate only active attributes with a product classification.` otherwise. Verify with `SELECT Name, IsActive FROM AttributeDefinition` before running Step 2. Org-verified 2026-07-29.
-- Home Loan product exists (Act 3).
-- Home Loans category exists (Act 2).
-
-## Schema — required fields (org-verified 2026-07-29)
-
-| Object | Required fields (createable, non-defaulted, non-nillable) | Notes |
-|---|---|---|
-| `ProductClassification` | `Name`, `Code` | Status enum: Draft/Active/Inactive. Default is Draft. Set to Active on create. |
-| `ProductClassificationAttr` | `Name`, `ProductClassificationId`, `AttributeDefinitionId` | Also creatable: `AttributeCategoryId`, `IsHidden`, `IsRequired`, `Status`, `Sequence` (**int**), `DefaultValue`, `IsPriceImpacting`. Referenced `AttributeDefinition.IsActive` MUST be true. |
-| `Product2` — `BasedOnId` | reference, updateable | Field name confirmed: **`BasedOnId`** (help doc says "Based On"). |
-| `ProductCategoryProduct` (junction) | `ProductCategoryId`, `ProductId` | Insert one junction record per product ↔ category link. |
-
-## Ordering (within this act)
-
-1. Create classification (`ProductClassification` with `Status=Active`).
-2. Assign attributes to classification (one `ProductClassificationAttr` per attribute; requires `AttributeDefinition.IsActive=true`).
-3. Edit default values on the assigned attributes (set `DefaultValue` on each `ProductClassificationAttr`).
-4. Set product `BasedOnId` = classification Id.
-5. Insert `ProductCategoryProduct` junction — product ↔ category.
-
-## Step 1 — Create Home Loans product classification
-
-Help-doc summary: A product classification is a template used to create similar products.
-Create a classification you can assign attributes to and base products on.
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Product Classifications**.
-2. On the Product Classifications list view page, click **New**.
-3. Enter:
-
-   | Field | Value |
-   |---|---|
-   | Product Classification Name | Home Loans |
-   | Code | Home Loans |
-   | Status | Active |
-4. Save.
-
-## Step 2 — Assign the five attributes to the classification
-
-Help-doc summary: Product classifications hold a collection of attributes describing
-general properties of products. Assign individual attributes or a collection via attribute
-categories.
-
-**Steps.**
-
-1. From App Launcher, select **Product Catalog Management**, then select **Product Classifications**.
-2. Click the Home Loans classification created in Step 1.
-3. Click the **Attributes** tab.
-4. In the Attributes section, click **Assign**.
-5. Select **Assign Attributes by Category** and click **Next**.
-6. Select **LoanTerm**, **MaxLoanAmount**, **MinLoanAmount**, **OmniScriptName**, and **OfferValidPeriod** and click **Assign**.
-
-**Note (Article 14 considerations).** Add these five attributes in the same attribute
-category or as uncategorized attributes.
-
-## Step 3 — Edit default values
-
-**Steps.**
-
-1. From App Launcher, select **Product Catalog Management**, then select **Product Classifications**.
-2. Click the Home Loans classification.
-3. Click the **Attributes** tab.
-4. For each attribute, click the action icon → **Edit** → enter the default value → save:
-
-   | Attribute | Default (unsecured) | Default (secured — auto/home loan) |
-   |---|---|---|
-   | MinLoanAmount | 1000 | 1000 |
-   | MaxLoanAmount | 100000 | 100000 |
-   | OmniScriptName | ApplicantIntake | ApplicantIntakeSecured |
-   | OfferValidPeriod | 30 | 30 |
-
-**Secured-loan variant.** Help-doc note (Article 10): for a secured loan product — a home
-loan is secured — enter **ApplicantIntakeSecured** as the default value for OmniScriptName.
-
-LoanTerm has no default value edit in the help doc — its values come from the picklist
-created in Act 3.
-
-**Programmatic equivalent.** Combine Steps 2+3 into one `ProductClassificationAttr` insert
-per attribute (set `DefaultValue` at create time):
-
-```text
-ProductClassificationAttr:
-  Name: <attr name>                 # e.g. MinLoanAmount
-  ProductClassificationId: <classification Id>
-  AttributeDefinitionId: <attr def Id>
-  Sequence: <int>                   # 10 / 20 / 30 / 40 / 50 recommended (int, not "1")
-  Status: Active
-  DefaultValue: <value>             # per table above; omit for LoanTerm
-```
-
-`Sequence` is **integer** (not the string "1" the UI shows for picklist-value sequences).
-
-**⚠️ PCA DefaultValue can be overridden by AttributeDefinition-level default (org-verified
-2026-07-29).** If the referenced `AttributeDefinition.DefaultValue` is non-null (e.g.
-OmniScriptName was created per help Article 8 with
-`DigitalLending_DFApplicantIntakeSecured_English`), the insert silently stores the
-AttributeDefinition-level value in `ProductClassificationAttr.DefaultValue` — even when
-the PCA insert body explicitly passes a different `DefaultValue`. Two fixes:
-- **Preferred (per Act 3 update):** don't set `AttributeDefinition.DefaultValue` at create
-  time; own the default at the PCA (classification) layer.
-- **Alternative for legacy orgs:** after each PCA insert, verify with `SELECT DefaultValue
-  FROM ProductClassificationAttr WHERE Id = <pca id>` and issue `UPDATE
-  ProductClassificationAttr SET DefaultValue = <target value>` if it drifted.
-
-**Verify.** Re-open each attribute on the classification; confirm the default value saved.
-Programmatically: `SELECT Name, DefaultValue FROM ProductClassificationAttr WHERE
-ProductClassificationId = <id>` and confirm each row matches the target unsecured/secured
-value from the table above.
-
-## Step 4 — Set the product's Based On to the classification
-
-Help-doc summary: Assign the Home Loans classification to the product created in Act 3.
-
-**Steps.**
-
-1. From the App Launcher select **Product Catalog Management**, then click **Products**.
-2. Click the product created in Act 3 (for example, Home Loan).
-3. In the **Based On** field, select **Home Loans**.
-4. Save.
-
-**Programmatic.** UPDATE `Product2` SET `BasedOnId` = <classification Id>. Field name
-confirmed as `BasedOnId` (org-verified 2026-07-29).
-
-**Verify.** `SELECT Id, Name, BasedOnId FROM Product2 WHERE Id = <product Id>`. `BasedOnId`
-must equal the classification's Id.
-
-## Step 5 — Assign the product to a catalog category
-
-Help-doc summary: Organize products by assigning them to catalog categories and
-subcategories.
-
-**Steps.**
-
-1. From the App Launcher, select **Product Catalog Management**, then select **Categories**.
-2. From the Categories list view, click the category (or subcategory) to which you want to assign one or more products.
-3. From the Category page, click the **Related** tab.
-4. In the Products section, click **Assign Products**.
-5. Select the Home Loan product.
-6. Click **Next** and save.
-
-**Programmatic.** The UI "Assign Products" action inserts a `ProductCategoryProduct`
-junction row:
-
-```text
-ProductCategoryProduct:
-  ProductCategoryId: <category Id>
-  ProductId: <product Id>
-```
-
-**Verify.** `SELECT Id FROM ProductCategoryProduct WHERE ProductId = <product Id> AND ProductCategoryId = <category Id>`. Exactly one row expected.
-
-**Note (Article 14 considerations).**
-- You must add products to a category if you're not using parent and child categories.
-- When you use parent and child categories, categorize products by using subcategories.
-
-## End state
-
-- `ProductClassification` exists with `Status=Active` (e.g. Home Loans).
-- Five `ProductClassificationAttr` rows exist under the classification, each with the correct `DefaultValue` for the loan variant (unsecured OR secured). LoanTerm carries no `DefaultValue`.
-- `Product2.BasedOnId` = classification Id.
-- One `ProductCategoryProduct` row links product ↔ category (or subcategory if using parent/child hierarchy).
-
-## See also
-
-- Salesforce Help: Product Classifications
-- Salesforce Help: Assign Attributes to a Product Classification
-- Salesforce Help: View Products Based on a Product Classification
-- Salesforce Help: Assign Products to Catalog Categories and Subcategories
-- [`../../references/attributes-and-defaults.md`](../../references/attributes-and-defaults.md)