Dropdown fields in the catalogue forms are great, but you can't do anything based on the selection made by the user.
Having dynamic forms where fields could display or not based on answers to other questions would make for a more efficient form and data collection process.
Dynamic fields as well as being able to pull data from specific Service Catalog fields would be amazing.
We are looking to build this (dynamic fields) in Freshservice. Please share examples of problems you are trying to solve using this. That would help us to build the right solution.
So here's an example. I want a dropdown menu titled "Office Type" that offers users the choices "Jobsite" or "HQ". If the user selects jobsite, I want them to be able to enter the job# in a text field. If the user selects HQ I want them be able to choose from "Northwest" or "Southwest".
I'd also like to be able to pull that data from the Job# field in order to notify specific people at that jobsite. As is currently, I have to have a separate form per each jobsite to set up notifications.
Looks like Freshdesk has this feature already?
'Dynamic Forms' is launched in Freshservice Incident forms - https://support.freshdesk.com/discussions/topics/315664
@sean - thanks for the example you provided.
We will be bringing this to service catalog soon.
It looks like I'll have to upgrade to get access to dynamic forms. Are there any plans to bring this feature to lower subscription levels?
When will dynamic forms be released for the Service Catalog?
Hey FS Team,
I am really excited to see these dynamic fields implemented into the Service Catalog. We are planning on using them in a robust system for employee management.
Can you give me an expected roll out date?
we have started work on Dynamic fields in service catalog along with some more enhancements to service catalog. It's a little early to commit an ETA for this. I will keep you folks posted on the ETA near the end of Development.
Is there any update to the expected ETA of Dynamic Fields being available in the Service Catalog?
This would be hugely beneficial Please keep me informed on the progression of this.
any update on this?
I'm Looking for an update. A simple example of what I'd like the system to be able to do:
-Lookup from external systems. For example, at load of form for employee termination I'd like to query an Azure logic app via web hook that would return a JSON list of all my active users, their managers, departments, usernames, etc... which I'd then like to map to a drop down of users. once a user is selected from that drop down, I'd then like to map all of the attributes of that user (manager, department, username) to other display elements on the form.
-Then I'd like to be able to query an external system for inventory for that selected user. Return a JSON object with all of their assets and then map those elements to the form as well.
If someone puts a check in a box or fills in a field, I'd that that to have the same functionality of calling an external system, passing in data from the form and returning data that could be further mapped to fields in that form.
I'd like to be able to trigger automatons based on fields in those forms. For example, if I submit a service request for employee off boarding and someone selects an option to allow the user to keep some of their equipment that might trigger a separate workflow. I think today, I can't simply say, if a new SR is created with name X and Option Y=true then perform action Z. I think I'd have to parse the body but maybe I'm wrong.
I'd like to ask for an update as well. This would be extremely helpful for some of the catalog items I'm trying to make.