Setting up miscellaneous metadata

Metadata, or data about data, is important in the context of BMC Release Process Management (RPM). Only the administrator of RPM and users with Coordinator or Deployer roles can manage metadata lists and settings for the application. To access the metadata, click the Environment tab and select Metadata.

Note

For basic information about metadata, see the Application metadata section in the Product overview topic.

This topic consists of the following sections:

To create agent types

Go to Environment > Metadata, click Manage Lists, and then click AgentTypes.
In the Edit List dialog box, in the Add List Item box, enter a name of a new agent type, and then click Add Item.
(Optional) To make an agent type value inactive, in the Active List items list, select the appropriate agent type, and then click Archive.
(Optional) To make an agent type value active, in the Inactive List items list, select the appropriate agent type, and then click Unarchive.
To save your changes, click Update List.

To create OS types

Go to Environment > Metadata, click Manage Lists, and then click OSTypes.
In the Edit List dialog box, in the Add List Item box, enter a name of a new OS type, and then click Add Item.
(Optional) To make an OS type value inactive, in the Active List items list, select the appropriate OS type, and then click Archive.
(Optional) To make an OS type value active, in the Inactive List items list, select the appropriate OS type, and then click Unarchive.
To save your changes, click Update List.

To manage automation errors

By adding list items for AutomationErrors in metadata, you can customize conditions under which automation scripts are marked as failed.

Go to Environment > Metadata, click Manage Lists, and then click AutomationErrors.
In the Edit List dialog box, in the Add List Item box, specify a word or phrase that will cause automation to be marked as failed if this word or phrase is found in the results of an automation script, and then click Add Item.
To find automation results, go to the Notes tab of the appropriate step, and then click Automation run full results.
Example
If you add STDERR to Active List items in AutomationErrors, and then STDERR will be found in the results of an automation script, this script will be marked as failed and the corresponding step and request will have the Problem status.
(Optional) To archive an active list item, in Active List items, select the required item, and then click Archive. To unarchive an inactive list item, in Inactive List items, select the required item, and then click Unarchive.
To save your changes, click Update List.

To create package contents

Package content refers to labeling requests. For example, you might enter items such as "Database modification", "Code change for calendar functionality", and others.

From Environment > Metadata, click Manage Package Contents.
On the right side of your screen, click Create Package Content.
In the Name box, enter the package content name, and then click Create.
Add as many package contents as you want.

To create phases

From Environment > Metadata, click Manage Phases.
On the right side of your screen, click Create Phase.
In the Name box, type a phase name.
In the Runtime Phase(s) box, type a runtime phase name.
To add more runtime phases, click more.
Click Create.
Create as many phases as you want.
(Optional) After you have created the phases, you can drag the icon on the left to change their order.

For more information about how to use the phases, see the General tab in Managing steps.

To create plan templates

Before creating a plan, you need to create a plan template, which contains stages. A stage is the process through which the application passes, for example, development, QA, and whatever stage that you want to define.

From Environment > Metadata, click Manage Plan Templates.
Click Create Plan Template on the right.
In the Name field, type a name.
From the Template Type list, select the template type.
Click Create.
To complete the plan template creation, add stages by clicking Add Stages.
Add as many stages as you require to define the template.
Note

While adding a stage, you can associate as many default request templates as you require.

To create procedures

A procedure is a group of steps.

From Environment > Metadata, click Manage Procedures.
On the right side of your screen, click Create Procedure.
In the Name box, enter a procedure name.
(Optional) In the Description box, enter a procedure description.
In the Applications list, select applications for which you want to use the procedure.
Click Create.
In the Steps section, add steps to the procedure.
You can reorder the steps in the procedure by clicking Reorder Steps.

To create processes

From Environment > Metadata, click Manage Processes.
On the right side of your screen, click Create Business Process.
In the Name box, enter a process name.
In the Label color list, select a hexadecimal code that represents the label color.
Using colors, you can identify processes easily.
In the Applications list, select applications for which you want to use the label.
Click Create.

To create release tags

A release tag is a categorization that you can apply to plans and requests.

Go to Environment > Metadata, and then click Manage Release Tags.
On the right side of the screen, click Create Release Tag.
In the Name field, type a name or a date.
Click Create. The created release tag can be selected in the Release tag list when creating a plan or a request.
Add as many release tags as required.
(Optional) To change the order of the release tags, drag the icon on the left.
To edit a release tag, in the Action column, click Edit.
To make a release tag inactive, in the Action column, click Archive.

To create release tag templates

You can use release tag templates to autoincrement versions of releases created in the BMC Release Lifecycle Management Requester UI (now called Release Process Management - Requester UI, 5.0.03.001 onward).

Go to Environment > Metadata, and then click Manage Release Tag Templates.
On the right side of the screen, click Create Release Tag Template.
In the Name box, type a name of the template.
In the Application list, select a required application.
Note

You can have only one active release tag template per application.
In the Version template box, type the template for the release version tag.
In the Autoincrement from box, type the number from which release version tag will be autoincremented.
Example

If you set Version template to 2.1.# and Autoincrement from to 0, then the first release that you create for the application with this template will have version 2.1.0. The next release version tags are autoincremented on each consequent release created for the application that uses this release tag template. In this example, the next release version tags will be: 2.1.1, 2.1.2, 2.1.3, and so on.
Click Create. The created release tag template automatically populates the Release # box when creating a release in the BMC Release Lifecycle Management Requester UI (now called Release Process Management - Requester UI, 5.0.03.001 onward).

To create work tasks

From Environment > Metadata, click Manage Work Tasks.
On the right side of your screen, click Add a new Work Task.
In the Name box, enter a work task name.
Click Create.

Create as many work tasks as required. You can drag the icon on the left to reorder the work tasks.

For more information about how to use the created work tasks, see the General tab in Managing steps.

To create version tags for components

You need to create newer and newer versions of your applications depending on your releases. You can create as many versions as required.

Go to Environment > Metadata, and then click Manage Version Tags.
On the right side of your screen, click Add new Version Tag.
Add the details in the fields.
The Version, Environment, and Application fields are required.
Click Create.
Note

If you select the Limit Versions to Metadata check box in Settings > General > Module - Requests, the component versions in the Version list of the step dialog box are limited to the versions created in metadata.

Page tree