Kbase 15300: Import controls Orphans, objects as EXC excluded Roundtable
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Import controls Orphans, objects as EXC excluded Roundtable
Problem:
========
Import Control has Orphans or objects showing up as EXC (excluded).
Explanation:
============
Import control is the process of assigning a group of objects that was
released in the source workspace to the current workspace. After the
BUILD step and before the IMPORT step, the Import Control Table
should be reviewed. During this review look for 2 cases: Objects with
the Orphan flag: YES, and Status: EXC:
* Objects with the orphan status means that two object versions were
created in two workspaces from the same parent object.
* Objects with the EXC status can come from a number of situations.
The system defaults the Status to EXC when the object being
imported has a different Pmodule than the object that already exist
in the workspace. The system also defaults the status to EXC when
a deleted Schema object is being imported.
Examples:
========
Orphan:
1. MENU.P - 1.0.0 exists in the DEVEL workspace and the TEST
workspace.
2. A new version of MENU.P is created in DEVEL; MENU.P - 2.0.0.
3. A new version of MENU.P is created in TEST; MENU.P - 1.1.0.
4. MENU.P - 1.1.0 and MENU.P - 2.0.0 are both orphans, because
changes exist in each that are not necessarily in the other.
Changing Pmodule:
1. An custom object MENU.P that belongs to the CUSTOM product
module exists in the CUSTOM workspace.
2. A change has been made to the base application and those changes
are being imported into the CUSTOM worksapce.
3. If MENU.P has changed and been released, it will appear on the
Import Control Table.
4. Since the CUSTOM workspace contains that object belonging to the
CUSTOM product module, and the object being imported belongs to
the BASE product module, the default Status will be EXC.
Deleted Schema Objects:
If a PFILE object exists in the DEVEL and TEST workspace, then
a Field that belongs to that PFILE is deleted from the file and the
DEVEL workspace. When that deletion is imported, the object shows
up with a Status of EXC, and an Action of DELETE.
Solution:
=========
Orphan:
The system security can be set up in such a way that orphans are not
allowed. Once the orphans have been created here are the choices:
Pick one or the other object as the current object. Create a new
version that contains the changes that were made in both orphaned
versions.
Pmodule change:
Pick one or the other object as the current object. Create a new
version that contains the changes that were made in both of the
versions.
Deleted Schema Objects:
DO NOT CHANGE THE STATUS OF DELETED SCHEMA
OBJECT. It's good to be aware of those objects when they come in,
but leave them alone.
12/1/95 -- nno
Progress Software Technical Support Note # 15300