Question
US
Last activity: 2 Oct 2025 22:43 EDT
File name truncated to 61 character in Pega Pulse attachment
While uploading attachment in pulse , pega calls a OOTB final activity pxUploadFile of @baseclass. In that activity its truncating filename to 61 character due to which if user is uploading file which has long name then file name is getting truncated while uploading and also while downloading file its downloaded as truncated name. As per business requirement user don't want file name to be truncated in pega pulse . So is there a reason why file name is truncated to 61 cha in pxUploadFile activity?
HCA Healthcare
US
Pega truncates Pulse attachment names to 61 chars inside @baseclass.pxUploadFile to fit legacy column limits (pxAttachName ~64 chars) while preserving the file extension and avoiding oversized keys, so the activity shortens the base name by design and it’s final, so you can’t change it. The practical fix is to preserve the original filename separately and use it for display/download. Create a property like .pyOriginalFileName on Data-WorkAttach-File (or the Pulse message payload) and set it before/after upload via a wrapper activity/DT that calls pxUploadFile. Update the Pulse attachment cell (section/control) to show .pyOriginalFileName when present, falling back to pxAttachName. For downloading, call pxDownloadAttachment (or your own download activity) and pass the desired download name (Param.DownloadFileName = .pyOriginalFileName) so the browser saves it with the full name. If you store files in a Repository (S3/Azure), keep the object key short but write .pyOriginalFileName into metadata and render that in UI. This keeps storage safe and still gives users the full, non-truncated name they want.