One Time Only - Set Up A DB Process To Copy Scripts

You need a "copy scripts" database process (DB process) configured in the target database (e.g.,, your implementation's database). This DB process must have the following instructions:

A primary instruction for the script maintenance object (MO)
A child instruction for each MO referenced as a foreign key on a script (i.e., algorithm, navigation option, and icon reference)

The demonstration database contains such a DB process; it's called CI_COPSC. In order to copy scripts from the demonstration database, you must first copy this DB process from the demonstration database.

CAUTION:

The remainder of this section is confusing as it describes a DB process that copies another DB process. Fortunately, you will only have to do the following once. This is because after you have a "copy scripts" DB process in your target database, you can use it repeatedly to copy scripts from the demonstration database.

You can copy the CI_COPSC DB process from the demonstration database by submitting the CL-COPDB background process in your target database. When you submit this process, you must supply it with an environment reference that points to the demonstration database. If you don't have an environment reference configured in your target database that references the demonstration database, you must have your technical staff execute a registration script that sets up this environment reference. Refer to Registering ConfigLab Environments for more information.

CL-COPDB is initially delivered ready to copy every DB process that is prefixed with CI_ from the source database (there are numerous sample DB processes in the demonstration database and this process copies them all). If you only want to copy the CI_COPSC DB process, add a table rule to the primary instruction of the CL-COPDB database process to only copy the CI_COPSC DB process. The remainder of this section assumes you have added this table rule.

When the CL-COPDB process runs, it highlights differences between the "copy scripts" DB process in your source database and the target database. The first time you run this process, it creates a root object in the target database to indicate the CI_COPSC DB process will be added to your target database. You can use the Difference Query to review these root objects and approve or reject them.

Note: Automatic approval. When you submit CL-COPDB, you can indicate that all root objects should be marked as approved (thus saving yourself the step of manually approving them using Difference Query).

After you've approved the root object(s), submit the CL-APPCH batch process to change your target database. You must supply the CL-APPCH process with two parameters:

The DB Process used to create the root objects ( CL-COPDB)
The environment reference that identifies the source database (e.g., the demonstration database)