HD57544: PROPAGATE POSITION TO REFERENCE IS BROKEN

APAR status

• Closed as suggestion for future release.

Error description

• Propagate position to reference is broken
  .
  SCENARIO
  .
  User needs a mechanism by which the user can
  specify what the default behavior should be for a
  product when it is brought into the process.
  Currently, the "default", that is fixed is that the
  Product will be Flexible. What we are asking for is
  that we be given the CHOICE to indicate what that
  default should be: Flexible or Rigid. It should work
  like a CATSetting - once the user specifies the
  behavior (Flexible or Rigid), that setting should be
  stored and remembered by the System across
  CATIA sessions. If you give us this functionality,
  our problem will be solved.
  .
  PROBLEM
  .
  The user is trying to pass a constraint back to the
  reference Product from within a Catprocess. After
  attempting to use the ﾨPropagate position to
  referenceﾨ command, the reference Product does
  not reflect the new constraints passed from the
  Catprocess
  .
  EXPECTED RESULT
  .
  The Users wants to propagate the changed
  constraints without changing back and forth
  between Flexible and Rigid. The Users wants a
  clean method for passing on new constraints back
  to their reference.
  .
  .
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• THIS APAR IS CONSIDERED AS A SUGGESTION
  FOR IMPROVEMENT WHICH CANNOT BE
  INCORPORATED IN VERSION 5R18
  PLEASE CONTACT YOUR SUPPORT DEPARTMENT IN
  ORDER TO OPEN A REQUIREMENT FORM.
  .
  Incident Diagnosis :
  User needs a mechanism by which the user can
  specify what the default behavior should be for a
  product when it is brought into the process.
  Currently, the "default", that is fixed is that the
  Product will be Flexible. What we are asking for is
  that we be given the CHOICE to indicate what that
  default should be: Flexible or Rigid. It should work
  like a CATSetting - once the user specifies the
  behavior (Flexible or Rigid), that setting should be
  stored and remembered by the System across
  CATIA sessions.
  .
  Development Request Justification
  There needs to be a way to define the default type
  of assemblies in machining workbenches. This
  implementations requires a huge development,
  which cannot be done in APAR timeframe.
  .
  

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