Change Management module setup validation workflows

You can use the workflows in the Setup Validation folder as both a template for creating new workflows and a method to test the success of a newly created process. This section describes the following Change Management setup validation workflows:

Test Create Change Association workflow

Use this workflow as a template for associating a change record to an incident record (creating an association between them) and as a method for testing such an association.


Test Create Change Association 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 you use BMC_AR_System


Test Create Change Association workflow outputs

Output

Description

success status

Indicates whether the workflow finished successfully

status message

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

change

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

Back to top

Test Create Change workflow

Use this workflow as a template for creating a change record and as a method for testing record creation.


Test Create Change workflow inputs

Input

Description

Required

change description

Describes the change

Yes

configuration name

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

Yes


Test Create Change workflow outputs

Output

Description

success status

Indicates whether the workflow finished successfully

status message

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

changes

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

Back to top

Test Get Change by Change ID workflow

Use this workflow as a template for finding a change record by its change ID and as a method for testing that process.


Test Get Change by Change ID 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


Test Get Change by Change ID workflow outputs

Output

Description

success status

Indicates whether the workflow finished successfully

status message

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

changes

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

Back to top

Test Update Change Status workflow

Use this workflow as a template for updating the status of a change record and as a method for testing that process.




Test 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:

  • 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: This parameter is not supported for BMC Remedyforce.

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 a 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 a 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 start on a 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 a 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


Test Update Change Status workflow outputs

Output

Description

success status

Indicates whether the workflow finished successfully

status message

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

changes

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

Back to top

Test Update WorkInfo workflow

Use this workflow as a template for updating the workinfo journal field of a change record and as a method for testing that process.


Test 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

Specifies a description about the workinfo

BMC_AR_System: Test that summarizes the workinfo notes

HP_ServiceCenter: Summary text to store in the misc1 field

Yes

workinfo details

Specifies details about the workinfo

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

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

Yes

workinfo type

Specifies the type of workinfo

Example:

  • Development
  • General Information
  • Rejection Information
  • Test Results

No

locked

Specifies whether to keep the workinfo locked

Valid values: Yes, No

No

view access

Specifies the users who can view this workinfo

Example values: Internal, Public

No


Test Update WorkInfo workflow outputs

Output

Description

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

changes

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

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