Extend Default Context Definition for Work Order Estimation

You can extend the Out-Of-The-Box (OOTB) context to create a custom context definition with additional attributes, without modifying existing ones. Similarly, you can extend the mapping to include additional mappings, without changing the existing ones.

Required Editions

Available in: Lightning Experience

Available in: Automotive Cloud, Communications Cloud, Consumer Goods, Energy and Utilities Cloud, Manufacturing Cloud, Service Cloud, and Media Cloud. View edition availability.

User Permissions Needed
To set up Salesforce Pricing	Salesforce Pricing admin AND Salesforce Pricing Manager AND Salesforce Pricing Design Time User

Note

Work Order Estimation supports only OOTB or extended context definitions and mappings

1. From Setup, in the Quick Find box, enter Context Service, and then select Context Definitions.
2. On the Standard Definitions tab, find WorkEstimationCoveragesContext, click the dropdown menu, and choose Extend.
   The Context Definition page appears.
3. Enter context definition details.
   1. Enter a name and description for the custom context.
   2. Click Next.
      The Create Structure page appears.
4. New nodes aren't supported. Click Next.
   The Add Attributes page appears.

   

   Note Don’t modify existing nodes.
5. Add attributes.
   1. Add new attributes at the correct node level. For each new attribute, select the appropriate Type (Input, Output, or InputOutput) and DataType.
   2. If applicable, fill in the Referred Object field (this is auto-populated based on the hierarchy).
   3. Click Next.
      The Create Attribute Tags page appears.

      

      Note

      Don’t modify existing attributes.

6. Create attribute tags.
   1. Create unique attribute or context tags for the new attributes.
      These tags must be unique within the entire context. These tags are used to identify attributes across levels within the context and also in the Pricing Procedure Definition.

      

      Note

      Don’t modify existing attributes or their attribute tags.

      It’s currently not recommended to assign multiple attribute tags to a single attribute.

   2. Save your changes.
      The new context definition is created and listed on the Custom Definitions tab with its status set to Inactive.
7. On the Custom Definitions tab, open the custom definition you created.
8. Go to the Map Data tab.
   By default, an extension of the OOTB context mapping (IFSQuoteLineItemEntityMapping) is listed.
9. From the dropdown menu for IFSQuoteLineItemEntityMapping, select Edit.
   The Edit Mapping page appears.
10. Select the Mark as Default check box and then click Map.
    The Context Mapping’s builder page opens in a new tab.
11. Link the new or existing unmapped attributes on the Structure tile to the corresponding entity fields on the Connect Objects tile. First, select the attribute, then select the entity field.
    You can map the fields only if the parent node level maps to the corresponding entity. These mappings are provided by default as this mapping extends the OOTB context mapping.
12. Map attributes to entity fields within foreign key references in the parent entity.
    1. Click the Add icon next to the foreign key field.
       For example, Product2Id.
    2. Select an appropriate field from the list.
    3. Make sure the entity field path is correct, doesn’t contain repeated characters, and then map the desired attribute to this field.
    4. Save your changes.
13. On the Context Definitions page, go to the Custom Definitions tab.
14. From the dropdown menu for the context definition you created, select Activate.
    The status of the context definition changes to Active.