25.3 enhancements and patches
Related topics
Review the BMC Helix Intelligent Automation 25.3 enhancements and patches for features that will benefit your organization and to understand the changes that might impact your users.
| Version | Saas | On-premises | Fixed issues | Updates and enhancements |
|---|---|---|---|---|
| 25.3.02 | ✅ | - | Known-and-corrected-issues | updates |
| 25.3.01 | ✅ | - | Known-and-corrected-issues | updates |
| 25.3 | ✅ | ✅ | Known-and-corrected-issues | 25.3 enhancements |
For a list of recent updates and enhancements across multiple versions, see Release-notes-and-notices.
BMC Helix applies upgrades as described in the BMC Helix Upgrade policy. BMC Helix applies upgrades and patches during Maintenance windows .
25.3.02
Improved JSON editor with support for additional functions
When you create a policy, use the added transformation functions for date and array operations to reduce reliance on hard-coded values.
For more information, see Creating automation policies.
Access Target Host and Target Port details from the Configured Connectors
On the Configured Connectors page, view the Target Host and Target Port details to identify the endpoint and associated port used by the connector. This enhancement simplifies troubleshooting. If you do not specify a port while configuring the connector, BMC Helix Intelligent Automation automatically displays 443 for HTTPS and 8080 for HTTP. For connectors where the target port and target host are not applicable, the UI displays N/A.
Automatically retry running failed policy runs
Configure the Maximum Retry Duration option on the Configure an Action tab to automatically retry failed remediation policy runs. BMC Helix Intelligent Automation retries running these policy runs by using an exponential backoff strategy for up to 4 hours. You can specify retriable error codes and view the retry status on the History page.
For more information, see:
- Running a Jenkins job
- Terminating, starting, or stopping an EC2 instance
- Restarting PATROL Agent on a server
- Resizing a deployment
- Executing a workflow
- Invoking a process in BMC Helix Innovation Studio
- Viewing automation policy runs history
Use event slots to set the change ticket schedule in automation policies
Use the Scheduled Start Date and Scheduled End Date fields to map any relevant event slots to the corresponding start and end dates for the change request in BMC Helix ITSM. The automation policy is triggered based on the scheduled start date value.
For more information, see Creating automation policies.
25.3.01
Execute automation policies based on the scheduled start date and time of a change request
When an automation policy also creates a change request in BMC Helix ITSM, the policy runs after the change request moves to the Scheduled state and based on the scheduled start time.
When the change request status is Scheduled, the policy run status also changes to Scheduled and is executed based on the start time. This action enhances compliance, reduces operational risk, and ensures that the automation policy follows ITSM-defined schedules.
For more information, see Creating automation policies.
Assign an incident to a specific support group by using the Ops-category and product category
While configuring Proactive Service Resolution for automating incident creation, you can dynamically assign an incident to a specific support group in BMC Helix ITSM. This incident routing is based on the rules configured in BMC Helix ITSM. To do this, you add an event payload with the Ops category, product category, or both. This enhancement helps reduce manual routing of incidents, improves accuracy, and ensures faster resolution by directing incidents to the most relevant teams.
For more information, see Configuring Proactive Service Resolution for incidents in BMC Helix ITSM.
Transform variables by using special characters and preview the transformation logic
When you add a variable while configuring a policy, use the enhanced variable panel for applying transformation with special characters such as commas and curly braces. Additionally, preview the complete command and view the applied transformation logic, including the number and names of transformations applied to a variable or field in the JSON editor. These improvements simplify debugging, ensure accurate command construction, and help you build dynamic remediation actions without relying on hard-coded values.
For more information, see the following topics:
25.3
The following video (2:33) describes the enhancements in BMC Helix Intelligent Automation 25.3:
Watch the YouTube video about What's new in BMC Helix Intelligent Automation 25.3:
Improved JSON editor with support for additional functions and a variables panel
When you configure an action by using the generic REST connector, use the improved JSON editor with added transformation functions for string, date, and array operations. Additionally, use the variables panel to copy and paste variables that you defined while creating the policy. These enhancements help you dynamically modify the JSON structure and apply transformations to reduce reliance on hard-coded values.
For more information, see:
Access incident details by using the cross-launch link from the event
When an incident is automatically created in ServiceNow ITSM, BMC Helix Intelligent Automation provides the incident URL in the CMDB Instance Name field of the information event in BMC Helix Operations Management. If you are investigating a situation in BMC Helix AIOps, the incident URL is populated in the Incident ID field. This enhancement helps you to access related incident information faster, reducing the mean time to resolve (MTTR).
Use event slots from the previous execution to configure trigger conditions
Use event slots from previous executions to configure trigger conditions in automation policies that run in automatic execution mode. This feature helps you reduce unnecessary incident traffic and creates more accurate and context-aware automation triggers.
For more information, see:
