Packaging and deploying a custom application object
Perform the following steps to integrate a custom application with an application object and deploy the custom application to the production environment:
- Register the custom application object
- Add workflows to stage data
- Add validation workflow
- Add workflow to promote the custom application to the production environment
- Register validation errors
Registering the custom application object
In order to integrate the custom application with an application object, you must first register your custom application on the AR System Application Object:Control form.
When you register your custom application on the AR System Application Object:Control form, you must identify the secondary forms where you are going to export the data. Enter the following information on the AR System Application Object:Control form:
- In the Application Name field, enter the name of the custom application.
- In the Type field, enter the name of the object that identifies the application.
For example, if the Application Name is RDCSampleApplicaton, the Type can be Sample Application Object.
The Application Name and Type are displayed on the AR System Deployment Management form when you create a package.
- In the Production Form Name field, enter the primary form name.
For example, RDA:SampleApplicationObject_Primary.
- In the Staging Form Name field, enter the name of the first staging form.
For example, RDA:SampleApplicationObject_Primary_Staging.
- In the Unique Identifier field, enter the Field ID of a field that uniquely identifies records on the primary or secondary form.
For example, Instance ID
- In the Mark Record for Delete field, select Never Delete Records.
- In the Sequence field, enter a number (starting from 1) to set the sequence for the main form so that the child forms follow the dependency.
For example, set 1 for the primary form and follow the numbering for the secondary forms.
- In the Primary Form field, select Yes to identify the primary form.
- In the Menu Name field, enter menu name of the menu that is created in the primary form.
- In the Record Access field, select appropriate permission for the custom application.
For example, select Public if you want to allow everyone to access the custom application while creating a deployable package.
- Click Save.
Your custom application is now registered as an application object. After you register your custom application, use BMC Remedy Developer Studio and create an active link on the RDA:DeploymentDataDetails form. This active link sets the Unique Identifier field.
See the following example:
You can now add workflows for your custom application.
Adding workflow to stage data
After the application object is registered, you can move data from the primary form to the corresponding staging form so that you can perform validations on the staging form before promoting the custom application to the production environment.
Create a filter on the primary form by using BMC Remedy Developer Studio. This filter is used when you build the package from the AR System Deployment Management console. One filter is sufficient if you use only the primary form. However, if you want to export data from dependent secondary forms, you must create a filter for each secondary form.
See the following examples:
|StageForExport filter on the primary form|
|StageForExport filter on the secondary form|
Data in the custom application is on the staging form and is ready to export.
Adding validation workflow
After the filter is created, you can optionally add validation workflows to validate your custom application. Prior to importing the custom application to the production environment, BMC recommends adding the validation workflows on the staging form.
- In BMC Remedy Developer Studio, create a validation filter on the primary staging form and optionally on the secondary stagging form.
- Create a filter to handle errors during validation.
This filter sets an error message and error flag on the staging form. See the below example:
The custom application is validated and is available to promote across environments.
Adding workflows to promote the custom application
After you validate the custom application, you can write workflows to promote the custom application to the production environment.
Use BMC Remedy Developer Studio to create promotion filter on the primary staging and secondary staging forms.
Registering validation errors
After you add a workflow to promote your custom application to the production environment, you can set error filters to show validation or promotion errors on the AR System Deployment Management console.
See the following examples:
A filter on the RDA:SampleApplicationObject_Primary_Staging form
|A filter on the RDA:SampleApplicationObject_Primary_Staging form shows|
validation errors (if any).
Where to go from here