Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Open Generated S-Docs in Live Edit from Screen Flow

Build a Screen Flow that lets users select a record, choose a generated S-Doc, and open it in Live Edit from an Experience Cloud page.

Use this guide when you want a Screen Flow to open an existing generated S-Doc in Live Edit.

Use this pattern in Experience Cloud when users need guided access to editable documents.

This Flow opens an existing generated S-Doc.

It does not generate a new document.

Live Edit currently supports PDF / PDF-Upload formats.

Start here if you are newer to Flow

New to Flow? Start with Getting Started: Automate Document Generation.

Prerequisites

  • A Screen Flow

  • A template with Allow Edit enabled

  • A generated SDoc record from that template

  • Access to the Flow, base record, related SDoc record, and generated file

  • Two screen table components that each allow one selected row

Screen Flow outline for Live Edit

Step-by-step tutorial

Step 1: Create or open the Screen Flow

Open Flow Builder.

Create a Screen Flow, or open an existing one.

Use a Screen Flow because users must choose a record and a document on Flow screens.

Admin Tip: If this Flow runs from a record page, create a Text variable named recordId. This name is case-sensitive. Then enable Available for input.

Step 2: Get the records users can work with

Add a Get Records element for the records users should see.

Filter for the records this experience should expose.

Sort the results in descending order.

Choose Store all records.

Step 3: Add the first selection screen

Add a Screen element with a table component.

Show the record collection from the first Get Records element.

Allow one selected row.

Add another Get Records element after the screen.

Use the selected row value to store one base record for later steps.

Step 4: Get the related S-Docs and let the user choose one

Add a Get Records element for SDoc records.

Filter the SDoc object for documents related to the selected base record.

Return only documents the user should be able to edit.

Add a second Screen with a table component.

Show the returned SDoc records.

Allow one selected row.

Step 5: Add the SDoc Edit Live component

Add a final Screen element.

Drag the SDoc Edit Live component onto the screen.

Map the selected SDoc ID into the component.

Make sure you pass the selected row from the SDoc table, not the base record ID.

Step 6: Save, activate, and place the Flow

Save the Flow.

Activate it.

Add the Flow to the target page in Experience Builder.

Then test the full path and confirm users can:

  • select a record

  • select a related S-Doc

  • open the document in Live Edit

Step 7: Confirm access and sharing

Grant the target profile or permission set access to the Flow.

Make sure users can access the base record.

Make sure users can access the related SDoc record.

Make sure users can access the generated file used by Live Edit.

If any one of these is missing, the Flow can open while the document list or editor fails to load.

Troubleshooting and common errors

The S-Doc table is empty

  • Symptom: The first record selection works, but no SDoc records appear on the next screen.

  • Cause: The Get Records filter does not match the selected base record, or the user cannot access the related SDoc records.

  • Fix: Check the related record filter first. Then confirm object access, record sharing, and file visibility for the target user.

The Live Edit screen opens, but the document does not load

  • Symptom: The final screen opens, but the editor is blank or does not load the selected file.

  • Cause: The mapped SDoc ID is blank, invalid, or taken from the wrong screen component.

  • Fix: Confirm the SDoc Edit Live component receives the selected SDoc row value from the second table.

The Flow works for admins, but not for site users

  • Symptom: Admins can open and edit the document, but Experience Cloud users cannot.

  • Cause: The site user is missing access to the Flow, base record, SDoc record, or generated file.

  • Fix: Review Experience Cloud sharing, Flow access, and file visibility. Then retest as the target user.

The editor opens, but users cannot save edits

  • Symptom: The document loads in Live Edit, but users cannot make or save changes.

  • Cause: The source template does not have Allow Edit enabled, or the file format is unsupported.

  • Fix: Enable Allow Edit on the template that generated the document. Then confirm the file is PDF or PDF-Upload.

Advanced configurations and reference