This topic provides the following information about overlays:
- Behavior of overlays
- Granular overlays
- View overlays
- Field overlays
- Overlayable and non-overlayable objects
- Properties shared between overlays and origin objects
- Overlay object names
- Overlay limitations
An overlay is a copy of a BMC Remedy AR System server structure or workflow object that is used in place of the origin object.
An origin object for which an overlay has been created is an overlaid object. Until you modify the overlay, its appearance and functionality are identical to that of the overlaid object.
BMC Atrium CMDB does not support overlay functionality.
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
Overlays are separated into granular components, which allow you to add to or overwrite some aspects of an object and inherit other aspects.
When aspects are inherited, changes made to the origin object are also inherited in the overlay. For example, when you upgrade, any inherited aspects that are updated in the new version of the product are also updated in your overlay.
Where aspects are added (such as forms added to a filter, or permissions added to a form), the changes made to the origin object are also inherited in the overlay.