AST_CI_Unavailability_Interface operations
The AST_CI_Unavailability_Interface web service enables you to create a CI unavailability record in BMC Asset Management.
Create_Unavailability
Use the Create_Unavailability operation to create an Unavailability record using the AST_CI_Unavailability_Interface web service. A CI unavailability record can be created only for a valid CI.
The following table lists the input fields and their mappings. These fields are also available on the AST:CI Unavailability Interface form.
Field | Value | Description |
|---|---|---|
Unavailability Class | Incident/Change | The type of unavailability. |
Unavailability Type | Scheduled/Unscheduled | Based on type, dates are required |
Description | <ci desc> or <inc desc> | Defaulted, but can be changed |
Scheduled Start Date |
| Required when type = scheduled |
Scheduled End Date |
| Required when type = scheduled |
Actual Start Date |
| - Required when type = unscheduled |
Actual End Date |
| - Required for closing the unavailability |
Recon ID |
| CI Recon ID. This ID will return the CI information |
Cross Reference ID | Incident or Change ID | Optional - ID of Incident / change to be related to |
Parent Cross Reference | N/A | N/A |
Bypass Permissions | Yes/No | default to yes. bypasses the permission check |
Bypass assignment check | Yes/No | Will bypass assignment check to allow record to be created |
Assigned Support Company |
| Assignment Structure. If it's not passed, the routing is done based on the "Assignment set from field" |
Assigned Support Org |
|
|
Assigneed Support Group |
|
|
Assignee |
| Optional with assignment structure |
Assignment Set From | Items | Choose where assignment is set from (Manually, Routing, CI, Incident) |