2019.2

Web pages
Apart from the form, there are lots of ways to modify the template. You could add text, images
and other elements (see "Content elements" on page628) and change the layout of the web
pages (see "Styling and formatting" on page741).
Once the template is ready, send it to Workflow (see "Sending files to Workflow" on page457).
Finally, in Workflow, adjust the process: double-click the Create Web Content task to open it,
and select the new template. This is only necessary when the file name has changed.
Send the Workflow configuration to the server (see Saving and sending a Workflow
Configuration in Workflow's Online Help).
Note
If you want the web pages to be responsive (have a different layout on screens of
different sizes), you could add Media Queries to the style sheet (see Media Queries on
W3schools), or start a new template with a wizard; see "Creating a Web template with a
Wizard" on page541.
Workflow configuration
Serving the two web pages could also be achieved using separate processes, but in fact it is
more efficient to have a single process, as activity needs to be monitored for each process.
In real life the submitted data will probably not be stored in the Data Repository, but used
differently. This means that the Push to Repository task will need to be replaced by the
appropriate tasks, but that won't change the way the submitted data is retrieved.
To see how the current process does that, double-click the Push to Repository task and take a
look at the task's properties. The xmlget() function, used in the Value fields, is a data selection
function (see Data Selections). Data selection functions are available in many plugins, in any
field that accepts variables. Try right-clicking a field and select Get Data Location from the
contextual menu. (See also: Variable Task Properties.)
For general information about processes in Workflow see About Processes and Subprocesses,
in the Online Help of Workflow.
Page 207