Merging Changes to Merge-able Attributes

Changes from Application Update	Changes from Customer	Result of the Merge on the Pivot Grid Object
Configurations from application development which require secondary merge. For example, adds a new dimension.	Configurations from customer which require secondary merge. For example, adds a new dimension which has a related action.	Customer’s configurations are preserved and the application fixes are also copied.

After the instance level compare of the merge-able objects:

1. The compare process highlights a newly added dimension.

2. If there are any merge-able attributes, the values are preserved in the target database.

3. Additional dimension in the target are reconciled with the source because the dimension is preserved. The additional dimension in the source is also preserved.

4. If there are any view related changes because of the additional dimensions, then those changes are also preserved.

5. The same merge and compare process is run for the related action object.

6. The related actions object in the merge reconciles the menu folders and layouts.

7. In the compare report visualization, user can identify the merge-able attribute values which are preserved in the target. The newly added dimension in the target are also preserved whereas the dimension in the source is displayed as a change to be added.

   This behavior also applies to the related actions object.

8. Customer selects to uptake the fixes and initiates a copy.

9. The merge framework is run to preserve the customer’s configuration.