Another example could be multiplying the quantity by a price and then writing the result to a field in a target document.
When an Action is called from a Ruleset, it can only return a single argument. On the other hand, Business Process tasks (called by a Business Process), can pass in more than one parameter which can be changed from within the task. This is something to consider when choosing to use Actions and/or Tasks in your integrations.
There are over 100 additional Actions shipped with the Studio. For more information refer to the sections on Actions (complete list, or by category).
The Ruleset editor contains the Actions panel which displays groups of selectable Ruleset Actions used to perform some type of operation on your data. Categories displayed in the panel reflect the general usage of those Actions within. Expanding each folder displays individual Actions that can be added to a Rule. (See the section Ruleset Actions by Category).
Open Projects ( in Project Explorer) also display certain resources that can also be used as a rule, when applicable. An example of this is calling a Business Process from a Ruleset.
Two ways to add Actions to a Rule
Add Actions to Rules by following either one of these methods.
- Click the New Rule (or Composite) button to display the list of all available Actions, and then double-click the Action to select it from the list.
- Drag an Action directly from the Action panel to a specific Rule, or to the empty field in the Rule section of the Properties view.
Note: Either way still requires you to define values for the Inputs and Outputs in the Properties view.
The two methods shown in this example create a Rule with the RawMoveAction.
Comments
0 comments
Please sign in to leave a comment.