Contents of SE-65319

Hi,

We ran into an issue about attachment preview and download functionality, and we traced this back to a change made in SE-65319, which we saved in our own ruleset about two years ago. Since I cannot find any details of the SE anymore, could you help me out with this? That way we will know if we should keep this change or not.

Kind regards,
Bas

Hoi @BasG0629.

I have gone through the details of the ticket which generated SE-65319 which was INC-136091 (FSM Mobile: downloading/viewing attachments online).

Unfortunately we are no longer able to access the system containing the SE item. I can see that when our UI Offline and FSM and Native engineering teams reviewed the issue they determined that the native layer was sending the request for a file but the file is corrupted. At the same time when they checked plain FSM they could see that the pdf is retrieved from local store (there is no request to server for that).

They suspected the issue to be somewhere in the DMGFieldService customization but the support ticket informs me we could not point to the exact place.

The way the ticket has been worded is that they then found the root cause of the issue via the SE item. It was related to one of the activities on the server side. The fix was developed in the 8.4 and they then fixed it in the 8.3.5 patch release which you were recommended to upgrade to. Unfortunately there is no mention in the support ticket itself of any temporary manual changes recommended to you at the time via the SE engineers.

The Resolved Issues document and online info details the changes as follows:

BUG-598907 - Activity updated for Mobile attachment access

“Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message ‘Class pxLinkedRefTo does not exist’. This has been resolved by updating “pzpega_control_attachutil” to use the activity “GetAttachmentReference” for interactions with the attachments from any storage type.”

I will check internally to see if the original engineer who dealt with your support ticket can comment any further but as this is two years ago I’m not sure we’ll be able to access these details.

@MarijeSchillern Well thank you for the extensive response! Since we have already upgraded to Pega 8.3.5, we can always check if the INC still occurs if the change from the SE is no longer present, with some additional regression testing on this functionality. I can imagine the engineer does not now the exact details of such an old change anymore :wink:

Kind regards,
Bas