22.1 enhancements and patches
Review the BMC Helix Intelligent Automation 22.1 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.
| Version | SaaS | On premises | Fixed issues | Updates and enhancements |
|---|---|---|---|---|
| 22.1.01 |  | - | Known and corrected issues | 22.1.01 enhancements |
| 22.1.00 | | - | Known and corrected issues | 22.1 enhancements |
For the updates in the previous monthly releases, see
2021 enhancements
.
BMC applies upgrades as described in
BMC Helix Upgrade policy
. BMC applies upgrades and patches during
Maintenance windows.
22.1.01
Support for additional data types in the automation policy trigger conditions
You can define numbers, null and Boolean values, strings with special characters along with the string data types in a trigger condition while creating automation polices. If an incoming event contains any of these data types, the policy gets triggered.
For existing policies, ensure that the trigger condition matches the event JSON.
For more information, see Creating automation policies.
Ability to select users while specifying change request details in a policy
While specifying change request options in a policy, in the First Name field you can specify only the users that belong to the company. Based on the selected company, the list of users appears. When you select the first name, the last name is also selected. You cannot add a user name if it is not associated with the company in BMC Helix IT Service Management.
For more information, see Creating automation policies.
Updates to the automation status
When automations are triggered for an open event from BMC Helix AIOps, the automation status is updated based on the policy status in BMC Helix Intelligent Automation. If a change request associated with the policy is rejected or waiting for an approval, the automation status is shown according to the policy status.
22.1.00
The following video (4:49) showcases the features and enhancements available in the BMC Helix Intelligent Automation release.
Ability to create change requests in BMC Helix ITSM
If infrastructure changes are to be made as part of an automation policy, you can keep track of the changes and get them approved by creating a change request in BMC Helix ITSM (SaaS only).
You can specify the change request details while creating a policy. For more information, see Creating automation policies.
On the History page, you can view the status of the change request against a policy run. The policy runs only after the change request is approved. The change request is closed irrespective of whether the policy runs successfully or fails.
For more information, see Viewing automation policy runs.
Comments
Log in or register to comment.