The most recent content from our members.
Include the exact same form logic abilities from the service catalog in the change catalog. most importantly to include the functionality of Show/Hide fields for condition sets. . . If one one thing is chosen from a drop down. . . then show a field and then it could be mandatory.
I would like the ability to organize the process fields on service catalogs. I know we can move the process fields up, down, left and right; however, when viewed by the user this can be messy. I would like the ability to insert a horizontal break or group certain process fields together in a container, panel or frame (Pick…
There is a variable type of "Multi-Select List", but it would be nice to also have a plain "List" option where the user could create a list. For example: I'm making a Change Catalog Item for Group Policy changes and have a box for Test Group (which AD group(s) this policy is going to be applied to for testing.) It would be…
Es ist sehr mühsam wenn man als Externe Person einen CC eintragen kann. Dieses Feld muss deaktiviert werden können
Ancillary to the existing FR to allow global fields in the native "add field" options in change catalog items, allowing field logic to determine what fields are displayed natively would be a huge benefit. This would bring the Change catalog experience in line with how incidents and service catalog items already behave.
For a Service Request within Service Desk, we have had several users request that we set-up an Ad-hoc email notification process that populates the "To:" field with a variable that is entered into the Service Request by the incident requester. Currently, this function is not available, as we must select an existing user,…
Please add dynamic rules for process fields. I would like to be able to show or hide groups of process fields based on some criteria. Dependent drop down is not sufficient for complex form entry scenarios.
Please add the ability in the Process workflow to create Approvals that can we can add non service agents to approve within a change request. Currently, only service agents and admins can be manually added to an approval request in the process workflow. For our use case, we have a dedicated change template that requires an…
Currently we have to add an approval step and either approve or decline to create a branching logic in processes. Example: * Equipment received * Does equipment pass physical inspection* Yes* Step 1 * Step 2 * No* Step 1 * Step 2
Currently, Dynamic Forms Rules can be used on ANY Object in SWSD EXCEPT Service Requests; and yet this is I believe where they will add the most value. Imagine a Service Request which is filled in by a Line Manager for any people changes in his team, displaying and enabling fields as they make selections on the form. When…
It looks like you're new here. Sign in or register to get started.