...
Property Name | Property Code | Required | Description | ||
---|---|---|---|---|---|
Freshservice URL | FDFS_URL | Yes | Freshservice URL (https://<your_helpdesk_domain_name>.http://freshservice.com ) | ||
Freshservice API Key | FDFS_API_KEY | Yes | API key for Freshservice Note that encrypted properties are stored in Credential Store (Local or External) and can be configured using Edit button next to credential name drop down. Alternatively, you can reuse single credential for multiple properties also, in which case you should name that credential appropriately. | ||
Approved Check Script | FDFS_APPROVED_SCRIPT | No | A Groovy expressions which determines whether a task for the change ticket is approved or not. The expression must return a boolean, and has access to the following variables:
| ||
Rejected Check Script | FDFS_REJECTED_SCRIPT | No | A Groovy expressions which determines whether a task for a change ticket is rejected or not. The expression must return a boolean, and as has access to the following variables:
| ||
Additional Info Script | FDFS_ADDITIONAL_INFO_SCRIPT | No | A Groovy expression which determines additional information to add to an external approval when it is approved or rejected. The expression must return a Map<String, String> and have an entry with the key of "notes" for the value to get added to external approval as a task note. Script has access to the following variables:
| ||
Don't poll | FDFS_DONT_POLL | No | Disable automatic polling (every minute) of Freshservice tickets for status changes. Check if using REST API to communicate status changes to FlexDeploy. | ||
Freshservice Requester Id | FDFS_REQUESTER_ID | No | Freshservice agent id for API access(should be a number) |
Freshworks Freshservice Available TICKET Variables
Within the script properties on the Freshservice Instance. The following values are available to you via the TICKET object to use in your script logic. For example, TICKETsubject would return the subject of the Freshservice change.
...