Sharing and Deploying a Configuration

Sub Banner

If you have registered to share one or more Zendesk accounts or registered your Sandbox to use CloudSET Services (1), it is possible to deploy the use of a configuration created within one of your shared accounts (2).

Doing so makes it possible to reuse any customizations, extensions,  capabilities and settings that have previous been created and tested, without the need to manually reenter in each of your Zendesk accounts.

Locate Deployable Configurations

A list of deployable configurations (3) for the current Zendesk account can be located via CloudSet Framework sidebar icon (1) within the Configurations tab (2).

Select the deploy link (4) to initiate the process involved in the deployment of all components of the configuration.

Review Components and Confirm Deployment

For each type of component (1), select the type label (2) to open up a list of all instances that will be deployed as part of the configuration (3).

Some components included within the configuration will require one or more parameters to be set before deploy,ent can take place (1).

For example a trigger might send a notification to a User or Group in the source Zendesk that doesn't exist in the target Zendesk and when this occurs it will be necessary to select an existing recipient to complete the action in the trigger (2).

Select the "Deploy" button (3) to commit the deployment of the configuration and all associated components into your Zendesk account.

Check this box (4) to allow any existing components to be overwritten with the contents of this configuration where a match is found.

A deployment log is presented showing details of successfully deployed components (1) and error messages for any failures (2).

As can be seen in the example above, the deployment of components such as triggers, automation's and macros will fail if the conditions or actions refer to any custom fields and/or option values that don't exist in the target Zendesk and haven't been successfully deployed as part of the configuration (2).

*Note: it isn't possible to overwrite an existing Ticket Field and so if any are found with a matching name in the Target Zendesk an error will be reported confirming the failed attempt to deploy the field.

Confirm Successful Deployment

Following successful deployment all components of the configuration should now be installed within your Zendesk account, e.g. custom Ticket Fields (3).

*Note: the deployment process has no control on the position and order of the components and so it might be necessary to reorder items post deployment (4).

Sharing and Deploying a Configuration

Sub Banner

Sharing and Deploying a Configuration

If you have registered to share one or more Zendesk accounts or registered your Sandbox to use CloudSET Services (1), it is possible to deploy the use of a configuration created within one of your shared accounts (2).

Doing so makes it possible to reuse any customizations, extensions,  capabilities and settings that have previous been created and tested, without the need to manually reenter in each of your Zendesk accounts.

Locate Deployable Configurations

A list of deployable configurations (3) for the current Zendesk account can be located via CloudSet Framework sidebar icon (1) within the Configurations tab (2).

Select the deploy link (4) to initiate the process involved in the deployment of all components of the configuration.

Review Components and Confirm Deployment

For each type of component (1), select the type label (2) to open up a list of all instances that will be deployed as part of the configuration (3).

Some components included within the configuration will require one or more parameters to be set before deploy,ent can take place (1).

For example a trigger might send a notification to a User or Group in the source Zendesk that doesn't exist in the target Zendesk and when this occurs it will be necessary to select an existing recipient to complete the action in the trigger (2).

Select the "Deploy" button (3) to commit the deployment of the configuration and all associated components into your Zendesk account.

Check this box (4) to allow any existing components to be overwritten with the contents of this configuration where a match is found.

A deployment log is presented showing details of successfully deployed components (1) and error messages for any failures (2).

As can be seen in the example above, the deployment of components such as triggers, automation's and macros will fail if the conditions or actions refer to any custom fields and/or option values that don't exist in the target Zendesk and haven't been successfully deployed as part of the configuration (2).

*Note: it isn't possible to overwrite an existing Ticket Field and so if any are found with a matching name in the Target Zendesk an error will be reported confirming the failed attempt to deploy the field.

Confirm Successful Deployment

Following successful deployment all components of the configuration should now be installed within your Zendesk account, e.g. custom Ticket Fields (3).

*Note: the deployment process has no control on the position and order of the components and so it might be necessary to reorder items post deployment (4).

Sharing and Deploying a Configuration

Sub Banner

If you have registered to share one or more Zendesk accounts or registered your Sandbox to use CloudSET Services (1), it is possible to deploy the use of a configuration created within one of your shared accounts (2).

Doing so makes it possible to reuse any customizations, extensions,  capabilities and settings that have previous been created and tested, without the need to manually reenter in each of your Zendesk accounts.

Locate Deployable Configurations

A list of deployable configurations (3) for the current Zendesk account can be located via CloudSet Framework sidebar icon (1) within the Configurations tab (2).

Select the deploy link (4) to initiate the process involved in the deployment of all components of the configuration.

Review Components and Confirm Deployment

For each type of component (1), select the type label (2) to open up a list of all instances that will be deployed as part of the configuration (3).

Some components included within the configuration will require one or more parameters to be set before deploy,ent can take place (1).

For example a trigger might send a notification to a User or Group in the source Zendesk that doesn't exist in the target Zendesk and when this occurs it will be necessary to select an existing recipient to complete the action in the trigger (2).

Select the "Deploy" button (3) to commit the deployment of the configuration and all associated components into your Zendesk account.

Check this box (4) to allow any existing components to be overwritten with the contents of this configuration where a match is found.

A deployment log is presented showing details of successfully deployed components (1) and error messages for any failures (2).

As can be seen in the example above, the deployment of components such as triggers, automation's and macros will fail if the conditions or actions refer to any custom fields and/or option values that don't exist in the target Zendesk and haven't been successfully deployed as part of the configuration (2).

*Note: it isn't possible to overwrite an existing Ticket Field and so if any are found with a matching name in the Target Zendesk an error will be reported confirming the failed attempt to deploy the field.

Confirm Successful Deployment

Following successful deployment all components of the configuration should now be installed within your Zendesk account, e.g. custom Ticket Fields (3).

*Note: the deployment process has no control on the position and order of the components and so it might be necessary to reorder items post deployment (4).

Sharing and Deploying a Configuration

Sub Banner

Sharing and Deploying a Configuration

If you have registered to share one or more Zendesk accounts or registered your Sandbox to use CloudSET Services (1), it is possible to deploy the use of a configuration created within one of your shared accounts (2).

Doing so makes it possible to reuse any customizations, extensions,  capabilities and settings that have previous been created and tested, without the need to manually reenter in each of your Zendesk accounts.

Locate Deployable Configurations

A list of deployable configurations (3) for the current Zendesk account can be located via CloudSet Framework sidebar icon (1) within the Configurations tab (2).

Select the deploy link (4) to initiate the process involved in the deployment of all components of the configuration.

Review Components and Confirm Deployment

For each type of component (1), select the type label (2) to open up a list of all instances that will be deployed as part of the configuration (3).

Some components included within the configuration will require one or more parameters to be set before deploy,ent can take place (1).

For example a trigger might send a notification to a User or Group in the source Zendesk that doesn't exist in the target Zendesk and when this occurs it will be necessary to select an existing recipient to complete the action in the trigger (2).

Select the "Deploy" button (3) to commit the deployment of the configuration and all associated components into your Zendesk account.

Check this box (4) to allow any existing components to be overwritten with the contents of this configuration where a match is found.

A deployment log is presented showing details of successfully deployed components (1) and error messages for any failures (2).

As can be seen in the example above, the deployment of components such as triggers, automation's and macros will fail if the conditions or actions refer to any custom fields and/or option values that don't exist in the target Zendesk and haven't been successfully deployed as part of the configuration (2).

*Note: it isn't possible to overwrite an existing Ticket Field and so if any are found with a matching name in the Target Zendesk an error will be reported confirming the failed attempt to deploy the field.

Confirm Successful Deployment

Following successful deployment all components of the configuration should now be installed within your Zendesk account, e.g. custom Ticket Fields (3).

*Note: the deployment process has no control on the position and order of the components and so it might be necessary to reorder items post deployment (4).