This topic provides information to a job operator or an automation engineer about the transformation and remediation actions performed on the data provided by automation system while creating a change record. Information about all the transformation and remdediation actions is added to the change worklog. See Viewing worklog updates.
Data transformation and remediation actions are performed in the following scenarios:
The following table provides information about data conversion and remediation performed to create a meaningful change record.
|Automation system parameter||Parameter received as input from the automation system?||Data remediation action||Worklog information update|
|Data conversion to a format acceptable to Change Management|
|Date||Date in UTC format||Date is converted from UTC format to Epoch format|
|Data remediation action for inputs not provided by automation system|
|Schedule_start_date||No||The Requested Start Date is updated with the server time stamp value.||Yes|
If the schedule end date is not provided by the automation system, a default end date is calculated based on the scheduled start date.
For more information, see Configuring change rules for requests from automation system.
|Risk level||The risk level is calculated considering other parameters in the RFC.||Yes|
|Customer details||No||Customer details are defaulted to requester details.||Yes|
|Change location||No||Change location is defaulted to the customer location.||Yes|
|Change process flow||Not defined|
The following order of precedence is followed:
For more information, see Overview of Standard Process-Automation System process flow.
|Change template||No Template Name/Template ID/Template Instance ID is defined||The applicable template is searched from template configuration rules. If no template is applicable, the change record is populated with default values.||Yes|
|Change class||No||Class is set as Normal||Yes|
|Change impact||No||Impact is set to 4-Minor/Localized||Yes|
|Change urgency||No||Urgency is set to 4-Low||Yes|
|Change priority||No||Priority is calculated based on impact and urgency values.||Yes|
|Automation task||No||An automatic task is created and associated with the change template.||Yes|
|Data remediation actions to correct data inconsistencies|
|Change class||Change class is No Impact and value of change impact is set to any value less than 4-Minor/Localized.||The value of impact is reset to 4-Minor/Localized.||Yes|
|Change class is Emergency and value of urgency is set to any value greater than 1-Critical.||The value of urgency is reset to 1-Critical.||Yes|
|Change class is Expedited and value of urgency is set to any value greater than 2-High.||The value of urgency is reset to 2-High.||Yes|
|Change class is Latent and scheduled_start_date is in future.||The value of class is reset to Normal, because the Change is not yet performed.||Yes|
|Change class is anything other than Latent and scheduled_start_date is in the past||The value of class is reset to Latent, because the Change has been performed.||Yes|