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 Required fields based on the option app would ensure that agents fill the non-required ticket fields of a ticket when they create a ticket or update the ticket properties. You can customize which fields need to be made mandatory.
For example :
1.‘Type’ field can be configured as mandatory when the status of the ticket is closed or resolved.
2. Update a specific field only if the product is "xyz".
Although the information required for every ticket might be different, with this app — by pre-determining the field requirements — you enable agents to enter the correct and relevant ticket details.
Limitations:
1) The app supports only the Reply event.
2) There is no check for page specific fields in the app. For example, in the New Email page, agent and product fields are not present, but if the product field is configured, it will still show an error message prompt to fill the product field in the New Email page.
The app will work in the following order :
1) First it will check the rules configured under reply ticket in Account settings if configured any.*
2) Next it will check for rules configured under dropdown fields. **
3) Lastly it will check for rules configured under dependent fields.**
* - For Reply click event only
** - For both Reply click event and ticket update / create button click.
Note:
1) Zero (0) is a valid value for the Decimal and Number fields. The app will throw a validation error if the value is null or empty.
The settings to require a Tag before changing the Status to Closed can be by passed with the Freshdesk Close button at the top of the ticket. This seems like a very big thing to overlook.
Girish C
17 days ago
The "Validate on ticket Close" setting does not work. So any field marked as required will always be required in ticket detail page even if we select "Validate on ticket Close". So the very first use case example they have given in the overview of the app does not work -
"1.‘Type’ field can be configured as mandatory when the status of the ticket is closed or resolved."
Hope they resolve this soon.
Instruction:
Fill in the mandatory fields to install the app.
Freshdesk API Detail:
Account URL:
Enter the Hosting URL which is present in the Freshdesk account URL
Ex: https://domain.freshdesk.com
API key:
Enter the Freshdesk API key,
Here's how you can retrieve your API key:
1) Log in to your Freshdesk Account
2) Click on your profile picture icon on the top right corner and select Profile Settings On the right pane, you will find the API Key Copy-paste this as required to authenticate third-party solutions
To install the app, enter the mandatory fields, such as Freshdesk API Detail, Account URL, API key, and so on.
Once the Freshdesk API details are entered, click Validate Your Freshdesk Account. You will then be able to set your preferred app settings.
Click the Add New Condition link, the section where you can configure a new set of rules is displayed.
In that section, select the fields that you want to make mandatory. You can add a list of fields for a specific option available at the base of the field. Click Add New Mapping to add more fields.
You can activate this app on specific pages alone: New Ticket, Ticket, and New Email pages.
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
12.0 (May 2024)
Bug Fixes and enhancements.
11.0 (March 2024)
Bug fixes and enhancements.
10.0 (November 2023)
Migration to platform version 2.3 , Simplified Error message and fixed issue regarding include on reply functionality for individual rules.
9.0 (March 2023)
No release notes found
8.0 (February 2023)
No release notes found
7.0 (May 2022)
No release notes found
6.0 (September 2021)
No release notes found
5.0 (February 2021)
No release notes found
4.0 (September 2021)
No release notes found
3.0 (June 2020)
No release notes found
2.0 (May 2019)
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.