Decision Table - Customer Discount

The Decision Table - Customer Discount project illustrates the appRules Evaluate Decision Table activity.

Product & Hosting Options

Platform Product Availability

The workflow activities and other modules used in this sample project are available in the following appRules Platform products:

Platform Product

Availability

Hosting & Execution Environment

If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:

Hosting Option

Recommended for Project

Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL

The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Decision Table - Customer Discount" project.

EvaluateDecisionTable is the only workflow activity required for configuring a decision table in appRules. It can be accessed from the Business Rules module in the toolbox.

For simplicity, we have used a single activity in this sample project. In an actual project, the EvaluateDecisionTable activity is used in conjunction with other activities.

Also, in this sample, the values to be evaluated are passed to the EvaluateDecisionTable activity from the arguments used to run the project. In an actual project, the values passed to the activity typically come from record values in data sources such as CRM, ERP, Databases, etc. The project can also be called via the appRules WebAPI.

Note that the View Execution Results box of the EvaluateDecisionTable activity is checked to display the result when the activity is executed. This is the practice for debugging appRules activities. At deployment, the View Execution Results box is automatically deactivated if the project is not run in interactive mode.

You can experiment with this project by making changes and running the project to view results. No external data sources are required.

Define Conditions to be used in the decision table:

Define Actions to be used in the decision table:

Set up Conditions and Actions:

Define Decision Conditions Items:

Define Decision Action Items:

Configure Condition and Action combinations:

Run the project directly and pass arguments to be used for evaluating the decision table:

View the Execution Results and notice that row 3 in the result table below meets the criteria as defined by the arguments passed to the project.

The project can also be called via the appRules WebAPI.