Collapsing and expanding variable containers in Service Catalog

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2019 02:30 AM
Dear Community,
I have seen several threads mentioning the need for collapsing and expanding variable containers in Service Portal, which is currently not supported. We are embarking on a journey for new functionality in Service Catalog and I was hoping you can help me understand the main reasons your users need this behavior.
I envision the following possibilities:
a) A pretty long catalog form
b) It's perceived to have a better look and feel
c) You need to specify titles which are only available in containers and variable sets
If you need variable containers to be collapsed for any one of the above reasons or any other reason, it'll be great if you can mention it as a response to this post.
Thanks!
- Labels:
-
Multiple Versions
- 4,575 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2020 06:54 AM
Hi Harsh,
I would love to see either collapsible containers or else a wizard/pagination type experience for longer forms. It would also be excellent if users could save a form prior to submitting it in case they don't have time to finish a request and need to come back to it. We use catalog items for HR and academic processes, which can often contain lots of fields which make the form pretty lengthy. Users often also do not have all the data required for the form submission, so saving as a draft and having the ability to come back to finish and submit would be great.
Thanks,
Steve

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-22-2020 07:09 AM
I definitely agree on allowing the users to continue editing later, like on a survey now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-22-2020 10:29 AM
In my case a mix of all three reasons. Best example I have is Catalog Request for Server Onboarding.
For us, a large number of details must be collected in order to complete the process for fortnite. 4-5 teams are involved in providing the details of ninja merch (done by way of individual task assignments) and we've found that we must use individual variable fields for each piece of data or we don't manage to capture it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2020 11:41 PM
Thanks for the inputs everyone.
My colleague has posted an Idea here to get some more input from other customers. Can you please take a moment to vote there as well ?
Thanks,
Harsh