In ALBPM you can define dynamic business rules. A dynamic business rule is a set of one or more conditions evaluated against project variables or business parameters.
You define dynamic business rules in the business rule editor, which has two modes: A simple GUI mode and an advanced mode where you define the rule by writing PBL code. You define each business rule with a unique name.
Dynamic business rules are defined for the project. Once you define a dynamic business rule, you can use it in any process from a business rule transition, or from code in any PBL method. You can design your project so that WorkSpace participants can edit business rules at run time.
In ALBPM, conditional transitions can be used to control the flow of an instance within a process. However, standard conditional transitions are defined at design time and cannot be edited in run time.
Business rules can also be used to control process flow when used by business rule transitions. Business rule transitions are similar to conditional transitions except that they evaluate a business rule instead of a conditional expression.
The Rules Editor and rule evaluation use the standard component Fuego.Rules.Rule. For advanced use cases this component may be used directly from PBL code. This allows you to add or evaluate rules from any type of activity or BPM Object.
Dynamic business rules are considered dynamic because they can be modified at run time. Dynamic business rules can be edited by any participant who is a member of a role which has been enabled to edit business rules.