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 4 Next »

Manual to perform a manual migration of features from Herzum Approval on-premises to Herzum Approval for Cloud. The following is a manual that you may find useful at the moment for migrating the tool's features to a cloud instance. This manual focuses on the features that are mapped to the cloud, and the correct order to perform the imports. Features obtained from Herzum Approval on-premises version 5.4

  1. Global Configuration Section

    1. Approval General Settings

      1. Approval Conditions Settings: for now, the variable is set to true, it is not necessary to change the value.

      2. Approval delegation: not implemented, must not pass the value of the variable.

      3. Require Authentication: not required, the application does not need a credentials confirmation.

    2. Approval Superusers:

      1. Super Approver: Add all users within the field.

      2. Approval Log Superuser: functionality is not yet developed. Do not pass the value.

      3. Approval Expression Superuser: Add the user that you have saved in the field.

      4. Conditional Rule Superuser: Add the user you have entered the field. The "Grant Browsing Permission Automatically" option is not available for now.

    3. Automatic Workflow Transition:

      1. Responsive workflow transition: this functionality is not yet developed, there is no need to pass the variable.

      2. Minimum required approbations and rejections: this functionality is not yet developed, there is no need to pass the variable.

    4. Approval Actions:

      1. Reject Approval Action: you must pass the value that is set in your instance.

      2. Abstain Approval Action: pass the value that is currently set in your instance.

      3. Lock Reversing Approval Actions: pass the value that is currently set in your instance. If the value is true, add the users to the selector.

    5. Approval Display Options:

      1. Actions on Command-Bar: Do not pass value, functionality is not developed yet.

      2. View Approval Flow: Do not pass value, functionality is not developed yet.

      3. Web panel Expanded: Do not pass value, functionality is not developed yet.

      4. View Percentage Number: pass the value that is set.

      5. Display Approvals: Do not pass value, functionality is not developed yet.

      6. Display Large action Buttons: pass the value that is found. In case, this is enabled. Also, add the users to the selector.

      7. Request Button Label: Pass the value found in the text field.

      8. Customize Field Labels: pass the value found in each of the text fields.

    6. Approval Logs via Comments: Do not pass values, functionality is not implemented.

    7. Approval History:

      1. Enable Approval History: Do not pass the value, the functionality is not implemented.

      2. Show Event Grouped by:  add all values to the selector. The only value that is not available for now is Source Status - Start Date.

      3. Hide Events: add all values to the selector. Options not available for now are "Automatic Transitioning", "Automatic Notification", and "Approvals Notification".

      4. Expand or Collapse Rows: select the appropriate value.

      5. Apply Filter: Do not pass, functionality not yet developed.

      6. Fields Name: Select the value that corresponds to the field.

      7. Customize History Fields: Fill the fields with the corresponding values.

    8. Approval Email: Do not pass values, functionality is not implemented.

  2. Conditional Rules: Add all the conditions you have registered in your instance. If any of the conditional rules you have added has a "custom field" as an evaluator user, please select another evaluator user. The custom field is not developed yet.

  3. Approvals: Create all the approvals that you currently have created. Note that the current version of Herzum Approval for Cloud does not allow the creation of approvals for multiple properties, only for single properties. Also, the menu with the options in the approvals is not available currently.

  4. E-mail Templates:

    1. Approval request tab:

      1. Default Approval Request e-mail template: edit the template if necessary to modify the default attributes of the template.

      2. Add all the e-mail templates that have been created in the instance with each of its characteristics. Do not forget to select the Project or the conditional rule if you need to add it to your template.

    2. Approval reply tab:

      1. Default Approval Request e-mail template: edit the template if necessary to modify the default attributes of the template.

      2. Add all the e-mail templates that have been created in the instance with each of its characteristics. Do not forget to select the Project or the conditional rule if you need to add it to your template.

    3. Service desk Approvals: Do not pass information regarding these templates. This tab has not yet been implemented in the cloud version.

  5. Permissions:

    1. Approval Request: add the selected projects if any, otherwise add the permissions based on project and issue type and select the correct properties.

    2. Configure Approvals for Single Issue: add the selected projects if any, otherwise add the permissions based on project and issue type and select the correct properties.

    3. Approval Menu: Do not pass any of the selected data. Not yet implemented in Herzum Approval for Cloud.

  6. Recipients:

    1. Approval request: Add each of the properties you have set.

    2. Approval Reply:

      1. Default Notification Scheme: Edit the default scheme if necessary.

      2. Notification Schemes: Add each of the notification schemes created and add each of the configured properties.

  7. Approvals Mappings: Add the mappings you have created for your projects, issue types, and transitions, select the approvals you are going to use for the approvals mappings. Once you have created the approval mapping, don't forget to modify your workflow, and add the validator, "Herzum Approval Validator" to each of your transitions. If you need help, you can check the following link https://herzummarket.atlassian.net/l/cp/mpeBngA0

    1. If any of your approvals mapping has any configuration, please do not forget to add them to your approvals mappings. Note that the features available for configuration are as follows:

      1. Abstain

      2. Automatic Approval Request notification

      3. Approval Reply Notification Scheme

      4. Automatic workflow transition

      5. Condition enabling/disabling the approvals

      6. E-mail templates

      7. Minimum Required approbations/rejections unconditioned

      8. Minimum Required approbations/rejections conditioned

      9. Optional approvals

      10. Require Approvals Comments

      11. Sequential approval

      12. Super Approvers

      13. Transition on rejection

    2. If you have any configuration in the single issues approval, don't forget to make the configuration, if necessary, otherwise, the issue will not have the same properties as your instance.

  8. Troubleshooting and Support: feature not yet implemented in Herzum approval for Cloud

  9. Manage Delegation: Add all the delegations you have created in your instance. Keep in mind that you must have the projects, issue types and users in the instance to avoid inconsistencies later.

10.   Language Packs: feature not yet implemented in Herzum approval for Cloud

11.   Anonymization: functionality not yet implemented in Herzum approval for Cloud

12.   Advanced: functionality not yet implemented in Herzum approval for Cloud

13.   Audit Log: functionality not yet implemented in Herzum approval for Cloud

Configurations that cannot be mapped in Herzum Approval for Cloud

  • Global Configuration Section

    • Approval General Settings

      • Approval Conditions Settings

      • Approval delegation

      • Require Authentication

    • Approval Superusers

      • Approval Log Superuser

    • Automatic Workflow Transition:

      • Responsive workflow transition

      • Minimum required approbations and rejections

    • Approval Display Options:

      • Actions on Command-Bar

      • View Approval Flow

      • Web panel Expanded

      • Display Approvals

    • Approval Logs via Comments

    • Approval History:

      • Enable Approval History

      • Apply Filter

    • Approval Email

  • Approvals Multiple Properties

  • E-mail Templates:

    • Service desk Approvals Templates

  • Permissions:

    • Approval Menu Tab

  • Approvals Mappings:

    • Advanced settings:

      • Notify approvals via comments

      • Decision Automation

      • Approval Request Email Automation

  • Troubleshooting and Support

  • Language Packs

  • Anoymization

  • Advanced

  • Audit Log

  • Gadgets

  • Custom Fields

  • Approval History

Important Note: Perform the following process before performing a migration to avoid having problems with your workflows in the cloud instance

You should follow the instructions below:

  1. In your version of Approval On-Premises Server/Data Center, you should go to the application administration.

  2. Select the option "Troubleshooting and Support".

  3. Click on the tab "Workflow Cleaning".

  4. Click on the "Remove Approval Condition" button (This process will remove all the conditions that are related to Approval from your workflows).

  5. After the process is done, you will be able to perform your migration without the conditions in your workflows

To restore the conditions in your workflows after performing a migration, you must follow the following process

  1. In your version of Approval On Premises Server/Data Center, you should go to the application administration.

  2. Select the option "Troubleshooting and Support".

  3. In the first tab, "Integrity Checker", select the Recovery option.

  4. Click on the option "Recovery Jira Data impacting app functionalities".

  5. Finally, click on the "Recovery" button.

  6. Wait for the process to finish correctly to continue using Approval on-premises as normal.

  • No labels