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

UploadFile using # symbol for file path and Rightfax issue



You are trying to pass the property pxAttachName as a file reference to a 3rd party Application (e.g., Rightfax).  This property was configured automatically via the normal Pega "file attach" process.  Your 3rd party application cannot find the file to which pxAttachName refers.  When you examine the contents of pxAttachName, (or examine the error message reported by the 3rd party product) you realize that the filename has spaces, and each of those spaces has been encoded as "#20" instead of the expected "%20".

Error Messages

This is the error you might see from the Rightfax application:

Rightfax logs:
[2014-07-15 09:05:57] Use Embedded Documents for attachment
[2014-07-15 09:05:57] Only One Embbeded Document
[2014-07-15 09:05:57] Embbeded Document: Test#20Fax#20document.doc,
[2014-07-15 09:05:57] Document Name: Test#20Fax#20document.doc
[2014-07-15 09:05:57] Pages:
[2014-07-15 09:05:57] Document attachment not found. return false. send email alert.

Steps to Reproduce

Not Applicable 

Root Cause

The root cause of this problem is a divergence between Industry standards and Pega internal usage. Pega uses some proprietary constructs in the reference to the attached file.  In particular, we use "#20" to represent a space, different from the expected "%20". When the 3rd party product digests the file name, itt does not know how to interpret the "#20".


Preprocess the value of the filename and replace every "#20" with "%20" prior to passing the information to the 3rd party Application.

Published March 17, 2016 - Updated October 8, 2020

Was this useful?

0% 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