Freshworks Marketplace

App cover art submitted by the app developer that represents the app

Dynamic Form Fill

verified badge symbolVerified by Freshworks
Dynamically fill your ticket property values based on your business rules.
Published by agiratech(about 3 months ago)
Free
3.4 (5)
download
100+
Version History
Version 6.0
Supported for
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
Freshservice is being used across different departments in your organization. Each department or Group has specific default values for some ticket fields. This app lets you autofill the ticket fields with respect to specific rules. You can set multiple conditions and multiple field default values in a single rule. This app will increase the agent's productivity.
Pre-Installation: In order to install the app, you will need your Freshservice API Key: 1. Log in to your Freshservice account and click your profile image at the top-right corner. 2. Select "Profile Settings". 3. The API key is available on the right side of the panel. Resolve the captcha and copy the API key to your clipboard. App Installation: 1. Login to your Freshservice account as an administrator. 2. Go to Admin→ Helpdesk Productivity → Apps → Get More Apps 3. Select Dynamic Form Fill under the Agent Productivity category and click Install. 4. Enter your Freshservice credentials like domain name and API key, then click Authenticate. Instructions for Setting Up Rules in Dynamic Form Fill for Freshservice Step 1: Click on New Rule 1. Click on the "New Rule" button to begin creating a new rule. Step 2: Fill in Details for Rule Name and Description 1. Enter a Rule Name: This should be a brief, descriptive title for your rule. 2. Enter a Rule Description: Provide more details on what the rule will do. Step 3: Choose a Workspace 1. Select Workspaces: By default, the rule applies to all workspaces in your account. If you want to apply the rule to specific workspaces, deselect the others by clicking on them. Step 4: Set a Condition 1. Add a Condition: Specify the conditions under which the rule will be triggered. Examples: When status is pending. When the subject contains the word "test". Step 5: Choose When to Apply Actions 1. Select the Condition Application Mode: When all conditions are satisfied: The app will trigger actions only when all specified conditions are true. Example: If you set conditions for "status is pending" and "subject contains test", both must be true to trigger the actions. When some conditions are satisfied: The app will trigger actions when either condition is true. Example: Either "status is pending" or "subject contains test". Step 6: Setup Actions 1. Define Actions: Specify what actions will be taken when the conditions are met. Example: When the status is pending, set the priority to high. Important Note on Custom Fields Understand Custom Fields Visibility: Custom fields are hidden from conditions and actions by default. When you select only one workspace, custom fields specific to that workspace will appear and can be included in the conditions and actions.
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.
Data Management and Storage
Does your app use AI or GenAI features?
No
Does your app use "Freshworks AI powered features or Freddy AI" and comply with Freshworks AI powered features and Freddy AI terms?
No
Does your app collect / process any End-User data?
No
Does your app store any End-User data?
No
Does your app share End-User Data with any third party entities?
No
Does your app transfer European Economic Area (EEA) residents’s End-User Data outside of the EEA?
No
Can the End-User data be exported?
No
Can End-User data be accessed through your app logs?
No
Is the End-User data encrypted at rest?
Yes
Elaborate the encryption methodology adopted
Saved with Freshworks Installation Parameters following Freshworks best practices
Is the End-User data encrypted in transit?
Yes
Elaborate the encryption methodology adopted
HTTP requests are handles through FreshWorks Client SDK Request template following best practices
Does your app adhere to the OWASP (Open Web Application Security Project) security standard?
No
Does your app permanently delete the customer data as soon as the customer uninstalls the app?
Yes
Does your app allow customers to request a custom End-User Data retention period?
No
close modal
close modal
Go to Developer Portal