Managing Change Recording in the Portal

Behavior and Constraints

• When change recording is activated, the Portal Content panel shows the status of PCD objects using the following icons:

  • 

    Checked out for add

  • 

    Checked out for add by other

  • 

    Checked out for edit

  • 

    Checked out for edit by other

  • 

    Recorded folder

• When change recording is activated, the My Open Changelists panel displays the changelists of the user and shows their status using the following icons:

  • 

    Checked out for delete

  • 

    Default changelist

  • 

    Changelist

  • 

    Change operation

  • 

    Related operations: several change recording operations having common objects

• Change recording granularity - PCD change recording records changes at unit level. When a subunit object is modified, the entire unit to which it belongs is checked out by the PCD. Information about changes to non-unit, internal objects is provided to the change recording service, and displayed in the change recording UIs, but actions are performed on the entire unit.

• Object locking - If an object is in an open changelist, change recording prevents other users from modifying it.

  If change recording is activated and a user modifies PCD unit objects, the objects are added to the user's default change list.

  If an application is using a PCD object, the locking infrastructure sets a lock on the object.

  Caution

  Verify if an object you require is not part of an open changelist of a different user. The locking infrastructure allows portal applications to retrieve the change recording information of an object that is locked by change recording.

• Multiple object changes - Some change recording operations, such as moving an object (which involves both a delete and a create operation) or mass property changes, affect more than a single object. To maintain consistency, change recording groups all actions performed by a single user and change recording operations, such as activate, revert, or moving objects between different changelist, apply to the entire group.

• Cross-system content synchronization - The PCD content in the recorded areas is synchronized across the landscape when change recording is activated. Recorded content is not modified on target systems while change recording is active.

• If a portal user is deleted while owning an open changelist, the changelist remains and all the items in the changelist remain locked. The solution is for the administrator of the changelist organizer to assign this changelist to an existing user.

  Caution

  Make sure that users who are to be deleted are not owners of open changelists.

• When a portal service configuration is changed (for example, after a revert or import action), you must restart the service to regain its functionality.

• After change recording operations, the administrator of the changelist organizer can cause PCD objects, which are part of an open changelist, to revert. The reverted object returns to the state it was in before being checked out, as follows:

  • Folders:

    • A folder created since checkout is deleted if empty

    • A folder updated since checkout has its former attributes restored to it

    • A folder deleted since checkout is reimported, but without its subfolders

• Unit objects:

  • An object created since checkout is deleted upon revert

  • For an updated object, its former state is imported

  • For a deleted object, its former state is imported

• When an object is recorded and added to a changelist, a notification appears to the user, except after the following actions:

  • Copy/paste or cut/paste of a delta link into a recorded folder

  • Deletion of an object in a recorded folder

  • Import of an EPA or an XML into a recorded folder