Applications → Defining Rules → About Rules → Rule Overview
Rules evaluate how an item should be routed from a decision in an application workflow. The workflow executes the outgoing transition associated with the first rule that evaluates as "true." If no rule evaluates as "true," the transition mapped to the "Otherwise" rule is executed. The "Otherwise" rule must be selected for one transition. For more information, see Conditional Routing Overview.
Rules can determine whether a transition will be available to users. If the rule evaluates to true, and if no other restrictions on the transition apply, the transition appears on the form for the source state.
Rules can be included in action expressions that define events, conditions, and actions that result in dynamic behavior on a form. If a rule specified in a condition evaluates to true or false, the action will be performed. For more information, see Working With Form Actions.
Most rules that you create in SBM Composer can be reused as report filters as well. A report filter is a predefined set of conditions that users can insert into a report definition to limit report results at runtime. This means you can build a complex rule once, and then users can reuse it in one or more SBM reports.
Rules contain evaluation criteria that includes fields from the primary table, comparison operators appropriate for the field type, and values to compare. A value can be converted into an application variable. See About Application Variables for the advantages of using application variables.
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.