powered by CADENAS

Manual

Manual

4.7.3. Catalog - Update

During a catalog update old and new versions are compared. This process follows the scheme below:

  1. Compare catalog date

  2. Compare projects

    Project path, Project name and Standard number are compared to ensure that the version remained the same.

    • Expired projects receive an "old" version number

    • For newer versions, the old projects receive an "old" version number and a new project is created.

    • Unknown projects receive a new project.

Points 1 and 2 are always carried out, even if no ERP integration exists.

The following point is only of importance if an ERP integration exists. See Workflow - Katalogupdate.

  1. Compare the project rows with changes in the columns "ACTIVE_STATE" and "REQUESTED_STATE"

    When checking the project rows, the following may occur:

    • Rows without connection to the LinkDB

      Additional project rows may not have a connection to the LinkDB. Another check takes place.

    • Rows with connection to the LinkDB

      For all project rows which have a connection in the LinkDB an exact check of the changes (Project, table, geometry) May take place.

    • In addition, before the update, it is determined which of the columns "ACTIVE_STATE" and "REQUESTED_STATE" are to be kept in the LinkDB.

The following flow chart displays the steps in a catalog update:

Workflow during catalog update

Workflow during catalog update