CMI Release 10.1 Functional Overview - CATIA Teamcenter ...
CMI Release 10.1 Functional Overview - CATIA Teamcenter ...
CMI Release 10.1 Functional Overview - CATIA Teamcenter ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Minimize CATProduct updates<br />
In prior releases of <strong>CMI</strong> it could often be observed that CATProducts needed an update<br />
even if only the geometry of a CATPart had been changed.<br />
We have been able to minimize this effect for <strong>CMI</strong> <strong>10.1</strong>. Products will still need to be<br />
updated if they are shown as modified in the <strong>CATIA</strong> save management, however.<br />
OOTB Delete for CATParts<br />
Configuration<br />
Generally, in case a non-BOM CATPart instance is deleted in <strong>CATIA</strong>, an empty<br />
customization method is called in Synchronize <strong>Teamcenter</strong>. Because several variations of<br />
the <strong>Teamcenter</strong> data model are supported by <strong>CMI</strong>, an OOTB implementation was not<br />
provided and the instance was not deleted in <strong>Teamcenter</strong>.<br />
Since <strong>CMI</strong> <strong>10.1</strong>, a default implementation is provided that deletes the PartDocument<br />
relation between the Document attaching the CATPart data item, and the Part.<br />
This methodology is suitable only if your business logic is that each CATPart has its own<br />
document.<br />
Set <strong>CMI</strong>_REMOVE_GEOMETRY “DOCUMENT”; in the <strong>Teamcenter</strong> configuration to<br />
enable this functionality.<br />
4 <strong>CMI</strong> <strong>Release</strong>s – <strong>Functional</strong> <strong>Overview</strong>