Attachment framework internals in the latest Pega Infinity release

General
, ,
1

Hi all,

I am looking for a detailed, current release view of how the attachment framework is implemented internally in the latest Pega Infinity release. Environment: Constellation UI, attachments stored in [Pega DB / external repository].

  1. Class model

Could someone clarify the responsibility and scope of each of these classes, and how they link together?

Data-WorkAttach-File
Link-Attachment
Embed-CaseAttachment
Embed-Attach-File
PegaSocial-Document

In particular:

How are case-level attachments and data-level attachments related at the data model level?
Where does PegaSocial-Document sit relative to case attachments - is it purely the Pulse/collaboration model, or does it participate in case attachment persistence?

  1. Lifecycle by scenario

What records and pages are created, and which rules/APIs are involved, in each of these?

Manual upload from the case UI
System-generated PDF attached during case processing - is persistence any different from a manual upload?
Inbound email with attachments that creates or updates a case - how are attachments parsed, persisted, and linked, and how does propagation from an email/triage case to the business case work?

  1. Retrieval and display

Which OOTB data pages are the supported way to list a case;s attachments (e.g. D_AttachmentList, D_AttachmentFieldInfo)?
What is the recommended pattern for showing attachments in a constellation case view or DX component?
Are there patterns to avoid (e.g. querying Data-WorkAttach-File directly)?

  1. Reference material

Any docs, Knowledge Share articles, Academy modules, or architecture/class diagrams covering the attachment framework end to end would be very helpful - especially anything reflecting changes in the most recent releases (data-level attachment fields, repository streaming).

Thanks in advance.

2
  1. Data-WorkAttach-File stores the attachment metadata/content, while Link-Attachment links the attachment to the case. Embed-CaseAttachment and Embed-Attach-File are primarily UI/runtime structures used for attachment representation and processing. PegaSocial-Document is mainly associated with Pulse/social collaboration rather than the core case attachment persistence model.
  2. For both manual uploads and system-generated PDFs, the persistence model is essentially the same: an attachment record is created and linked to the case.
  3. The recommended retrieval approach is to use OOTB attachment APIs and data pages such as D_AttachmentList.