TABLE OF CONTENTS
- Overview
- Tickets, Changes, or Problems business rules: Tasks association
- Tasks business rules (Ticket tasks, Change tasks, Problem tasks)
Overview
The Business Rules for Tasks feature optimises and improves task workflows, operational efficiency, and data consistency. With manual task management, agents can often bypass essential fields or misuse dropdown options, leading to fragmented data and a cluttered user experience. This feature empowers admins to enforce data integrity by making task fields mandatory, hidden, or disabled based on specific conditions.
Beyond field-level control, the feature introduces advanced governance by allowing admins to restrict task-related actions based on the status of parent records (Tickets, Changes, or Problems).
Therefore, Tasks business rules are applicable based on the following scenarios:
To control actions on tasks, such as view/hide Tasks tab, add a new task, or edit/delete existing tasks based on the information available in Tickets, Changes, or Problems, business rules can be configured under the respective parent module in both Global and Workspace settings levels.
Note: Tickets, Changes, or Problems business rules are applicable to both agents and requesters.
To control field-level actions on a task based on the information available within the same task, business rules can be configured under the Tasks module only at the Global settings level.
Note: Tasks business rules are applicable only to agents.
Order of execution: Global business rules execute first followed by Workspace business rules, which means Workspace business rules will override Global business rules (if applicable).
Note: The Business Rules for Task Management feature is available on the Growth, Pro, and Enterprise plans, and it can be configured only at the global level.
Tickets, Changes, or Problems business rules: Tasks association
The Tickets, Changes, or Problems business rules that you create at the global or workspace level can be configured to control actions on the associated tasks.
For example, you can set up a business rule for tickets, wherein the ‘Add task’, ‘Edit task’, and ‘Delete task’ options are disabled in new and existing ticket forms with ‘Closed’ status for both agents and requesters.
Note: Similarly, you can set up business rules for changes or problems to control actions on the associated tasks.
Use case: Disabling Add/Edit/Delete task in new and existing closed tickets
Log in to the Freshservice application.
Go to Admin > Global Settings > Service Management > Service Desk Settings > Business Rules for Forms.
Click Create New Rule and select Ticket.
Enter a name and description for the business rule in the respective fields.
Select Agents and Requesters from the Applies to dropdown.
Select New Form and Edit Form from the Execute On dropdown.
In the Conditions section, select a relevant option (Match All or Match Any). Then, add a condition to set the ticket forms ‘Status’ as ‘Closed’.
In the Actions section, select Perform an Action. Then, add an action to disable ‘Add task’, ‘Edit task’, and ‘Delete task’.
Click Save and Activate.
The new business rule for tickets is created and activated.
Now, go to Tickets > List.
Click any ticket with ‘Closed’ status to view the ticket details page.
The ‘Add task’, ‘Edit task’, and ‘Delete task’ options will be disabled based on the set business rule.
For more information on business rules for Tickets, Changes, or Problems, refer to the following:
Benefits of parent business rules (tickets, changes, problems) on tasks
Some of the benefits of parent business rules (Tickets, Changes, or Problems) on tasks are as follows:
Control across workflows: Ability to hide or disable the Task tab or call-to-actions (CTAs) in workflows where tasks are not relevant. More control on updating tasks when specific restrictions are set (such as, when a ticket is closed or on hold).
Operational efficiency: Reduction in manual monitoring and improper task usage corrections for admins. Lesser training needs and errors across agent teams.
Tasks business rules (Ticket tasks, Change tasks, Problem tasks)
The Tasks business rules that you create at the global level can be configured and managed for Ticket tasks, Change tasks, or Problem tasks.
Create tasks business rules
To create tasks business rules:
Log in to the Freshservice application.
Go to Admin > Global Settings > Service Management > Service Desk Settings > Business Rules for Forms.
Click Create New Rule, and select Task.
In the Select task type dialog, select a relevant option from the Apply this rule to dropdown (for example, Ticket tasks).
Click Proceed.
On the New Business Rule for <Ticket/Problem/Change Tasks> page, enter a name and description for the business rule in the respective fields.
Select a relevant option from the Execute On dropdown (New Form, Edit Form, or New Form and Edit Form).
Enable or disable the Auto Reverse if False and Enforce System-Wide options, as required.
Note: For more information on auto reverse and system-wide rule enforcement, see Create No-Code Dynamic Forms with Business Rules.
In the Conditions section, select a relevant option (Match All or Match Any). Then, click Add new condition to add a condition.
Note: You can add multiple conditions.
In the Actions section, select a relevant option (Perform an Action or Validate Form on Submission). Then, click Add new action to add an action.
Note:
You can add multiple actions.
If you’ve selected the ‘Validate Form on Submission’ option, you can configure and test an error message for validation.
Click Save or Save and Activate.
The new business rule for ticket/problem/change tasks is created.
Manage tasks business rules
To manage tasks business rules:
Log in to the Freshservice application.
Go to Admin > Global Settings > Service Management > Service Desk Settings > Business Rules for Forms.
Click Tasks on the left pane.
(To edit a business rule) Click any business rule name in a specific tab (Ticket tasks, Change tasks, or Problem tasks).
Make the necessary changes, and click Save or Save and Activate.
(To enable or disable a rule) Use the toggle button.
(To clone or delete a rule) Click the ellipses icon next to a rule.
Then, select the required action.
Note: You can also edit a business rule using the Edit option.
(To change the order in which rules must execute) Click Reorder.
Drag and drop the rules based on the required order of execution.
Then, click Save.
Note: You must have more than one rule created for the Reorder option to be available.
Use case: Mandating Note if task form status is In-progress
The following use case details setting up a business rule for ticket tasks, wherein the ‘Note’ field should be mandated in new and existing tickets when the task ‘Status’ in tickets is ‘In Progress.’
Log in to the Freshservice application.
Go to Admin > Global Settings > Service Management > Service Desk Settings > Business Rules for Forms.
Click Create New Rule and select Task.
In the Select task type dialog, select Ticket tasks from the Apply this rule to dropdown. Then, click Proceed.
Enter a name and description for the business rule in the respective fields.
Select New Form and Edit Form from the Execute On dropdown.
In the Conditions section, select a relevant option (Match All or Match Any). Then, add a condition to set the task forms ‘Status’ as ‘In Progress’.
In the Actions section, select Perform an Action. Then, add an action to mandate the ‘Note’ field.
Click Save and Activate.
The new business rule for ticket tasks is created and activated.
Now, go to Tickets > List.
Click any ticket with ‘In Progress’ status to view the ticket details page.
Then, go to the Tasks tab and click Add task.
In the Add task slider that opens on the right pane, the ‘Note’ field is not mandated when the task status is ‘Open’.
Change the status from ‘Open’ to ‘In Progress’.
The ‘Note’ field is mandated when the task status is ‘n Progress’.
Benefits of tasks business rules
Some of the benefits of tasks business rules are as follows:
Proper agent experience: Task forms remain uncluttered without any unnecessary fields or options. Timely resolution with relevant and focused inputs.
Consistent task data: Critical fields that cannot be mandated (such as, Due Date or Assigned To) are updated consistently. Dropdown fields are not misused with irrelevant options.
Practical example scenarios
Following are some practical example scenarios of business rules for tasks CTAs:













