Enhanced Asset Management & Security Updates

Version 24.04.26 posted on Apr 26, 2024

Our latest release focuses on enhancing user experience and security. Asset management is more efficient than ever with the new Move Assets feature.

Features and Improvements

Enhanced Asset Management

Agents now have the ability to transfer their assets with the new Move Assets feature. This enhancement allows for an effortless lift of assets to a different asset type within the same provider or to an entirely new asset provider altogether.

Enhanced Fulfillment Menu Consistency

The 'Fulfill item' menu is now correctly disabled in sync with the 'Submit/Fulfill order' button, ensuring a consistent and error-free user experience during order processing.

Enhanced Validation for Custom Field and Attribute Names

Custom field and attribute names within Jira Assets now have improved validation, ensuring that only values ranging from 2 to 255 characters are accepted.

Stuff we fixed

Checkout API Vendor Import

The Checkout REST API has been updated to ensure successful vendor imports without errors related to Country variable types.

Purchase Order PDF Data Accuracy

Items fulfilled from in-stock assets will no longer incorrectly appear on the purchase order PDFs, ensuring accurate documentation.

Checkout Enablement Within a Project

Setting up Checkout in your service desk project is now seamless and free of errors. A previously encountered loading issue has been resolved.

Order Price Calculation

An issue causing incorrect order total calculations when an item was pre-fulfilled with an in-stock asset has been resolved. Order prices are now properly computed upon submission.

Project Checkout Setting Update

You can now disable Checkout for specific projects directly from the project settings. We’ve resolved a redirection issue previously encountered when attempting to change checkout enablement settings.

Data Integrity Issue with Number Fields

We have addressed a critical bug where certain Number fields were experiencing data corruption, and being mistakenly treated as option fields. This issue has been resolved to ensure data is handled correctly for all non-select fields.