HD94022: CAA APIs are not setting MIME type properly for certain document types

APAR status

• Closed as documentation error.

Error description

• 1. Launch CATIA from client WS and Go to Tools->Macro->Visual Ba
  sic Editor
  2. Create a new VBA project if none exist
  3. Create new Library
  4. Enter the path for the catvba file
  5. Double click on this catvba file, it should open a visual bas
  ic editor
  6. Right click on ???VBAProject1??? in the Visual Basic Editor a
  nd click on Insert->Module
  7. Copy the attached code to the module1. Replace iFullFilePath
  and iVaultName appropriately.
  8. Click on "Tools->References" and browse for for the Automatio
  nTypeLib library in ???<WS>\intel_a\code\bin??? directory and se
  lect the file
  9. Click on ???OK??? button to exit the References window
  10. Put any pdf file and name it as XXXXX_PDF_FROM_CAA_KO at C:\
  temp
  11. Modify the VBA project so as to point to this PDF file
  12. Execute the VBA. It will save the pdf file in ENOVIA.
  13. Launch ENOVIA and search for the pdf file in Content Managem
  ent
  14. Put any pdf file and name it as XXXXX_PDF_FROM_LCA_OK at C:\
  temp
  15. Through Content Management save this file in ENOVIA
  16. Check the Attribute View for both the above documents
  Observed result: The MIME Type attribute for XXXXX_PDF_FROM_LCA_
  OK is application/pdf while the MIME Type attribute for XXXXX_PD
  F_FROM_CAA_KO is application/octet-stream
  Expected Result: The MIME Type attribute should be same irrespec
  tive of whether it is saved interactively or through CAA
  A. Please note that for CATPart the MIME Type attribute is same
  as application/catiaV5-Part irrespective of whether it is saved
  interactively or through CAA.
  B. Customer has also tested the following file types as an attac
  hment and found that programmatically created documents MIMEType
   is not matching with interactively created documents MIMEType.
  Hence please manage these too.
  S.NO. File Extension Interactive MIMEType  Programmatic MIMEType
  1 *.cgm  application/catia-local2D application/octet-stream
  2 *.CATSystem application/CATIA.System application/octet-stream
  3 *.tar  application/x-tar  application/octet-stream
  4 *.zip  application/x-zip-compressed application/octet-stream
  5 *.vsd  application/vnd.visio  application/octet-stream
  6 *.dtd  application/xml-dtd  application/octet-stream
  7 *.gif  image/gif   application/octet-stream
  8 *.dat  application/dat   application/octet-stream
  9 *.ico  image/x-icon   application/octet-stream
  10 *.xml  text/xml   application/octet-stream
  11 *.css  text/css   application/octet-stream
  12 *.xsl  text/xml   application/octet-stream
  13 *.sql  application/sql   application/octet-stream
  14 *.jar  application/jarfile  application/octet-stream
  15 *.cgi  application/octet-stream application/octet-stream
  16 *.au  audio/basic   application/octet-stream
  17 *.js  application/JSFile  application/octet-stream
  18 *.CATSettings application/CATIA.Settings application/octet-st
  ream
  19 *.PDF  application/pdf   application/octet-stream
  20 *.mdb  application/msaccess  application/octet-stream
  21 *.mrgman application/MergeManager.File application/octet-stre
  am
  22 *.wav  audio/wav   application/octet-stream
  23 *.rtf  application/msword   application/octet-stream
  

Local fix

• empty
  

Problem summary

• 1. Launch CATIA from client WS and Go to Tools->Macro->Visual
  Basic Editor
  2. Create a new VBA project if none exist
  3. Create new Library
  4. Enter the path for the catvba file
  5. Double click on this catvba file, it should open a visual
  basic editor
  6. Right click on ???VBAProject1??? in the Visual Basic Editor
  and click on Insert->Module
  7. Copy the attached code to the module1. Replace
  iFullFilePath and iVaultName appropriately.
  8. Click on "Tools->References" and browse for for the
  AutomationTypeLib library in ???<WS>\intel_a\code\bin???
  directory and select the file
  9. Click on ???OK??? button to exit the References window
  10. Put any pdf file and name it as XXXXX_PDF_FROM_CAA_KO at
  C:\temp
  11. Modify the VBA project so as to point to this PDF file
  12. Execute the VBA. It will save the pdf file in ENOVIA.
  13. Launch ENOVIA and search for the pdf file in Content
  Management
  14. Put any pdf file and name it as XXXXX_PDF_FROM_LCA_OK at
  C:\temp
  15. Through Content Management save this file in ENOVIA
  16. Check the Attribute View for both the above documents
  Observed result: The MIME Type attribute for
  XXXXX_PDF_FROM_LCA_OK is application/pdf while the MIME Type
  attribute for XXXXX_PDF_FROM_CAA_KO is
  application/octet-stream
  Expected Result: The MIME Type attribute should be same
  irrespective of whether it is saved interactively or through
  CAA
  A. Please note that for CATPart the MIME Type attribute is
  same as application/catiaV5-Part irrespective of whether it
  is saved interactively or through CAA.
  B. Customer has also tested the following file types as an
  attachment and found that programmatically created documents
  MIMEType is not matching with interactively created documents
  MIMEType. Hence please manage these too.
  S.NO. File Extension Interactive MIMEType  Programmatic
  MIMEType
  1 *.cgm  application/catia-local2D application/octet-stream
  2 *.CATSystem application/CATIA.System application/octet-strea
  m
  3 *.tar  application/x-tar  application/octet-stream
  4 *.zip  application/x-zip-compressed application/octet-stream
  5 *.vsd  application/vnd.visio  application/octet-stream
  6 *.dtd  application/xml-dtd  application/octet-stream
  7 *.gif  image/gif   application/octet-stream
  8 *.dat  application/dat   application/octet-stream
  9 *.ico  image/x-icon   application/octet-stream
  10 *.xml  text/xml   application/octet-stream
  11 *.css  text/css   application/octet-stream
  12 *.xsl  text/xml   application/octet-stream
  13 *.sql  application/sql   application/octet-stream
  14 *.jar  application/jarfile  application/octet-stream
  15 *.cgi  application/octet-stream application/octet-stream
  16 *.au  audio/basic   application/octet-stream
  17 *.js  application/JSFile  application/octet-stream
  18 *.CATSettings application/CATIA.Settings application/octet-
  stream
  19 *.PDF  application/pdf   application/octet-stream
  20 *.mdb  application/msaccess  application/octet-stream
  21 *.mrgman application/MergeManager.File application/octet-st
  ream
  22 *.wav  audio/wav   application/octet-stream
  23 *.rtf  application/msword   application/octet-stream
  

Problem conclusion

• THIS MODIFICATION WILL BE INCLUDED IN THE DOCUMENTATION
  DELIVERED WITH VERSION V5R21
  Additional Closure Information:
  The documentation has been fixed to inform how to take into
  account new mime types. The documentation can be found at
  LifeCycle Administration Guide -> Adding MIME Types to
  VPMMIMETypes.xml File.
  A note has been added in this documentation as below:
  Note : Work Package Reports functionality related information
  is implemented in R14+ code,but if there are any other MIME
  types which are to be considered then it is required to add
  them manually to the VPMMIMETypes.xml file.
  

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

• Fixed component name

  ENOVIA V5 VPM N

• Fixed component ID

  569151400

Applicable component levels