Jump to: navigation, search

Exporting Rules Templates

You can export rule templates to an .xml file. Rule templates are stored in the repository as separate assets so they can be used by multiple rule packages. The rule templates are not part of the rule package themselves; the rule package refers to the rule templates that it needs.

It is not necessary to import or export the rule templates if you are importing or exporting to the same system (for example, backing up or restoring a rule package) or to an equivalent system (for example, a lab versus a production environment). However, if you are moving the rule package to a new system or sending it to Genesys for service, you should export both the rule templates and the rule packages so that, when imported, all referenced templates are available in the target system.

Refer to Exporting Rule Packages for details on how to export rule packages.

To export a rule template, you must have View Template permission and Read access for the Script objects that represent the templates being exported.

To export a rule template (up to 8.5.302.xx)

  1. In the Explorer Tree, select the Tenant tab.
  2. Click Export Rule Templates. The .xml file is generated.
You must export all versions of the templates so that on the target system, the repository can be reconstructed with the same version numbering as on the source system.
Be careful when changing templates or template versions, as it could affect existing rules. For example, an existing rule might use a condition that does not exist in a different version of the template. Consult with the rule template developer to ensure that you are choosing the correct templates and versions for your application.

To export a rule template (from 8.5.303.xx)

  1. In the Explorer Tree, select the Tenant tab.
  2. Click Export Rule Templates.
  3. Select the individual template or templates that you wish to export. All versions of the selected templates will be exported in order to maintain the version sequence at the target system.
  4. The .xml file is generated.

Comment on this article:

blog comments powered by Disqus
This page was last modified on 28 April 2017, at 04:07.