When storing Assembly data into ENOVIA, it is
strongly recommended to do not have broken constraints. Note that a broken constraint is not a data corruption, it is a normal state, supported in CATIA, but the design of the ENOVIA integration constraints considers this state as a trouble. |
|
Needed Options |
|
None. | |
Before You Begin |
|
|
|
Macro Usage |
|
The macro is delivered in the application runtime view (./operating_system/VBScript/AssemblyConstraints/SelectBrokenConstaints.catvbs) | |
|
|
Result File Location |
|
It is possible to dump traces in a text file by valuating the DumpFileName variable with the absolute path to the text file, e.g. DumpFileName = E:\temp\dump_traces.txt | |
Example |
|
|
|
|
|
The assembly name processed is displayed in a message box: |
|
|
|
The number of broken constraints is displayed: |
|
|
|
Broken constraints are selected in the specification tree: |
|