Within the Compliance and Security functionality, activation rules allow you to define specific conditions to control when a form should be displayed during the execution of a task or Work Order (WO).
This mechanism ensures that compliance and security validations are requested only when truly necessary, preventing overloading the technician with irrelevant information and maintaining an efficient execution flow.
Rule Definition
Click on the Activation Rules tab.
Click on the (+) icon to add a rule.
Fill in the following fields:
a) Rule Description
Choose a clear and descriptive name that indicates its purpose. For example:
“Mandatory prior inspection”
“Post-operational checklist”
“Final quality validation”
b) Execution Timing
Select when the form should be activated:
Pre-execution (before starting the task)
Post-execution (after completing the task)
Save the Rule
After saving, your form will be available to continue creating fields and validation settings in the next steps.
Conditions
Conditions determine when the rule will be applied during the execution of the form. That is, they allow you to activate validations only when certain operational criteria are met.
Select the type of evaluation
Before adding conditions, define how they should be evaluated:
At least one is true
The rule will be activated if any of the configured conditions are met.All must be true
The rule will only be activated when all the configured conditions are met simultaneously.
Add Operational Conditions
To add a condition:
Click on the (+) icon Add condition.
A list of available fields will appear to filter the rule’s behavior.
Available segments are:
Responsible (assigned technician)
Location
Asset type
Asset code
Type (task or activity)
Priority
Classification 1
Classification 2
Cost center
Select values based on context
By choosing one of these segments, a contextual menu with options related to your operation will open.
These lists may vary depending on:
The cadastral structure of your organization
The types of assets created
The configured cost centers
The classification of tasks
The responsible team
Your company’s custom taxonomy
This allows you to adapt the conditions in a fully customized way, ensuring the rule applies only to the desired scenarios.
Activation Conditions
Regardless of the parameter, you will always find a key field:
Operation
Defines the logic that will be evaluated. Examples of operations:
“is equal to”
“is not equal to”
This operation indicates the comparison the system will perform to activate (or not) the form.