Configuring change rules for requests from automation system
This topic provides information to an administrator about configuring change rules for requests from automation system and provides procedures to configure these rules.
You can configure change rules for a specific company or you can create a global rule applicable to all companies. For information about configuring chanage rules, see Configuring change rulesin the BMC Remedy Change Management 9.1 online documentation.
About change rules
In Change Management, there are certain rules that are applicable only to requests from an automation system. A request from an automation system is a request created using the new Service Interface with the change type as "Automation". The rules that are applicable only to requests from automation system are added to the Automation System tab of the Configure Change Rules form.
There are also some rules that are not applicable to requests from automation system. For example, rules that require user interaction, are not required in case of automation systems. Such rules are bypassed if you are implementing Operator-Initiated Change. These rules are present in the the General tab of the Change Configuration Rules form, but are separated from other rules.
For example, the rule Require Service CI Related after Draft is not applicable to requests from automation system, because the service CI is not mandatory in these requests. A service model is not present with external automation system. Even if you set the rule to Yes, change records for requests from automation system are created without service CI and moved to closure.
The following screenshot illustrates rules not applicable to requests from automation system from the General tab.
The rules that are specific to requests from automation system can be defined in the Automation System tab. The following screenshot illustrates the Automation System tab. The following table provides information about Global rules that can be configured for requests from automation system. Rule Default value Description Create Service Request on Submit Note - This rule applicable only when Remedy Service Request Management is installed. No If you set the rule to Yes, a corresponding Service Request is created for automation requests. Default Automation Change Process Flow Standard Process-Automation System If your change template does not have any process flow defined, the process flow defined in this rule will be applied. The default rule is Standard Process-Automation System. You can create your custom process flow if required, and set it to default process flow. For information about configuring custom process flow, see Configuring custom process flows in BMC Remedy Change Management 9.1 online documentation. Default Change Duration Three days If the Job End Date is not provided by the automation system, value specified in this field is used to calculate the requested or scheduled end date of the change record. You can specify the duration in days, hours, minutes and seconds. Outbound Communication Approval Status Scheduled For Approval This rule represents the approval status. The selected approval status is communicated back to the automation system after the change is approved. Default status is "Scheduled for Approval". However, if you set an approval process for any other phase than Implementation Approval, you need to select an approval status accordingly.
Rules applicable to requests from automation system
