Deploying projects

Learn how to deploy projects.

Before you begin

Projects cannot be deployed to destination environments running an older version than the source environment. Ensure that the destination environment is on the same or a higher version before proceeding with the deployment.

Key points to note

  • The configuration values entered during deployment are not saved until the deployment process is completed. This is to make sure that only finalized configurations are applied, reducing the risk of partial or incorrect setups.
  • From version 12.0.1 onwards, if a deployment does not include any configurations, then no configurations are displayed in the deployment wizard. In this case, you must create new accounts.
  • Configurations that include default authorization are not published. You must manually add and reconfigure in the deployment wizard.

About this task

By default, projects are set to private mode when deployed. If you are deploying for the first time, an administrator or developer can do it, and they become the owner of the project. Subsequent deployments can be done based on project access privileges.

Procedure

  1. Go to the Projects dashboard.

    If a project has a new deployment available, a rocket icon indicates deployment availability and a New tag identifies projects that are yet to be deployed.

  2. Click the project card that has the deployment message.
    A confirmation messages appears.
  3. Click Yes.
    The Deployments page appears to list all deployments.
  4. Click Deploy.
    The Configure Accounts page appears.
  5. In the Parameters & Variables page, configure parameters.
    1. In the Configure parameters section, check the parameters to be configured. If the message No updated data appears, no new parameters require input.
    2. In the Configure variables section, check Variables to be configured. If the message No updated data appears, no new variables require input.
    3. Review Previously configured parameters and variables to confirm existing values.
    4. To overwrite any value with the source environment value, select the Overwrite with source value checkbox.
    5. Click Next. The Accounts page appears.
  6. Optional: Provide account configurations.

    In Account details, select an account from the unconfigured accounts for the specified connector and click Edit to provide values for any dependent lookup fields to run the relevant actions. After you save the details, the account is moved under the Configured accounts section.

    Or

    You can keep the previous account configurations as they are or specify a different account and provide dependent lookup field values to run the relevant action.

    Click + to create a new account.

    Note: Click Next to skip this step. If you do so, you must manually configure the relevant accounts before you run the workflow or flow service.
  7. Click Next.
    The Triggers page appears.
    Note: You must configure all triggers that are displayed to proceed to the next step.
  8. Provide trigger configurations.

    Select an account from the existing accounts for the specified connector and provide values for any dependent lookup fields to run the relevant actions. After you save the details, the account is moved under Configured accounts section.

    Or

    You can keep the previous account configurations as they are or specify a different account and provide dependent lookup field values to run the relevant action.

    Click + to create a new account.

  9. Click Next.
    The Parameters page appears.
  10. Click Edit to provide a parameter value.
    If the parameter value is changed at source before redeployment, it appears as a masked value.
  11. Click View to view the masked value.
  12. Provide the parameter value.

    If you want to change the parameter value, click Edit to enter a new value and if you want to preserve the existing value, select the Overwritten parameter with source value checkbox.

  13. Click Deploy.

    The project that is published by another tenant is successfully deployed in your tenant. If you check your Projects dashboard, you can see the project card that is associated with the deployed project and use the integrations.

What to do next

  1. Verify the project configurations. When publishing and deploying a project, certain assets are not automatically included. Ensure that all necessary assets are manually added and properly configured in the target environment after deployment.
  2. If the deployed workflow contains a webhook, its associated payload data is not retained. Add the webhook payload data when you configure the deployed workflow.
  3. To enhance data security, deployed workflows using a webhook default to Tenant Credentials for authentication, regardless of the method configured during design. However, you can modify the webhook authentication method during deployment to suit your specific requirements
  4. Test and monitor your integrations in the target environment after successful deployment.