PDF review components
Use a PDF review component when a person needs to inspect a templated PDF before the service generates or submits the final document. It works with a configured templated-PDF action and is intended for controlled review, not as a substitute for an accessible service journey.
Design the review sequence
Configure the PDF template and mappings first, then add the review component to the appropriate point in the journey.
flowchart LR
A[Collect answers] --> B[Map answers to PDF template]
B --> C[Read and review PDF]
C --> D{Changes needed?}
D -- Yes --> E[Edit allowed answers or return to service]
D -- No --> F[Confirm and submit]Use a read-and-review step by default. A person should have a clear opportunity to check the document before committing to it.
Choose editing and adjustment controls carefully
You can allow editing of supported mapped answers and adjustment of mapped answer boxes. Enable these only where people genuinely need that control and where the resulting document remains understandable and reliable.
If people can change answers in the review, test that the changed value is used consistently in the PDF, the journey data, review pages and downstream actions. If boxes can be moved or resized, test long answers, small displays, print output and the final generated file.
Confirm submission clearly
The component can show print or download controls and a submission confirmation dialog. Write a confirmation message that states the outcome of submitting the reviewed PDF. Do not require printing or downloading unless there is a real business need; it can create unnecessary barriers.
Test the PDF with representative long values, missing optional values, and every mapped field. Verify the selected action is the intended template and that the completed PDF is available through the designed record and support process.