Translate Business Criteria into Configuration
Represent decisions through attributes, operators, values, and grouped conditions.
Rules Configuration
Apply Conditional Logic to Data, Presentation, and Business Behavior
Define the condition. Evaluate the record. Apply the configured behavior.
Explore the capabilityOverview
Protrak Rules Configuration enables administrators to define conditions that evaluate record information and apply configured outcomes when those conditions are met.
Rules use attributes, operators, and comparison values to describe the required logic.
Domain Modelling Studio
Configure Conditional Behavior Around Business Data
Build Rules from Business Conditions
Rule Definition
Each rule is created as a named configuration so that it can be identified and reused in the applicable platform context.
Attribute-Based Conditions
Conditions can evaluate values stored in configured attributes, including status, category, dates, selections, assignments, or other values captured on the record.
Operators and Comparison Values
A condition combines an attribute with an operator and an expected value to create a readable expression.
Multiple Conditions
Rules can include more than one condition where a decision depends on several pieces of information.
Create Reusable Conditional Logic
Maintain Rules Centrally
Configured rules are maintained in a central list where administrators can review, edit, or remove them.
Use Rules Across Configured Experiences
A rule can be selected by other platform configurations that support conditional behavior.
Adapt Rules as Requirements Change
The evaluated attribute, operator, or value can be changed without redesigning the entire user experience that uses the rule.
Control What Users See and How Information Is Presented
Conditional Visibility
Rules can be used where a component, attribute, action, or configured section should be available only when record information meets the defined condition.
Conditional Formatting
Conditions can determine when a configured visual treatment is applied, helping users identify information that requires attention or represents a particular business state.
Context-Specific Interaction
The same design can behave differently based on the evaluated data and current record.
Use Rules with Type and Attribute Configuration
Evaluate Type-Specific Information
Rules operate on attributes available to the relevant configured type.
Combine Controlled Values and Conditions
Pick lists, users, dates, numbers, and Boolean values provide controlled inputs that can be evaluated consistently by rules.
Support Broader Configured Logic
Rules can provide the condition used by other configurable capabilities, supporting different business needs through the same rule-building model.
Configured application
Representative Configuration Scenarios
- A rule can evaluate an attribute value and make a configured element available only for records that match the condition.
- A rule can be associated with conditional formatting so that a row, cell, or other supported presentation changes when the configured criteria are satisfied.
- Where a business decision depends on more than one value, the rule can combine conditions so that the configured behavior occurs only when the required combination is present.
Operational value
Business Benefits
Reuse Logic Across Applicable Configurations
Maintain named rules centrally and select them wherever the same condition is required.
Create Data-Aware User Experiences
Use evaluated record information to control visibility and presentation.
Improve Consistency
Apply the same condition whenever the related business rule must be enforced or displayed.
Respond to Changing Requirements
Update configured conditions without rebuilding each consuming form or view.
Work with the Configured Data Model
Evaluate structured attribute values associated with the applicable business type.
Domain Modelling Studio
Configure Conditional Behavior Around Business Data
Protrak Rules Configuration provides a declarative way to evaluate record information and apply conditional behavior throughout supported platform configurations. Named rules, attribute-based expressions, operators, values, and grouped conditions allow administrators to represent business criteria while retaining the flexibility to use those criteria in different contexts.
Define the condition. Evaluate the record. Apply the configured behavior.