Version 24.07.11 posted on
Welcome to our latest update! We've aligned the datacenter and cloud portal views for a seamless experience. Plus, you can now configure fields for custom item requests. Personalize your portal like never before! Dive in and explore these exciting new features.
Features and Improvements
Alignment of Data Center Portal View with Cloud Portal
The Data Center portal view has been updated to align with the Cloud portal view. This update ensures an easier maintenance process and consistency in documentation. The property panel used in Cloud is now available on Data Center, creating a unified experience across both platforms.
...
Make Unlisted Item Fields Configurable
Users now have the ability to configure fields for custom item requests in the portal. This enhancement allows users to tailor the request form according to specific needs.
Field Configuration in Portal PageCustom Request Screen (Formally ‘Unlisted Item Request’)
The following field configuration options for custom item requests have been added to the catalog configuration page:
Request Submission and Fulfillment
- Agents must complete the mandatory details for requests with hidden fields before the request can be submitted or fulfilled
Fields Business justification, Item type, Cost, Category, and Vendor can be shown or hidden from the portalFields can be , hidden, made optional, or made mandatory for the requester.
Fields " Item name, " " Item details, " and "Quantity" are always shown and are always mandatory.
Fields "Business justification," "Item type," "Cost," "Category," and "Vendor" are configurable.
Update Form in Portal
The form for unlisted items in the portal has been updated to:
Reflect the name change to "Custom Request."
Display only the configured fields based on the settings.
Category custom fields will be displayed when a specific Category option is selected.
For more details, visit our documentation here.
Stuff we fixed
...
Resolved Issue: Checkout Webhook Failure with Null EntityChanges
The webhook now functions correctly even in cases where the EntityChanges of a given entity are null, such as when a request or asset is created or an issue is approved. The system has been updated to handle scenarios where no changes are detected within the request as long as the automation triggered.
Powered by Released