Applies to: All customers.
Most Katapult customers import a job. You can also start a job blank or seed it from a KML/KMZ file.
Step 1: Select your job
Selecting your job. Before you can collect anything, the job has to exist in Cloneable. Importing pulls your poles, aerial path, and existing attributes out of Katapult (or a map file) and turns them into a Cloneable job you open on the app in the field. It only happens once per job, in the web portal.
Note: Who actually imports the job depends on your organization's workflow and who has web portal access. At some companies the fielder imports each job before heading out; at others an admin or org admin imports jobs ahead of time, so the job is already waiting for you when you open the app. Check with your team so you know which applies to you. If you do not use the web portal, an admin handles this part and you pick the job up on the app.
Import from Katapult (the common path)
This happens across two web tools: first in Katapult to prep your data, then in the Cloneable web portal to pull it in. The two systems connect over an API that Cloneable initiates. The connection is set up once at the organization level: if your organization has already connected Katapult you will not be asked for a key, and on your organization's very first import the wizard asks for the Katapult API key once and saves it for everyone.
First, prep your data in Katapult:
Open your job in Katapult and verify all poles are present.
Make sure your aerial path is in place, whether it is a new build or an overlash.
Get everything clean before you move on; the import carries over what is already in Katapult.
Then, in the Cloneable web portal (app.cloneable.ai):
Sign in (see Start here).
From the dashboard, choose to add a job and select Import from Katapult.
Select your configuration. Choose the configuration your administrator set up for this customer. The name is specific to your organization and can change.
Pick the Katapult job. A searchable picker pulls the job list from your Katapult account. Type part of the job name to filter. You can rename the job here or leave the Katapult name.
Review and create. A summary screen ("Review and Create") appears. Confirm the details and choose Create Job & Start Import.
Start a blank job or import a KML/KMZ (non-Katapult paths)
When you add a job you can also choose Create Blank Job (it still needs a configuration). A blank job starts empty; you populate it either by adding poles in the field (Step 10) or by importing a KML or KMZ file. On KML/KMZ import you upload the file, choose the job it belongs to, map the file's feature types to your data-object templates so its points become poles (and so on), then preview the result before importing. This is the path for organizations that do not use Katapult, including DDS-based KML workflows.
Whoever imports jobs at your organization, note that changing the field form itself is never a field task; if a form or dropdown needs to change, that is a configuration change your administrator makes (see Start here and Configuration).
Common issues
API hiccups happen occasionally. If something imports wrong, do not panic.
If a job imports incorrectly, set its status to Cancelled and redo the import. Your administrator can clean up cancelled jobs on the admin side.
Step 2: Set the job status
When a job finishes importing, Cloneable sets it to Draft. Moving it to In Progress signals that you are ready to head to the field.
From the dashboard, open Jobs, find your job (its status shows Draft in amber), click the status, and choose In Progress.
Before you do, glance at the map to confirm the import looks right (poles present, aerial path sensible). Fix anything off first.
What the status means. Status is a communication tool for the team. It is purely a visibility flag; changing it does not trigger an export, notification, or lock in the app. See the job-status table in Appendix and reference for the full four-status table. (The first state is stored internally as "pending" and shown as "Draft.")
If you do not use Katapult
Applies to: Non-Katapult customers.
If your organization does not use Katapult, you skip the Katapult prep and the API key entirely. You still start from the dashboard, but you create the job yourself instead of importing it from Katapult.
Create the job. From the dashboard, choose to add a job, then pick how it starts:
Create Blank Job. The job starts empty (it still needs a configuration). You populate it by adding objects in the field, or by importing a map file as below.
Import a KML or KMZ file. Upload the file, choose the job it belongs to, map the file's feature types to your data-object templates (so its points become poles, and so on), then preview the result before importing.
Either way, the job is built on a configuration. If you need one first, an administrator sets it up, and a map file can seed the configuration too (see Build a configuration from a KML file).
Then continue exactly like everyone else. Set the job status as described in Step 2 above, then head to the field. Everything from Step 3 on is the same whether or not you use Katapult.