Export of folders should support absolute and relative paths

Current Situation

When exporting inventory objects such as workflows from the Configuration view to an archive, the complete folder hierarchy is stored to the archive. Users cannot change this behavior.

Use Case 1

The export/import functionality can be used to backup and to restore inventory objects such as workflows. To restore the configuration the same folder hierarchy has to be present in the archive.

Use Case 2

The export/import functionality can be used to transport the scheduling objects to another JOC Cockpit instance. In this case a user may or may not want to import the same folder hierarchy.

Use Case 2a

The user wants to export the workflow /a/b/c/myWorkflow and import in another instance with the same folder hierarchy. Currently possible.

Use Case 2b

The user wants to export the workflow /a/b/c/myWorkflow and import in another instance to a different target folder, e.g. /target/a/b/c/myWorkflow. Currently possible.

Use Case 2c

The user wants to export the workflow /a/b/c/myWorkflow relatively as c/myWorkflow without the given parent folder. Currently not possible.

Desired Behavior

The user will decide if the folder hierarchy should be exported with absolute paths starting from the top-level folder, e.g. /a/b/c, or using relative paths starting from the selected folder, for example /c .