Business Rules 101: Configuring Actions and Conditions in appRules

In this Business Rules 101 post, we will cover Actions and Conditions – the building blocks of the appRules Business Rules Engine.

At an atomic level, the activities in appRules are based on Actions and Conditions.  A very simplistic description of appRules Actions and Conditions is shown below:

Action         – What to do

Condition    – When to perform the action

 

Actions, Conditions and composite activities based on them are accessible through the appRules Core Business Rules module:

We will take a look at the first two activities in the business rules module (Action and Condition).  The other activities will be considered in future posts since they are beyond the scope of this introductory post.

 

Action

To add an Action to your business rules project, drag and drop the Action activity on to the designer.  The Configure Action window will be displayed:

appRules includes thousands of Actions right out of the box.  Only the actions that you have licensed will show up in the Action Tree.

The Actions are organized in Action Categories.  The following are the available categories:

  • DataSource
  • Primitives
  • Data Quality
  • Execution

 

To configure an Action, expand the category on the action tree and drill down to select the action.

For example, to associate entities in Microsoft Dynamics CRM, expand the CRM group under the DataSource category.  Select DynamicsCRM, and then double-click on AssociateEntities as show below:

The following window will be displayed:

Set the properties and click the OK button.

Condition

To add a Condition to your business rules project, drag and drop the Condition activity on to the designer.  The Configure Condition window will be displayed:

appRules includes thousands of Conditions right out of the box.  Only the conditions that you have licensed will show up in the Condition Tree.

The Conditions are organized in Condition Categories.  The following are the available categories:

  • DataSource
  • Primitives
  • Data Quality
  • Execution

 

To configure a Condition, expand the category on the condition tree and drill down to select the condition.

For example, to verify if a date is the first day of a fiscal year quarter, expand the DateTime group under the Primitives category as show below:

Double click on IsDateFirstDayOfFiscalYearQuarter.  The following window will be displayed:

Set the properties and click the OK button.  Execution of a Condition activity returns a value (True or False) that you can evaluate in other activities such as the If, While, DoWhile, etc. activities.

 

 

Conclusion

The appRules Business Rules Engine is based on appRules Actions and Conditions.  With thousands of out-of-the-box, no-code activities, appRules makes it easy to compose powerful business rules projects without writing code.

Whether you are building a complex decision table, evaluating conditions for scoring and rating purposes, or adding rules to data quality projects, appRules actions and conditions make it easy to accomplish your task.

You can download appRules with sample business rules projects at: http://www.appstrategy.com/appRulesTrial

Author: appStrategy Team

appStrategy Support Team blog

1 thought on “Business Rules 101: Configuring Actions and Conditions in appRules”

Comments are closed.