Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.


Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

Actions Editor

The Actions Editor allows you to create and edit rule actions. Each action contains the same fields:

  • Name—The name of the action. This is what appears in the Project Explorer to identify the action.
  • Language Expression—The plain language description of the action that the rule author sees when constructing a business rule in the Rules Authoring Tool.
Important
Always enclose language expressions in double quotes.
  • Rule Language Mapping—The action expressed in code. See Rule Language Mapping for more information.

When configuring actions, parameters can be used in the Rule Language Mapping and Language Expression.

For example, the action Target Agent may be configured as follows:

  • Name—Target Agent
  • Language Expression—Target specific agent "{agent}"
  • Rule Language Mapping— $Caller.targetAgent='{agent}'

In this example, {agent} is a parameter.

Important
The above example also assumes that there is a fact called Caller with a field called targetAgent.

Actions in Linear Rules

For a linear rule, there is a maximum limit 6 columns of parameter data (including static text labels). So, for example, if your expression is:

Set customer data to: {parm1} and {parm2} and 
{parm3} and {parm4}


In this case, {parm4}, as the 7th parameter, will not be displayed. Reword your actions to fit within these boundaries.

This page was last edited on May 27, 2014, at 09:21.

Feedback

Comment on this article:

blog comments powered by Disqus