workflow:template-editor

Template editor

The Template Editor is a design environment that has everything you need to build custom forms for your specific workflows. It’s easy enough to use that you can do it by yourself, no coding or technical skills required.

Click Edit template on the workflow page to access the Template Editor.

The editor window consists of three parts. The first column contains the fields that you may add to a template. The second column is a list of fields already constituting the form template. The third column shows selected field settings.

In this example, the Vendor field is selected and its properties are displayed. To change a property, enter a new value and save the template.

Adding and Removing Fields

To add text, amounts, dates, drop-down lists or other elements to a form template, drag the appropriate field from the left-hand panel onto the template.

Click this new field. Its properties are displayed on the right. Adjust the validation, default value, formatting, and other settings as necessary and save the template.

To delete a field from a template, click the trashcan next to it's name and save the template.

Pyrus has user-defined and system-defined fields. The user-defined fields contain information that users will enter in a new form. The system fields are automatically calculated by Pyrus as the workflow progresses. See Form Field Types for more details.

Field Order

The fields are arranged on the form in the same order as they are arranged on the template. To change the order, just drag a field to a new position and save the template.

All the fields you add to the template are displayed in the form, but sometimes you’ll need to hide fields from view. One way to do this it to put the fields you want hidden in the Processing section of the form template.

Let’s say your website contains an online form that visitors use to send help requests. Some of the fields are filled out by the requestor, like name, email address, and the issue at hand. Other fields are filled out by a help desk specialist, like designating the person responsible or identifying the type of the request. In the example above, we put these fields in Processing. They will not be seen to the person filling in the form, but will remain visible to the help desk specialist.

You can also hide fields under a Multiple choice field. For more details on how to do that, see the article Form field types.

Was this article helpful?

Yes, thanks! No, I have a question