Automation rules
Automation rules are used to create tickets and issues automatically in the defined third-party ticketing system based on the specific triggers or conditions impacting an application or environment. For more advanced automation, you can use Concert Workflows to facilitate automated actions, such as automated certificate renewal.
Automation rules for ticket creation
After establishing a connection with an external issue tracking system, such as Jira or GitHub,
you can configure automation rules to automatically open and assign a ticket in the connected system
if one of the following conditions occurs:
- A high-priority CVE is detected.
- An environment is not compliant with an assessed compliance control.
- A certificate is approaching expiration or is already expired.
- A package or license (software composition) recommendation is available.
After selecting the condition and the relevant object, you can specify the parameters or threshold that should trigger the automation rule, such as defining a minimum CVE risk score or specifying a compliance profile. The parameters vary depending on the selected condition.
Deleted the following section until we can confirm the role of automation rules for Concert Workflows as an add-on versus as an external integration.
Concert Workflows is an embedded integration with IBM Rapid Network Automation that allows you to configure and manage advanced automation workflows, such as automatic certificate renewal, within the Concert UI. Refer to Automating Concert Workflows using automation rules for details.