What Happens During a Repository Merge?
The repository merge process identifies differences between the repository in your old release (Prior Customer Repository) and the repository in the new release (New Siebel Repository). The merge process then merges these differences into the New Customer Repository. The merge process searches for the following types of objects in the Prior Customer Repository: customer-created, customer-deleted, and customer-modified.
Customer-Created Objects
Customer-created objects are high-level (or first-level) objects, such as screens, applets, and business components, that you have created in the Prior Customer Repository. If an object is present in the Prior Customer Repository but not in the Prior Siebel Repository, then it is customer-created. The merge process copies customer-created objects intact to the New Customer Repository.
Customer-Deleted Objects
Customer-deleted objects are high-level objects you have deleted in the Prior Customer Repository. If an object is absent in the Prior Customer Repository but present in the Prior Siebel Repository, then it is customer-deleted.
If you delete a high-level object in the Prior Customer Repository and it is present in the New Customer Repository, then the merge process does not delete the object from the New Customer Repository. After the merge, you must review these objects and remove them as desired.
If you delete a high-level object from the Prior Customer Repository, and it is obsolete (inactive) in the New Customer Repository, then the object will be present and inactive in the New Customer Repository.
Customer-Modified Objects
A customer-modified object has the following characteristics:
It is a high-level object, such as screen, applet, or business component.
The object exists in the Prior Siebel Repository and the Prior Customer Repository. (The object is not customer-created or customer-deleted.)
The properties of the object in the Prior Customer Repository and Prior Siebel Repository are not the same. (You have modified the object.)
If the object properties are also different between the Prior Siebel Repository and New Siebel Repository, then the object has changed in the new release, and a conflict exists. The merge process logs the conflict and resolves it. After the merge, you must review how these conflicts were resolved and change the resolutions as desired.
For customer-modified objects where no conflict exists, the merge process copies the modifications to the object to the New Customer Repository.
If you modify a high-level object by deleting any of its child objects, then the merge process does not delete these child objects in the New Customer Repository. After the merge, you must review child objects and remove them as desired.
Control
List Column
Page Tab
Chart
Applet Web Template Item
View Web Template Item
For example, if you delete a button from Applet-A in the Prior Customer Repository. The merge process deletes this button from Applet-A in the New Customer Repository.
The following table shows how a regular merge handles both customer-modified and customer-created objects. The columns list the status of a repository object:
Standard. The object appears in the Prior Standard Repository, and in the New Siebel Repository, and is not customer-modified.
Deleted. You have deleted the object from the Prior Customer Repository (customer-deleted).
Customized. You have modified the object in the Prior Customer Repository (customer-modified).
Revised. The object has changed in the new release (New Siebel Repository).
New. You have created the object in the Prior Customer Repository (customer-created), or the object is new in the new release (New Siebel Repository).
Inactive. The object is present in the New Siebel Repository and New Customer Repository but is inactive and not used in the new release. The object is obsolete.
The first three columns list the status of the object in the three repositories that the merge process compares during the merge. The last column, Merged New Customer Repository, lists the status of all high-level repository object types after the repository merge is complete and the postmerge utilities have run.
| Prior Standard Repository (PSR) | Prior Customer Repository (PCR) | New Siebel Repository (NSR) | Merged New Customer Repository |
|---|---|---|---|
Standard |
Standard |
Standard |
Standard |
Standard |
Standard |
Revised |
Revised |
Standard |
Standard |
Standard, or Inactive |
Standard, or Inactive |
Standard |
Customized |
Customized |
Customized |
Standard |
Customized |
Customized, or Inactive |
Customized, or Inactive |
Standard |
Customized |
Revised (conflict) |
Revised (conflict) |
Not applicable |
New |
New |
New |
Not applicable |
Not applicable |
New |
New |
Standard |
Deleted |
Standard | Standard |
Standard |
Deleted |
Not applicable |
Not applicable |
Standard |
Deleted |
Not applicable |
Not applicable |