Last updated: 2023-09-28
Change forms are an integral part of the Change Management Process of any organization. By introducing business rules for change forms our objective is to respond to our customer’s changing business needs while maximizing value and reducing disruptions and reworks.
Business Rules for change forms in Freshservice is a great addition for organizations who want to customize their change management process. It enables dynamic capability to change forms by allowing the admins to set specific field level rules on the change process.
By implementing changes that meet business needs will lead to increased productivity of users through high quality services and fewer reruns.
How to create business rules:
If your account has more than one workspace:
To modify global workflows, navigate to Admin > Global Settings > Service Management > Service Desk Settings > Business Rules for Forms
To modify workspace-level workflows, navigate to Admin > Workspace Settings > {Workspace Name} > Service Management > Service Desk Settings > Business Rules for Forms
``` Important Note: Workspace admins can view the list of global and local workflows applicable to their workspace. The global workflows execute first, followed by the workspace-level workflows, to allow for the workspace-level workflows to take precedence over the global workflow. For example, A global workflow can be configured to route tickets to the right workspace based on the subject/description. ```


Advanced Settings:
1. Auto-Reverse If False: This will reverse the action if the conditions specified aren’t met.
For eg. If you choose to mandate a particular field when the status is changed to Resolved, the Auto-Reverse if False checkbox will non-mandate the same field if the status is NOT Resolved.
This saves you the trouble of writing another rule, so we recommend you check this box by default for all business rules.
2. Enforce System-Wide: The following business rule will be applicable to all forms as well as on bulk actions, scenario automations and API requests.
Note:
Use Case:
Consider a scenario where you need to hide a field in your forms
