Deployment Notes

Catalyst by Zoho supports two distinct environments - Development and Production. This allows you to build, test, and validate your application in a sandboxed space before moving stable components to a live production environment.

To understand the differences and usage of these environments, refer to the Catalyst Environments help guide.

Below are key considerations when deploying Catalyst Signals to the production environment:

Deployment User Permissions

The user initiating the deployment in Catalyst must be an admin in the Zoho Publisher applications used. This is essential to ensure proper authorization between Catalyst Signals and Zoho publishers.

Deploy All Dependent Catalyst Components

If your Signals setup uses other Catalyst components, such as:

• Cloud Scale Services as publishers
• Serverless Functions or Circuits as targets
• Connections for webhook authorization

Ensure that all these dependent components are deployed together with Catalyst Signals.

Publisher Deployment Limit

You can deploy a maximum of 25 publishers to the production environment in a single deployment. This limit applies regardless of the publisher type supported in Signals.

Rules Are Locked in Production

In the production environment, you are permitted to enable or disable existing rules. However, you cannot create, edit, or delete rules directly in production. All structural changes to rules must be made in the development environment and then deployed.

For Zoho CRM Publisher, you can modify the organization associated with it during deployment. This allows you to switch from a Sandbox organization used in development environment to the corresponding Production organization during deployment.

Align Custom Components

Before deploying Catalyst Signals, ensure that all custom modules and custom fields used in your rules within the development environment are available in the production organization during deployment.