Export/import for management of tag groups

Current Situation

• Tags and Tag Groups are managed per JS7 environment.
• When users export scheduling objects such as workflows that are assigned tags, then on import to the target environment the following checks are performed:
  • If the Tag does not exist in the target environment, then the Tag will be created and the Tag Group will be created if it does not exist. The relationship between Tag and Tag Group will be created and will be persisted.
  • If the Tag is assigned a Tag Group in the target environment, then the existing relationship will be maintained and will not be updated from a Tag Group assignment in the import file.
  • If the Tag exists in the target environment but is not assigned a Tag Group, then this non-existent relationship remains unchanged and the Tag's relationship will not be updated from a Tag Group assignment in the import file.

Desired Behavior

• Users would like to manage Tags and Tag Groups across JS7 environments.
• The export operation offers a checkbox to include all Tag Groups and related Tags to the export file.
  • If the checkbox is not used, then only Tags and Tag Groups assigned the exported scheduling objects will be added to the export file. The behavior explained by JOC-1998 applies.
  • If the checkbox is used, then a file tags.json is created at root-level in the export file.
• The import operation offers a checkbox to update relationships between Tags and Tag Groups from the import file.
  • If the checkbox is not used, then the behavior explained by JOC-1998 applies.
  • If the checkbox is used then existing relationships between Tags and Tag Groups are updated from the tags.json file available with the import file.