Successful integration of partner systems requires deep knowledge of the ITSM Change Management process. A complete description of the ITSM module Change Management is given by the BMC Software product documentation.
 This chapter provides information, necessary for partners to successfully implement the E-Bonding Runbook interface.

Change Status

The section describes the usage of the ITSM Change Management Status values through E-Bonding Runbook operations.
Status Draft
 With the operations "chgCreateTicket" or "chgCreateTicketByTemplate", the ticket status must be set Draft (or 0) always.
Status Request for Authorization
 If a partner system changes the ticket status to Request for Authorization (operation chgUpdateTicket), then a value for the ChangeCoordinator LoginID and the ChangeCoordinator Login ID is required.
Status Planning in Progress
 If a partner system changes the ticket status to Planning in Progress (operation chgUpdateTicket), then values for the fields Scheduled Start Date and Scheduled End Date are required.
Status Scheduled for Review
 No additional requirements.
Status Scheduled for Approval
 No additional requirements.
Status Scheduled
 If a partner system changes the ticket status to Scheduled (operation chgUpdateTicket), then values for the fields Scheduled Start Date and Scheduled End Date are required.
Status Pending
 If a partner system changes the ticket status to Pending (operation chgUpdateTicket), then a value for the Status Reason field is required.
Status Implementation in Progress
 No additional requirements.
Status Completed
 If a partner system changes the ticket status to Resolved (operation chgUpdateTicket), then a value for the Status Reason and Resolution field is required.
 From this point of time on, no tasks can be sent to ITSM anymore.
 If the partner systems try to set this status with currently open tasks attached to the Change Request, then the operation can result in an error based on the ITSM application settings for the Change Management module.
Status Closed
 ITSM closes resolved tickets automatically after a configured amount of days. Partner systems can change the status to Closed by usage of the operation chgUpdateTicket.
Status Rejected
 This status change is reserved for Change Request approvers and shouldn't be used by E-Bonding Runbook partner systems.
Status Cancelled
 Partner systems can change the status to Cancelled by usage of the operation chgUpdateTicket.
The table provides information regarding status values and change phases:

Phase	Initiate	Review and Authorize	Plan and Schedule			Implement		Closed
Status	Draft	Request for Change	Planning in Progress	Scheduled for Review	Scheduled for Approval	Scheduled	ImplementationinProgress	Completed	Closed
Status Reason	<none>	<none>	<none>	<none>	<none>	<none>	<none>	Required	Optional

Pending	Cancelled	Rejected
Required	Optional	Optional

Figure 64 Change Status and Phases

Change Tasks

Partner system can use the E-Bonding Runbook operations chgCreateTask and chgCreateTaskByTemplate to create new Tasks in ITSM.
 Interface partner must implement this ITSM rules:

• Transmitted Tasks are always created in sequence
• The sequence number is always calculated as the highest number and new Tasks are added at the end of the Task list
• Tasks can only be created in the Change ticket status New, Assigned, Pending or Work in Progress