Use Appian’s PDF Doc From Template smart service in a process model to fill an Adobe Acrobat form with process data and save the result as a PDF document. Store the form in Appian Document Management, map its recognized fields to process values, choose whether to create or replace a document, and save the new document output to a process variable. These steps follow Appian’s 24.3 documentation; verify the node’s behavior and interface in the version deployed in your environment.
What you need before configuring the process
This workflow generates a PDF by populating form fields in a PDF template. The template must be an Adobe Acrobat form, not just an ordinary PDF, and it must be available in Appian Document Management. Appian’s documentation describes the smart service as a way to populate a form with process data and save the result as a PDF document (Appian 24.3: PDF Doc From Template Smart Service).
- Prepare the PDF form and its field names before setting up the node.
- Put the template in Appian Document Management and confirm that the process’s run-as user can retrieve it.
- Decide whether each run should create a new document or replace an existing one, and identify the destination folder or document.
- Create a process variable with the Document data type for the generated output if later process steps need to use it.
Appian’s documented browser for selecting a template makes PDF files selectable; it does not make a non-form PDF usable as a form template. The smart service’s substitution grid is populated from recognized form fields, and image fields are not supported as recognized fields. Do not plan on using this node to populate image fields.
Configure PDF Doc From Template in a process model
- Add the smart service. In the process model, find PDF Doc From Template under document generation and add it to the model. Appian describes its assignment option as Always Unattended.
- Select the base template. In the node’s Setup, select the PDF by name or browse to it in Appian Document Management. Once the form is selected, Appian scans its recognized form fields into the substitution grid.
- Map form fields. For each field in the grid, supply the process value intended to populate that field. Check that the form field names and the mapped process data correspond to the values the process will have at runtime. If a field is absent from the grid, check the source form: it may not be a recognized form field, and image fields are not supported.
- Choose the output behavior. Configure the node to create a new document or replace an existing document. For a new document, set its name and destination folder; a description is optional. Avoid filename characters Appian disallows, including
/ : ; < > " * ' ?. - Store the result. In Outputs, select New Document Created and map it to a process variable of the Document data type. Later nodes can then refer to the generated document through that variable.
- Validate access and publish. Confirm the run-as user has the needed rights for the selected template and output destination, and for the existing document as well if the process will replace one. Test the process with representative data and verify the generated file in its destination.
Map fields and handle templates selected at runtime
If every process run uses the same form, select it as the node’s template and map its fields in the substitution grid. When the template must vary by process data, Appian 24.3 documents a Runtime Template expression that can use a variable or constant to select the template at runtime.
#1 Best Overall
A runtime template’s substitution fields do not have to match the base template exactly, but any fields the process uses at runtime must be present in the base template. Treat the base template as part of the node’s configuration, not merely as an example file: its fields affect which substitutions can be configured and used.
Plan changes to form fields
Template changes have different implications depending on whether the field names and properties stay the same. According to the 24.3 documentation, a new template version with identical field names and properties updates in active processes. If fields change, remap the node inputs and republish the process model; active processes must also be edited to use the new template. Account for that rollout when changing a form used by running processes rather than assuming that replacing a file will update every mapping.
Permissions, failures, and process behavior
The user under which the service runs needs permission to retrieve the template and write to the chosen destination. If replacing a document, that user also needs access to the document being replaced. Appian’s 24.3 documentation notes that an absent or unretrievable template can cause an exception. Insufficient access or a missing destination resource can notify the Process Administrator and pause the process.
| Symptom | What to check | Practical correction |
|---|---|---|
| The template cannot be selected or retrieved. | Confirm it is a PDF form in Appian Document Management and that the run-as user can retrieve it. | Use an Acrobat form stored in Appian Document Management, then confirm the process user’s access. |
| A field does not appear in the substitution grid. | Check whether the PDF contains a recognized form field; image fields are not recognized by this smart service. | Use a supported form field for the value, or choose a different document-generation approach if the output requires image substitution. |
| The process pauses or reports an access or destination problem. | Check access to the template, destination folder, and, for replacement, the existing document. Also check that the destination resource still exists. | Grant the run-as user the required access or correct the destination before retrying or resuming according to your process operations. |
| The output does not reflect a changed runtime form. | Compare its field names and properties with the base template and the node’s mappings. | If fields changed, remap inputs, republish the process model, and edit active processes to use the updated template. |
| A new document is not created as expected. | Review the selected output behavior, configured name and folder, filename characters, and the New Document Created output mapping. | Correct the destination or name, then map the output to a Document-typed process variable if the workflow needs to pass the result on. |
Choose a different Appian template service only when the output calls for it
PDF Doc From Template is the documented path when the source is a PDF form and the desired output is a populated PDF. Appian also documents separate template services for other formats; these should not be treated as interchangeable ways to generate the same PDF form output. Check the documentation for the release you run before choosing or configuring another service.
- HTML Doc From Template produces HTML.
- MS Word 2007 Doc from Template uses DOCX templates to produce Word documents.
- Open Office Writer Doc From Template uses ODT templates to produce Writer documents.
- Text Doc From Template is a text-oriented path whose documented supported formats include CSV, JSON, RTF, TXT, XLSX, and XML.
Those service pages are for the Appian versions in their URLs, not necessarily the release deployed in a given environment. Confirm the available service, configuration details, and supported inputs against your target Appian release.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
Important distinction: ScreenshotNeo is a website screenshot API, not an Appian process-model service, and it does not populate an Acrobat form with Appian process data. Use it only if your separate requirement is to capture a website as an image or PDF. For that task, one GET request can return a capture; see the ScreenshotNeo API documentation.
Rank #4
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers indicate the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to try website captures.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Version and rollout check
The PDF smart-service instructions above are based on Appian 24.3 documentation, while the listed alternative service pages identify their respective releases in their URLs. Interface labels and node behavior can differ by deployed version. Before changing a production process, compare its configuration with the documentation for that version and account for active instances when changing templates or mappings.
Best Value
- Used Book in Good Condition
Frequently Asked Questions
Can this smart service fill a regular, non-interactive PDF?
No. The documented input is an Adobe Acrobat form with recognized form fields; a PDF that is only a static page does not supply those fields for substitution.
Can the service insert a signature image or logo into a form field?
Appian 24.3 says image fields are not supported as recognized form fields. The documentation cited here does not establish image replacement through this smart service.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
