We have a scenario of embedded attachments (data layer embedded attachments - multi-layer embedded attachment feature ) and I tried this in pega version 25.1.1 to validate this feature .
Lets say we have something called capture photos and its there in Multiple embed layers .
We uses data structures in following hierarchy
Class A → Class B-> Class C
Class A has an attribute embed data (List) of Class B
Calss B has an attribute embed data (List ) of Class C
and each class we have attachments of type List of Records
I could see a difference in behavior in following areas:
Control how it works in UI
When it submits from these two channels
In web it allows you to capture attachments ( more than one ) in each data layer when we build UI in constellation and submit with the same .
But in Mobile the same View only allows you to capture single document in each data layer and when you submit the case with docuemnt from lets say Layer B which is embed in Layer A it doesnot allow you to submit as the formation of page instrction is not fully qualified path
In Web Lets Say I have One instances of each layers from UI (from page instrctions))
A(1).Attachments
A(1).B(1).Attachments for embed B attachments
But in Mobile it forms like ( from page instrctions)
A(1).Attachments
B(1).Attachments
thus resulting in an error while submitting
Are these two the known issues in Mobile in version 25?
@Unnikrishnan T N a good question. I was no aware there was a difference, we recently had a mobile webinar but I can not recall this being mentioned. @Mateusz do you know where we can find that answer?
The difference in how attachments behave between web and mobile is expected behavior in Pega Infinity 25.
In Infinity 25 and earlier, the Pega Mobile Client does not support List of Record Attachments. This limitation applies to both standard and embedded Attachment List of Record configurations. When the same view is rendered on mobile, only a Single Attachment is available (specifically, the first attachment from the attachments list). As a result, behavior differs between web and mobile, which may lead to submission or validation issues when a list of attachments is expected.
We attempted to configure a scenario similar to the one described here; however, with our configuration, we were not able to reproduce any issues when submitting a case from the Mobile Client. This indicates that the observed behavior may be driven by specific configuration differences and may not exactly align with the setup described in the article. To help us reproduce the issue and investigate it more closely, it would be very helpful to receive screenshots or details of the relevant configuration, particularly which Views are included in the form and how the embedded components with attachments within those Views are configured.
Support for List of Record Attachments, including embedded List of Record Attachments, in the Pega Mobile Client will be introduced inInfinity 26.1, aligning mobile and web behavior.