APAR status
Closed as Permanent restriction.
Error description
Short Scenario: 1. Product contains a Part. 2. Part is having two bodies 3. One of the body is in hidden status. . 4.Start CATIA in Visualization mode and open the Product. New cgr is created for the Part in the Product 5. Switch the Product to design mode Activate the Part and unhide the body Save the Part 6. Check the cgr time stamp (it is the same as the one when cgr was created) 7. Activate Product 8. Use Representation>Deactivate Terminal Node on the Part Again Activate Terminal Node on the same Part. 9. Again check the time stamp for the cgr (it is changed to the time when the Terminal node is activated) Also check the cgr by inserting it in a new Product with the Existing Component option OBSERVATION: The cgr is updated when the activate/deactivate terminal node is used. Tile Windows Vertically for the Product and the CGR, both have same representation. . Repeat the same scenario but instead of activate/deactivate terminal node use activate/deactivate node. OBSERVATION: The cgr is not updated in this case. Tile Windows Vertically for the Product and the CGR, both do not have same representation. . EXPECTED RESULT: cgr should be updated in case of Activate/Deactivate Node also.
Local fix
empty
Problem summary
Short Scenario: 1. Product contains a Part. 2. Part is having two bodies 3. One of the body is in hidden status. . 4.Start CATIA in Visualization mode and open the Product. New cgr is created for the Part in the Product 5. Switch the Product to design mode Activate the Part and unhide the body Save the Part 6. Check the cgr time stamp (it is the same as the one when cgr was created) 7. Activate Product 8. Use Representation>Deactivate Terminal Node on the Part Again Activate Terminal Node on the same Part. 9. Again check the time stamp for the cgr (it is changed to the time when the Terminal node is activated) Also check the cgr by inserting it in a new Product with the Existing Component option OBSERVATION: The cgr is updated when the activate/deactivate terminal node is used. Tile Windows Vertically for the Product and the CGR, both have same representation. . Repeat the same scenario but instead of activate/deactivate terminal node use activate/deactivate node. OBSERVATION: The cgr is not updated in this case. Tile Windows Vertically for the Product and the CGR, both do not have same representation. . EXPECTED RESULT: cgr should be updated in case of Activate/Deactivate Node also.
Problem conclusion
THIS PROBLEM IS PERMANENT RESTRICTION IN CATIA. Additional Closure Information: Incident Diagnosis: The cgr file is not updated when "Activate Node"was performed . Restriction Explanation: Activate Node command is used to activate intermediate node as well as Terminal node Activate Terminal node command activates the terminating nodes (common occurrences- CATPart). CATPart(Terminal Nodes) contains geometry and on geometry change CGR should be recalculated to update the representation. For the intermediate nodes (namely Sub Products), the representation associated is a static one i.e. there cannot be any change in the representation, the cgr updation is therefore not provided for this functionality. . Activate Node and Activate Terminal Node are two different commands and therefore the behavior associated is also different. Also if the cgr updation is provided for Activate Node, on large Assemblies CATIA will have to check for geometry on each node which causes performance issues. In the BR scenario the Terminal Node is only one and there is no intermediate node. However in case of large assemblies, the number of intermediate nodes can be large which will cause a performance problem in CATIA. So this behavior is only provided with Activate Terminal Node and user should use Activate Terminal node to refresh the cgrs. . By-Pass: Use of Activate Terminal Node
Temporary fix
Comments
APAR Information
APAR number
HD93674
Reported component name
CATIA V5 NT>XP
Reported component ID
569151000
Reported release
519
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-17
Closed date
2010-04-16
Last modified date
2010-04-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"519","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
16 April 2010