We are facing an issue with document uploads implemented in Pega Constellation UI using a Screen Flow.
Overview of the Implementation:
We have a Document Upload section within a Screen Flow.
A Document Type field (Autocomplete picklist) is provided, containing all supported document types.
Based on the selected document type, the relevant Attachment upload fields are dynamically displayed.
Users upload the required documents and submit the flow.
Observed Issue:
Upon submission, the uploaded attachments are being stored in the Data-WorkAttach-File-Temp class.
As a result, the attachments are not being associated with the work object, and the Attachments widget in the Constellation UI shows a count of 0.
This occurs even though the files were successfully uploaded during the flow execution.
Validation Performed:
To rule out limitations related to Screen Flow, we also implemented the same document upload logic in a Process Flow.
However, the behavior remains the same—attachments still move to the temporary class and are not visible in the Attachments widget.
Impact:
Users are unable to view the uploaded documents after submission.
The attachment count remains zero, leading to confusion and usability issues.
Request: Could someone please advise on:
The correct way to persist attachments uploaded via Screen Flow or Constellation UI so that they are associated with the work object, or
Any known configuration, best practice, or workaround to ensure attachments move from Data-WorkAttach-File-Temp and are reflected in the Attachments widget.
Any guidance or suggested approach to resolve this issue would be greatly appreciated.
The attachments which you are uploading are list of embedded property list attachments or a single/multiple attachments field directly on the work case.
Because, starting from infinity i guess, Link-Attachment record is not created when your attachments are residing in the embedded property list pages of the work case. Hence you will not be able to see them attached to the case.
Even if its an attachment field which contains list of attachments will also work fine. But if its a property on the embedded data class level, then it won’t be saved onto the work case.
There is a similar post on the same requirement you can have a look at,
You can go through and let us know if its the same use case or anything different.
When you upload the attachment, you will have the the Data-WorkAttach-File-Temp entry gets created. Once you finish the assignment, the temp file instance is committed to actual Data-WorkAttach-File table and linked to the case using Link-Attachment instance. Along with this the temp instance also removed. Due to this, you should be able to see the attachments linked to the case.
I see the above behaviour working fine in v25.1.2 and v24.1. Which version are you using?
You can find more details about this behaviour explained in another article regarding updation/deletion of attachments
my thoughts too - embedded data attachments are commonly misunderstood to be Case Attachments. They are separate concepts and the Attachments widget does not consider embedded data list attachments (for the Link-Attachment reason you outline, which is a deliberate design choice).
We’re uploading the documents using Attachment property in Pega 25.1.1 version as part of the screenflow and it works fine. We’re able to able to see the attachments in the attachment widget once after the Upload is completed.
Hi @MarcCheong@JayachandraSiddipeta
currently this is the UI we have built (PFA), the attachment properties are in Work Class - Single Page - Page Definition : Embed-Attach-File
PageList - Page Definition : Embed-Attach-File
Once you submit the form, are the temp work attach instances getting deleted ?
Are you seeing any errors in the tracer or logs once you submit the form ?
I believe based on the option you choose in the dropdown, you have added separate views for each of the document type and based on the existence of the option you are controlling the visibility of each view. Is the understanding correct ?
Do you see any Data-WorkAttach-File or Link-Attachment instances getting created for your case, post form submission ?
If you can answer these questions, we might be able to dig deeper and try the same on our end and let you know
It seems that on submit of the assignment, in the post processing something is stopping your attachments to be saved. If you have any logic in the post processing, remove it and check for the same.
Because Save for later action is just a plain save of the assignment and hence the saving of attachments working.
Hi @JayachandraSiddipeta
we are using the same flow action, same logic, same type of view for 2 case types, in 1 casetype it is working fine, but in another one it is not attaching to the attachment widget
Also when I am adding the attachments from local action, it is also attaching, only in the flow, when I am submitting, it is not attaching to constellation attachment widget and is stored as an TEMP instance
If it’s working for another case type, then surely there should be something wrong happening to the second case type when your post processing triggers. Please check if you have any differences in roles and/or privileges associated with both of your classes.
Also check for the attachment category instances for both of your classes to see if they have necessary options checked.
@Priyam are you using parallel processing? I remember seeing something recently where the same flow action used twice, system not sure the context to save…
I would be raising a Pega Support ticket so they can drill deeper on your configuration.
Ok @Priyam, @DianeSK and I met on a call. A bit more detail:
There is a flow action at work- that contains the ability to upload the attachment
Case attachments are at work-
The view and flow action pre-processing defines which attachment types can be uploaded
Case Type A - Works for Screenflow or triggering via local action
Case Type B - Works for Local Action but not for Screenflow (though @Priyam confirmed that even refactoring this to process, it still didn’t work)
If that helps at all? Very strange, never seen this before and curious on others experiences here.
Was unable to see anything that was specialized between case types (even accidentally). @Priyam will raise a Pega Support Ticket as this will need a deep dive on config and specialist expertise.
