Workspace Enabled Admin Data

The Siebel application enables certain data types (called Admin Data) to participate in Workspace life cycles just as Repository objects such as Applets and Business Components do.

You create/update/delete the records in the end user application and deliver, rebase, migrate the data exactly as you would with Web Tools.

The current Admin Data types that are available to participate in Workspaces are:

• LOVs (enabled by default)

• Predefined Queries

• Data Maps

• EAI Data Maps

• Responsibilities (and their relationship to Views)

Enabling Admin Data Types for Workspaces

You must enable each type of Admin Data that you wish to use in Workspaces. LOVs are automatically enabled, but the other types of Admin Data require a that the schema and underlying database be updated to support Workspaces. All types except LOVs are optional. Enabling Admin Data types is done in Web Tools by a user with the Workspace Administrator Responsibility.

To Enable Admin Data Types

To Enable Admin Data Types in Web Tools follow the steps given below:

1. Go to Tools→ Workspace Enable Admin Data.

2. In the Admin Data Types Applet, you can select the type of Admin Data you wish to enable. You can select more than one type at a time.

3. When you select an Admin Data Type, the tables that will be affected show in the Affected Tables Applet. This informs you of the Tables that will change.

4. The Workspace Enabled check box shows if a particular Admin Data Type has already been enabled. List Of Value will automatically be checked because PostInstallDBSetup will already have enabled it. The check box is read only.

5. Once you have chosen all the Admin Data Types you want to enable you have two options.

   Note: These actions cannot be undone without restoring the database.

   1. Apply Schema – This button applies the schema and physical database changes to the affected tables. When you click this button, the database parameters dialog will display. Fill in the data and click OK to start the process. After a few minutes the progress bar will disappear, and the data type will be enabled.

   2. Generate Schema– This button applies the schema changes to the affected tables so that the correct SQL can be generated for application to the physical database. Use this option if someone other than the one using Web Tools to generate the Schema changes will apply them to the database. For example, sometimes only the Database Administrator (DBA) is allowed to update the physical database. In that case, one person generates the Schema changes and the DDL files by clicking the Generate Schema button and the DBA applies the SQL files to the physical database.

   3. Update Repository– Use this button only if you used the Generate Schema button and a DBA has applied the changes to the physical database. Once those changes are complete, come back to Web Tools to finish the process by clicking this button.

Once these steps are complete, the Admin Data Types that you have enabled are ready to use in the end user application such as Call center.

Note: Once you enable an Admin Data type to participate in Workspaces, you cannot undo this action without restoring your development database to its state before you enabled the Admin Data type.

Note: In your design Repository, while in the process of Workspace enabling any Admin Data type (the process is not complete) avoid changing any of the Admin Data types. For example, you have chosen the EAI Data Map Admin Data Type and have clicked the Generate Schema button. The database administrator has not yet applied the SQL to the physical database so the Workspace Enablement of the EAI Data Map type is incomplete. During this time, do not change records in the EAI Data Map Admin Data type.

Similarly, while the IRR migration that will enable Workspaces on your Target Repository is in progress, do not make changes to the Admin Data types that will be enabled once the IRR completes.