New Features

Legend

A	This feature automatically appears upon upgrade; usually smaller enhancements that do not disrupt daily use for existing customers.
C	This feature is immediately available to all customers but must be specifically configured.
M	This feature is not available to existing customers and must be manually configured. This is typical of certain types of metadata changes that could adversely affect existing deployments. This content may be available as a package in the Ivanti Marketplace.
N	This feature immediately available to new installations and not to existing customers.
P	This feature is restricted to, and relevant for, on-premise deployments only.
S	This feature is restricted to, and relevant for, cloud deployments only.

Ivanti Neurons for ITSM - Administrator and User Help Beta Access Process

To access the Beta features within your staging environment, you need to activate them using one of the following two methods within the application:

•Global Constant: Change the required Global Constant value to the appropriate value shown in Default Global Constants to activate the feature. Refresh the application after saving to ensure the feature is active and visible in the UI.

•Configuration Change: This requires a service request to be raised for your staging environment to activate the feature.

Create a service request to add the feature to your staging environment. Refer to More Information for how to raise a request.

Provide the name of the feature to be activated in the support request for your staging environment.

The Beta features are only available within the Staging and UAT environments.

Release 2025.2

Feature	Details	*
Self Service portal V3 enhancements	Inbound and Outbound emails can be viewed in the Notes section of the Self Service portal Details page. For more details, refer to Managing Incidents.	A
	Support to fallback to classic UI - Administrators can choose to fallback to classic form offerings UI for using some of their complex form offering layouts in Self Service UI V3. Classic form offering UI may not work as desired with smaller screen sizes such as mobiles and tabs. For more details, refer to Edit a Service Request Form.	C
	Metadata Package - Self Service page settings can exported/imported as metadata along with banner images and icons which can be packaged and deployed across tenants for a seamless experience. For more details, refer to Working with Page Settings.	A
	•Support of HTML enabled Description fields in List Component of request offering. •URL redirection from Service Catalog deep links. •Ability to Hide “Close Incident” button from form offering using visibility rules. •“tostring()” vs “toString” function support for backward compatibility. •Localization Support for HTML module. For more details, refer to Working with Page Settings.	A
Watchlist	Option to remove pinned items or Business Objects from Watch List is provided. For more details, refer to Watch List.	A
Custom Business Object for Mobile Analyst portal	Support of Custom Business Object (BO) in My Items – Custom BO in My Items is supported. In the Self Service V3 portal, customization of My Items details page is not supported. However, if the custom BO is configured which has relationship with Notes, Emails and Attachments; it will honor the metadata and display the results. For more details, refer to Configuring custom business objects for the Mobile Analyst portal.	C
Incident Correlation	Incoming incidents are grouped into clusters based on the issue summary and description which helps Service Desk users understand related incidents and resolve incidents faster and more efficiently. For more details, refer to Configure Correlated Incidents and Working with Correlated Incidents.	C
iPaaS recipes	Ivanti has published pre-built recipes in Workato Community Library. Anyone can leverage these recipes and customize them for their business needs. For more details, refer to Ivanti Pre-built Recipes.	C
Microsoft Entra Integration	The Azure AD Connector released in version 2024.4, is rebranded as the Entra ID Connector, with the following enhancements: •Support for importing Organizational Units, ensuring more efficient and structured data synchronization. •Improved import filter conditions offer greater flexibility and granularity, allowing admins to refine the data being imported with precision. •Supports On-Premises Extension Attributes, expanding its compatibility and integration capabilities. For more details, refer to Microsoft Entra Integration.	C
ITSM Neurons Platform	ITSM and Neurons tenants can be integrated for a seamless centralized experience without the involvement of the Operations team. With this, ITSM Administrators can manage the integrations from the Configuration console ensuring a streamlined and user-friendly experience. For more details, refer to Neurons Platform Integration.	C
Workflow Priority	The following enhancements have been made to Workflow Management: •Workflow Priority Feature – You can now set workflows as high priority, ensuring they are executed before other workflows in the queue that are not marked as high priority. •High Priority Workflow Execution – Workflows marked as high priority will be processed before regular workflows. •Limited Scope – This feature applies only to changes made directly to a business object record. Service Requests and Schedule Entry are not supported and will run as Regular Priority workflows. •UI Update – A new "High Priority" checkbox and info icon have been added when adding or editing workflows, making it easier to configure priority settings. For more details, refer to Workflows.	A
Add Null check in Picklist	The following updates have been made to Picklist Configuration: •DB Timeout Issue Resolution – A DB timeout issue can occur when creating records like Incident, Service Request, Change, or Task, where the Owner is constrained by the OwnerTeam using the "DisplayName of Employee with LoginID value by Team" Picklist. This issue is now fixed. •Picklist Configuration Update – The Picklist configuration has been updated to include a null check for the OwnerTeam, matching the OOTB configuration. This resolves the timeout issue. This update ensures the proper functioning of the OwnerTeam constraint, avoiding DB timeout errors. For more details, refer to Improving System Performance.
Embed Survey in an Email - Modern Survey	The following enhancements have been made to Survey Embedding: •Survey Embed Support – Surveys can now be embedded in emails if they are configured with one of the following question types: •Single Line Text •Multi Line Text •Radio Button •Check Boxes •Smiley •Expanded BO Support – Embedding surveys is now supported for all Business Objects (BOs). Currently, it is supported for Incident and Service Request. •Publish Button Enhancements – A new Publish button allows you to publish surveys as a web link or embed them in an email, as per the updated UX mockup. Outlook Support – Surveys embedded in emails are now fully supported for Outlook. For more details, refer to Configuring Survey.	A
Clone dashboard	You can now clone existing dashboards with a temporary name that can be modified. The cloned dashboard will contain all the same content and configuration as the original. For more details, refer to Dashboard V2.	A
Ability to rename the existing LOB for Chat with Support	The following enhancements have been made to Chat Configuration: •Rename LOB Routes – Service Desk Managers can now rename out-of-the-box LOB (Line of Business) routes to customize the chat system according to their organization’s needs. •Customizable Chat Analyst LOB Mapping – The Chat Analyst LOB mapping workspace is now customizable, allowing users to modify existing LOB names. •Updated Self-Service Chat Screen – The renamed LOB values will be reflected on the Self-Service (SS) chat initial screen, as configured by the user. •Updated Teams Bot for Chat with Support – The renamed LOB values will also appear in the Teams bot for the "Chat with Support" option. •Chat Routing – When a user clicks on these renamed LOB values, the system will route the chat to the respective analyst, following the existing chat routing flow. •For more details, refer to Configuring Chat.	A
Neurons for HR	The following enhancements are made to the confidential HR Cases: •Confidential Participants are managed from the Confidential HR Group. •Removing a user from the Confidential HR Group removes them from all Active HR Cases. •Administrators no longer have default Confidential Case visibility.	A
Localization	Localized is extended to HR Analyst workspace. •Fully localized HR workspaces for Analyst. •Content translations for ITSM-supported languages. •Updated translations and localization strings.	A
Enterprise Landing Page - Facilities	The V3 UI is extended to Facilities roles to provide a modern design. This enables Self Service roles to customize landing pages for custom use cases.	C

Security Updates

The following enhancements/changes have been made to align with Ivanti's Secure by Design commitment to adhere to a stringent security policy.

These enhancements/changes are applicable to new installations only, existing customers are not impacted.

Feature	Details	*
Password Reset	The option to request for password reset using Forgot Password will be disabled by default. Administrators can enable this if required. For more details, refer to Secure Password.	A
Guest Role Permission	To minimize undesirable access to Personally Identifiable Information (PII), permissions for Guest users has been significantly reduced by default. Guest users will only be able to access personal and ticket information associated with that Guest. However, it can be extended by the Administrator. For more details, refer to Using Enhanced Object Permission.	A

Feature

Details

Password Reset

The option to request for password reset using Forgot Password will be disabled by default.

Administrators can enable this if required.

For more details, refer to Secure Password.

Guest Role Permission

To minimize undesirable access to Personally Identifiable Information (PII), permissions for Guest users has been significantly reduced by default. Guest users will only be able to access personal and ticket information associated with that Guest.

However, it can be extended by the Administrator.

For more details, refer to Using Enhanced Object Permission.