About application templates and application object templates
This topic describes application templates and application object templates.
About application templates
Application templates are templates that are part of other applications, for example:
- Work order templates are used with the Work Order Management application, which is included with BMC Service Request Management.
- Change templates are used with the BMC Change Management application, which is included with BMC Remedy IT Service Management Suite.
- Incident templates are used with the BMC Incident Management application, which is included with BMC Remedy IT Service Management Suite.
Application templates are used to generate work orders, change requests, and incident requests that users frequently request. For example, work order templates are useful in any work order that follows well-defined methods for specific and repeated requirements — for example, Installs, Moves, Adds, and Changes (IMAC). When, for example, a user requests a service to upgrade office furnishings, BMC Service Request Management can create a work order with pre-defined company, categorizations, tasks, and assignments, if the appropriate work order template exists.
Application templates are sometimes called "application fulfillment templates" because you create them from the underlying applications that fulfill their tasks, such as BMC Work Order Management or BMC Change Management.
Recommendation
You can create as many application templates as needed, but the best practice is to create application templates for routine incidents, standard changes, or work orders that users frequently request.
About application object templates
An application object template (AOT) is a container object for an application template. The AOT definition includes the company, application, and application template.
You can associate application target data with an AOT, and then map that target data to variables defined in the PDT. Doing so allows you to pass data from a service request to the fulfillment application. For more information, see Using variables in a process definition template.
You must create an application template first, and then associate it with an AOT. Each AOT can include only one application template, and each application template can be included in only one AOT. When you specify an application template in an AOT, the application template is registered with the AOT. Only an unregistered application template can be added to an AOT.
Note
Quick launch and no-template AOTs do not use application templates. No-template AOTs create the fulfillment request without a fulfillment application template.
Comments
Log in or register to comment.