Skip to content

A BPA Failure End Event's message property is set to a variable (like `${errorMessage}`) populated by an earlier script task, but the variable never actually gets substituted into the message shown to the user.

Answer

Direct variable substitution inside the Failure End Event's own message text doesn't reliably work — instead, create a projection custom action wrapping Error_SYS.Appl_General (or equivalent), call that action from the workflow as an IFS API step, and pass your dynamic message as the action's parameter using variable substitution there; this reliably surfaces the actual computed message text to the user, in a way that setting it directly on the Failure End Event does not.

← Browse Workflows and automation questions