Overview of Configurations

Sub Banner

The CloudSET Extension Framework enables the ability to share configurations of customizations, extensions,  capabilities and settings between each of your Zendesk accounts.

This allows for thorough testing of the configuration within your Sandbox* before deployment within your primary Zendesk accounts and/or reuse configurations amongst each of your Zendesk shared accounts*, without the need to manually replicate and reapply the changes.

Configurations also provide the opportunity to deploy pre-configured collections of Zendesk components as enhancements to generic Zendesk functionality.

 

The above diagram shows a contextual overview of the process and architecture involved:

  1. Collections of reusable components in a Zendesk account (Source Zendesk) can be packaged up as configurations ready for deployment to one or more alternative Zendesk accounts (Target Zendesk)
  2. Once created, details of all configurations together with their contents are stored centrally within the CloudSET database from where they can be accessed by all authorized Zendesk accounts
  3. Before a configuration can be deployed a share agreement must be established for the Target Zendesk using the credentials for the Source Zendesk (API Token)
  4. Once a share has been registered in the Target Zendesk account, all configurations created in the Source Zendesk will be visible and available for deployment
  5. Selecting the option to deploy a configuration will retrieve all contained components from the CloudSET Database and create equivalents in the Target Zendesk account

*Note: the Target Zendesk might be a Sandbox or alternative Zendesk account in use by your organization or a customer you are supporting. However, it is also possible to deploy a configuration into the Source Zendesk within which it was created should there be a need to recover components that have been deleted or erroneously updated.

Locate the CloudSET Configuration Management Services

Once the CloudSET Extension Framework has been registered, the CloudSet Configuration Management Services can be located from under the CloudSet Framework sidebar icon (1), within the Configurations tab (2).

From here it is possible for your Administrator to perform the following (depending upon your level of subscription):

  • deploy or undeploy the use of Global template configurations that have been pre-prepared for use by all CloudSet users to support and enhance generic Zendesk functionality (7).

 

Overview of Configurations

Sub Banner

Overview of Configurations

The CloudSET Extension Framework enables the ability to share configurations of customizations, extensions,  capabilities and settings between each of your Zendesk accounts.

This allows for thorough testing of the configuration within your Sandbox* before deployment within your primary Zendesk accounts and/or reuse configurations amongst each of your Zendesk shared accounts*, without the need to manually replicate and reapply the changes.

Configurations also provide the opportunity to deploy pre-configured collections of Zendesk components as enhancements to generic Zendesk functionality.

 

The above diagram shows a contextual overview of the process and architecture involved:

  1. Collections of reusable components in a Zendesk account (Source Zendesk) can be packaged up as configurations ready for deployment to one or more alternative Zendesk accounts (Target Zendesk)
  2. Once created, details of all configurations together with their contents are stored centrally within the CloudSET database from where they can be accessed by all authorized Zendesk accounts
  3. Before a configuration can be deployed a share agreement must be established for the Target Zendesk using the credentials for the Source Zendesk (API Token)
  4. Once a share has been registered in the Target Zendesk account, all configurations created in the Source Zendesk will be visible and available for deployment
  5. Selecting the option to deploy a configuration will retrieve all contained components from the CloudSET Database and create equivalents in the Target Zendesk account

*Note: the Target Zendesk might be a Sandbox or alternative Zendesk account in use by your organization or a customer you are supporting. However, it is also possible to deploy a configuration into the Source Zendesk within which it was created should there be a need to recover components that have been deleted or erroneously updated.

Locate the CloudSET Configuration Management Services

Once the CloudSET Extension Framework has been registered, the CloudSet Configuration Management Services can be located from under the CloudSet Framework sidebar icon (1), within the Configurations tab (2).

From here it is possible for your Administrator to perform the following (depending upon your level of subscription):

  • deploy or undeploy the use of Global template configurations that have been pre-prepared for use by all CloudSet users to support and enhance generic Zendesk functionality (7).

 

Overview of Configurations

Sub Banner

The CloudSET Extension Framework enables the ability to share configurations of customizations, extensions,  capabilities and settings between each of your Zendesk accounts.

This allows for thorough testing of the configuration within your Sandbox* before deployment within your primary Zendesk accounts and/or reuse configurations amongst each of your Zendesk shared accounts*, without the need to manually replicate and reapply the changes.

Configurations also provide the opportunity to deploy pre-configured collections of Zendesk components as enhancements to generic Zendesk functionality.

 

The above diagram shows a contextual overview of the process and architecture involved:

  1. Collections of reusable components in a Zendesk account (Source Zendesk) can be packaged up as configurations ready for deployment to one or more alternative Zendesk accounts (Target Zendesk)
  2. Once created, details of all configurations together with their contents are stored centrally within the CloudSET database from where they can be accessed by all authorized Zendesk accounts
  3. Before a configuration can be deployed a share agreement must be established for the Target Zendesk using the credentials for the Source Zendesk (API Token)
  4. Once a share has been registered in the Target Zendesk account, all configurations created in the Source Zendesk will be visible and available for deployment
  5. Selecting the option to deploy a configuration will retrieve all contained components from the CloudSET Database and create equivalents in the Target Zendesk account

*Note: the Target Zendesk might be a Sandbox or alternative Zendesk account in use by your organization or a customer you are supporting. However, it is also possible to deploy a configuration into the Source Zendesk within which it was created should there be a need to recover components that have been deleted or erroneously updated.

Locate the CloudSET Configuration Management Services

Once the CloudSET Extension Framework has been registered, the CloudSet Configuration Management Services can be located from under the CloudSet Framework sidebar icon (1), within the Configurations tab (2).

From here it is possible for your Administrator to perform the following (depending upon your level of subscription):

  • deploy or undeploy the use of Global template configurations that have been pre-prepared for use by all CloudSet users to support and enhance generic Zendesk functionality (7).

 

Overview of Configurations

Sub Banner

Overview of Configurations

The CloudSET Extension Framework enables the ability to share configurations of customizations, extensions,  capabilities and settings between each of your Zendesk accounts.

This allows for thorough testing of the configuration within your Sandbox* before deployment within your primary Zendesk accounts and/or reuse configurations amongst each of your Zendesk shared accounts*, without the need to manually replicate and reapply the changes.

Configurations also provide the opportunity to deploy pre-configured collections of Zendesk components as enhancements to generic Zendesk functionality.

 

The above diagram shows a contextual overview of the process and architecture involved:

  1. Collections of reusable components in a Zendesk account (Source Zendesk) can be packaged up as configurations ready for deployment to one or more alternative Zendesk accounts (Target Zendesk)
  2. Once created, details of all configurations together with their contents are stored centrally within the CloudSET database from where they can be accessed by all authorized Zendesk accounts
  3. Before a configuration can be deployed a share agreement must be established for the Target Zendesk using the credentials for the Source Zendesk (API Token)
  4. Once a share has been registered in the Target Zendesk account, all configurations created in the Source Zendesk will be visible and available for deployment
  5. Selecting the option to deploy a configuration will retrieve all contained components from the CloudSET Database and create equivalents in the Target Zendesk account

*Note: the Target Zendesk might be a Sandbox or alternative Zendesk account in use by your organization or a customer you are supporting. However, it is also possible to deploy a configuration into the Source Zendesk within which it was created should there be a need to recover components that have been deleted or erroneously updated.

Locate the CloudSET Configuration Management Services

Once the CloudSET Extension Framework has been registered, the CloudSet Configuration Management Services can be located from under the CloudSet Framework sidebar icon (1), within the Configurations tab (2).

From here it is possible for your Administrator to perform the following (depending upon your level of subscription):

  • deploy or undeploy the use of Global template configurations that have been pre-prepared for use by all CloudSet users to support and enhance generic Zendesk functionality (7).