Where: your configuration, under Data Templates. Also step 5 of the Katapult import wizard, if you are setting one up for the first time.
Needs: the Org Admin role.
When you finish: a crew can look at the map and see which poles are done, started and untouched without opening any of them.
Icons are how a crew reads a job without tapping anything. Done right, a fielder sees which poles are finished, started and untouched. Done badly, every pole looks the same.
Coming from Katapult? You may not need to build anything
If your configuration came from a Katapult model, Cloneable can bring your Katapult map across as it is: the same icons, colours and rules, on the web and in the iPhone app. Turn on Use Katapult's map style and icons at step 5 of the Katapult import. [CONFIRM: step]
Use this article when you want to:
build icons for a configuration that did not come from Katapult
add a state Katapult does not show, such as measured or already exported
change an imported icon
Imported icons are ordinary icons once they arrive. You edit them the same way as any other, from the template.
Two ways in
Icons belong to a data template. Whether you built them or they came across from Katapult, they are stored on the template, which is why there are two routes to the same editor and you are never locked out of changing them later.
From your configuration, any time. This is the one to use once you are set up.
Open your configuration
Go to Data Templates, step 2 of the five configuration steps
Click Edit on the template you want, for example your pole template
On the template page, click Edit icon
During the Katapult import, will be at step 5. Same-ish editor, same result. Turn on Use Katapult's map style and icons here to bring your Katapult map across instead of building icons.
If you are already past the import, Go to Edit selections, then step 5.
Build the icons for one object type
Pick a template. The list shows how many icons each has. Anything sitting at one icon has only its default, and looks identical in every state.
Set the base icon, the resting state of an untouched pole. A point icon has a label, a shape, a stroke colour and a fill colour, with a live preview. Fill can be none; stroke cannot. Line types have a label, one colour and a line style, and no fill.
Write labels that say what the icon means, not what it looks like. Measured still makes sense in a year. Red circle will not.
Add rule icons for the states that matter. Each gets its own look and a condition: a field and a test.
Order the rules. The first rule that matches wins, so the most specific rule goes on top. The base icon shows only when no rule matches, and its position in the list does not matter.
Run the simulator on every rule.
Confirm.
Adding to imported Katapult icons. Put your own rule above the imported ones if it should win, for example Measured over Katapult's default pole. The first rule that matches is the one crews see.
The tests you can use
Test | Use it for |
has a value | Something has been filled in at all |
is empty | Something is still missing |
is | An exact match |
is not | Anything except one value |
is more than / is at least | Numbers above a threshold |
is less than / is at most | Numbers below a threshold |
Which tests you are offered depends on the field you pick. This catches people out, so it is worth knowing before you start.
Field you are testing | Tests you get |
Photos, files, location, and other multi-part fields | has a value and is empty only |
Numbers | All eight |
Everything else, including text and status | is, is not, has a value, is empty |
So you can say "this pole has a photo", but not "this pole has more than two photos". If the test you expected is missing, the field type is why.
has a value and is empty do most of the work, because most of what a crew wants to see is whether a thing has been done yet. You can stack conditions with all-of or any-of, and Cloneable reads the result back in plain language: Done has a value AND Pole Class is "3". If that sentence does not describe what you meant, the rule is wrong.
A rule that never fires looks exactly like one you forgot to write. If a rule tests a field the object does not carry, the phone silently moves to the next rule with no error anywhere. The simulator is the only place the difference shows, so use it on every rule. Edit as JSON is available for fiddly rules; it checks the rule is well formed, not that it is right.
A pattern that works
Icon | Condition | Means |
Base | none | Untouched |
Rule 1 | measurement data has a value | Measured |
Three icons, and a crew lead can see the state of a whole job from the map. That is the bar: not pretty icons, but a screen that answers "what is left" without opening a single pole.
If you imported Katapult's icons, add these as rules above them rather than replacing them.