HD70154: ASD: UPDATE/THE CONSTRIANT MADE BY REUSED RECTANGULAR PATTERN C AN NOT BE UPDATED

APAR status

• Closed as suggestion for future release.

Error description

• THE PROBLEM WAS REPORTED ON V5R18 SP01.
  THE PROBLEM IS REPRODUCIBLE ON CXR19 (12-
  18-2007).
  .
  MATERIAL:
  http://denedsy.ds/pub/db/c760/pmr76075472.6X2/
  .
  OS:
  Reported OS: WIN XP
  Tested OS: WIN XP
  .
  SCENARIO:
  1. Open Product1.CATProduct and change to
  Assembly wb.
  2. To Part1 and Part2, define Surface contact for
  the faces and Coincident constraint for axis, then
  Update.
  3. Define Rectangle Pattern of Part2 by Reused
  Rectangular Pattern of Part.1.
  4. To Part2 and Part3, define Surface contact for
  the faces and Coincident constraint for axis.
  5. Define Coincident constraint to Part3 and part by
  Reused Rectangular Pattern, then update.
  6. Move the part by Reused Rectangular Pattern by
  compass.
  7. Select Update All.  Update Diagnosis Product1 is
  displayed and can not be
  updated. This  is the problem
  .
  PROBLEM:
  Update error & product can?t be updated.
  .
  EXPECTED RESULT:
  Update should be performed correctly without any
  error.
  .
  ADDITIONAL INFORMATION:
  Double click Reused Rectangular Pattern.1 in the
  tree, and then select Local
  Update in definition dialog box. Then, Update All
  can be performed.
  .
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• THIS APAR IS CONSIDERED AS A SUGGESTION
  FOR IMPROVEMENT FOR CATIA.
  PLEASE CONTACT YOUR SUPPORT DEPARTMENT IN
  ORDER TO OPEN A REQUIREMENT FORM.
  Incident Diagnosis:
  When a reuse pattern is made, using
  option "Generated components? position is
  maintained by Pattern's Definition. The pattern part
  is parent for solving constraints of the new pattern
  instances. Bottom plate is found in the parent of
  the pillar so it is considered to be fixed. The top
  plate also cannot move because of the constraint
  with another pillar which was used as input for
  reuse pattern. So Over constraint error appears.
  This error stops the overall update cycle which
  leads to non update of the reuse pattern.
  .
  Development request Justification:
  Presently the updates cycle is as follows, first
  constraints update & then feature. In the present
  scenario when update tries to update constraint
  then it shows over constrained situation & hence
  the update cycle stops. As the update cycle stops
  the reuse pattern feature does not get updated.
  This problem can be solved by changing the
  sequence of update cycle. That means first feature
  gets updated & then constraints. Also change in
  update behavior can lead to lot of other problems
  which cannot be managed easily. For this huge
  study & development is required. This will be
  managed by an ERD. Please open an Enhancement
  request.
  .
  Answer & By-pass:
  If the user wants to create such type of data then
  option "Generated components position is
  maintained by generated Constraints" must be
  used. Then there will not be an over constraint
  error. When the local update of feature is done
  then also problem will be solved.
  .
  

APAR Information

• 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