This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

BMC Remedy Developer Studio enhancements in 9.0.00

This topic provides information about the following BMC Remedy Developer Studio enhancements in this release.

Reconciling AR customizations

BMC Remedy Developer Studio now allows you to reconcile your changes by comparing existing definition, overlay definition, and new definition of the objects.

After upgrading your BMC Remedy Action Request (AR) System Staging server, you can reconcile your overlays from the reference server so that your customizations are not lost and you can use the latest features that BMC provides with every new release.

You can copy and merge the changes from the new definition to your previous overlay definition. BMC Remedy Developer Studio allows you compare your old base definition with the new definition and the overlay definition. Based on the comparison results, you can copy the changes from your new definition to the overlay definition.


Only the Overwrite type of overlay is used for comparison.

For more information about reconciling AR customizations, see  Reconcilizing AR customizations in BMC Remedy ITSM 9.0 Deployment space and Comparing and reconciling objects using objects list.

Associations object

Before this release, two forms were associated by configuring individual workflows in BMC Remedy Developer Studio. For example, if you wanted to archive the audit form entries when any form is archived, you had to manually create a workflow to archive the audit form along with that form.

Starting this release, BMC Remedy Developer Studio now provides a new association object. An association is a BMC Action Request (AR) System server object that describes relationships between entries in BMC Remedy AR System forms. These relationships enable you to support referential integrity, cascade deletes, and archiving related entries.

An association describes a relation between entries in two or more forms. The relationship can have three cardinality options: One to One, One to Many, and Many to Many.  For One to One and One to Many relationships, an association between two forms is defined by specifying one form as primary and another form as secondary. For these relationships, the primary form can have only one entry in the relationship. For Many to Many relationships, there are no primary and secondary forms.

For more information about associations, see Associations overview.

Archiving related forms using associations

Starting with this release, you can select specific forms that should be archived along with the main form based on the associations. You have the option to select associations that ensure related forms are also archived with the main form in BMC Remedy Developer Studio. For more information, see Defining associations to follow.

Restricting developer studio modes

Starting with this release, you can use the Dev-Studio-Development-Mode configuration setting to enable the Base Development mode, Best Practice mode, or both in BMC Remedy Developer Studio. When you install BMC Remedy AR System, you can choose to work in the Best Practice mode, Base Development mode, or both modes. To configure modes, you must modify the Dev-Studio-Development-Mode configuration settings.

For more information, see:

Adding an alias for the server name

Starting with this release, you can add an alias when you add a new server in BMC Remedy Developer Studio. A new parameter named Server Alias is in the Edit Server List so that when you have multiple servers, you can identify them using alias, such as Dev Server and QA Server. For information about configuration, Starting and logging on to BMC Remedy Developer Studio.

Was this page helpful? Yes No Submitting... Thank you