Test and publish
Before a real person receives the form, you can fill it in yourself with sample data and confirm that Zoan Cloud would accept the answer. Once you are happy with it, you publish it as a new version.
Preview
Section titled “Preview”The Vista previa (Preview) shows the form exactly as the person answering will see it, at desktop size or Móvil (Mobile), with rules and calculations working. Files are not uploaded: they are simulated.
- Datos de ejemplo (Sample data): the values of the inputs the task would be created with. They are proposed automatically from each input’s type; change them to try other cases (a high amount, a customer without an email).
- Respuesta a simular (Answer to simulate): the Decisión (Decision) and a Comentario (opcional) (Comment, optional), to test the rules that depend on the decision.
- Validar aquí (Validate here): checks the answer in your browser, instantly.
- Probar envío (Test submission): sends the draft and your data to Zoan Cloud, which checks them as if it were a real task, without creating anything. It tells you whether El servidor aceptaría esta respuesta (The server would accept this answer), with Ver lo que guardaría (See what it would store: the answer exactly as the flow, assistant or robot would receive it), or why not: «La tarea no se podría crear con estos datos de ejemplo» (The task could not be created with this sample data) or «El servidor no la aceptaría» (The server would not accept it), with each error. It also confirms whether the portal and the server agree, and which server date was used to evaluate date rules.
- Restablecer (Reset): goes back to the initial sample data.
Publish a version
Section titled “Publish a version”Click Publicar (Publish). Zoan Cloud saves and checks the draft and shows you:
- If there are errors, what to fix before publishing.
- A summary of the changes compared with the previous version (new, removed or changed fields, sections and inputs), or Primera versión (First version).
- The warnings that do not block publishing.
- Notas de la versión (opcional) (Release notes, optional), so the team knows what changed.
Click Publicar versión N (Publish version N). A published version never changes: tasks already created keep theirs.
Who uses which version
Section titled “Who uses which version”| Who uses it | Which version |
|---|---|
| Flow (person step) | The version pinned in the step. The canvas warns you when there is a newer one, and you adopt it with Actualizar a v_N_ (Update to v_N_). |
| Assistant (approval) | The version that was current when the assistant was published. |
| Robot (Create Human Task) | The current one when each task is created, unless the robot pins formVersion. |
That way, changes that break nothing reach robots on their own, and flows and assistants adopt them when you decide.
Incompatible changes
Section titled “Incompatible changes”Some changes can break whoever uses the form without pinning a version, usually a robot:
- A new required input, or an input that becomes required.
- A removed input or one with a different type.
- An answer field removed or renamed, or with a different type.
- A field that always arrived and may now be missing (for example, because you gave it a visibility rule).
- Rules that use a new decision.
If your change is one of these, when publishing you will see Este cambio no es compatible con la versión N (This change is not compatible with version N), with the list of robots that used the form in the last 30 days without pinning a version, and the flows and assistants pinned to an earlier version (those are not affected). To publish, check Entiendo que es un cambio incompatible (I understand this is an incompatible change). Before that, update those robots or have them pin the version.
Next steps
Section titled “Next steps”- Use a form: in a flow, in an assistant and from a robot.