Call Decision Table action

AI-generated summary

, the decision table generates corresponding outputs for downstream processing. Flow authors add the action to tasks through the Architect interface by selecting from the Data category, naming the action, choosing a published decision table from any division, and configuring input, output, and failure outputs according to the decision table's rules schema. Configuration options include a Name field for distinctive action identification, a Decision Table dropdown with search capability, and Input definition supporting both Standard and JSON editing modes. Standard mode provides input fields derived from the decision table's input schema, while JSON mode enables direct property definition using Architect's custom JSON editor. Both modes accept literals and expressions as input values, with existing values retained when switching between modes. Output assignment allows users to select or create variables for returned JSON objects, with dot notation enabling access to specific properties through Update Data actions. Supported data types include standard types (Boolean, Date, DateTime, Enum, Integer, Number, String) and platform types (Queue), with Enum values requiring Item Keys rather than Item Labels. Null value handling follows standardized mapping rules where no values map to Null, blank literals to empty strings, and JSON nulls remain null. The action supports Success and Failure path configuration for comprehensive error handling. Success indicates error-free process completion without guaranteeing intended data results, while Failure indicates errors during action completion or result processing. Failure output mapping captures errorType and errorMessage variables to enhance flow resiliency, supporting two primary error categories: ActionInvocationLimitExceeded (triggered after five successful executions) and ExecutionOutOfCapacityError (occurring during decision table preparation and optimization phases). GeneralExecutionError and InvalidRequest errors may occasionally occur during execution, typically not in normal production workloads. Usage charges apply based on the number of rule-based decision execution API invocations, and users can configure retries to handle errors appropriately.

Use the Call Decision Table action within a task to select and execute a rule-based decision table configured previously by an administrator in Genesys Cloud. When you call a decision table, you bring the associated input and output JSON schemas into the flow. Architect handles these JSON schemas as custom JSON data types that are available only with the Call Decision Table action. However, after you add a Call Decision Table action to your flow, you can also use the custom JSON data type with an Update Data action.

Decision tables allow administrators to define input and output criteria, and if the input values meet the set criteria, the decision table produces an output. Flow authors can call a decision table, define the input values, and then use the output JSON object that the decision table produces for further processing in the flow. For more information about decision tables, see About rule-based decisions.

Note: Usage charges apply for rule-based decisions, metered for the number of times you invoke the execution API. For more information, see .

Add a Call Decision Table action to a taskClick to expand

From the Architect home page, click or hover over the Flows menu and select the desired flow type.
Create a new flow or select an existing one. The flow’s configuration page opens.
Select the task and click Click to open. The task editor opens.
From the task editor Toolbox, expand the Data category and drag a Call Decision Table action to the desired location in the task editor.
In the Name box type a meaningful name for the action. This name becomes the name of the Call Decision Table action in the task workflow.
From the Decision Table list, choose the desired decision table.
Depending on the rules schema of the selected decision table, define Input, Output, and Failure Outputs for the action to execute at runtime.
Note: The input properties that appear come from the input schema created for the decision table.
Continue building the task per your flow design, including the Call Decision Table’s Success and Failure paths.

Configure the Call Decision Table actionClick to expand

Name	Description
Name field	Type a distinctive name for the Call Decision Table action. The label you enter here becomes the action’s name displayed in the task sequence.
Decision Table	Click the arrow at the end of this list and select the appropriate decision table. To narrow the selection, type the first few letters of the appropriate decision table. You can select any published decision table regardless of the division to which the decision table belongs. However, if your decision table has a queue data type, you can use the queue only in the applicable divisions.
Input	Define the input values the action carries out at runtime. Depending on how an administrator configures the decision table in Genesys Cloud, these options vary and may be optional. Select Standard or JSON to toggle between the standard and JSON editing modes. Standard: Allows you to define the input values in the provided input fields. The fields that appear come from the input schema created for the decision table. JSON: Allows you to define the input values directly using JSON properties. In this mode, you can access Architect’s custom JSON editor and its tools to define the input values. The editor displays the schema type, whether it is input or output, and the decision table. For more information about using the custom JSON editor, see Architect custom JSON editor. Both the standard and JSON editing modes allow literals and expressions as the input values. If you have not set a property and its value in JSON mode, the corresponding field in standard mode indicates that no value is specified. Notes: Architect retains the existing values when you switch between editing modes. If there are any validation errors at the time of switching the mode, Architect alerts you and provides an option to revert to the previous valid values or cancel switching the mode. If the custom JSON data has any complex value structure such as collections, you cannot switch back to standard editing mode. Switching from literal to expression mode for the entire input object resets the input data. The option to access the custom JSON editor also disappears in expression mode.
Output	Select an existing variable or enter a new variable to assign the output JSON object returned by the decision table. Note: Architect assigns the variable with the entire JSON object returned by the decision table, allowing you to access the JSON values using dot notation. For example, if you named the variable as `Task.output`, you can access the values contained in the output JSON object using an Update Data action with a variable expression, `Task.output.<JSON property name>`.

Null value handling

The following table shows how Null values that Architect sends as inputs are validated for decision table rules:

Input value in Architect	Editing mode	Mapped value in Decision Tables
No value	Standard	Null
Blank literal value Note: This applies only to a string data type.	Standard JSON	Empty string
Not_Set	Standard JSON	Null
Null	Standard JSON	Null

Supported data typesClick to expand

The Call Decision Table action supports the following data types for input and output variables:

Standard data types
- Boolean: A Boolean expression can have only one of two values: true or false.
- Date: A Date value is a string in the format prescribed by the XML standard for date data, similar to ISO 8601.
- Date & Time: A DateTime value is a string in the format prescribed by the XML standard for date data, similar to ISO 8601.
- Enum: An Enum is a predefined list of selectable options.
  Note: Architect natively handles the Enum values as strings. When you define an Enum input value for the Call Decision Table action, you must use the Item Key that is configured under Enum options in the rules schema used by the decision table. Do not use the Item Label. Similarly, if a rule matches the input values, Architect returns the Item Key in the output variable if the result is of type Enum.
- Integer: An integer is a whole number such as 987 or 5.
- Number: A number includes any numeric values, including decimals.
- String: This is a standard text string or a custom series of alphabetical, numerical, and symbolic characters.
Platform data types
- Queue: Queues are the waiting line of interactions. In Architect, a queue expression routes a work item to an eligible queue. Queues are established and configured by the Genesys Cloud administrator.

Define failure outputsClick to expand

Name	Description
Failure Outputs	These outputs allow the flow author to map the results of any resulting errorType and errorMessage variables when the Call Decision Table action takes the failure path. The failure outputs help you anticipate potential issues and manage them effectively, improving your flow’s resiliency. errorType: A nonempty string that contains the type or category of the error. errorMessage: A non-localized failure message. The string can be empty or NOT_SET. Note: Hover over the information icon next to errorType to display the list of allowable errorType values. Select the variables that you want to assign to the failure data values returned by the Call Decision Table action. You can use the following errorType values: ActionInvocationLimitExceeded: If a flow has successfully run the Call Decision Table action five times, any subsequent invocations of the action take the failure path. ExecutionOutOfCapacityError: When a flow executes a newly published or rarely used decision table, Genesys Cloud first prepares the decision table and optimizes it for use. Though this preparation process is typically very fast, an occasional error may occur for execution requests made during this phase. The error generally does not occur during normal production workloads. If this error occurs, the flow must simply retry the execution. It is recommended that you configure enough retries to handle it. After the decision table has been prepared, Architect executes it without any issue. GeneralExecutionError: A general error occurred during execution. InvalidRequest: The request was not formed properly for execution. For example, an HTTP 400 error occurred. Note: Click the arrow next to Failure Outputs and expand or collapse the list of variables.

Name

Description

Failure Outputs

These outputs allow the flow author to map the results of any resulting errorType and errorMessage variables when the Call Decision Table action takes the failure path. The failure outputs help you anticipate potential issues and manage them effectively, improving your flow’s resiliency.

errorType: A nonempty string that contains the type or category of the error.
errorMessage: A non-localized failure message. The string can be empty or NOT_SET.

Note: Hover over the information icon next to errorType to display the list of allowable errorType values.

Select the variables that you want to assign to the failure data values returned by the Call Decision Table action.

You can use the following errorType values:

ActionInvocationLimitExceeded: If a flow has successfully run the Call Decision Table action five times, any subsequent invocations of the action take the failure path.
ExecutionOutOfCapacityError: When a flow executes a newly published or rarely used decision table, Genesys Cloud first prepares the decision table and optimizes it for use. Though this preparation process is typically very fast, an occasional error may occur for execution requests made during this phase. The error generally does not occur during normal production workloads.
If this error occurs, the flow must simply retry the execution. It is recommended that you configure enough retries to handle it. After the decision table has been prepared, Architect executes it without any issue.
GeneralExecutionError: A general error occurred during execution.
InvalidRequest: The request was not formed properly for execution. For example, an HTTP 400 error occurred.

Note: Click the arrow next to Failure Outputs and expand or collapse the list of variables.

Define success and failure pathsClick to expand

Path	Description
Success	A completed Success path indicates that the system encounters no errors during the process. It is not a measure of whether the system receives data that is the intended result or functionality.
Failure	This path indicates that there was an error attempting to complete the action or a problem processing the results from the Call Decision Table action. Drag the appropriate action below the Failure path.

[NEXT] Was this article helpful?

Get user feedback about articles.

Name

Description

Name field

Type a distinctive name for the Call Decision Table action. The label you enter here becomes the action’s name displayed in the task sequence.

Decision Table

Click the arrow at the end of this list and select the appropriate decision table. To narrow the selection, type the first few letters of the appropriate decision table.

You can select any published decision table regardless of the division to which the decision table belongs. However, if your decision table has a queue data type, you can use the queue only in the applicable divisions.

Input

Define the input values the action carries out at runtime. Depending on how an administrator configures the decision table in Genesys Cloud, these options vary and may be optional.

Select Standard or JSON to toggle between the standard and JSON editing modes.

Standard: Allows you to define the input values in the provided input fields. The fields that appear come from the input schema created for the decision table.
JSON: Allows you to define the input values directly using JSON properties. In this mode, you can access Architect’s custom JSON editor and its tools to define the input values. The editor displays the schema type, whether it is input or output, and the decision table. For more information about using the custom JSON editor, see Architect custom JSON editor.

Both the standard and JSON editing modes allow literals and expressions as the input values. If you have not set a property and its value in JSON mode, the corresponding field in standard mode indicates that no value is specified.

Notes:

Architect retains the existing values when you switch between editing modes. If there are any validation errors at the time of switching the mode, Architect alerts you and provides an option to revert to the previous valid values or cancel switching the mode.
If the custom JSON data has any complex value structure such as collections, you cannot switch back to standard editing mode.
Switching from literal to expression mode for the entire input object resets the input data. The option to access the custom JSON editor also disappears in expression mode.

Output

Select an existing variable or enter a new variable to assign the output JSON object returned by the decision table.

Note: Architect assigns the variable with the entire JSON object returned by the decision table, allowing you to access the JSON values using dot notation. For example, if you named the variable as Task.output, you can access the values contained in the output JSON object using an Update Data action with a variable expression, Task.output.<JSON property name>.

Input value in Architect

Editing mode

Mapped value in Decision Tables

No value

Standard

Null

Blank literal value

Note: This applies only to a string data type.

Standard
JSON

Empty string

Not_Set

Standard
JSON

Null

Standard
JSON

Null

Name	Description
Failure Outputs	These outputs allow the flow author to map the results of any resulting errorType and errorMessage variables when the Call Decision Table action takes the failure path. The failure outputs help you anticipate potential issues and manage them effectively, improving your flow’s resiliency. errorType: A nonempty string that contains the type or category of the error. errorMessage: A non-localized failure message. The string can be empty or NOT_SET. Note: Hover over the information icon next to errorType to display the list of allowable errorType values. Select the variables that you want to assign to the failure data values returned by the Call Decision Table action. You can use the following errorType values: ActionInvocationLimitExceeded: If a flow has successfully run the Call Decision Table action five times, any subsequent invocations of the action take the failure path. ExecutionOutOfCapacityError: When a flow executes a newly published or rarely used decision table, Genesys Cloud first prepares the decision table and optimizes it for use. Though this preparation process is typically very fast, an occasional error may occur for execution requests made during this phase. The error generally does not occur during normal production workloads. If this error occurs, the flow must simply retry the execution. It is recommended that you configure enough retries to handle it. After the decision table has been prepared, Architect executes it without any issue. GeneralExecutionError: A general error occurred during execution. InvalidRequest: The request was not formed properly for execution. For example, an HTTP 400 error occurred. Note: Click the arrow next to Failure Outputs and expand or collapse the list of variables.

Name

Description

Failure Outputs

errorType: A nonempty string that contains the type or category of the error.
errorMessage: A non-localized failure message. The string can be empty or NOT_SET.

Note: Hover over the information icon next to errorType to display the list of allowable errorType values.

Select the variables that you want to assign to the failure data values returned by the Call Decision Table action.

You can use the following errorType values:

ActionInvocationLimitExceeded: If a flow has successfully run the Call Decision Table action five times, any subsequent invocations of the action take the failure path.
ExecutionOutOfCapacityError: When a flow executes a newly published or rarely used decision table, Genesys Cloud first prepares the decision table and optimizes it for use. Though this preparation process is typically very fast, an occasional error may occur for execution requests made during this phase. The error generally does not occur during normal production workloads.
If this error occurs, the flow must simply retry the execution. It is recommended that you configure enough retries to handle it. After the decision table has been prepared, Architect executes it without any issue.
GeneralExecutionError: A general error occurred during execution.
InvalidRequest: The request was not formed properly for execution. For example, an HTTP 400 error occurred.

Note: Click the arrow next to Failure Outputs and expand or collapse the list of variables.

Path

Description

Success

A completed Success path indicates that the system encounters no errors during the process. It is not a measure of whether the system receives data that is the intended result or functionality.

Failure

This path indicates that there was an error attempting to complete the action or a problem processing the results from the Call Decision Table action. Drag the appropriate action below the Failure path.

Call Decision Table action

[NEXT] Was this article helpful?

Loading...

Call Decision Table action

[NEXT] Was this article helpful?