Configuration Manager

Sub Banner

  • Overview
  • Sharing Access
  • Extraction
  • Injection
Overview
A flexible capability that enables the extraction and injection of any or of the following Zendesk configuration components:
  • Custom Fields
  • Triggers
  • Automations
  • Macros
  • Reports
  • Views
  • Widgets
  • Groups
Arbitrary configuration of components can be made and shared across Zendesk as either repeatable patters, development-to-production promotion, or back-ups. This includes a Group, Organization, and User data re-mapping tool, since rules can contain references to specific operational data ID's.

To support this facility a shared access to your Zendesk is established. This can be bidirectional or in only one direction.The principle of operation is to extract a configuration set of components from a source Zendesk, and then from the target request an injection from the source.



Sharing Access
The CloudSET Framework account management facilities enable the setting up of shared access to transportable configuration data sets extracted and stored on CloudSET. Typically shared access is set-up with the Zendesk Sandbox available to the Zendesk Plus Plan and above. However, shared access to extracted configuration data sets, can be granted to any other Zendesk.

This achieved by registering other Zendesk accounts, verified by supplying the target Zendesk's API token access credentials. The Configuration Manager license includes the sandbox, but a separate license is needed for other Zendesk accounts. Discounts are available for Hub & Spokes architectures.



Extraction
Fine granular control is available to name and define multiple set's of configuration components, down to individual rules. The configuration tool has a tab per configuration type, with handy select all or individual tick selections.

Naming and adding a description will help manage the configurations and support easy identification for injection pulls on shared configuration data access Zendesk's. Extracted configuration data sets can be deleted at any time from the source Zendesk.



Injection
From a target Zendesk, which has shared configuration data access to the source Zendesk, the Configuration Manager will section list all the configurations data sets shared by the registered source's.

Deploying a configuration data set will open up the Configuration Manager tool, the same common interface as the extraction usage, listing all the components that form the configuration data set. Automatic ID re-mapping, and dependency ordering will minimize re-mapping. However, if configuration set's make reference to rule elements that are not contained in the extraction set's or contain Organization or User reference (which is operational data), then a remapping facility is provided for each reference element. This is implemented as a drop-down selectable list for ease of set-up.

An option exist to overwrite existing configuration components, the default being to not overwrite. The exception being custom fields, since important background associations with their tags could be adversely effected.

An un-deploy function is also provided to remove a deployment due to untended use.  


 

Configuration Manager

Sub Banner

Configuration Manager

  • Overview
  • Sharing Access
  • Extraction
  • Injection
Overview
A flexible capability that enables the extraction and injection of any or of the following Zendesk configuration components:
  • Custom Fields
  • Triggers
  • Automations
  • Macros
  • Reports
  • Views
  • Widgets
  • Groups
Arbitrary configuration of components can be made and shared across Zendesk as either repeatable patters, development-to-production promotion, or back-ups. This includes a Group, Organization, and User data re-mapping tool, since rules can contain references to specific operational data ID's.

To support this facility a shared access to your Zendesk is established. This can be bidirectional or in only one direction.The principle of operation is to extract a configuration set of components from a source Zendesk, and then from the target request an injection from the source.



Sharing Access
The CloudSET Framework account management facilities enable the setting up of shared access to transportable configuration data sets extracted and stored on CloudSET. Typically shared access is set-up with the Zendesk Sandbox available to the Zendesk Plus Plan and above. However, shared access to extracted configuration data sets, can be granted to any other Zendesk.

This achieved by registering other Zendesk accounts, verified by supplying the target Zendesk's API token access credentials. The Configuration Manager license includes the sandbox, but a separate license is needed for other Zendesk accounts. Discounts are available for Hub & Spokes architectures.



Extraction
Fine granular control is available to name and define multiple set's of configuration components, down to individual rules. The configuration tool has a tab per configuration type, with handy select all or individual tick selections.

Naming and adding a description will help manage the configurations and support easy identification for injection pulls on shared configuration data access Zendesk's. Extracted configuration data sets can be deleted at any time from the source Zendesk.



Injection
From a target Zendesk, which has shared configuration data access to the source Zendesk, the Configuration Manager will section list all the configurations data sets shared by the registered source's.

Deploying a configuration data set will open up the Configuration Manager tool, the same common interface as the extraction usage, listing all the components that form the configuration data set. Automatic ID re-mapping, and dependency ordering will minimize re-mapping. However, if configuration set's make reference to rule elements that are not contained in the extraction set's or contain Organization or User reference (which is operational data), then a remapping facility is provided for each reference element. This is implemented as a drop-down selectable list for ease of set-up.

An option exist to overwrite existing configuration components, the default being to not overwrite. The exception being custom fields, since important background associations with their tags could be adversely effected.

An un-deploy function is also provided to remove a deployment due to untended use.  


 

Configuration Manager

Sub Banner

  • Overview
  • Sharing Access
  • Extraction
  • Injection
Overview
A flexible capability that enables the extraction and injection of any or of the following Zendesk configuration components:
  • Custom Fields
  • Triggers
  • Automations
  • Macros
  • Reports
  • Views
  • Widgets
  • Groups
Arbitrary configuration of components can be made and shared across Zendesk as either repeatable patters, development-to-production promotion, or back-ups. This includes a Group, Organization, and User data re-mapping tool, since rules can contain references to specific operational data ID's.

To support this facility a shared access to your Zendesk is established. This can be bidirectional or in only one direction.The principle of operation is to extract a configuration set of components from a source Zendesk, and then from the target request an injection from the source.



Sharing Access
The CloudSET Framework account management facilities enable the setting up of shared access to transportable configuration data sets extracted and stored on CloudSET. Typically shared access is set-up with the Zendesk Sandbox available to the Zendesk Plus Plan and above. However, shared access to extracted configuration data sets, can be granted to any other Zendesk.

This achieved by registering other Zendesk accounts, verified by supplying the target Zendesk's API token access credentials. The Configuration Manager license includes the sandbox, but a separate license is needed for other Zendesk accounts. Discounts are available for Hub & Spokes architectures.



Extraction
Fine granular control is available to name and define multiple set's of configuration components, down to individual rules. The configuration tool has a tab per configuration type, with handy select all or individual tick selections.

Naming and adding a description will help manage the configurations and support easy identification for injection pulls on shared configuration data access Zendesk's. Extracted configuration data sets can be deleted at any time from the source Zendesk.



Injection
From a target Zendesk, which has shared configuration data access to the source Zendesk, the Configuration Manager will section list all the configurations data sets shared by the registered source's.

Deploying a configuration data set will open up the Configuration Manager tool, the same common interface as the extraction usage, listing all the components that form the configuration data set. Automatic ID re-mapping, and dependency ordering will minimize re-mapping. However, if configuration set's make reference to rule elements that are not contained in the extraction set's or contain Organization or User reference (which is operational data), then a remapping facility is provided for each reference element. This is implemented as a drop-down selectable list for ease of set-up.

An option exist to overwrite existing configuration components, the default being to not overwrite. The exception being custom fields, since important background associations with their tags could be adversely effected.

An un-deploy function is also provided to remove a deployment due to untended use.  


 

Configuration Manager

Sub Banner

Configuration Manager

  • Overview
  • Sharing Access
  • Extraction
  • Injection
Overview
A flexible capability that enables the extraction and injection of any or of the following Zendesk configuration components:
  • Custom Fields
  • Triggers
  • Automations
  • Macros
  • Reports
  • Views
  • Widgets
  • Groups
Arbitrary configuration of components can be made and shared across Zendesk as either repeatable patters, development-to-production promotion, or back-ups. This includes a Group, Organization, and User data re-mapping tool, since rules can contain references to specific operational data ID's.

To support this facility a shared access to your Zendesk is established. This can be bidirectional or in only one direction.The principle of operation is to extract a configuration set of components from a source Zendesk, and then from the target request an injection from the source.



Sharing Access
The CloudSET Framework account management facilities enable the setting up of shared access to transportable configuration data sets extracted and stored on CloudSET. Typically shared access is set-up with the Zendesk Sandbox available to the Zendesk Plus Plan and above. However, shared access to extracted configuration data sets, can be granted to any other Zendesk.

This achieved by registering other Zendesk accounts, verified by supplying the target Zendesk's API token access credentials. The Configuration Manager license includes the sandbox, but a separate license is needed for other Zendesk accounts. Discounts are available for Hub & Spokes architectures.



Extraction
Fine granular control is available to name and define multiple set's of configuration components, down to individual rules. The configuration tool has a tab per configuration type, with handy select all or individual tick selections.

Naming and adding a description will help manage the configurations and support easy identification for injection pulls on shared configuration data access Zendesk's. Extracted configuration data sets can be deleted at any time from the source Zendesk.



Injection
From a target Zendesk, which has shared configuration data access to the source Zendesk, the Configuration Manager will section list all the configurations data sets shared by the registered source's.

Deploying a configuration data set will open up the Configuration Manager tool, the same common interface as the extraction usage, listing all the components that form the configuration data set. Automatic ID re-mapping, and dependency ordering will minimize re-mapping. However, if configuration set's make reference to rule elements that are not contained in the extraction set's or contain Organization or User reference (which is operational data), then a remapping facility is provided for each reference element. This is implemented as a drop-down selectable list for ease of set-up.

An option exist to overwrite existing configuration components, the default being to not overwrite. The exception being custom fields, since important background associations with their tags could be adversely effected.

An un-deploy function is also provided to remove a deployment due to untended use.