📄️ Initialising a release tree
Follow these steps to initialise a release tree.
📄️ Dropping, moving, archiving a release tree, or starting over
The intended use of release folders in Delivery Manager is to have them all as children of the same root folder.
📄️ Creating a new release
Follow these steps to create a new release:
📄️ Reverting to the previous release
If you revert to the previous release, all deliverables of the current release are lost.
📄️ Renaming a release version
Delivery Manager does not allow you to rename a release version directly.
📄️ Defining a task
To define a task and have it checked:
📄️ Running a task
To run a task in the Delivery Manager tool interface (you can also run a task programmatically, see end of this article):
📄️ Defining a task category
To define a task category:
📄️ Loading deploy samples and added XSL samples
See also
📄️ Loading registry samples
To load registry samples:
📄️ Creating a deploy script
See also
📄️ Running a deploy script
See also
📄️ Creating a registry
For more information about registries, go to the Registries help topic.
📄️ Including an attachment
To include an attachment:
📄️ Blocking an attachment
You can block an attachment so that, as long as it remains blocked, it is not delivered when you release.
📄️ Writing an upgrade script
To write an upgrade script for the top-level application:
📄️ Archiving an upgrade script
You archive current upgrade scripts for user applications indirectly by moving to the next release version.
📄️ Restoring an upgrade script
Follow these steps to restore an archived script:
📄️ Setting a source variable
First check if the variable you want to create or set already exists as a predefined or user-defined source variable.
📄️ Setting a target variable
Target variables enable configuration by computer. For a complete overview of the tasks involved in configuring your application version, go to the Configure help topic.
📄️ Comparing data
For the concept of comparing metadata or appdata, go to the Compare help topic.