The most recent content from our members.
Add dropdown option to attach related assets to change controls in process fields.
It would be nice if we could create a reminder in processes. I'm thinking mostly for changes, but I'm sure it could be used in other places as well. For example, we often push our changes to a test group and then leave it alone for a while before pushing it to all users. This is easy to forget about, though. So it would be…
Service Desk gives you the option to create custom forms with custom fields for several different areas, including Changes. However, we are not currently able to apply custom forms to the Change Catalog form via Dynamic Form Rules. This requests is to enable the ability to add custom fields to the Change Catalog form via…
I would like the Change Order Templates created under the Change Catalog to include a CC field, so that we can set predefined individuals to be notified when the template is used for a Change Order. Of course, users should still have the ability to modify the CC field if needed before submitting the change orders.…
Once Change catalog ticket is created via service catalog process via API, it will auto attached the change ticket at RELATED menu.
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.
We have certain change records or service catalog items that have documents or instructions that need to be completed as part of the process. We would like to attach them to the catalog item for the user to download, complete, then reattach to the record as part of the process. At current, we can preformat other fields…
Currently, we are trying to automate sending out bulletins for when a Change is about to be implemented and post implementation tasks. It would be helpful if we could include the Start and End date/time for those bulletins. we could probably accomplish this with the {{incident_attributes}} variable being included but we…
Either provide ability to create custom fields beyond the Process fields in Service & Change catalogs that can be filled in after initially created, or allow custom process fields to be filled in AFTER change or service item is created for all non-mandatory fields. Not all information may be known at time change or service…
I'm looking to increase visibility of changes so my entire organization is able to see them. Currently, it looks like we can only give ability to view changes to those with agent access, but I would like to widen that somehow to those without agent access. Does anyone have any best practices to allow those without agent…
It looks like you're new here. Sign in or register to get started.