Agentforce for Business Rules Engine

Considerations for Referencing Business Rules Engine in Agent Actions

Before you reference an expression set or a decision table in an agent action, review these considerations.

• Only active expression set and decision table versions can be enabled as agent actions.
  

  Note You can’t deactivate an expression set or decision table that is used as an agent action. First delete the agent action, and then deactivate the expression set or decision table.
• Expression sets that use a context definition can't be enabled as agent actions.
• For expression sets, each variable that's defined in the expression set version is added as an input or output on the agent action, using the variable's data type and description.
• For decision tables, each input and output field that's defined on the decision table is added as an input or output on the agent action, using the field's data type and description.
• If a decision table returns multiple output rows, an agent action reads only the first result. For an agent to work with multiple matching rows, call the decision table from an expression set, and reference the expression set in the agent action instead.
• Business Rules Engine variables and fields that use data types unsupported by agent actions aren't available to map as inputs or outputs.
• An agent action created from an expression set or decision table doesn't automatically pick up later changes to that expression set or decision table's variables or fields. If you add, remove, or change a variable or field after you create the agent action, update the agent action to bring its inputs and outputs back in sync.
• Access to an agent action that references an expression set or decision table follows the access control configured for that expression set or decision table in Business Rules Engine, in addition to any permissions required for the agent action itself.