Industries Common Resources Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Industries Common Resources
AI Accelerator and Scoring Framework
Action Launcher
Actionable List Members
Actionable Segmentation
Business Rules Engine
Expression Set
Expression Set Standard Objects
Expression Set Business APIs
Resources
Request Bodies
Business Rules Input
Context Definition Input
Expression Set Advanced Condition Step Input
Expression Set Aggregation Step Input
Expression Set Assignment Step Input
Expression Set Condition Criteria Input
Expression Set Condition Expression Step
Expression Set Custom Element Parameter Input
Expression Set Custom Element Step Input
Expression Set DES Token Mapping Input
Expression Set Input
Expression Set Lookup Table Step Input
Expression Set Options Input
Expression Set SubExpression Step Input
Expression Set Version Input
Expression Set Version Step Input
Expression Set Version Variable Input
Response Bodies
Expression Set Invocable Actions
Expression Set Metadata API Types
Expression Set Tooling API Objects
Decision Table
Decision Explainer for Expression Set
Lookup Tables
Collections and Recovery
Context Service
Criteria-Based Search and Filter
Data Processing Engine, Batch Management, and Monitor Workflow Services
Digital Lending
Discovery Framework
Decision Explainer
Einstein Relationship Insights
Einstein Standard Invocable Actions
Engagement
Group Membership and Households
Identity Verification
Intelligent Document Reader
Intelligent Form Reader
Interest Tagging
Omnistudio Business APIs
Outcome Management Developer Guide
Outreach List
Process Compliance Navigator
Record Alerts
Record Rollup Definitions
Scheduled Reminders
Sentiment Insights
Service Process Studio
Timeline
Virtual Calls
Associated Objects
IndustriesSettings
Industries Object Access by Community License
Access Industries Features Deployed Using Managed Packages
PDF

Expression Set Options Input

Input representation of the options for executing an expression set.
JSON example
{
  "inputs": [
    {
      "age": "25",
      "state": "CA",
      "PatientId": "001xx000003GYjnAAG"
    }
  ],
  "options": {
    "effectiveDate": "2022-12-03T10:15:30Z",
    "useDatesOnly": "true",
    "actionContextCode": "9QLxx0000004C92GAE",
    "explainabilitySpecName": "ES_One_Explainability"
  }
}
Properties
Name Type Description Required or Optional Available Version
actionContext​Code String The code of the action context used to log explainability for a specific execution of an expression set.

To exclude decision explanations for expression set version steps from action logs, ensure that you exclude the actionContextCode and explainabilitySpecName properties from the payload.

Note

 Optional 55.0
effectiveDate String The date from which an expression set comes into effect. The date format is yyyy-mm-dd’T’hh:mm:ss’Z.

Multiple versions of an expression set can exist with different date ranges. For example, Version 1 is effective before December 2019, and Version 2 is effective from January 2020 to the present. If you specify effectiveDate as "2019-03-15T00:00:00Z", Version 1 is executed. If you do not specify effectiveDate, the currently active version, Version 2, is executed.

Note

 Optional 55.0
explainability​Spec​Name String The name of the explainability specification that is used to log explainability for a specific execution of an expression set.

To exclude decision explanations for expression set version steps from action logs, ensure that you exclude the actionContextCode and explainabilitySpecName properties from the payload.

Note

 Optional 55.0
useDatesOnly String Specifies that only the date portion (yyyy-mm-dd) of the value of effectiveDate field is to be used at the time of execution. Optional 55.0
versionNumber String The version number of the expression set version record. Optional 55.0