Using Workspaces for Seed Data

Workspaces are also used for certain types of seed data. This feature enables developers to have their work neatly isolated. It also maintains the changes that are set at the design time and the runtime as a single package. This feature requires no downtime of the seed data to deploy.

Using Workspaces for the seed data, note that:

• By default, Oracle Siebel delivers seed data Workspace-enabled for LOVs and you cannot disable those Workspaces on seed data.

• The concept of Workspace for seed is similar to the concept of Workspace for metadata. The only difference is metadata changes are specific to the user whereas seed data changes apply to all users under the nearest integration branch.

• Modifying the seed data occurs in the closest integration branch; hence, all users under the same integration branch can see each other’s changes immediately.

• Seed data is copied automatically when a user creates a new integration branch, so there is a separate copy of the seed data for every integration branch, including the MAIN branch.

• Modifying seed data does not create the Workspace version. You must always modify metadata to create the Workspace versions.

• Workspace delivery from the user-to-integration branch carries only metadata modifications because seed data modification exists in the integration branch.

  However, Workspace delivery from Integration-to-Integration Workspace carries both seed data and metadata changes.

• You can access Siebel Tools or the thick client using the \editseeddata option to create a corporate record and then start using the Workspace.

  For more information on how to use the \editseeddata option, see Siebel Developer's Reference Guide.

• You cannot perform the Revert process for the changes in the seed data.

For more information on how to use database utilities to migrate metadata and seed data, see Siebel Database Upgrade Guide.

To change seed data

1. Create a user Workspace under the integration branch.

   For more information on how to create new Workspaces, see Creating New Workspaces.

2. Modify the seed data and metadata as needed.

   The modification of seed data in the user Workspace causes the modification in the nearest integration branch.

3. Perform the Checkpoint process on the Workspace.

   For more information on how to perform the Checkpoint process, see Performing the Checkpoint Version Process.

4. Submit the Workspace for delivery.

   For more information on how to submit the Workspaces for delivery, see Submitting Workspaces for Delivery.

5. Deliver the Workspace to the nearest integration branch.

   For more information on how to deliver Workspaces, see Delivering Workspaces.

6. Deliver the Integration Workspace to the MAIN branch.

   For more information on how to deliver the Integration Workspace to the MAIN branch, see Delivering Workspaces.

7. If there is non-trivial change or conflict in the seed data, perform the following steps to rebase and deliver the Workspace:

   1. Rebase the Workspace.

      For more information on how to perform the Rebase process, see Rebasing Workspaces.

   2. Select the original value to override the current Workspace value; otherwise, use the default new value.

      For more information on how to fix the conflict errors and apply resolutions, see Detecting Conflicts in Workspaces and Applying Resolutions.

   3. After the Rebase process is completed, deliver the Workspace again.

      For more information on how to deliver the Workspace, see Delivering Workspaces.

Example: Inserting Seed Data Records

1. Create the Integration Workspace called INT_CRM2017 under the MAIN Workspace.

   For more information on how to create new Workspaces, see Creating New Workspaces.

2. Create another Workspace called EXAMPLE_WS under the INT_CRM2017 Workspace.

3. Optionally, modify the metadata record.

4. From the menu bar in the Siebel Tools window, choose the Screens menu, System Administration, and then select the List of Values menu item.

5. Change the Type value to CUT_ACCOUNT_TYPE.

6. Change the display name from BILLING to BILLINGNEW.

   The new display name BILLINGNEW is available in the INT_CRM2017 Workspace.

7. Perform the Deliver process to deliver the EXAMPLE_WS Workspace to the INT_CRM2017 Workspace.

   For more information on how to deliver Workspaces, see Delivering Workspaces.

8. Perform the Deliver process again to deliver the INT_CRM2017 Workspace to the MAIN Workspace.

9. Open the MAIN Workspace.

10. Navigate to the Account List view and select the Account Class drop-down list.

    The BILLINGNEW value is listed in the Account Class drop-down list. If the BILLINGNEW value is not listed, you must clear the cache by navigating to System Administration\Data\List of Values and click the Clearcache button.

11. Check to ensure that both INT_CRM2017 and MAIN Workspaces now list the BILLINGNEW value.