This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

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

Customization features

This section introduces the features that streamline the customization process and enable you to define, manage, and preserve customizations on BMC Remedy AR System objects. Using these features increases the likelihood that your customizations are preserved when an application or server is upgraded.

  • Overlays — An overlay is a copy of a BMC Remedy AR System server object that is used in place of the origin object. All out-of-the-box BMC Remedy AR System application and server objects in release 7.6.03 or earlier and objects created in Base Development mode of BMC Remedy Developer Studio are origin objects.

    The overlays feature enables you to customize applications with a minimal chance of conflicts with future versions of applications. The feature tracks customizations and preserves changes to application objects even if they are modified during an application upgrade.

    To ensure that customizations are not lost during upgrades, you modify the overlay, not the origin object. During upgrades, the overlay is preserved, if the upgrade program modifies the origin object definition. After an upgrade, BMC Remedy AR System server continues to use the overlay in place of the origin object.

    See Introduction to Overlays.
  • View overlays — A view overlay allows you to customize the display properties of the fields in a view. You can modify the display properties of existing fields in a view or add new fields to a view. You can choose to effect these changes to a single or multiple views. Any change to the base objects is applied to objects in the view overlay while preserving customizations.

    See Introduction to view overlays.
  • Custom objects — A custom object is an object created by a BMC Remedy AR System user. Objects created in Best Practice Customization mode of BMC Remedy Developer Studio are considered custom objects. Upgrades do not modify or destroy custom objects.

    See Development modes.

    The following figure shows how unmodified objects, overlays, and custom objects are used in place of the original objects for a customized application.

    Difference between a base application and a customized application

These features protect your business investment in customizations by providing the following benefits:

  • Enforcing best practice development in BMC Remedy Developer Studio.
  • Preserving customizations during upgrades of BMC Remedy AR System servers, components, and applications.
  • Enabling you to find all your customizations quickly and easily.

In addition to these new features, the Best Practice Conversion utility enables you to convert pre-7.6.04 customizations into overlays and custom objects. See Development modes.

Use the following information to understand custom objects, Overlays and their limitations, and guidelines for overlaying forms and fields.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.