Page tree
Skip to end of metadata
Go to start of metadata

View the worklog to see information about updates performed for an RFC (Request For Change).

  1. Navigate to Applications > Change Management > Search Change.
  2. In the Infrastructure Change (Search) form, enter the Change ID of the RFC.
  3. Click Search.
  4. To view the the worklog, click the Work Details tab.
    The following screenshot illustrates entries in the Work Details tab for an RFC.

     

The following table provides information about the updates performed for an RFC.

Use CaseWorklog entryReason for creating the worklog entry
Completing CI association

[DATA ERROR]: Unable to create associations.

[DATA ERROR]: Unable to update associations.

[DATA ERROR]: Unable to delete associations.

<comma separated CI string> does not exist in the database.

More than one CIs with CI Name(s): <comma separated CI string> found in the database.

Created if failures are encountered while creating/updating CI association with task.
CI association
CI Association startedCreated when a plug-in is run to create a CI relationship with task.
CI association
CI Association successfulCreated when no errors are encountered while establishing a CI relationship with a task and all CI associations are successful.
Schedule change by Change Manager<User_Name> has modified the Change scheduleCreated when change schedule dates are updated in the outbound form.
Schedule change for resilience to avoid exception related to class

Use <expedite/Emergency> as the class for this Change if you need to create a Change before <Date>.

Change is created with Normal class because the system cannot create a Change with 'No Impact' class if impact specified is greater than <lowest impact>

Change is created with Normal class because the system cannot create a Change with 'Emergency' class if urgency specified is lower than <lowest urgency>

Indicates that the change class that is sent in the request is improper for the requested schedule date. If the schedule date changes, the user needs to update change class appropriately in order to execute the change immediately.
Requested Start Date calculation using templateRequested Start Date was not received from the Automation System. The Requested Start Date is updated with the server time stamp value.

Created to indicate that default value is applied because no input was provided.

The Requested Start Date is defaulted to system current date.

Calculating Risk LevelRisk Level <Risk_level> is calculated for this Change.Created when risk level is calculated by considering other parameters of change.
Populating Customer informationCustomer details were not received from the Automation System. System reset to the default requester details.Created when customer details are not received and the value is reset to Requested by user.
Populating Location informationChange Location was not received from the Automation System. System reset to the default customer location.Created when company location is not provided and value is reset to Customer location.
Class is set as No Impact[DATA ERROR]: Value of Impact has been reset to 4-Minor/Localized because Class is set as No Impact.Created when impact is set to any value less than 4.
Class is set as Emergency[DATA ERROR]: Value of Urgency has been reset to 1-Critical because Class is set as Emergency.Created when urgency is set to any value greater than 1.
Class is set as Expedited[DATA ERROR]: Value of Urgency has been reset to 2-High because Class is set as Expedited.Created when urgency is set to any value greater than 2.
Class is set as Latent and Start Date is in the future[DATA ERROR]: Value of Class has been reset to Normal because Change is not yet performed.Created when the Start Date is in the future and the change class is set as Latent.
Start date is of the past and Class is anything other than Latent[DATA ERROR]: Value of Class has been reset to Latent because the Change was already performed.Created when the Start Date is in the past and the change class is set to any value other than Latent.

2 Comments

  1.  

    1.