Create a process

A process associates an automation package—in a specific version—to an environment. It is the “executable unit” of Zoan Cloud: what an agent runs when it receives an order, whether manual or programmed.

Package  "billing"  v1.2.0
        +
Entorno  "Producción"
        =
Proceso  "Facturación diaria"   ← esto es lo que se ejecuta

Separating package (what you designed) from process (how it runs and where) is what allows you, for example, to have the same package running with version 1.3.0 in Test and 1.2.0 in Production, each with their own credentials.

Requisitos previos

Before creating a process you need:

• A package published in your tenant. If you don’t have it yet, go to Publish and Version.
• An environment where to create the process. See Environments.

Steps

1. Open the environment in which you want to create the process.
2. Go to the Processes tab.
3. Click New Process.
4. Enter a descriptive name (e.g. Facturación diaria).
5. Select the package you want to run.
6. Select the version of the package.
7. Click Create.

The process is ready. Now you can run it manually or associate a trigger to it to run automatically.

Process states

Estado	Description
active	The process can receive executions
inactive	Desactivado — no puede ejecutarse

You can enable or disable a process at any time from the list. Turning it off is useful for pausing an automation without losing its settings or history — for example, while you fix a problem or during a system maintenance window you automate.

Update version

When you publish a new version of the package, the process does not adopt it on its own: it continues using the version it had configured. To update it:

1. In the list of processes, click the edit icon for the process.
2. Select the new version of the package.
3. Guarda.

Executions in progress are not affected

Changing the version only applies to new runs. Those that are already running end with the version they had. This allows you to update without interrupting an ongoing process.

Promote with control

Pointing the Production process to a new version is, in practice, “going to production”. Verify that same version first in the Testing process. See Promote between environments.

Next steps

• Publish and version — prepare the package.
• Run manually — launch a run on demand.
• Triggers — automate when it runs.