You can test the document template to see an example of the resulting file from the Editor and Settings substeps of the Configure template step.
The first option – testing from the Editor substep – will help to see how your modifications to the template affect the result.
The second option – testing from the Settings substep – will show you how the finalized document looks after you’ve customized all the settings.
After that, you will see a panel with dropdown. There are three options for testing the template - Auto-generated form, Web forms and JSON.
The process automatically creates a testing form based on tokens from the template. You just complete it and press Test & Download button to download the result or Test & Preview to open the result in a new browser tab.
It’s possible to adjust the testing form by changing token types.
Important
Nesting tokens referring to the single object, not the collection of items, won’t work in the testing form. Thus, if you have some nesting tokens like {{company.name}}
, {{company.address}}
, get rid of a dot operator and change them to simple tokens like {{companyName}}
and {{companyAddress}}
. Alternatively, you can keep them and submit JSON for testing the template.
If you want to design your own form for the testing select the gear button in the dropdown menu.
It opens the Start process page where you can bind an existing form or create a new one clicking on the New form button with Plumsail Forms application.
Note
Please find additional information on creating custom Plumsail forms in the article.
Insert the JSON object representing the data for the document template and click on the Test & Download button. This type of testing may be useful if your document template is complex or you already have JSON output from third systems.
Note
Once you tested the template you can configure how to deliver the result document (email, OneDrive, etc). Just click the Save & Next button in the Configure template step.