@IsraelU1 There is no OOTB way in Pega to render or edit a Quadient .tno file directly, because that format is specific to Quadient. The usual pattern is to let Quadient handle the template rendering and editing, and have Pega just pass data in and receive documents or XML back. You can expose a Quadient Interactive / web editor screen and embed it in a Pega harness or portal using an iframe or DX/mashup, passing the template ID and case data (keys, customer ID, etc.) on the URL or via an API. Quadient then shows the static text plus variable fields and the editable region to the end user. When the user finishes editing, Quadient can send the finalized XML or PDF back to Pega through a REST/SOAP callback, or Pega can call Quadient again to pull the result. In Pega, you map case properties to the dynamic variables Quadient expects and store the returned file as an attachment or in a document management system. So the integration is mostly about REST/HTTP configuration, data mapping, and embedding the Quadient UI, not about teaching Pega to understand .tno itself.