I have a Spike story assigned to analyse implementation of Iframe in pega. We are using CS framework in banking domain. we are going to create inquiry request in salesforce through pega where the necessary details corresponding to different inquiry types were collected in pega and sent to the Salesforce via api. Here I have to send and receive document in pega. In salesforce they are using a concept called iframe to upload attachment like storing separately. The same iframe needs to be implemented in pega for attachment. Can you tell if that is possible in pega and Explain in how to achieve this in pega and what steps needed to be done in detailed way. Also if possible can give me the resource which you came across if any.
If you are using Traditional UI, you can configure an iframe using any of the following rules: a paragraph rule, a section rule, or a custom control. You can simply add the code for the required iframe, and it will render. However, before doing that, please confirm if the documents can be attached traditionally into Pega first, and check if there are any APIs available to upload that attachment to your source location.
If you are using Constellation, the iframe can still be generated by using a custom component. That said, I think there should still be something running in the backend to drive the attachment transfer to the source destination.
It is technically possible, but the approach depends on whether you are using Traditional UI or Constellation, and also on whether Salesforce actually allows its page to be embedded in an iframe. In many cases, the bigger question is not “can Pega show an iframe” but “should the attachment flow be integrated through APIs instead of UI embedding.”
If you are using Traditional UI, you can embed an iframe using a section, HTML fragment/paragraph, or a custom control. That part is straightforward from the Pega side.
If you are using Constellation, Constellation does not support this in the same direct way as Traditional UI, so the usual approach is to build a custom DX component and render the external iframe there. Pega’s custom DX component tooling and UI gallery are the relevant references for this pattern.
Even if the iframe is rendered successfully, that only solves the UI embedding part. You still need to define how the file is actually uploaded, stored, linked back to the case, and later downloaded. In Pega, attachments are handled as separate attachment instances and can also be integrated with external repositories through repository APIs.
Things to validate before implementation
Whether Salesforce allows the upload page to be opened inside an iframe, because X-Frame-Options or CSP can block it.
Whether the upload/download should really happen through APIs instead of embedding Salesforce UI.
Whether you want the document stored in Pega attachments, in an external repository, or fully managed by Salesforce.