Promoting configurations and customizations across environments

You can use Deployment Application to promote an application object across development, QA, and production environments. You can promote application objects such as Incident templates, Task templates, Change templates, and Service Level Targets (SVTs) by adding them to a deployment package.

Also, you can integrate any custom application with an application object and promote the custom application object across environments. For more information about integrating a custom application, see Packaging-and-deploying-a-custom-application.

Important

While staging and promoting the data for application objects on the destination server, the system updates the existing data or creates new data if the data is not found.
CIs must be available on both, the source and the destination servers.

User permissions to promote an application object

You must have the following set of permissions to promote an application object:

Role	Application	Permissions
Package Creator	Incident template	Incident Configuration
	Change template	Change Configuration or Change Master
	Work order	Work Order Configuration
	Task template or Task Group template	One of the following permissions: Task Application Configuration Task User Task Process Configuration
	Service Targets	One of the following permissions: SLM Config SLM Manager

A Package Deployer can deploy packages by using these application objects. For more information about roles and permissions, see Remedy Deployment Application roles and permissions in the AR System online documentation.

List of forms

The following table lists the application objects and the related forms that are migrated by using Deployment Application:

Application object	Related forms	Considerations
Task templates	TMS:TaskTemplate TMS:VariableMapping TMS:VariableTemplate	When an application object contains a Task Template or a Task Group Template, the package includes the Task or Task Group template associations.
Task group templates	TMS:TaskTemplate TMS:VariableMapping TMS:VariableTemplate TMS:TaskGroupTemplate TMS:AssociationTemplate TMS:FlowTemplate
Incident templates	HPD: Template HPD:Template Associations HPD:TemplateSPGAssoc	When an application object contains an Incident template, the package includes the Support Group and the CI associations of the Incident template.
Change templates	CHG:Template CHG:Template Associations CHG:TemplateSPGAssoc	When an application object contains a Change template, the package includes the Support Group and the CI associations of the Change template.
Work Order templates	WOI:Template SRD:STAGE:WOT_Template	When an application object contains a Work Order template, the package includes the Task or Task Group template and the CI associations.
Service Targets	SLM:ServiceTarget

To migrate application objects

Prepare the destination server by making sure that the following items are present on the destination server before importing the application objects. These items are essential for the application objects to function as expected.
- Foundation data—All the foundation data must be identical in the source and destination servers.
- Customizations—(If applicable) Reconcile all the customizations before importing the application objects.
- Configuration data—The configuration data populates fulfilment configuration forms that are used in the Application Administration Console. This data must be migrated.
On the source server, use BMC Remedy Deployment Application and create a package that includes the application objects to be deployed to the destination server.
On the destination server, use BMC Remedy Deployment Application to import and deploy the package.

For detailed instructions about migrating the application objects by using Deployment Application, see Defining a package in the AR System online documentation.

Promoting configurations and customizations across environments

User permissions to promote an application object

List of forms

To migrate application objects

On this page