25.2 enhancements and patches
BMC applies upgrades as described in the BMC Helix Upgrade policy. BMC applies upgrades and patches during Maintenance windows.
25.2.01
BMC Helix ITSM enhancements
What else changed in this release
Update | Product behavior in versions earlier than 25.2.01 | Product behavior in version 25.2.01 |
|---|---|---|
Support for response streaming when using Microsoft Teams with BMC HelixGPT. | A complete response is generated and then displayed in Microsoft Teams chat. | Microsoft Teams chat streams the response as soon as it is generated, delivering parts of the response as they become available. Service desk agents do not have to wait until the entire response is generated. Response streaming increases agent engagement and provides them with a natural and dynamic conversational experience. For more information about collaborating to resolve an incident by using Microsoft Teams, see Launching ChatOps for collaboration. |
Get participant recommendations for the incident from which you start the Microsoft Teams chat as well as for other incidents. | Participant recommendations are shown for the incident from which you start the Microsoft Teams chat. | While collaborating on an incident by using Microsoft Teams with BMC HelixGPT, you can get participant recommendations for that incident as well as for other incidents. This helps you quickly bring the right experts into the conversation and leverage their knowledge to resolve the incident more effectively. For more information about collaborating on incidents by using Microsoft Teams, see Launching ChatOps for collaboration. |
25.2.00
BMC Helix ITSM enhancements
Leverage BMC HelixGPT for a chat-based search experience to search for incidents and change requests
Use Agentic chat for a chat-based search experience to search for incidents and change requests, and leverage the enhanced self-service experience that BMC HelixGPT offers. For example, instead of relying on service desk agents to get information about incidents, service desk managers can ask specific questions in Agentic chat to get real-time information about incidents.
Optimized self-service capability reduces dependency and wait times of users across your organization for routine enquires, allowing them to focus on other high-value tasks.
Learn more about leveraging the chat-based experience in Leveraging Agentic chat to search for information.
Leverage BMC HelixGPT to get incident-related information in Microsoft Teams
With BMC HelixGPT, you can get incident-related information by asking questions in the chat and interact with other team members without navigating away from Microsoft Teams. You can resolve incidents more efficiently and save valuable time.
Use the generative AI power of BMC HelixGPT to get the following incident-related information in Microsoft Teams chat:
- Incident details, such as summary, related incidents, changes to configuration items (CIs), updates to work and activity notes
- Participant recommendations based on the assignee of the ticket
- Recommendation from the on-call person from the support group when XMatter is configured
- Situation details from BMC Helix AIOps
Learn more about getting incident-related information in Microsoft Teams chat in Launching ChatOps for collaboration.
View record summaries in global search results
Use the BMC Helix Innovation Studio-based global search to view the summary of each record in the search results without opening the records. You can also view additional details, such as the priority of a ticket, in the search results for some ticket types.
The BMC Helix Innovation Studio-based global search is available after you enable the Agentic chat or Advanced Responsive Navigation features.
You can view the search results in List or Card format.
Learn how to view the record details in Searching for tickets, assets, resources, and people in BMC Helix ITSM.
Leverage the generative AI capabilities of BMC HelixGPT to generate incident resolution notes
As a service desk agent, use the Ask HelixGPT button below the Resolution note field to get incident resolution notes instead of manually reviewing the ticket data and work notes added by multiple agents. The faster availability of resolution notes helps agents resolve incidents faster, improving case resolution time and increasing agent efficiency, service desk productivity, and customer satisfaction.
Learn how to view the BMC HelixGPT-generated resolution notes in Configuring BMC HelixGPT to generate incident resolution notes.
Manage contracts from a single, intuitive Contracts console
Use the BMC Helix Innovation Studio-based Contracts console for an intuitive experience for managing contracts. The Contracts console provides rich filtering and sorting capabilities that help you find contracts quickly.
You can perform various actions on the contracts from a single interface. For example, edit contracts, view a contract's related contracts and CIs, and export search results to a .csv file.
Learn more about the Contracts console in Accessing and navigating the Contract console.
Progressive Web Application (PWA) screens for contract management
The support for Progressive Web App (PWA) screens has been extended to contract management to offer a customizable, dynamic, modern UX that exactly fits your needs.
PWA screens are already available for changes, releases, work orders, incidents, assets, broadcasts, problem investigations, and tasks. With contract management also available in PWA screens, you can enjoy a seamless experience across different BMC Helix ITSM application modules. For more information about PWA screens, see Progressive Web Application (PWA) screens.
Learn more about enabling PWA screens and managing contracts in Enabling Progressive Web Application screens and Managing Contracts.
Filter configuration items in Asset Console in fewer steps based on keywords
As an asset manager, you can filter and view Configuration item (CI) records in Asset Console based on preconfigured fields, such as CI name, Product name, and Description, without having to apply multiple filters, saving your time and effort to take on other critical issues. Based on your organization's specific requirements, customize and filter other fields as well. You can also share the Keywords filter as a preset with other users to perform a similar analysis, reducing time and effort.
Learn more about filters in Accessing and navigating Asset Console.
Automatically assign attribute values to assets to eliminate efforts
As an asset administrator, you can create automation rules to automatically assign attributes and their values to your organization's newly created assets. Because you do not have to perform the association for multiple assets manually, this feature saves you time and increases efficiency.
Learn more about assigning attribute values in Assigning attributes to assets automatically.
Download Proactive management clusters with job configuration for offline analysis
As a problem coordinator, when you download Proactive problem management clusters, the complete job configuration details appear in the downloaded file. When you share the file with other users, the job configuration help them understand how the clusters are created, promoting clustering transparency and collaboration amongst problem coordinators.
Learn more about downloading clusters in Proactive problem management and Resolution insights overview.
Relate Proactive problem management cluster incidents to known errors in fewer steps
As a problem coordinator, you can relate existing known errors with the incidents within the Proactive problem management clusters through BMC Helix ITSM Insights. You need not spend time and effort navigating to BMC Helix ITSM to establish the relationship. You can use the saved time and effort to address other critical issues.
Learn more about relating incidents with known errors in Managing clusters.
Track resolved and closed incidents in Real-time incident correlation clusters
As a service desk manager, you can view the list of resolved and closed incidents in Real-time incident correlation clusters. You can then download the list for further analysis to improve incident management in your organization.
Learn more about tracking resolved and closed incidents in Incident correlation.
Assign outages from the PWA screens
As a service desk agent or change coordinator, assign outages of tickets, incidents, or change requests from the PWA screens. With this capability, you can save time and effort, because you don't need to navigate to the Mid Tier to assign outages. You can also assign outages for multiple CIs simultaneously from the PWA screens.
Learn more about how to assign outages from a change request in Relating items to the change request.
Restrict change schedules by creating change freeze windows
Use the BMC Helix ITSM Calendar based on BMC Helix Innovation Studio to create, edit, and view the change freeze schedules.
During these designated change freeze windows, no change requests can be scheduled. This feature helps maintain stability during critical periods, such as significant product launches, year-end financial closures, or other important events.
The change freeze schedule feature is available only on the Progressive Web App (PWA) screens in BMC Helix ITSM.
The change freeze schedules can be defined for change requests in specific locations, related to specific operational or product categories, and associated with a specific CI. Set the change freeze schedules as one-time or recurring, and either strictly prohibit changes or require additional approvals to implement changes.
For more information, see Creating and managing change freeze schedules.
What else has changed in this release
| Update | Product behavior in versions earlier than 25.2.00 | Product behavior in version 25.2.00 |
|---|---|---|
| A transparent loader on PWA screens restricts you from performing any other operations until the ongoing operation is completed. | On PWA screens, when you perform certain operations, such as create or edit a ticket, a loader is displayed for a partial duration and not until the operation is completed. This allows you to perform other operations on the PV screen even while the earlier operation is still in progress, resulting in errors. | On PWA screens, when you perform certain operations, a transparent loader is displayed until the operation is completed, indicating that the operation is in progress. You cannot perform any other operation during this time. Learn for which operations the transparent loader is displayed in Handling the transparent loader for customizations. |
| Support for additional filtering options in Shared Ticket Console. | The additional filtering options are available in the Smart IT Ticket Console but not in Shared Ticket Console. | The following additional filtering options are available in Shared Ticket Console:
Learn more about the new filtering options in Adding sub-filters to the Shared Ticket Console. |
| Support to attach a menu to a character field inside a cell-based table on PWA screens. | On PWA screens, menu fields are shown as input boxes in cell-based tables. | On PWA screens, you can attach a menu to a character field inside a cell-based table so that the field contains a predefined list of choices. Learn more about attaching a menu to a character field in Differences between Developer Studio features available for Mid Tier and Progressive Web Applications. |
| The Agentic chat feature is generally available. | The Agentic chat feature was under controlled availability to select customers. | The Agentic chat feature is generally available. For more information, see Leveraging Agentic chat to search for information. |
| The advanced responsive navigation feature is generally available. | The advanced responsive navigation feature was under controlled availability to select customers. | The advanced responsive navigation feature is generally available. For more information, see Enabling Advanced Responsive Navigation. |
| Change in names of the out-of-the-box skills for the Ask HelixGPT feature for generating resolution information for incidents. | The names of the out-of-the-box skills for the Ask HelixGPT feature for generating resolution information for incidents are:
| The names of out-of-the-box skills for the Ask HelixGPT feature for generating resolution information for incidents are changed to:
For more information, see Configuring Ask HelixGPT for BMC Helix ITSM. |
| Change in the name of the out-of-the-box skill for the Agentic chat feature. | The name of the out-of-the-box skill for the Agentic chat feature is ITSM Global Chat Skill. | The name of the out-of-the-box skill for the Agentic chat feature is changed to Agent in Global Context. For more information, see Configuring Agentic chat for BMC Helix ITSM. |
The following system fields no longer appear in columns and filters of Real-time incident correlation and Proactive problem management:
| If selected in the data set, these system fields appeared as filters and table columns in the Real-time incident correlation and Proactive problem management. | These system fields are used internally by the ITSM Insights algorithm and serve no usage to the user. Therefore, these fields have been removed to simplify the user interface. However, these system fields still appear in the data set configuration. |
Ability to set the character limit of each descriptive field for clustering.
| The Proactive problem management algorithm did not support the ability to set the character limit of each descriptive field for clustering. | The Proactive problem management algorithm supports setting the character limit of each descriptive field used for clustering. You can set this limit in the job and Proactive problem management settings. This limit reduces the load on the system resources while generating clusters. For more details, see Configuring proactive problem management settings, Configuring Proactive problem management settings for recurring jobs, and Configuring one-time job settings for proactive problem management. |
Ability to hide Proactive problem management clusters based on the number of incidents they contain. Note: You must upgrade to the 25.2.00 version of the ADE release to use this feature. | The Proactive problem management algorithm did not support hiding clusters based on the minimum number of incidents. | The Proactive problem management algorithm supports hiding clusters based on the minimum number of incidents they contain. This setting helps you eliminate clusters that are insignificant in your problem investigation. For more details, see Configuring Proactive problem management settings for recurring jobs, and Configuring one-time job settings for proactive problem management. |
New configuration parameter enableChangeFreeze | This configuration parameter is not present. | This configuration parameter is used to enable the change freeze feature. For more information about setting the CCS parameter, see Setting configuration parameters in BMC Helix ITSM. |
BMC Helix Innovation Suite enhancements
25.2 enhancements and patches
25.2.01 updates
Use updated support for technology stack
BMC Helix Service Management supports the following technology stacks:
- Kubernetes version 1.32
- OpenShift version 4.18
- Nginx Ingress Controller version 1.12.1
- Helm 3.17
For more information, see System requirements in the BMC Helix Service Management documentation.
Integrate BMC Helix Service Management with the CyberArk vault
Integrate BMC Helix Service Management with a CyberArk vault to securely store sensitive information, particularly privileged account credentials and secrets..
For more information, see Integrating BMC Helix Service Management with the CyberArk vault.
Enhanced support for PostgreSQL database versions
BMC Helix Service Management supports PostgreSQL database version PostgreSQL 17.x.
For more information, see System-requirements.
Verify the container image integrity by using the image digest
Verify the digests of container images in your local registry. This capability helps you ensure that only trusted and untampered images are used when installing BMC Helix Service Management.
For more information, see Setting up a Harbor repository to synchronize container images.
Use additional deployment sizes
Use the Insights_C, Insights_S, Insights_M, Insights_L, and Insights_XL sizing profiles to install BMC Helix ITSM Insights with BMC Helix Service Management.
For more information, see Sizing and scalability considerations and Performing the BMC Helix Service Management installation.
25.2.00 updates
The following video (00:53) provides a quick overview of the enhancements in the BMC Helix Innovation Suite 25.2.00.
Watch the video that describes the new features in Innovation Suite 25.2.00
Customize the disclaimer message for the BMC HelixGPT chat component
As a developer or an application business analyst, customize the disclaimer text, URL, and label on the screen when using the BMC HelixGPT chat component. Tailor the disclaimer text according to your organization's policy, ensuring that it aligns with your specific requirements. You can also add a link to the policy details through the disclaimer URL and customize the content for different locales.
For more information about customizing the disclaimer text, see Adding an AI-based conversational search interface to a view.
Prepare custom-coded application bundles for upgrade
You can prepare and stage the updated application bundles, which are deployed during the upgrade to ensure minimal downtime. Upgraded UI elements and third-party libraries might cause issues for custom-coded applications built on BMC Helix Innovation Studio. For example, when you upgrade BMC Helix Innovation Suite from the 25.1 version to the 25.2 version, custom-coded applications might not function due to Angular SDK changes. To avoid compatibility issues, you must rebuild all custom-coded libraries by using the latest SDK.
For more information, see Preparing custom-coded applications for upgrade.
Simplified licensing model for BMC Helix Service Management Suite
You have the option to adopt the new Helix Service Management Suite licensing model. This model is based on a suite approach. It includes licenses for the BMC Helix Innovation Suite, AR System-based applications, BMC Helix Innovation Studio-based applications, BMC Helix ITSM, and all Service Management applications. By utilizing this licensing model, customers receive a combination of multiple related SKUs, allowing them to derive value from the complete solution.
For more information about the licensing model, see Licensing overview.
Sync data from BMC Helix SaaS to an external destination
Starting with BMC Helix Innovation Suite 25.2, administrators can use BMC Helix Data Connector in BMC Helix Innovation Suite to sync service management data. You can sync data from BMC Helix SaaS to an on-premises database (Microsoft SQL Server) or to Snowflake. You must subscribe to BMC Helix Data Connector to enable this capability. Using BMC Helix Data Connector, you can perform interval-based ongoing syncs. This capability ensures your data is consistently available in your chosen data lake or warehouse for executive reporting, compliance audits, or advanced analytics.
For more information, see Syncing data from BMC Helix SaaS to a destination database.
Creation of web reports disabled by using the AR System Report Console
As an administrator, you can no longer create web reports by using the AR System Report Console. We recommend that you create new web reports by using BMC Helix Dashboards.
You still have full access to view, schedule, and publish BIRT web reports without any restrictions.
For more information, see Creating and managing custom web reports.
Import specific knowledge articles to BMC Helix Knowledge Management by ComAround
As an administrator, import specific knowledge articles to BMC Helix Knowledge Management by ComAround by providing the article IDs. The key advantages of importing only the required knowledge articles are:
- Improved control, efficiency, and flexibility when using the import tool
- Reduced risk of errors and data corruption during the import process due to the limited scope of the import
- Faster import process and optimized tool performance
For more information, see Importing the knowledge bases.
What else changed in this release
The following table lists the changes in the product behavior:
| Update | Product behavior in versions earlier that 25.2.00 | Product behavior in version 25.2.00 |
|---|---|---|
| Support for the latest Generative AI models | NA | BMC HelixGPT supports the latest Generative AI models. For more information, see Adding an AI-based conversational search interface to a view. |
| Use advanced filtering in a record grid to apply complex expressions. | You could perform basic filtering at the field level. | You can use advanced filtering on a record grid to apply complex expressions with AND/OR/NOT/LIKE/NULL operators, calculations, and keywords. For more information, see Creating a tabular view of record instances by using a record grid. |
| Use additional functions in the expression editor in view and shell designers. | Fewer functions were available in the expression editor in view and shell designers. | You can use additional functions in the expression editor in view and shell designers to build more complex expressions. For more information, see Expression Editor. |
Enhanced navigation to access support groups associated with companies while mapping permissions to BMC Helix Knowledge Management by ComAround | In Administration > Knowledge management > Knowledge access mapping, administrators could view all associated support groups of a company only by selecting this company from the Company list. However, when viewing all companies, they couldn’t access the support groups for any specific company from the table that displays all companies. | In the Administration > Knowledge Management > Knowledge Access mapping section, administrators can easily access the support groups associated with a specific company from a table that displays all companies. By clicking the drop-down arrow next to a company's name, administrators can view the list of support groups for that company. This improvement enhances navigation by allowing administrators to access support groups with a single click, eliminating the need to select the company from a separate field. Additionally, breadcrumbs offer a quick and clear method to return to the table of all companies, streamlining the user experience and reducing unnecessary steps. For more information, see Defining permission mappings for BMC Helix Knowledge Management by ComAround. |
| Display a loading indicator in an application. | You cannot display a loading indicator with a transparent overlay by using the run process ENABLE-WAIT-CURSOR-ON-LONG-RUNNING-PROCESS. | By using the run process ENABLE-WAIT-CURSOR-ON-LONG-RUNNING-PROCESS, you can display the loading indicator with a transparent overlay that prevents access to the application interface. For more information, see Process commands. |
| Use a field with a menu attached inside a cell-based table in PWA. | You could not use a field with a menu attached inside a cell-based table in PWA. | You can use a field with a menu attached inside a cell-based table in PWA by enabling the necessary CCS parameter. For more information, see Differences between Developer Studio features available for Mid Tier and Progressive Web Applications. |
BMC Helix CMDB enhancements
25.2.00
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default.
For more information, see Improving reconciliation job performance.Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.What else changed in this release
The following table lists the changes in the product behavior:Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
|
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
25.2.00
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|
Improvements to reconciliation jobs with Merge activity
The reconciliation merge service performs with better speed and efficiency by processing the merge activity on a separate pod by default. For more information, see Improving reconciliation job performance.
Update the Product Catalog with end-of-life attributes by using a normalization job
Use the Allow Updates to a Product Catalog Entry option in a normalization job to update the following end-of-life attributes:
- StartAvailability
- EndAvailability
- EndOfLife
- EndOfSupport
- EndOfSecuritySupport
- EndOfExtendedSupport
For more information, see Creating a normalization job.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 25.2 | Product behavior in version 25.2 |
|---|---|---|
Updates to the BMC_BaseElement class in the common data model. | Only the following end-of-life attributes are available:
| The following attributes are available along with the existing end-of-life attributes:
For more information, see Summary of changes to the Common Data Model. |
| Reconciliation jobs that exclude CIs that failed in the previous run. | In a reconciliation job, you could not exclude those CIs that had failed in a previous run of the reconciliation job. | In a reconciliation job, use the Ignore Failed CIs option to exclude those CIs that had failed in a previous run of the reconciliation job. Ignoring failed CIs helps improve the performance of the reconciliation job.For more information, see Improving reconciliation job performance. |
| Updates to locales for CMDB Portal | Only the following browser locales were supported:
| The following browser locales are also supported, in addition to the previously supported ones:
|