We recently upgraded one of our clients to Pega 25.1.3, and ran into an issue that I haven’t seen anywhere else. Posting this in case anyone else has a similar problem.
The behavior is related to attachments on apps using external repositories. Our app uses an Azure repository. Users could attach new files, but not open, preview, or download existing attachments, even ones that they just attached. The Data-Repository instance showed a successful Test Connectivity and Validate Connectivity.
After checking the logs, we found an error like so: “Abstract base class activity pyGetFileAtributes called: this repository type (Embed-Repository-Type-Azure) does not have an implementation of this API yet!”
Turns out, there’s an activity pyGetFileAttributes that appears to have been added by the upgrade, and is called when trying to access files on a repository. The default version in Embed-Repository-Type doesn’t do anything besides add this log. There are specialized versions in Embed-Repository-Type-S3 and Embed-Repository-Type-GCS that both just call pzRepoManagerGetFileAttributes.
All we needed to do to fix the error was to create a new version of pyGetFileAttributes in Embed-Repository-Type-Azure that also calls pzRepoManagerGetFileAttributes. I imagine this would be the solution for any repository type besides S3 and GCS. I’m surprised that Pega did not include support for all the listed repo types.
Hope this helps someone else!