2019.2

Table Of Contents
Secondly, the pURL must contain the data that Workflow needs in order to create the
personalized response (be it a web page or other file). For instance, creating a personalized
page that shows a client's invoice may require the Invoice Number to be present in the pURL,
which is then used by Workflow to retrieve the invoice data, generate the invoice in PDF or
HTML format using a template, and then return it to the browser.
The data needs to be included in the URL. In this URL, for example:
http://www.example.com/MakePDF?uuid=8c33eda8-72af-11e5-8bcf-feff819cdc9f, a unique ID
is passed as parameter. Parameters end up as key-value pairs in the request XML file. In the
Workflow process you may use a Set Job Infos and Variables task to assign a value from that
XML to a variable (see Data Selections, in Workflow's Online Help).
Finally, you need another Workflow process to provide the pURL to the user, in an email, for
example, or in a QR code. This process must add the necessary data to the pURL. That data
should be available through the Data Model used in the template.
Tip
In Workflow, you may make use of the system variable %U to create unique strings.
Inserting a pURL
Assuming that the necessary data and Workflow processes are available, here's how you insert
a personalized URL in a template.
1. Open the template and find or enter the text that you want to turn into a link.
2.
Select the text, right-click it and select Wrap in Span....
3. Give the span an ID, for example: get_pdf_link. Click OK.
The text Download PDF, wrapped it in a span with the ID get_pdf_link, would look
like this on the Source tab:<span id="get_pdf_link">Download
Invoice</span>.
4. With the span selected, click on 'ID' on the Attributes pane (click on the field name, not the
field itself). This will insert a script that has this ID as selector, and open it in the script
editor.
Since it's dynamic, inserting a personalized URL always implies writing a script, however
small and simple. For a basic explanation of scripts, see "Writing your own scripts" on
page853.
Page 825