Staging | Overview in the history

A special feature and a key advantage of copying objects via Staging is the history.

When importing into PIM, the modification date is usually updated each time an object is imported, regardless of whether data has actually been changed. In contrast, a PIM object is only updated from Staging if changed values are actually found. Therefore, the object in PIM always has an actual update date. If exports or workflow actions are linked to check-in events, these are not triggered incorrectly.

The module runs through several loops to check the possibility of new attributes being created by an import via autoclass (with SDZeCOM Rules), inheritance of parent elements, rules or similar.

Procedure (in the background)

First, each attribute is checked in Staging for a change of its contents. Only the attributes that are selected for being copied to PIM are considered.

The object is only checked out if the attribute value in the import file differs from the attribute value in the Staging object. The content check itself does not trigger a check-out of the object!

The new attribute value is then set.

As soon as all attributes have been checked and updated if necessary, the object is checked in again in Staging.

This process is repeated until no more attribute changes are found.

Only then is the object copied to PIM and the modification date of the PIM object updated.