Work Order Import

Build the job description and notes from a template

5 min read Work Order Import

A template writes the job description or the notes from several values the parser read, in a layout you choose. You can build a description from the order number, the tenant's name and the access notes, where the parser would otherwise give one block of text.

The page has two parts, each with its own Save: the description and notes templates at the top, and Template reference fields under them.

Step by step

  1. Save the rules on the parser page first. The field list in the editor is built from the parser's saved rules.
  2. Open your parser from Parse, then Templates in the left menu.
  3. Turn on Enable project description, and write the template in Description.
  4. To put a value in, place the cursor and pick it from Select reference field. A chip such as {{Order number}} is added at the cursor.
  5. Do the same under Enable project notes and Notes if you want a notes template.
  6. Click Save. The page says "Parser templates saved."

The editor has bold, italic, underline, strikethrough, bullet and numbered lists, highlight, undo, redo and tables (add and delete rows and columns, merge and split cells, toggle a header column).

Pick a field from the list. A placeholder typed by hand, such as {{Order number}}, isn't recognised, because only the chip the list inserts matches.

Which fields the list offers

Template PDF parser Email parser
Description Direct fields with a saved rule (order number, project name, description, due date, site name, site address, customer and site contact values, cost centre totals), Custom fields, Data fields (data points on the description), Direct fields (Multiple Jobs) and Template fields Order number, Project name, Project description, Site name, Site address
Notes The same kinds of fields, and data points on the notes The same five fields

A Custom field placeholder reads as {{Custom: field name}}.

What the import does with a template

  • A template is used when its Enable switch is on and it isn't empty.
  • Each placeholder is replaced with the value the parser read for that field.
  • If none of the placeholders could be filled, the template is dropped and the description or notes are what the parser read.
  • A placeholder for a field that has no value stays in the text as it is.
  • For a description, when the template doesn't include Project description and the parser read one, the description goes first, then two line breaks, then the template.
  • For notes, when the parser read notes, they go first, then two line breaks, then the template.

A PDF parser's notes template is only used when the PDF gave at least one data point. An email parser's templates only use fields. They can't use data points.

Template reference fields

Template reference fields are extra values for a template, filled from the repeating columns of a PDF that lists several jobs. A column mapped to a template field has its rows joined with line breaks, and the result can be put into the description or notes. See Several jobs in one PDF in PDF parser rules.

  1. Click Add reference field. A blank row is added.
  2. Fill in Field Name, the name the field shows in the list and in the template.
  3. Fill in Field Reference, letters only. Anything else you type is removed.
  4. Add a Description if you want a reminder of what it is for.
  5. Leave the switch on for a field in use.
  6. Click the Save under the table. It says "Parser template fields saved."

Remove asks "Are you sure you want to remove this field?".

This Save only writes the reference fields, and the Save above only writes the two templates.

How it maps to Simpro and Fergus

The finished description goes into the Simpro job or quote Description, and the notes into Notes. On Fergus the description becomes the job's description and the notes become a note on the job. See Destination fields.

When it goes wrong

Save says "Could not update parser template fields. Check field names and references."

Every row needs a Field Name and a Field Reference, and no two rows can share a reference. A row you added and left blank stops the save, so fill it in or remove it.

The field I want isn't in Select reference field

The list is built from the saved rules, so a field you marked and haven't saved on the parser page isn't there. Email parsers offer five fields only. For a PDF, a field needs a rule in the parser to be listed.

The template doesn't change the description

None of the placeholders was filled, because the fields had no value in that work order, so the description is what the parser read. Run the PDF through Test on the parser page to see what was read.

The notes template does nothing on a PDF parser

A PDF parser only uses the notes template when the PDF gave at least one data point. Add a data point on Project Notes, or on any text the parser reads as a data point.

The placeholder shows in the description

The field had no value in that work order, so its placeholder stays in the text.

Formatting shows as code in a Fergus job

The editor saves formatting as HTML. The Fergus import turns line breaks into new lines but passes other tags through as text.

A filter changes a data point in a template

When a template inserts a data point, every filter on the parser is applied to its text, whichever field the filter is for. See Field filters.