Loading
Feature degradation | Gmail Email delivery failureRead More
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Create and Map Context Definitions

            You are here:

            1. Salesforce Help
            2. Docs
            3. Financial Services Cloud Admin Guide

            Create and Map Context Definitions

            Define the context structure in which you want to determine the parameters for Integration Orchestration. The data from the context service is mapped as inputs to the Business Rules Engine (BRE).

            Required Editions

            Available in Lightning Experience in Developer, Enterprise, Professional, and Unlimitededitions for Industries clouds where Context Service is enabled.
            User Permissions Needed
            To create context definitions: Context Service Admin
            To run context definitions: Context Service Runtime

            Context Service defines the relationship between the nodes and the attributes within each node. By using nodes and attributes, your users can easily access relevant data from the mapped data source. 

            1. Create the context definition for a root node, and add relevant attributes.
              For example, add ApplicationForm as the root node, and add the Name and Stage attributes. For more information on how to create a context definition, see Create Context Definitions.
            2. Create child node or sibling node with the relevant attributes.
              For example, add Applicant and ApplicationFormProduct as child or sibling nodes. For more information on how to create a context definition, see Create Context Definitions.
            3. Create a sibling node and call it Integrations.
            4. Add attributes for the root node and child node. For example, for ApplicationForm and Applicant child node, add Name, Stage, and UsageType and select the appropriate Type and Data Type.
            5. Add attributes for the Integrations node: RunAsUserId, IntegrationProviderDefId, RelatedObject, Status, and Id. The attributes under Integrations are fixed and are mapped as output to the decision table.
              Integrations node with attributes.
            6. To create attribute tags, click Generate All Tags.
              The tag names should exactly match the attribute names.
            7. For the Integrations node, enter the tag name as IntegrationProviderDcsnRqmt.
            8. Save your changes.
            9. Open the custom context definition created.
            10. Add mapping to the context definition.
            11. For the Mapping Definition Details, enter a name and description.
            12. Select both Automatic Salesforce object mapping and Mark as Default.
            13. Click Next and then click Map.
            14. Click Connect Objects.
            15. For Select Data Sources, look for and select the IntegrationProviderDcsnRqmt object.
            16. Map the attributes of the context definition to the sObjects. For example, in Integration Orchestration, map the attributes with the Integration Provider Decision Requirement object as shown in the image.
              Context definition attributes mapped to sObjects.
              Mapping the Status attribute isn't required.
            17. Map the attributes as inputs for the decision table.
              ApplicationForm object defined in Context Service with Stage and Name attributes.
              After the fields are mapped, the data from the context service are used for the input and output parameters in the decision table.
            18. Activate the context definition.

            See Also

             
            Loading
            Salesforce Help | Article