Applies To | |||
Product(s): | Bentley Navigator | ||
Version(s): | 08.11.09.536 | ||
Environment: | N/A | ||
Area: | General | ||
Subarea: | |||
Original Author: | Darius Rimasauskas, Bentley Technical Support Group | ||
The following outline identifies new features and enhancements in this release of Bentley Navigator V8i (SELECTseries 5).
For more information about what's new, see What's New? > New in Bentley Navigator V8i (SELECTseries 5) in the online help. To open the help document in Bentley Navigator select Help > Contents.
For certain products (such as PlantSpace/MCS), element IDs do not remain stable when i-models are republished. Since the results of a clash job refer to clashing elements by their element ID, they will either be wrong or non-existent when the original i-model is replaced by a republished i-model.
Bentley Navigator V8i (SELECTseries 5) requires PlantSpace users to create configuration variables that allow you to get consistent results when running clash detection. Through the Configuration dialog (opens when you select Settings > Configuration), you will need to create and set the following two configuration variables:
CLASHDETECTION_USE_SYNCID_MAPPING: TRUE
CLASHDETECTION_SYNCID_PROPERTY: BUD_ID
Note: For other applications that do not have consistent IDs for publishing i-models, you may need to replace BUD_ID with GUID.
When CLASHDETECTION_USE_SYNCID_MAPPING is set to TRUE, the property defined by CLASHDETECTION_SYNCID_PROPERTY is added to the clash results. Then later, when a change is detected in the i-model, CLASHDETECTION_SYNCID_PROPERTY is used to locate the element in the new i-model and to update the element ID in the clash result.
Note: You need to set the two configuration variables PRIOR to running the clash detection job. If you are re-running a clash job, make sure to clear all previous clash job results. When you create a "fresh" clash detection job after defining these variables, element ID values are supplemented with the other provided identifiers. During reprocessing/launching the clash detection job again, and whenever it finds a new version of the i-model; clash detection will prompt to reprocess the job with a dialog. If the dialog appears, then all is set and you can process your jobs.