Managing request templates

The main unit of deployment in BMC Release Process Management (BRPM) is a request. You can save time by creating request templates from existing requests. You can use a new template for as many additional requests as needed.

A request template can either be global or local. A global template is visible to all the users in the system. A local template is visible only to the users who have access to the application on which the template was created. 

You can mark a template global either while creating the template or after creating it. You can also mark the templates created in previous versions as global. To make a template available to other users, its state must be other than Draft.

When creating a request from a new as well as an existing template (whether global or not), you can select the application to which you want to assign the request. Applications are available for selection based on the access permissions.

Creating a request template

1. Click the Requests tab.

2. In the requests list, click the appropriate request from which you want to create a template.

   Note

   When you create a template from a request with scheduled steps, the Set to Start at Scheduled Time check box and step start and end time are cleared in the template.

3. On the right pane, click Create Template.
4. In the Create New Template dialog box, in the Name of Template box, enter a name for the template.
5. (Optional) Toggle the Global Template option if you want to make this template globally accessible.
   You can make the template global even after creating it.
6. Click Create Template.
   The new template appears on the Request Templates page.
   
   
   This figure shows various sample templates, as follows:
   
   • e-commerce Deployment template: Icon  indicates that it is a global template. All the users can see this template and create requests from the template.
   • Remedy Deployment template: A template with only a link indicates that the logged-in user has permission to view the template. Only the users who have access to the application can create requests from such templates.
   • Request_ToDeploy template: A template with Icon  and without a link indicates that the logged in user does not have permission to view the template. However, the user can create requests from this template.
   • Continue execution on failure template: A request template with the  icon indicates that the Continue Execution On Failure function is activated for this template. Users can modify the step execution condition for the individual steps as required.
     
     The Continue Execution On Failure flag will be activated by default, for all requests which are created using this template. You can also deactivate this flag while creating requests using this template.
7. To change the state of the request template so that it becomes available for other users for creating requests, perform the following steps:
   1. Go to Environment > Metadata > Manage Request Templates.

   2. In the Actions column, change the status for the request template to a state other than Draft by clicking the appropriate state.

      For more information about the status of objects and available states for request templates, see Using-status-of-objects.

Making a template global or local after creating the template

A global template is available to other users only if its state is other than Draft.

1. Go to Environment > Metadata > Manage Request Templates.
2. Click the request template that you want to make global or local.
3. In the right pane, toggle the Global Template option.