Public Sector Developer Guide

Public Sector Data Models
Public Sector Standard Objects
PublicSectrSltn Namespace
Public Sector APIs
Public Sector Standard Invocable Actions
Public Sector Tooling API Objects
Public Sector Metadata API Types
Public Sector Associated Objects
StandardValueSet Names and Standard Picklist Fields
Upload Files to Amazon S3
Accounting Subledger
Action Launcher
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
Criteria-Based Search and Filter
Decision Explainer
Discovery Framework
Engagement
Group Membership and Households
Identity Verification
Intelligent Document Reader
Interest Tagging
Omnistudio Business REST APIs
Outcome Management Developer Guide
Record Alerts
Record Rollup Definitions
Service Process Studio
Timeline
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Expression Set Options Input

Input representation of the options for executing an expression set.
JSON example
1{
2  "inputs": [
3    {
4      "age": "25",
5      "state": "CA",
6      "PatientId": "001xx000003GYjnAAG"
7    }
8  ],
9  "options": {
10    "effectiveDate": "2022-12-03T10:15:30Z",
11    "useDatesOnly": "true",
12    "actionContextCode": "9QLxx0000004C92GAE",
13    "explainabilitySpecName": "ES_One_Explainability"
14  }
15}
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