Program fields in Logiqc to automatically assign key settings including who the issue is reported to, viewing permissions and notifications.
For legacy subscription plans, Business Rules Builder is an optional add-on for your platform. Click here to find out more.
About business rules
Business Rules give you more control over how events are coded, making sure reports follow your organisation's policies. This helps prevent important issues from being missed. You can create as many custom business rules as you need.
IF this, THEN that
Business Rules use a simple "IF this, THEN that" logic. When a user reports something (like an incident), and their report matches the "IF" part of a rule, the "THEN" part of the rule automatically fills in the related fields.
Key features
Evaluate all rules
Logiqc checks all Business Rules rules in order, from top to bottom. This means the order is important.
Add or Replace results
When setting who gets notified and who can view a reported item, you can choose to Add or Replace. Adding the results will combine the results like an 'AND' statement. For example, you can say 'if a rule is true, then add another user into the list of who will be notified'.
Selecting Replace, on the other hand, will override previous results and just apply the new business rule. This is why the order of your business rules is important.
Drag and drop ordering
You can easily change the order of your rules by dragging and dropping them into the new desired position. This is useful when you want a rule to take priority over others. So, if you wanted a single 'overarching' rule to take override all others, you would sent the values to Replace and drag the the rule to the bottom of the list. For example, if an incident was reported with a severity of SAC 1, you might want to change the pathway it takes by setting who it's reported to, who can see it and who is notified.
Create a business rule
You will need the admin permission 'Edit system configuration' to create and edit Business rules. Learn more about permissions here
- Switch to Admin mode via your user account menu and select Business rules.
- Choose the register to work with and click on the edit icon.
- Click on the + Add business rule button to add a new rule for the register.
Set 'If' conditions
These are the conditions that will activate the rule when they match the user's selection.
Note:
- Some fields allow you to select multiple options eg. multiple incident types can be selected. This is the same as saying 'if either of these values match to the user's selection'.
- Business Area can also be set as a 'Then' action but it can't be both an 'If' and 'Then'.
Set 'Then' actions
'Then' actions determine how to fields are populated when there is a match between the user's selection and the 'If' conditions.
'Then' actions can automatically populate values in the following fields:
- Report this issue to
- Related meeting
- Related business area
- Access control (Teams and/or Individuals)
- User notification
Note:
- If Business Area is selected as an 'If' condition, it won't be available as a 'Then' action.
Set access control
Set the access controls that the rule will apply to the item being reported. The rule will automatically assign viewing permissions to the Teams and/or individuals you select.
Because a user's report in Logiqc might trigger multiple business rules, you need to choose how the resulting access control settings will be applied. Select "Add to previous results" to combine the rules or select "Replace previous results" to override and replace discard any previous settings.
Set notifications
Set the users to be notified when the rule is applied. The rule will automatically populate the Notifications field with the users you select.
Because a user's report in Logiqc might trigger multiple business rules, you need to choose how the resulting notification settings will be applied. Select "Add to previous results" to combine the rules or select "Replace previous results" to override and replace discard any previous settings.
Example
In the following example from the Incident register, the fields within the Assign component of the form are designed to automatically populate based on the choices made by the user in the Incident details component.
