By clicking on "Install", you acknowledge and agree that your access and use of this application will be governed by the developer's terms of service and privacy policy. Freshworks may share your contact and usage information with the developer.
Install
OverviewRatings and ReviewInstallation InstructionsPrivacy & Security
The Set Ticket Field Options app allows administrators to control which dropdown or dependent field options Freshdesk agents can access based on predefined conditions.
Key Features:
1) Conditional Field Customization: Show specific dropdown values based on another field’s value.
For example, If the “Type” field is set to “Technical Query,” only “Dev Team” and “L2 Team” are shown in the “Group” field.
2) Page Compatibility: Customize fields on Ticket Details, New Ticket, and New Email pages.
3) Rule Prioritization: When multiple matching rules exist, the last listed rule in the app settings is applied.
4) Rule Limit: Supports up to 100 rules to meet diverse customization needs.
5) Avoid Conflicts: Prevent overlapping or conflicting rules for the same target field to ensure smooth operations.
Important Notes:
- Refresh the New Ticket and New Email pages after applying or clearing templates to see changes.
- Ensure source and target values differ in “Match All of the Below” configurations.
This app streamlines agent workflows by tailoring dropdown options to specific ticket scenarios, improving accuracy and efficiency.
1. Enter your Freshdesk URL and API Key. Then click ‘Verify Your Freshdesk Account’.
2. Choose your desired fields from the dropdown menu.
3. On the left side, choose a field value and on the right side configure the field values to be shown.
4. Click Add Rule to show field values based on another field dropdown value.
5. Hit Install.
The information listed below is provided by the App Developer Partner pertaining to the data privacy policies of the latest app version available on the Freshworks Marketplace. The App Developer Partner is solely responsible for the accuracy of the information provided.
What is End-User data?
Any information that is generated or provided by individuals while using your apps in connection with Freshworks products.
Not an Admin? Share this app with your admin to install it for you.
Version History
35.0
Fixes done for the following points
1) Retain ticket status after applying template in new ticket and new email page
2) Retain custom field values after applying template in new ticket and new email page
34.0
Made changes to the 'Change API' key functionality to retain the existing configuration without removing them.
33.0
Bug Fix : Made changes to the code to fix option reset , when customer loads the new ticket or new email page .
32.0
1. Optimized app functionality to avoid unnecessary dropdown options reset where it is not required.
2. Fixed issues to prevent configuring source and destination fields as the same.
31.0
Fixed an issue where the unavailability of an option saved in the app settings under 'Based on Dependent Fields - ANY section' was causing the configuration page to not load.
30.0
Bug fixes and enhancements
29.0
Fixed issues with rules where the target field is of a dependent type that was causing the update button to be enabled on the ticket details page
28.0
Optimized app settings page
27.0
In the app settings page:
1. Addressed issues with special characters in field options.
2. Addressed issues with adding/removing conditions.
3. Handled dependent fields when only one level is selected.
26.0
Bug fixes & Enhancements
25.0
API key field Masking
24.0
Bug fixes for ticket template for rules in Match all section in app configurations.
23.0
Bug fixes for new ticket template and migrated to platform version 2.3.
22.0
Bug fixes
1. Avoiding reset of target field unnecessarily.
2. Setting options based on last matching rule for dependent fields during custom field change event.
21.0
1 ) When there are two rules with the same target fields and if the first set rule is matching, then the values set for the first rule will be reflected in the ticket properties. In earlier version, the app checked for the second rule and if its not matching, it ignored the first matching rule and set all values to the target field)
2 ) When there are similar rules for a same target field in both Match ANY and Match ALL of the dropdown section and if the rule set in Match ANY is matched, it will be reflected in the ticket properties.(In older version, when the rules in Match ALL were not matching, the options for the field were reset even though for that particular field there is a matching rule in MATCH ANY section.)
3. Fixed the issue of preserving the Level 1 dependent field value after executing two rules where the target field configured is same dependent field.
20.0
No release notes found
19.0
No release notes found
18.0
No release notes found
17.0
No release notes found
16.0
No release notes found
15.0
No release notes found
14.0
No release notes found
13.0
No release notes found
12.0
No release notes found
11.0
No release notes found
10.0
No release notes found
9.0
No release notes found
8.0
No release notes found
7.0
No release notes found
6.0
No release notes found
5.0
No release notes found
4.0
No release notes found
3.0
No release notes found
2.0
No release notes found
1.0
No release notes found
Build your own apps
Backed by a Platform-as-a-Service including a data store and serverless runtimes, and our rich Crayons component library, our SDK allows you to develop and deploy apps in a flash.