Storing product information
Pega Sales Automation retrieves product information from either an external or internal Pega Sales Automation-maintained product catalog. In contrast, Pega Sales Automation uses the internal product catalog by default.
Pega Sales Automation for Financial Services uses a four-tiered product model:
Tier number | Product model hierarchy | Example |
1 | Category | Retail banking |
2 | Family | Lending |
3 | Group | Auto loan |
4 | Product | 24-month auto loan |
For more information, see Product Designer for Financial Services documentation on the Pega Foundation for Financial Services product page.
Building product information by using the Product Designer for Financial Services workflow
Build your product information by using the external, Product Designer for Financial Services product catalog, to bring your products to market faster.
- Create products and bundles in the product catalog with the Product Studio tool.For more information, see the Pega Product Designer for Financial Services Implementation Guide.
- Indicate which products are available for sale in which territories by editing the
inclusion and exclusion tables in the Pega Foundation for Financial Services application.For more information, see the Pega Product Designer for Financial Services Implementation Guide.
- Map the Product Designer for Financial Services product structure to
the Pega Sales Automation product structure by using the
OpenMapForSAFSProductStructure data transform. This mapping
populates the product data in the D_ProductsForSAFS and
D_InterfaceProductListFromExternal data pages.For more information, see Configuring an external product data source.
- Optional: Create additional product information in the Product Designer for Financial Services application.
Configuring an external product data source
If your products are maintained in an external system of record, you must update the crmAppExtModel data transform and the D_InterfaceProductListFromExternal data page for your implementation.
- In the header of Dev Studio, search for and select the crmAppExtModel data transform.
- Locate the .IsProductSORExternalTarget and in the Source field for the target, enter true.
- Click Save.
- In the header of Dev Studio, search for and select the D_InterfaceProductListFromExternal data page.
- In the Data sources section, configure the external system of
record for your products.To see a sample interface data model, review the crmBuildSampleInterfaceData and ConstructSampleProductInstance data transforms. For more information about data page rules, see Data page rules - Using the Usage tab.
- Click Save.
Using Product Designer for Financial Services product catalog to store product data
Use Product Designer for Financial Services to create and manage financial products in a financial institution's product catalog, and to quickly bring those products to market. If you plan to use a Product Designer for Financial Services product catalog, it is helpful to understand how a product is modeled in both Pega Foundation for Financial Services and Pega Sales Automation for Financial Services.
When creating a territory in Pega Sales Automation for Financial Services, you must associate it with a parent territory and an organization unit. Territories are used to organize the sales team into groups, for example, geographic location. In Pega Sales Automation for Financial Services, organization units are classified based on market segments. By associating territories with organizations, the system displays only products related to a particular sales ops.
- Log into the application as an operator with the Sales Ops persona.
- In the navigation pane, click Territories.
- Click Create territory.
- In the Name field, enter your territory name.
- In the Parent Territory field, select your territory.
- In the Organizational unit field, add a related
organization, for example UPFS-GBB-US-Boston.
- Click OK.
Previous topic Data model Next topic Importing customer data