Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Attachment names with spaces replaced with '_'

SA-90144

Summary



On creating a work object with attachments through Email Instantiation, the attachment names with spaces are replaced with '_'  in the Case Attachment section.

For example:

Consider an attachment named 'Test 123.pdf' in the email. When the case is created, the attachment name changes to 'Test_123.pdf' in Attachment section.


Error Messages



Not Applicable


Steps to Reproduce



Activities that create the attachment objects and link them to their work objects must perform the following:
  1. Create a page for the work object attachment (Data-WorkAttach-File class).
  2. Copy the file from the pyAttachment page (Data-ServiceMessage class) to the work object Attachment page.
  3. Save the attachment page (Obj-Save method).
  4. Create a link object (Link-Attachment class) that connects the attachment to the work object with the Link-Objects method.
  5. Commit the attachment object and the link object.
For more information, refer to: https://community.pega.com/knowledgebase/articles/correspondence/how-configure-email-service-use-email-attachment-work-object-attachment


Root Cause



When an Email Listener processes a mail with attachments, the attachment names changed because the special characters in the name are replaced by '­_' in the UtilsEmailMessageParser.cleanMsgAttchmentName() method.


Resolution



An enhancement request, FDBK-62347 is created for consideration by Pega Product Management.

Published July 21, 2020 - Updated December 2, 2021

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us