Change Management module root-level workflows

This section describes the following Change Management module root-level workflows, their inputs, and their outputs:

Associate Change and Incident

This workflow associates a change record in Change Management to an incident ticket in Incident Management and vice versa.


Associate Change and Incident workflow inputs

Input

Description

Required

configuration name

Specifies a configuration group defined in the module configuration

Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

change id

Specifies the unique identifier for the change

Yes

incident id

Specifies the unique identifier for the incident

Yes

change description

Describes the change association

Conditional; required if the configuration name is BMC_AR_System

incident description

Describes the incident association

Conditional; required if the configuration name is BMC_AR_System


Associate Change and Incident workflow outputs

Output

Description

success status

Indicates whether the workflow is executed successfully

Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

Close Change

This workflow updates the status of and closes the change record.


Close Change workflow inputs

Input

Description

Required

configuration name

Specifies a configuration item defined in the module configuration

Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

change id

Specifies the unique identifier for the change

Yes

status reason

Specifies the status reason

To select the correct status, you must be familiar with the change lifecycle

Valid values for BMC_AR_System:

 Click here to view...

  • No Longer Required
  • Funding Not Available
  • To Be Re-Scheduled
  • Resources Not Available
  • Successful
  • Successful with Issues
  • Unsuccessful
  • Backed Out
  • Final Review Complete
  • Final Review Required
  • Additional Coding Required
  • Insufficient Task Data
  • In Verification
  • In Rollout
  • Insufficient Change Data
  • Schedule Conflicts
  • In Development
  • In Test
  • In Build
  • In Rollback
  • In Documentation
  • Vendor Purchase
  • Support Group Communication
  • Task Review
  • Miscellaneous
  • Future Enhancement
  • Manager Intervention
  • Accepted
  • Assigned
  • Built
  • On Hold
  • Automatically Closed



Valid values for HP_ServiceCenter: This is a free-form text field to record comments on the closure of this change.

Note: If you use BMC Remedyforce, this parameter is not applicable.

No

status

Specifies the new status as Closed

Yes

actual start date

Specifies the actual date that work started on the change

BMC_AR_System example: 1262304060 (requires epoch format)

HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ)

Example: 2012-08-05T13:15:30Z (utc)

No

actual end date

Specifies the actual date that work finished on the change

BMC_AR_System example: 1262304060 (requires epoch format)
 
HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ)

Example: 2012-08-05T13:15:30Z (utc)

No

scheduled start date

Specifies the date that work is scheduled to begin on the change

BMC_AR_System example: 1262304060 (requires epoch format)

HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ)

Example: 2012-08-05T13:15:30Z (utc)

No

scheduled end date

Specifies the date that work is scheduled to finish on the change

BMC_AR_System example: 1262304060 (requires epoch format)

HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ)

Example: 2012-08-05T13:15:30Z (utc)

No


Close Change workflow outputs

Output

Description

changes

Displays an XML document that contains the information of the change record in a change management system; uses the change concept structure

success status

Indicates whether the workflow finished successfully

Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

Create Change Association

This workflow creates a change association between the change record in Change Management and the incident record, task record or a configuration item record in the respective applications.


Create Change Association workflow inputs

Input

Description

Required

configuration name

Specifies a configuration item defined in a configuration module
 
Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

changes

Displays an XML document that contains the information required to create a change and incident association in a change management system; uses the change concept structure

Note: This workflow associates only a change and incident if you are using the BMC_Remedyforce application.

Yes


Create Change Association workflow outputs

Output

Description

changes

Displays an XML document that contains the information of the change record in a change management system; uses the change concept structure

success status

Indicates whether the workflow finished successfully

Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

Create Changes

This workflow creates a change record.


Create Changes workflow inputs

Input

Description

Required

changes

Specifies the XML document that contains the information required to create a change record in a change management system; uses the change concept structure

Yes

configuration name

Specifies a configuration group defined in the module configuration

Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes


Create Changes workflow outputs

Output

Description

changes

Displays an XML document that contains the changes created based on the request

failed changes collection

Displays an XML document containing failed changes

success count

Provides the number of successful changes

failure count

Provides the number of changes that failed creation

success status

Indicates whether the workflow finished successfully

status message

Provides a process-specific explanation for the value of the success status

consolidated status

Displays an XML document that contains the consolidated results for multiple inputs

Back to top

Update Change Actual Start Date

This workflow updates the date work actually started on an existing change record.


Update Change Actual Start Date workflow inputs

Input

Description

Required

configuration name

Specifies a configuration item defined in a configuration module

Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

change id

Specifies the unique identifier for the change

BMC_AR_System example: CRQ000000000201 

HP_ServiceCenter example: C23

BMC_Remedyforce Example:CR00000055

Yes

actual start date

Specifies the actual date that work started on the change

BMC_AR_System example: 1262304060 (requires epoch format)

HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ)

Example: 2012-08-05T13:15:30Z (utc)

Yes


Update Change Actual Start Date workflow outputs

Output

Description

changes

Displays an XML document that contains the information of the change record in a change management system; uses the change concept structure

success status

Indicates whether the workflow finished successfully

Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

Update Change Impact

This workflow updates the Impact field in an existing change record with a specified value.


Update Change Impact workflow inputs

Input

Description

Required

configuration name

Specifies a configuration item defined in a configuration module

Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

change id

Specifies the unique identifier for the change

Yes

new impact

Specifies the new impact value

Valid values for BMC_AR_System:

1-Extensive/Widespread
2-Significant/Large
3-Moderate/Limited
4-Minor/Localized

Valid values for HP_ServiceCenter:

1 - Enterprise
2 - Site/Dept
3 - Multiple User
4 - User

Valid values for BMC_Remedyforce:

High
Medium
Low

Yes


Update Change Impact workflow outputs

Output

Description

changes

Displays an XML document that contains the information of the change record in a change management system; uses the change concept structure

success status

Indicates whether the workflow finished successfully

Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

Update Change Scheduled Start Date

This workflow updates the scheduled start date in an existing change record with a specified value.


Update Change Scheduled Start Date workflow inputs

Input

Description

Required

configuration name

Specifies a configuration item defined in a configuration module
 
Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

change id

Specifies the unique identifier for the change

Yes

scheduled start date

Specifies the scheduled start date

BMC_AR_System example: 1262304060 (requires epoch format)
 
HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ)

Example: 2012-08-05T13:15:30Z (utc)

Yes


Update Change Scheduled Start Date workflow outputs

Output

Description

changes

Displays an XML document that contains the information of the change record in a change management system; uses the change concept structure

success status

Indicates whether the workflow finished successfully

Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

Update Change Status

This workflow updates the status of an existing change record with a specified value.


Update Change Status workflow inputs

Input

Description

Required

configuration name

Specifies a configuration item defined in a configuration module

Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

change id

Specifies the unique identifier for the change

Yes

status reason

Specifies the status reason

Valid values for BMC_AR_System:

 Click here to view...

  • No Longer Required
  • Funding Not Available
  • To Be Re-Scheduled
  • Resources Not Available
  • Successful
  • Successful with Issues
  • Unsuccessful
  • Backed Out
  • Final Review Complete
  • Final Review Required
  • Additional Coding Required
  • Insufficient Task Data
  • In Verification
  • In Rollout
  • Insufficient Change Data
  • Schedule Conflicts
  • In Development
  • In Test
  • In Build
  • In Rollback
  • In Documentation
  • Vendor Purchase
  • Support Group Communication
  • Task Review
  • Miscellaneous
  • Future Enhancement
  • Manager Intervention
  • Accepted
  • Assigned
  • Built
  • On Hold
  • Automatically Closed



Valid values for HP_ServiceCenter: This is a free-form text field to record comments on the closure of this change.

Note: If you use BMC Remedyforce, this parameter is not applicable.

No

status

Specifies the new status

Valid values for BMC_AR_System:

  • Draft
  • Request For Authorization
  • Request For Change
  • Planning In Progress
  • Scheduled For Review
  • Scheduled For Approval
  • Scheduled
  • Implementation In Progress
  • Pending
  • Rejected
  • Completed
  • Cancelled

    Valid values for HP_ServiceCenter:
  • Initial
  • Pending
  • Closed 
    Valid values for BMC_Remedyforce:
  • Approved
  • Completed
  • Closed
  • In Progress
  • Opened
  • Pending Approval
  • Risk and Impact
  • Registered
  • Rejected

Yes

actual start date

Specifies the actual date that work started on the change

BMC_AR_System example: 1262304060 (requires epoch format)

HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ

Example: 2012-08-05T13:15:30Z (utc)

No

actual end date

Specifies the actual date that work finished on the change

BMC_AR_System example: 1262304060 (requires epoch format)

HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ

Example: 2012-08-05T13:15:30Z (utc)

No

scheduled start date

Specifies the date that work is scheduled to begin on the change

BMC_AR_System example: 1262304060 (requires epoch format)

HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ

Example: 2012-08-05T13:15:30Z (utc)

No

scheduled end date

Specifies the date that work is scheduled to finish on the change

BMC_AR_System example: 1262304060 (requires epoch format)

HP_ServiceCenter example: 2009.11.01 08:00:00

Note: BMC Remedyforce supports the ISO 8601 date format: yyyy-MM-dd'T'HH:mm:ssZZZZZ

Example: 2012-08-05T13:15:30Z (utc)

No


Update Change Status workflow outputs

Output

Description

changes

Displays an XML document that contains the information of the change record in a change management system; uses the change concept structure

success status

Indicates whether the workflow finished successfully

Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

Update Change Urgency

This workflow updates the urgency value in an existing change record.


Update Change Urgency workflow inputs

Input

Description

Required

configuration name

Specifies a configuration item defined in a configuration module

 Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

change id

Specifies the unique identifier for the change

Yes

new urgency

Specifies the new urgency value

Valid values for BMC_AR_System:

1-Critical
2-High
3-Medium
4-Low

Valid values for HP_ServiceCenter:

1-Critical
2-High
3-Average
4-Low

Valid values for BMC_Remedyforce:

1-High
2-Medium
3-Low

Yes


Update Change Urgency workflow outputs

Output

Description

changes

Displays an XML document that contains the information of the change record in a change management system; uses the change concept structure

success status

Indicates whether the workflow finished successfully

 Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

Update Changes

This workflow updates a change record; uses any data provided in concept element fields.


Update Changes workflow inputs

Input

Description

Required

configuration name

Specifies a configuration group defined in the module configuration

Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

changes

Specifies an XML document that contains the information required to update a change in a change management system; uses the change concept structure

Yes


Update Changes workflow outputs

Output

Description

changes

Displays an XML document that lists the changes updated based on the request

failed changes

Displays an XML document that lists requested changes that were not implemented because of a failure

success count

Provides the number of successful changes

failure count

Provides the number of changes that failed creation

success status

Indicates whether the workflow finished successfully

Valid values: success, failure

status message

Provides a process-specific explanation for the value of the success status

consolidated status

Displays an XML document that contains the consolidated results for multiple inputs

Back to top

Update WorkInfo

This workflow updates the work information log.


Update WorkInfo workflow inputs

Input

Description

Required

configuration name

Specifies a configuration group defined in the module configuration

Valid values: BMC_AR_System, HP_ServiceCenter, BMC_Remedyforce

Yes

change id

Specifies the unique identifier for the change

Yes

workinfo summary

BMC_AR_System: Test that summarizes the workinfo notes

HP_ServiceCenter: Summary text to store in the misc1 field

BMC_Remedyforce: Descriptive details to store in the Work Summary field.

Yes

workinfo details

BMC_AR_System: Descriptive details to be added into the work information log

HP_ServiceCenter: Descriptive details to store in the misc-array1 field

BMC_Remedyforce: Descriptive details to store in the work info details 

Yes

workinfo type

Specifies the type of workinfo

Example:

  • Development
  • General Information
  • Rejection Information
  • Test Results
    Note: If you use BMC Remedyforce, this parameter is not applicable.

No

locked

Determines whether to keep the workinfo locked

Valid values: Yes, No

No; not applicable for BMC Remedyforce application

view access

Specifies who can view this workinfo

Example: Internal, Public

No; not applicable for BMC Remedyforce application


Update WorkInfo workflow outputs

Output

Description

changes

Displays an XML document that contains the information of the change record in a change management system; uses the change concept structure

success status

Indicates whether the workflow finished successfully

Valid values: success, failure

status message

Provides a workflow-specific explanation for the value of success status

Back to top

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments