Use of Changes for Deployment, Export and Git Operations

Current Situation

Currently the operations to deploy, to export and to use Git integration do not know the Changes feature.

Desired Behavior

• Deploy
  • To use the Changes feature the modal window for deployment has to provide a new radio button"Changes" (default unselected) if the deployment operation is invoked at user folder level. The new radio button is not displayed when deployng from an individual object or from system folder level such as "Workflows".
    • if the radio button "Changes" is selected
      • the row "filter" (draft/deployed) and the row "handle recursively" have to be hidden
        • the current state of objects based on the inventory table will be used. Older versions will not be considered if Changes are used,
        • only items of the change will be processed, recursive handling makes no sense for Changes,
      • a drop-down list should be displayed for the user to select the change that should be deployed,
      • if the user selects the "Changes" radio button and selects a specific change, then all items of the change will be displayed.
      • For deployment the dependencies of the items of the change have to be processed - always - no user selection needed
        • for the API call use: "operationType": "DEPLOY".
• Export
  • To use the changes feature the modal window for export has to provide an additional radio button for "Export Type" named "Changes"
    • if the Changes radio button is selected
      • the rows "Object Types", "Filter Type", "Filter" and "Handle Recursively" have to be hidden.
        • "Object Types" is only available for radio button "Folders" and is not needed for Changes.
        • "Filter Type" is not needed as the relevant objects are already specified by the Change.
        • "Filter" is not needed as the current state from the inventory table will be used. older versions will not be taken into consideration for Changes.
        • use of the "Handle Recursively" with Changes makes no sense.
      • a drop-down list should be displayed to select the change to be deployed.
      • an additional checkbox "include dependencies" should be displayed - default: unselected.
      • when the user selects a change, then all items of the change must be displayed.
      • depending on the user's selection of "include dependencies" the dependencies of each item of the change have to be added to the export operation.
        • for the API call use: "operationType": "DEPLOY"
• Git
  • Store to Git Repository
    • To use the Changes feature, the modal window "Store to Git Repository" has to provide a new "Changes" radio button, default unselected. A second "Objects" radio button is displayed that implements the known behavior to store selected objects.
    • if the "Changes" radio button is selected,
      • the row "Deployed/Released", the checkboxes for "Draft" and "Valid Only" and the row "Handle Recursively" must be hidden.
      • a drop-down list should be displayed for the user to select the change to be deployed.
      • an additional checkbox "include dependencies" should be displayed - default: unselected.
      • when the user selects the change, all items of the change must be displayed.
      • depending on the user's selection of "include dependencies" the dependencies of each item of the change must be provided.
        • for the API call use: "operationType": "DEPLOY"

The Items of a change (and optionally their dependencies) are displayed to inform the user about the items that will be processed. No checkboxes are needed to un-/select any items. If it is desired to select or unselect items, then this has to be done in the configuration of the change.

The export- and the Git operation "store to repository" will always process all items of the change and optionally the dependencies of the items, too.

The "deploy" operation will always process all items of the change and related dependencies. For the "deploy" operation inclusion of dependencies is not optional.