Cx Assistant Logo
Blog
Toda la ayuda
App móvil

Scripts

16 secciones · Actualizado el 2026-10-03 · También disponible en Markdown

Esta guía está en inglés por ahora. La versión en español aparecerá aquí cuando esté lista.


What are scripts

Scripts are structured test and inspection procedures — for example commissioning scripts, checklists, or acceptance tests. A script is organised into sections of items; each item can ask for a result (such as pass/fail), data readings, and notes, and can carry evidence like photos and files. Scripts finish with signatures and a completion sign-off.

On mobile you find scripts and execute them in the field: fill results, capture photo evidence with the camera, sign, and complete.

Opening the Scripts screen and finding a script

Open the drawer (hamburger icon or swipe right from the left edge) and tap Scripts.

The list shows script cards, each with a progress bar and a status chip. To find a script:

  • Type in the search bar; results update after a short pause.
  • Tap a status chip in the horizontal filter row to show only scripts in that status.

The list loads more as you scroll (infinite scroll); pull down to refresh. Tap a card to open the script runner.

Why there is no create button on mobile

You cannot create scripts from the phone — this is by design. Scripts are authored on the web app or generated with the assistant, where the full template and editing tools live. The mobile app is for finding scripts and executing them in the field: filling results, attaching evidence, signing, and completing.

The script runner — layout

Tap a script to open the runner. It shows:

  • Sections with sticky headers; each header shows how many items in the section are done (for example 3/8).
  • The items of the current section, each with its result control, data fields, notes, and evidence.
  • A footer signatures panel.
  • A bottom bar with previous/next section buttons, an overall progress bar with percentage, and a contextual action button (Complete script, Sign off to complete, or Reopen depending on the script's state).

Filling in results, data fields, and notes

For each item in the runner:

  • Result — tap the outcome that applies (for example pass or fail; the options are defined by the script).
  • Data fields — enter the readings or values the item asks for. Out-of-range or blank values may raise warnings, but record what you actually measured — never adjust a reading to silence a warning.
  • Notes — add free-text observations.

Everything you enter is saved automatically as you go.

Attaching evidence — photos and files

Each item has an Evidence area where you can attach proof:

  • Take a photo with the camera.
  • Pick images from your photo library.
  • Attach files.

Tap an attached photo to view it full-screen in the lightbox. To remove a piece of evidence, use its remove control. Evidence saves automatically with the rest of the item.

Signatures — draw to sign

The signatures panel sits in the runner's footer. Tap your signature slot to open the signature pad and draw your signature with your finger, then confirm.

Signing requires the scripts.sign permission and applies to slots assigned to you or unassigned slots; signing any slot regardless of assignment requires scripts.sign.override. Ask a project admin if your slot won't accept a signature.

Completing, signing off, and reopening a script

The action button in the runner's bottom bar changes with the script's state:

  • No button — some items are still not done. Finish them first.
  • Sign off to complete — every item is done but a required signature is still missing. Tap it to jump to the signatures panel, then sign.
  • Complete script — every item is done and all required signatures are in. Tap it to finish the script.
  • Reopen — unlock a completed script for further editing.

When you tap Complete script, the app checks the script first:

  • Values that need a look: if a data field was left blank or holds a value outside its expected range, a "Complete this script?" message lists them ("Left empty", or "outside" the expected range). Tap Cancel to go back and fix them, or Complete anyway to freeze the script as it is. Completing locks the script.
  • Steps that are not finished: a "This script isn't finished" message lists steps with no result and missing sign-offs. These cannot be skipped — resolve them, then try again.

This needs an up-to-date version of the app. On an older version the phone only shows "Failed to complete script" without listing anything. In that case, fill in or correct the data fields and try again, update the app, or complete the script in the web app, which shows the same list and the same Complete anyway choice.

Once completed, the script becomes read-only until reopened.

Autosave and live updates from teammates

The runner saves automatically, so there is no Save button to remember. Each entry is first kept on your phone and then sent to the server — straight away when you have a connection, later when you do not.

The indicator in the script's header tells you where your entries are:

  • Syncing… — entries are being sent.
  • On this phone · 3 — that many entries have not reached the server yet. Tap it to open the Sync screen.
  • Sent — everything has just been sent.
  • Offline — nothing is waiting and you have no connection.

When the indicator shows nothing, everything has been sent. Older versions of the app show "Saving… / Saved" instead.

The runner is also live — while you are connected, if a teammate edits the same script from another device, their changes appear on your screen in real time.

Working offline — running a script with no signal

You can run a script on your phone with no connection (needs an up-to-date version of the app). There is nothing to switch on: it works the same way in every project.

What works with no signal, on a script that is on your phone:

  • Results, data fields, and notes.
  • Evidence — photos from the camera or your library, and files. They show on the step with a small cloud badge until they are uploaded.
  • Signatures.
  • Completing the script. The app runs the same checks as when you are connected and shows the same messages; the script then shows "Completed — waiting to sync" until the completion is sent.

Everything you enter is kept on the phone, also if you close the app, and is sent by itself when the connection returns. The header shows "On this phone" with the number of entries still waiting. When you open a script with no connection, a line under the header says "Showing the copy on this phone".

What needs a connection:

  • Opening a script that is not on your phone yet. With no signal the Scripts list shows only the scripts kept on this phone.
  • Reopening a script whose completion has already been sent. A completion that is still waiting on your phone can be taken back with Reopen.
  • Removing evidence that has already been uploaded. Evidence still waiting on the phone can be removed: tap it and choose Remove from this phone.
  • Seeing teammates' changes — they appear once you are connected again.

Keeping scripts on your phone before going to a site with no signal

A script opens offline only if a copy of it is on your phone (needs an up-to-date version of the app). There are two ways a copy gets there:

  • Automatically — every script you open while connected stays on the phone for a week.
  • Keep on this phone — a script you mark this way stays until you unmark it.

Before you leave for a site with no signal:

  1. While you still have a connection, open the drawer and tap Scripts.
  2. Swipe the script's card to the left and tap Keep on this phone. The label changes to Kept on this phone. You can also open the script and tap the phone icon in its header.
  3. Check that the card shows "Available offline". Repeat for every script you will need.
  4. Open the drawer and tap Sync to confirm nothing is still waiting from earlier work.

With no connection, the Scripts list shows "Showing the scripts kept on this phone." and lists only those copies; the search bar and status chips still filter them.

To free a copy, swipe its card left and tap Remove from this phone (unmark Kept on this phone first). A script with changes that are not sent yet cannot be removed — it stays on the phone until they are sent. This removes only the copy on your phone; the script itself is not deleted.

There is no button to download every script of a project at once — mark the ones you need.

The Sync screen — what is still waiting to be sent

The Sync screen shows what your phone has not sent yet (needs an up-to-date version of the app).

How to open it:

  • Open the drawer and tap Sync. The row shows a number when something is waiting or needs your attention.
  • Or, in a script, tap "On this phone" in the header.

What it shows:

  • A summary at the top: "Syncing…", the number of changes on this phone, or "Everything is sent"; the time of the last sync; and "Waiting for signal" when you have no connection.
  • Sync now — sends what is waiting straight away. It is unavailable with no connection or when there is nothing to send.
  • Needs attention — items that could not be sent as they are and wait for your decision. Shown only when there are any.
  • On this phone — each script with changes or photos still waiting, and when it last synced.
  • Scripts on this phone — copies with nothing waiting. Each has a Keep on this phone switch; a copy with the switch off also has Remove from this phone.

Tap a script's title to open it. If it belongs to another project, the app switches to that project first.

You rarely need Sync now: waiting changes are sent by themselves when the connection returns, when you open the app, and when you come back to it. The list covers all your projects, not only the one you are in.

Needs attention — conflicts and items that could not be sent

Sometimes a change made offline cannot simply be sent — for example because a teammate answered the same step in the meantime (needs an up-to-date version of the app). Nothing is discarded for you: the change stays on your phone and the item appears under Needs attention on the Sync screen. In the script, a line under the header shows how many items need your attention; tap Review to go there.

Each card says what happened and offers the choices that apply:

  • "Someone else answered this step while you were offline." — the card shows your value (Mine) and theirs (Theirs), with who changed it and when. Send mine replaces their value with yours. Keep theirs drops your change. Later leaves it for now.
  • "This signature was decided by someone else." — Keep theirs or Later.
  • "This script was completed by someone else. Your changes cannot be sent." or "This script was deleted." — Discard all my changes is the only choice.
  • A step, field, or signature that no longer exists in the script, or no permission to sign or complete — Discard.
  • A completion that was refused because steps are unfinished — the card lists them. Finish them in the script, then tap Retry, or Discard the completion.
  • A completion with blank or out-of-range values — the card lists them. Complete anyway, or Discard and fix the values first.
  • "Could not send" — the app tried several times and stopped. Retry or Discard.
  • "This photo could not be uploaded." — Retry or Discard.

Discard removes that change from your phone for good, so note the value down first if you still need it.

Completed scripts are locked

Once a script is completed it becomes read-only: results, data, notes, evidence, and signatures can no longer be changed. This protects the integrity of the signed record.

If something genuinely needs correcting, use the Reopen action in the runner's bottom bar, make the change, and complete the script again.

Who can see and execute scripts — permissions

Scripts are admin-gated by default — only Project Admins hold the scripts permissions unless your project grants them to other roles:

  • scripts.read — see the scripts list and open scripts.
  • scripts.execute — fill in results, data, and evidence.
  • scripts.sign — sign slots assigned to you or unassigned; scripts.sign.override signs any slot.
  • scripts.create / scripts.update / scripts.delete — manage scripts (authoring happens on the web).

The project owner can always do everything. If you can't see the Scripts screen or can't edit a script, ask a project admin to grant your role the needed permissions.

Script won't save or complete — troubleshooting

If the runner misbehaves:

  • "On this phone" stays in the header — your entries are safe on the phone but have not been sent yet. Check your internet connection; they are sent by themselves when it returns, or open the Sync screen and tap Sync now. On an older version of the app that shows a stuck "Saving…" instead, check your connection and update the app.
  • A line under the header says items need your attention — tap Review and decide each one on the Sync screen.
  • "This phone could not keep your change. Restart the app and try again." — the entry was not saved. Close and reopen the app, then enter it again.
  • No Complete script button — some items are not done yet, or the button reads Sign off to complete because a required signature is missing.
  • "Failed to complete script" with no list — you are probably on an older version of the app, and a data field is blank or outside its expected range. Update the app to see the list and the Complete anyway choice, fix the values and try again, or complete the script from the web app.
  • Can't edit anything — the script is completed and locked; use Reopen. If Reopen is unavailable, you may lack the needed scripts permissions (admin-only by default).
  • List empty or erroring — pull down to refresh, clear search and status filters, and confirm with a project admin that your role has scripts.read.

¿No lo encontraste?

Cuéntanos qué intentabas hacer. Soporte responde en dos días hábiles, y la guía se corrige si no estaba clara.

Contactar soporteAbrir la app