Parameters for registering application templates with AOTs
After defining application object templates (AOTs), you must register the application templates with your AOTs. You can modify these values as needed for your own environment.
| AOT | Tab or field | Value | Function |
| Incident Management AOT | Application Object Template fields | Enter required information to complete the AOT (for example, AOT_IM). | Receives data input (Categorization Tier 1) from service request |
| App Registry Name | BMC Incident Management | ||
| Add Target Data |
|
||
| Change Management AOT | Application Object Template fields | Enter required information to complete the AOT (for example, AOT_CM). | Receives data input (Categorization Tier 1) from incident |
| App Registry Name | BMC Change Management | ||
| Add Target Data |
|
||
| Work Order AOT 1 | Application Object Template fields | Enter required information to complete the AOT (for example, AOT_WO1). | Receives data input (Categorization Tier 1) from change request and places it in the Description field Note: Output variable is not required in this scenario. |
| App Registry Name | Work Order Application | ||
| Add Target Data | Summary (Exposed) | ||
| Work Order AOT 2 | Header | Enter required information to complete the AOT (for example, AOT_WO2). | Receives data input (Categorization Tier 1) from change request and places it in the Detailed Description field Note: Output variable is not required in this scenario. |
| App Registry Name | Work Order Application | ||
| Add Target Data | Detailed Description (Exposed) |
Comments
Log in or register to comment.