HD90894: FILES LOADED IN CATIA V5 CAN BE DELETED WITH MANAGE WO ................................................................

APAR status

• Closed as Permanent restriction.

Error description

• PROBLEM DESCRIPTION:
  Files loaded in Catia V5 can be deleted with Manage Workspace
  - Create a small assembly (1 CATProduct + 1 CATPart) from
  template in
  Enovia.
  - Checkout, files are loaded in Catia, renaming of files is
  performed.
  - Open Manage Worspace-window: You will see, both files are
  selectable.
  - Select the files and perform Delete.
  - The files are deleted from Workspace Manager and from disk.
  This happens only checkouts of templates. The expected
  behaviour would
  be: Loaded files can't be deleted. This is the way it works
  for normal
  files, that are already "existing"
  I know, that Catia allows to delete files from disk, that are
  already
  loaded in Catia V5
  But what is the reason for the different bahaviour in CT5:
  - on the one hand for files, that were checked out as already
  existing
  files (means, the files checked in to the Enovia-objects have
  already
  the correct names (identical to the name of the object)
  before and are
  not renamed by CT5 at the current checkout.) This files can't
  be deleted
  with manage workspace, this behaviour is ok in my opinion.
  - on the other hand for files, that were created in Enovia as
  templates
  and are checked out the first time (means, the files checked
  in to the
  enovia-objects have the name of the template (different from
  the name of
  the object) before and were renamed at the current checkout
  by CT5).
  This files can be deleted with manage workspace, this
  behaviour is not
  ok in my opinion.
  

Local fix

Problem summary

• PROBLEM DESCRIPTION:
  
  Files loaded in Catia V5 can be deleted with Manage Workspace
  
  
  
  - Create a small assembly (1 CATProduct + 1 CATPart) from
  template in
  Enovia.
  
  - Checkout, files are loaded in Catia, renaming of files is
  performed.
  - Open Manage Worspace-window: You will see, both files are
  selectable.
  - Select the files and perform Delete.
  
  - The files are deleted from Workspace Manager and from disk.
  
  
  
  This happens only checkouts of templates. The expected
  behaviour would
  be: Loaded files can't be deleted. This is the way it works
  for normal
  files, that are already "existing"
  
  
  
  I know, that Catia allows to delete files from disk, that are
  already
  loaded in Catia V5
  
  But what is the reason for the different bahaviour in CT5:
  
  - on the one hand for files, that were checked out as already
  existing
  files (means, the files checked in to the Enovia-objects have
  already
  the correct names (identical to the name of the object)
  before and are
  not renamed by CT5 at the current checkout.) This files can't
  be deleted
  with manage workspace, this behaviour is ok in my opinion.
  
  - on the other hand for files, that were created in Enovia as
  templates
  and are checked out the first time (means, the files checked
  in to the
  enovia-objects have the name of the template (different from
  the name of
  the object) before and were renamed at the current checkout
  by CT5).
  This files can be deleted with manage workspace, this
  behaviour is not
  ok in my opinion.
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN I-PLM Collaborative
  Innovation
  Additional Closure Information:
  THIS PROBLEM IS PERMANENT RESTRICTION IN I-PLM Collaborative
  Innovation
  .
  Issue occurs as the object checked out immediately after
  creation from Start design template and it has a different
  filename entry in the working set (i.e. the name of the
  template file).  The Local Workspace manager view is built
  from the filenames read from the directory on the disk.  The
  filename on the disk after checkout is changed by CT5 to
  match the created design object. The entry in the working set
  has old filename and so the file cannot be recognized and is
  shown as UNKNOWN.  CT5 sends the name and changed filename in
  the Manage Workspace request.
  While it is possible to recognize using this information,
  using data stored in IEF-ClientSideRenamedFileDetails of the
  LCO, if the user creates multiple instances from same
  template and checks out to the same directory, the
  IEF-ClientSideRenamedFileDetails approach will also fail.
  By-pass: If user checks in immediately after checkout, so as
  to update the renamed file in the server, this issue will not
  be seen from the next checkin.
  

Temporary fix

Comments

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