Herzum Approval Documentation
Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »



Overview

The Export Approval Data functionality allows to export Approval Configurations in order to import them in another Jira instance.

The sys admin will be able to replace the existing configuration or merge them with the one that already exist.

Notice that the capability to export Approval Data includes all data except the following:

  • Herzum Approval History
  • Herzum Approval Approval Configuration for Single Issue
  • Pending approval requests
  • Herzum Approval Mail handler
  • Herzum Approval Services
  • Herzum Approval Validators
  • Herzum Approval Post Functions

Export Procedure

On running an Approval Data export, the app will search referenced entities by usernames (for user key data) and by Name (for other entities, e.g. Project Name, custom field Name, etc.).

In order to allow the operation to succeed the app must be able to identify the username for each referenced user key and the Name or other entities, e.g. Project Name, custom field Name, etc.

If the procedure doesn't complete successfully a message appears:


Export Approval Configurations doesn't completed successfully.  Run a Dependencies Analyzer in order to review detected errors and fix that.


If the procedure complete successfully, the Approval Data will be saved into the file ApprovalDataExport.zip file.

The ApprovalDataExport.zip file will include also some information regarding the export options, export date, export author, system info, app version into the ExportInfo.xml file.

At the end of the procedure you can click Download Exported File, to download the file to your browser.

Approval Data export files by example

Export Table: AO_D195E9_CONDITIONAL_RULE  into CONDITIONAL_RULE_XML xml file

(info) If the USER_EVALUATOR field is set with a custom field, the app retrieves the custom field name in order to save it into the field USER_EVALUATOR_NAME.

(info) If the USER_EVALUATOR field is set with a user key, the app retrieves the username in order to save it into the field USER_EVALUATOR_NAME.

The app will insert into the CONDITIONAL_RULE_XML xml file the following data:

SELECT "CONDITIONAL_NAME", "CONDITIONAL_RULE", "ID" AS ID_EXPORT, "USER_EVALUATOR", USER_EVALUATOR_NAME

FROM public."AO_D195E9_CONDITIONAL_RULE";

Export Table: AO_D195E9_LANGUAGE_PACK" into LANGUAGE_PACK_XML xml file

The app will insertinto the LANGUAGE_PACK_XML xml file the following data:

SELECT "DESCRIPTION", "ENABLED", "ID" AS ID_EXPORT , "LOCALE", "MODIFIED_DATE", "MODIFIED_USER", MODIFIED_USER_NAME "NAME"

FROM public."AO_D195E9_LANGUAGE_PACK";

Export Table: AO_D195E9_LANG_PACK_KEY_VAL into LANGUAGE_PACK_ KEY_VAL_XML xml file

The app will insert into the LANGUAGE_PACK_ KEY_VAL_XML xml file the following data:

SELECT "ID" AS ID_EXPORT, "LANGUAGE_PACK_ID as AS LANGUAGE_PACK_ID_EXPORT ", "PROPERTY_KEY", "VALUE"

FROM public."AO_D195E9_LANG_PACK_KEY_VAL";

  • No labels