Check out the 8.0 online documentation where we had videos for granular overlay and it will give you concept about your upgrade

https://docs.bmc.com/docs/display/team/AR%2BSystem%2Bdraft%2Bdocumentation

Regards/Vaibhav

Hi Jennifer,

Please find the below links;

https://docs.bmc.com/docs/display/public/ars8000/Development+modes

https://docs.bmc.com/docs/display/public/ars8000/Introduction+to+Overlays

https://docs.bmc.com/docs/display/public/ars81/Granular+overlays

https://docs.bmc.com/docs/display/public/ars81/Creating+overlays+with+the+Best+Practice+Conversion+Utility

You need to use BPCU for moving objects from old version to new.

Hope this helps.

Hello All,

Could some one help me with whats the difference between Best Practice and Base Development Mode?

Please refer: https://communities.bmc.com/communities/message/274509#274509

Yes, if you create or modify any object in base development mode, all

the cahnges will be lost during the upgrade. BMC recommends to use

best practice customization for creating/modifying objects.

yes, Installer will replace old definitions by new one. To avoid this use BPCU and create overlays of these objects.

So when i import those forms by switching to base development mode and go for further ARS update in future will my forms imported in base dev mode will it be lost?

From what you have described I understand these are completely custom forms in ARS 6.3. If custom, these forms will not be lost during upgrade.

Regarding your query with respect to base vs overlay: (in short)

During upgrade only OOTB BMC forms will be overwritten with new versions (that too if they are part of the release or patch). Also understand that the base copy of form will be overwritten the overlays will always stay on top of the base copy of form. So what the user would ultimately see is the overlaid version of form.

Hope this helps.

In its default Best Practice Customization mode, BMC Remedy Developer Studio provides the flexibility required to customize BMC Remedy AR System by using overlays and custom objects. With overlays, you can customize out-of-the-box BMC Remedy AR System server objects. Overlays ensure that the customizations are not lost when a BMC Remedy AR System application or server is upgraded. Overlays and custom objects protect any new functionality in your BMC Remedy AR System enabled application.

AR System objects now use granular overlays. Using granular overlays, you can now add to, overwrite, or inherit

different parts of an object in an overlay. You can modify some characteristics of an object while inheriting other

parts. You can also add to aspects of an object while inheriting properties from the origin object. If parts of an object are inherited or added to, those updates to the origin object are made to the overlay. Using granular overlays minimizes the need to reconcile overlays after applying upgrades or patches.

Customizations made to the base objects in Developer Studio base development mode are not

preserved through upgrades.

If you are upgrading from pre-7.6.04 versions of BMC Remedy AR System to version 8.1, first

take a backup of the customizations (system forms of Approval Server, Assignment Engine,

Email Engine, and Flashboards), upgrade to version 8.1, and then manually add the

customizations for version 8.1.

Regards,

Jayesh

Hi Jennifer,

Best Practice Customization mode is used when we  create overlay of the object.

In this what customization you will do that will be saved as overlay.It will keep exsting objects as it is.

Base Development mode is used to develop  objects as a base objects.You dont need to create overlay for that.

Granular Overlays means you can choose subcomponents of an object and apply different overlay types to them. Granular overlays allow you to modify only some aspects of an origin object and inherit other aspects from the origin object.

Using granular overlays minimizes how much you must reconcile after you upgrade or apply patch.

we have three types of granular overlay.

1) Additive Overlay OR Extensions Overlay:

It is used when you would like to add customized information to what is already available in the origin object. If the origin object changes during an upgrade the additions are appended to whatever is in the new origin definition.

2)Overwrite overlay:

The entire overlaid object is used and the origin object is ignored. This is the same behavior as earlier versions – in non-granular overlays.  For example, removing permissions from an object is a case where an overwrite overlay would be appropriate.

3)No Overlay OR Inheritance Overlay:

Though its name is ‘No Overlay’, it is still technically an overlay. This type of overlay is the default for all types of objects and their parts. If you do not touch the out of the box object or its part, it would take inherit its properties during upgrade.  Inheritance overlays are used for the object properties which should be inherited from the origin object with no changes.

Regards,

Kalyani Shaha