Business Rule
What is a business rule?
A business rule for an infraon product refers to a specific guideline or constraint that governs the behavior, processes, or operations within the context of that product's infrastructure. These rules are typically defined and enforced to ensure consistency, compliance, and efficient functioning of the infraon product.
Types in business rule
There are two types of business rules:
Load Balancer: The ticket allocation system ensures a balanced workload distribution between users. It automatically routes any additional tickets beyond the initial allocation to the following user until the same number of tickets per user is reached.
For example, if user one has seven tickets and user two has five tickets, the next ticket will be automatically added to user two, since user one already has seven tickets, which is greater than user two's five.
Round Robin: Despite any existing ticket imbalances, prospective tickets raised are sequentially assigned to the first user, disregarding the need for a balanced distribution among users.
For Example, User One has five tickets, and User Two has three tickets; prospective tickets are automatically assigned to User One even though User Two has fewer tickets.
Instructions to add business rules
Go to Infraon Configuration → Infraon Automation → Business Rule.
Click Add.
On the Add Business Rule page, configure the rule using the fields described below.
Rule Name*
Enter a rule name
A unique identifier for the business rule. Example: Auto Assign L1 Tickets.
Module*
Select a module from the dropdown
Specifies the module where the rule is applied. Available options:
Ticket (rules applied to incidents/tickets)
Problem (rules applied to problem records)
Request (rules applied to service requests)
Approval (rules applied to approval workflows)
CMDB (rules applied to configuration items and assets).
The selected module controls the available rule types and rule setup fields.
Type*
Select a rule type from the dropdown
Defines the action performed by the rule. Options vary by module:
Assignment Rule: Automatically assigns records to a group based on conditions.
Delayed Assignment Rule: Assigns records after a defined time duration if conditions are met.
Set Value: Updates one or more fields with specified values when conditions match.
Priority Matrix Rule: Calculates priority based on combinations of urgency and impact. Immediate Delegation Rule: Instantly delegates approvals from one approver to another.
Duration-Based Delegation: Delegates approvals after a defined duration with optional reminders.
Precedence*
Select priority level
Determines the order in which rules are evaluated when multiple rules match. Options: High, Medium, Low. Higher precedence rules are executed first.
Description
Enter rule description
Short explanation of the rule’s purpose. Example: Assign network tickets to the L1 team.
Is Enable
Enable or disable the rule
Controls whether the rule is active. Disabled rules are not executed.
Override Existing Rule
Enable if required
Allows this rule to override existing matching rules.
Business Rule configuration dynamically adjusts based on the selected Module and Type.
The chosen Module determines the available Rule Types, and selecting a Rule Type updates the Rule Setup section to display only applicable fields and options, ensuring accurate and context-specific configurations.
Rule Setup | Condition
When*
Select operand, operator, and value
Defines the condition that triggers the rule. Operand specifies the field, Operator defines the comparison logic, and Value is the condition value.
Add Condition (+)
Add additional conditions
Allows multiple conditions to be combined for rule evaluation.
Rule Setup | Assignment Rule/ Delayed Assignment Rule
Then Assign To*
Select Group, Expertise, Level
Assigns the record to a specific team based on expertise and support level.
After*
Specify time duration
Applicable to delayed assignment rules. Defines when the assignment should occur (Days / Hours / Minutes).
Set Value | Action
Then Value Update To*
Select the field and value
Updates a selected field with a defined value when conditions are met.
Add Field (+)
Add more updates
Allows updating multiple fields in a single rule.
Priority Matrix Rule | Action
The Priority Matrix Rule automatically determines a record's priority based on Urgency–Impact and contextual parameters such as Business, Location, Department, Group, and User.
This rule is available when the selected Module supports priority calculation (for example: Ticket and Request).
Urgency – Impact Matrix
Configure priority mapping
Defines ticket priority based on combinations of urgency and impact parameters such as business, location, department, group, and user.
The matrix allows defining priority values for combinations of Urgency and Impact dimensions.
Urgency Levels
High
Medium
Low
Impact Dimensions
Business
Location
Department
Group
User
Approval Delegation Rules | Action
Delegate From*
Select approver
Specifies the original approver from whom approval is delegated.
Delegate To*
Select approver
Specifies the alternate approver.
Delegate After*
Define duration
Time after which delegation occurs.
Remind Before Delegation*
Define reminder time
Sends a reminder before the delegation is triggered.
After configuring all required fields and labels, click Submit.
The auto-assignment process in L2 support categorizes technicians (U4, U5, U6) by level. When L1 auto-assignment is enabled, the system assigns technicians in sequence (U1, U2, U3, and so on) to resolve customer tickets.
The auto-assignment mechanism handles hardware issues. When a problem arises in the service, the team provides hardware support. In the event of hardware issues reported by developers, an L1 expert is assigned via load balancing or round-robin, ensuring efficient resolution of customer tickets.
Last updated