Warning about Object Mapping when saving configured Move / Replace Operations

This task shows you how the mapping of UUID instances is lost between CATIA and ENOVIA when these instances are saved in configured mode. In particular, some operations such as Move and Replace, when performed on configured instances, will lead to the creation of new instances having new UUIDs (Universal Unique Identifier). The newly created instances are not mapped in the CATIA session, hence leading to inconsistent behavior. This issue is addressed by a warning (see image in Step 10. below).
  1. Create a configured PRC in ENOVIA V5 VPM.

  2. Create 2 Actions, ACT1 and ACT2, with 2 effectivities having intersecting ranges (for example: 1 - 50 and 20 - 100) and associate the two Actions to the PRC.

  3. Set Act1 as a current Action for the PRC.

  4. Send the PRC to CATIA V5.

  5. Under the PRC, add a Part with simple geometry.

  6. Save it in ENOVIA V5 VPM under Action ACT1.

  7. In ENOVIA V5 VPM, set ACT2 as a current action.

  8. Send the Part to CATIA V5.

  9. Move the Part.

  10. Save the assembly in ENOVIA V5 VPM. At this step, a new instance is created in ENOVIA with the effectivity of ACT2; hence the UUID of the corresponding instance in the CATIA session must be updated accordingly. But the UUID mapping is not carried out, and as a consequence the instance in CATIA remains with the old UUID leading to possible inconsistencies with the user's next interactions. In this case, a warning appears advising the user to close the current CATIA session and to reopen a new one:

  11. If the user does not restart his CATIA session, moving again the Part, another warning is displayed, because in the CATIA session, Part instances are not identified with the correct UUIDs:

    This warning will be displayed only once (independently of the number of item instances which have been created in EV5 and not mapped in CV5).

  This warning about object mapping informs the user that the Move or Replace operation led to the creation of new instances which may not be mapped to the ones loaded in CATIA session. It is important to emphasize that:
  • Moving or Replacing instances may lead (or not) to the creation of new ones depending whether the contextual assembly is configured or not.
  • Last but not least, the Replace operation actually leads to the same consequence as for the Move. The reason is that when Replace is performed in CATIA V5, interoperability will execute first a Replace operation in ENOVIA V5 and then a Move. It is this Move which will launch the warning.