How to Create a Condition?
Create Condition
To create a condition in BRE Log in to Labor > Navigate to Main Menu > BRE > Conditions.
You can also create and edit conditions directly from the Rule edit screen without navigating to Conditions. To do this, navigate to Rule > Select a Rule > Click Edit (to modify an existing condition) or Click Create (to create a new condition). By default, the "Created for" dropdown will be set to Rule, as the condition is being created or edited in the context of an existing Rule.
Create Condition screen is displayed.

Figure 1.1: Create Condition screen
Steps to Create Conditions
Header Section

Condition Name: Enter a descriptive name for the condition in the text field.
Example: "Late Payment Trigger" or "High Order Value Condition."
Defined For Entity: Select the entity the condition applies to. This could be any of the following entities:
Booking lines, Contact, Company, Inventory Master, Purchase Order, Schedule, Opportunity, Order Item Lines, etc.
Example: If Entity is selected as “booking lines” which is child entity of planning order. Conditions defined at the planning order level can include conditions for child entities like booking lines, ensuring comprehensive rule application across related entities.
Example: Select Order Item Lines if the condition is based on specific details related to an order item, like the order amount.
Created For: Choose what the condition is created for:
Rules: If the condition is part of a rule for automating business processes.
Templates & Recipients : If it's related to templates that are used to structure messages, If the condition applies to notifying specific recipients.
Active: Check this box if the condition should be active and in effect. If the condition is not active, it won’t even list in the condition list.
Save: After setting up the condition, the Save button is used to store the changes.
Condition Grid

This below table helps in understanding how to define conditions in a rule creation process within the system.
Field Name | Example/Options |
---|---|
When?: Specifies when the condition is evaluated, such as on a change in data or during the creation or deletion of records. | Always: This option means the rule will be triggered ‘every time' it is evaluated, regardless of any changes or actions in the R2 system such as Orders, PO, Warehouse tasks etc. On Change: This option means the rule will be triggered ‘only when the data associated with the rule changes’. On Create: This option means the rule will be triggered ‘when a new record is created’ from the system.
On Delete: This option means the rule will be triggered ‘only when an entity or record is deleted’ from the system.
|
Field: The specific field that the condition checks. This could be anything from order amount to billing details. | Condition Fields are listed based on entity selected. Active, Annual Revenue, Billable, Category, Customer Type, Description etc., |
Consider: Determines if the condition compares the current value or the previous value of the field. | Current Value, Previous Value. Example: If you want to define the condition before the value change or after the value change. Example:
|
Criteria: Defines the type of comparison used for evaluation. | Criteria is listed based on Field selected for entity. |
Compare With: Specifies other fields or values that the selected field will be compared to. | Compares with gives the list based on selected field If "Billing Contact" is selected in field, options may include: Advance, Amount, Billing Term, Billing Customer, Billing Contact |
Value: The actual value that is compared with the field's value | Value will be checked for Number, Date and name pattern. If selected field is date you can set compare with date, if you select field as amount then compare should be entered with values.
|
Ignore Time: If checked, time data is ignored when comparing fields that contain date values. | Yes or No |
Relational Operator: Logical operator (e.g., AND, OR) used to combine multiple conditions. | AND, OR Example for AND:
When both of these conditions are true, the notification is triggered. In short, when a booking line is created, AND the rule's value is 5000, a notification will be sent. Example for OR:
So, in simple terms: When a booking line is created, OR if the Start date is set to a date that is more than 30 days from today, the condition will be met and notification sent. |
Save | After setting up the condition, the Save button is used to store the changes. |
Add/Delete (Icons): Use these icons to add a new criteria or delete an existing one. | The add icon allows you to create additional conditions if needed. The delete icon removes unwanted conditions. |