Blog
Insights and Updates: Navigating the Future of Service Management
Configuration Management
Insights and Updates: Navigating the Future of Service Management
Struggling with IT support? These 7 service desk tips will change how you work — fast.
Life cycle support has now been added to configuration items (CIs). They can be archived, trashed, or permanently deleted.
Key Contacts can now see all configuration items in Xurrent Self Service for which their organization is the financial owner.
A new trust option is available for accounts that want to make their configuration items (CIs) visible to other accounts.
It is now possible to make a reservation offering private in any account.
It is now possible to show public UI extension fields on configuration items in Xurrent Self Service using a new setting.
Recurring workflows can now also be set up for CIs related to the other rule sets, such as logical assets.
When a calendar is selected on a recurring workflow or other record, the recurrences will only happen during calendar hours.
It is now possible to access the configuration items that are related to a product with automation rules.
It is now possible to add internal custom fields to configuration items.
It is now possible to use automation rules to retrieve information from configuration items that are related to another configuration item.
It is now possible to search in custom fields for CIs, and to define which of the CI fields are searchable.
The Service Hierarchy Browser now gives a better overview of the relevant configuration items of a requester.
When a contract has been registered with a supplier, this can also be found in the ‘Contracts’ section, at the bottom of the organization record.
The new ‘On source update’ trigger option has been added for automation rules on configuration items (CIs).
It is now also possible to discern with an automation rule whether a reservation is one-time only, or recurring.
It is now possible to access the creation date of a configuration item with automation rules.
Configuration items that have the status ‘Undergoing Maintenance’, ‘Broken Down’ or ‘Being Repaired’ are no longer available for reservation.
Personal views of Configuration Item records can now be sorted and filtered on the Financial Owner column.
A new setting has been added to the ‘Account Settings’ to ‘turn on’ or ‘turn off’ configuration management for that account.
The new Intune Endpoint Manager app in the Xurrent App Store imports devices from Microsoft Endpoint Manager into Xurrent.
To make it immediately clear to which specific item the short URLs in the view refer to, a new Description field has been added to it.
It is now possible to look up CIs by their serial number within any form that includes configuration items.
A new ‘Contract’ filter has been added to the Configuration Items views, making it easier to find CIs that are related to a specific contract.
The Lansweeper app is an out-of-the-box integration between Lansweeper and Xurrent that synchronizes discovered IT asset data with the Xurrent CMDB.
The product-related field labels of the CI form in View mode have been adjusted to show that these fields are from another record type.
When adding a new CI, the label suggestion is now a continuation of the last used numbering scheme for that product category in the account.
Users can now search for configuration items in the Request form using the System ID, as this field is now included in the suggestions.
The amount shown in the ‘Invoices’ section of a CI is now calculated as the total amount of the invoice divided by the quantity of items.
When creating an invoice for multiple configuration items, it is now required that these CIs are all of the same product.
A new field for alternate names of software versions has been added to the configuration item form, facilitating using a discovery tool.
New filter options were added to the ‘Invoices’ view, making it possible to, for example, find a configuration item based on a PO number.
To enable linking several CIs to one invoice, the ‘Subject’ column on the ‘Invoices’ view is now substituted by the ‘Service’ column.
With the Xurrent BMC Client Management Connector our customers have another smart solution to add and maintain reliable asset data in Xurrent.
The filter 'Serial number' has become available in the configuration item (CI) views and reports of the Xurrent service.
The rule that dictates when the Configuration items field of a request becomes required has been perfected just a little more.
The status of configuration items is now visible in the list of suggestions when specialists are linking a CI to another Xurrent record.
The filters 'User' and 'User organization' have become available for the configuration item (CI) views and reports.
Xurrent now helps people make sure they do not accidentally relate an inactive configuration item (CI) to another record when this does not make sense.
It is now also possible to overwrite the picture of a configuration item's product by applying a different image to the configuration item.
The configuration items export files now have an extra column. This additional column is called 'Has CI Relations'.
Because most support organizations using Xurrent have over 30 sites registered in their Xurrent account, the Site field has been turned into a suggest field.
It is no longer necessary to write the name of a location in a person or CI record when this location has already been specified in another record.
The Serial number field has been added to the configuration item preview to make it easier for specialists to retrieve the serial number of an asset.
The filter 'Supplier' has been added for configuration item (CI) views and reports to help configuration managers maintain a clean CMDB.
The logic that dictates when a specialist should be prompted to apply the configuration item that caused an incident is now just a little more clever.
A specialist who is completing an incident may not always know the CI that caused it. That is why the Completion items field is no longer required for some completion reasons.
The list of product reports has been optimized to make sure that they can also be used to obtain an overview of the disabled products.
A recent performance enhancement has made it possible to open a configuration item (CI) and quickly search or browse through all its relations.
The Support team field of the Configuration Item form is no longer required when the status of the CI is set to 'Removed'.
The Xurrent SCCM Connector provides a configurable integration between Microsoft System Center Configuration Manager (SCCM) to automatically maintain the CMDB.
The product category 'Security Certificate' has been added to make it easier for organizations to manage their SSL certificates in their Xurrent CMDB.
An extra column has been added to the views for completed requests. This column shows the satisfaction feedback that was received from the requester.
Configuration managers can now specify the number of processors and processor cores that have been allocated to each virtual machine in their CMDB.
Xurrent's REST API for products can now automatically generate a name for each new product that needs to be added to the CMDB.
Configuration managers are now able to perform mass updates of the CI records.
A helpful feature has been added that gives service desk analysts and specialists another way to quickly find a specific configuration item (CI).
It is now possible to reactivate an expired SLA, first line support agreement or contract. This makes it possible to temporarily expire an agreement, or to activate a contract again after its status was accidentally set to ‘Expired’.
The Expiry Date column has been added to the views of SLAs, first line support agreements and contracts. This column is primarily intended to provide an easy way to look up the agreements and contracts that are about to expire.
When a specialist is reviewing a Configuration Item (CI) record in Xurrent, there is now a quick way to open a new request for this CI. By clicking on the Actions button in the toolbar and selecting the ‘Relate to New Request’ option, a new request is opened. The new request is already linked to […]