Finishing a configuration, however you built it, is not the end of a form, it is the moment Cloneable builds your account. This is what actually appears, what you will be able to see, and how to tell it worked.
There are four ways to start a configuration from the New Configuration menu, and this collection covers three of them:
Blank configuration. Build it from scratch by hand.
From a KML file. See What you need before you start (map file).
From a Katapult model. See What you need before you start (Katapult).
From a Cloneable file. This restores a configuration someone already exported and sent you, rather than designing a new one. See Update an existing configuration.
What gets made
When you finish creating a configuration, however you built it, Cloneable shows you its progress as it works. It builds:
Workflows, which are what happens when a fielder starts working on one of your objects.
Custom types, which are the sets of options behind your fields. A pick list of anchor eye sizes is a custom type.
Data object templates, which are the shapes your data lands in. One for poles, one for spans, one for each custom object you brought across.
Then it saves the configuration itself.
Your configuration name is stamped on all of it
This is where naming your configuration carefully, whichever route you took to create it, pays off. Every template it creates carries your configuration name on the end, so you get a readable name and an internal one alongside it. A configuration called Q1_2024 produces a pole template shown as Pole - Q1_2024, stored as pole_q1_2024.
That is what makes two configurations liveable side by side. Without it you would have several templates all called Pole and no way to tell which belonged to which import.
The review screen is your receipt
If you're importing, whether from a Katapult model or a map file, the last step before you commit lists what Cloneable is about to make: your configuration name, how many data object templates, how many node mappings are configured, and how many workflows. One real import produced eight templates and two workflows.
Read those numbers and remember them. They are the only summary you get, and they are the fastest way to spot that you missed something. If you expected poles, spans, anchors and three custom types and the count is small, go back rather than forward.
If you're building from scratch, there is no summary screen like this to check. A blank configuration always creates the same fixed set of workflows and templates, so there is nothing to miscount.
What you will be able to see afterwards
Your day-to-day view of what your configuration created is:
Your configuration, in your configurations list, where you can reopen it and change your choices.
Your data objects, once crews start collecting. This is where the records themselves live, and you can narrow the list down to the ones that came from a particular template.
Your files, for anything attached.
The map, which is where the whole thing becomes real: your object types, with the icons you set up.
What Cloneable manages rather than you
The underlying pieces building a configuration creates, the custom types, the templates themselves, and the workflows, are not part of your day-to-day view. You will not find them in your navigation, so there is no point hunting for them.
What that means in practice: when you want one of those changed, the way to do it is to reopen your configuration and change your selections there, or to ask us.
Nothing is missing from your account. Those pieces exist and do their job. Your configuration is simply the place you steer them from.
How to check it worked
Create a job and confirm your new configuration is offered in the list. If it is not there, it did not finish.
Open the map on that job and confirm your object types are present and drawn with the icons you set up. If a type looks wrong here, check its icon rule before assuming something went wrong. See Set up your map icons.
If you imported, from Katapult or a map file, check one object type you brought across as a custom object, since those are the ones most easily left switched off at the mapping step.
If something looks missing
An element you left out at the elements step, or a type you left unticked in the unmapped list, will not be there. Both are fixable without starting from scratch.
If you built your configuration from a Katapult model, you can usually reopen your Katapult selections from the actions menu on the configuration. If that option is not offered, or you built the configuration from a map file, build it again as described in Build your configuration from a map file.
If you built from scratch, there is nothing to have left out at this stage, since a blank configuration always creates the same fixed set. To add more than that, edit your configuration directly. See Set up your configuration, stage by stage.
Next