Document Decision

Invoke a Decision Table, accept key-value pairs that match the Decision Table keys, and return either Document Types or Document Categories and the Document Types associated with them.

For example, one use case is applying for a driver’s license. Based on questions about where the applicant lives, a Decision Table can list the documents to be uploaded for proof of identity.

The Decision Table must be active and have DocumentDecisionRequirement, a platform object, as its Source Object. This platform object stores the Decision Table’s inputs, outputs, and business rules.

One of the Decision Table outputs must be DocumentReferenceObjectId, which references a Document Type or Document Category object. An optional output is isUploadRequired, which sets the default for the Document Categories property isRequired. These two outputs don’t appear in the connect API’s outputs.

Resource

1/connect/document-matrix/document-decision/{decisionTableId}

The {decisionTableId} parameter is the ID of the decision table.

Available Version

59.0

Requires Chatter

HTTP Methods

POST

Request Body for POST

JSON Example

1{
2  "inputs": [
3    {
4      "Country": "USA",
5      "State": "CA"
6    }
7  ]
8}

Properties

Name	Type	Description	Required or Optional	Available Version
`inputs`	List<Map<String, Object>>	List of inputs passed to Decision Table. Each key is a Decision Table field name, and each value is valid for that field.	Required	59.0

Response Body for POST

Document Decision Response