Change an inbox's defaults when the order number, name or description matches
A condition says "when the work order looks like this, use these values instead of the defaults". It is how one inbox handles several kinds of work order, such as sending one client's work orders to a different customer or a different status.
Before you start
The values a condition can change come from Simpro Defaults or Fergus Defaults, so set those first. The Simpro lists need the inbox's Simpro company saved.
Step by step
- Open the inbox from Inbox, then Conditions.
- Click Add condition.
- Under Query fields, click Add query field. Choose a Field, choose equals or includes, and type the text in the box beside it.
- Fill in only the values this condition should change, under Simpro Values or Fergus Values.
- Click Save. The page says "Inbox conditions saved."
The Save button only shows while the inbox has at least one condition.
Query fields
| Setting | Choices |
|---|---|
| Field | Order number, Project name or Project description. |
| Operator | equals needs the whole value to be the text. includes needs the text to appear in it. |
- Capitals count. "Ac" does not match "AC".
- A condition with several query fields matches only when every one matches.
- A query field with no text never matches, and neither does one for a field the work order doesn't have.
- A condition with no query fields is skipped.
- Choose a Field and an operator on every query field. A query field with either missing passes whenever it has text, so the condition matches more work orders than you meant.
Simpro Values
Project name override, Job Status, Job Stage, Salesperson, Manager, Tags, Private Notes, Response Time and Service template for cost centres and items. Each is ignored when left blank, and replaces the matching default when set. Tags and Private Notes replace what was there, and do not add to it.
Fergus Values
Job title override, Customer, Job type and Job notes. Customer overrides the default customer for that work order. Job notes are added to the job's note after the default note and the work order's own notes.
How conditions combine
Conditions run in the order they were added, and they can't be reordered. Every condition that matches applies. When two matching conditions set the same value, the later one wins. A value one condition leaves blank is not touched by it.
The Service template only applies when a new job or quote is created. A Response Time set by a condition is applied after the due date is worked out, so it doesn't feed Generate Due Date from Response Time on Rules.
A Fergus parser that makes quotes always makes a job of type Quote, whatever Job type a condition sets.
When it goes wrong
My condition never applies
Check the query fields against what the parser read, on the work order's record on the Dashboard. The comparison is exact on capitals, and equals needs the whole value.
A condition changed more than I expected
Every matching condition applies, and the later one wins where two set the same value. Make each condition's query fields specific enough that only one matches.
I need to test something other than the order number, name or description
A condition can only test those three fields. A work order that differs in another way, such as its site, can't be told apart here. Use Locations for site differences.
I removed my last condition and it came back
Removing the last condition leaves the page with "No conditions found." and no Save button, so the removal isn't saved. Remove its query fields instead and click Save. A condition with none is skipped.