Decision Explainer

Decision Explainer has setup objects that capture logs for how a rule or an expression set ran, making it easy for reviewers to explain the outcome of the rule to users. For example, a student wants to know why they received a lesser discount on their course fee than what they expected. With Decision Explainer, the student application reviewer can check the application's history and the expression set that's used to evaluate the application, and provide the student the reason for receiving a lesser discount.

• Create Application Subtype Definitions
  Create application subtype definitions to define the types of applications used in your Decision Explainer entities.
• Create Business Process Type Definitions
  Define the types of business processes that are applied to a rule.
• Create Explainability Action Definitions
  Define where the metadata of your business rules is stored.
• Create Explainability Action Versions
  Define and store versions of the explainability actions used by business rules that use Decision Explainer.
• Decision Explainer Default Limits
  To ensure optimal performance, consider these default limits while using Decision Explainer to retrieve action logs. If your business requires any default limits to be raised, contact Salesforce customer support for further guidance.
• Decision Explainer for Developers
  Developers in your Salesforce org can employ Decision Explainer developer resources to use and extend the Decision Explainer functionality.
• Decision Explainer for Expression Sets
  Use Decision Explainer with Business Rules Engine to show your users explanations for the results of steps in an expression set, and to capture action logs for expression set runs. Store explanations for expression steps in explainability message templates. And then add the templates to your expression set steps for which you want to show explanations. When you simulate the expression set version, switch to the Concise view option to preview how your users see the explanations.