Skip Ahead to:

5 topics

  1. Overview
  2. Navigation
  3. How a Rule Works
  4. A Quick Example
  5. Learn More

Overview

Business Rules 2.0 automates repetitive work in your project. A rule watches for an event, checks your conditions, and then does the work for you.

In a project, a few repetitive tasks need to be done regularly or on specific business criteria. Business Rules 2.0 automates these tasks within forms created through Forms 2.0. This eliminates repetitive work and improves accuracy. Therefore, with Business Rules 2.0, you can automate things in your projects depending on specific criteria.

However, a rule can do much more than set a field. For example, it can show or hide tabs, blocks, and fields on a form. It can also update, create, move, block, flag, or close cards, and send email notifications. Finally, it can run on a schedule.

Advantages of Using Business Rules

  • You do not need any coding or scripting.
  • You reduce manual work and speed up everyday processes.
  • Your team saves time for more important things.
  • You can see the flow of each rule, which helps you understand its triggers, conditions, and actions.

To configure a Business Rule 2.0, navigate to the project, hover over the top breadcrumb, expand the Configure menu, and select Business Rules 2.0.

Note

The menu is only accessible to the Project manager persona of that project.

Once the page opens, it lists the rules you have created. Then you can open, copy, or delete any of them. To learn about its columns and row actions, see Business Rules 2.0 Listing Page.

How a Rule Works

Every rule follows the same pattern: when something happens, if your conditions are met, then do the actions. Also, the editor draws the rule as a visual flow, so you can read it at a glance.

Visual flow of a rule: WHEN On any field change of Defect, IF Priority is Critical, THEN Flag card on the Current card

In detail, a rule is made up of the following parts:

  • Rule applies to: the personas the rule runs for. Choose All User Personas or pick specific personas.
  • Trigger (WHEN): the event that starts the rule, such as On create, On update, or On schedule. There are nine triggers.
  • Conditions (IF and ELSE IF): checks on field values that decide whether the actions run. You can combine conditions with AND and OR, and group them.
  • Actions (THEN): the work the rule does. The available actions depend on the trigger and on the context, which tells the action which card or record to act on.

Finally, for every option in these parts, see Business Rules 2.0: Triggers, Conditions and Actions.

After you save a rule, you can switch it on or off with the Enable Rule toggle. You can also turn on Execution logs to see every time the rule ran and whether it succeeded.

A Quick Example

For example, suppose you want every Defect whose Priority is set to Critical to be flagged automatically. Perform the following steps –

  1. First, go to Configure → Business Rules 2.0 and select ADD.
  2. Then enter a name, such as Flag Critical Defects, and select the persona in Rule applies to. Select NEXT.
  3. Next, select the trigger On update and the card type Defect. Select NEXT.
  4. After that, select Add → Condition. Set the field to Priority, the condition to is, and the value to Critical. Select NEXT.
  5. Then select Add → Action. Set the context to Current card and the action to Flag card, enter a flagging comment, and select NEXT.
  6. Finally, select SAVE. The rule is enabled by default.

Also, for a screenshot at every step, see How to Create a Business Rule 2.0.

Learn More

  • Was this helpful?
  • Yes   No