The Release Management Dashboard promotes releases across Unqork environments. Move applications between environments (for example, Staging to QA or Pre-Production to Production). Releases can group one or more applications, including their modules and Data Collections. Detailed release information keeps promotions organized, and rolling back to a previous release keeps a working application available while troubleshooting.
The UDLC Toolkit provides a powerful set of application lifecycle tools. By default, these tools are available in Staging, QA, and UAT environment levels. Administrators can promote UDLC tools to Pre-Production and Production environment levels. If promoted, clients are responsible for repromoting new versions of the UDLC Toolkit when released to lower environment levels. Before doing so, obtain approval from the organization's information security team. Tools like the Flexible Data Manager let end-users access and modify , which might include sensitive data or PII. Unqork recommends following the principle of least privilege for all roles, especially Designer and Express administration, and monitoring admin account activity.
Empty applications cannot be promoted. The application must include modules and/or workflows with entry points to promote.
Access Requirements
This tool requires specific role access in Environment Role RBAC or WSRBAC (Workspaces Role-Based Access Control).
- Environment Roles (without WSRBAC): Creator roles can view all data in this tool.
- WSRBAC: Creators must have at minimum Can View permissions to access this tool, and Can Manage permissions for the appropriate workspaces.
Release Dashboard
After accessing the tool, the Release Dashboard displays a table of releases organized by creation date, with the most recent at the top. Each entry shows the environment, version number, and promoted application. The table displays 10 entries at a time. Use the pagination buttons to see more.
Filters
Use filters to find a specific release. Any combination of filters can be used. Results update automatically as text is entered.
| Filter | Description |
|---|---|
| Apps | Filter by application. |
| Environment | Filter by environment. |
| Version | Enter a release version number. |
| Start Date | Enter a start date to filter a date range. |
| End Date | Enter an end date. If left empty, defaults to the current date. |
| Apply Filter | Applies the selected filters. |
| Clear Filter | Clears all filters. |
Release Details
Click View on any release row to see all release details, with options to promote, restore, or roll back.
Click View Details on any application in the release to open a dialog showing three tables:
| Table | Description |
|---|---|
| Modules | All modules in the release. |
| Data Collections | All Data Collections in the release. |
| Previous Version Modules | Modules from a previous release not included in the current one, and the release version where they currently exist. |
Each table shows up to 15 entries. Use the pagination buttons to see more. A icon marks modules or Data Collections modified since the last release.
Click View Diff on any module or Data Collection to review its revisions in the Module Revisions Dashboard.
Creating a Release
A release can include as many applications as needed. Individual modules or Data Collections within an application can also be selected.
Creating a release is also referred to as tagging a release.
Promoting an environment is client-specific. Only the next environment level is available for promotion.
Step 1: Add Release Information
- Click + Create New Release.
- In the Version* field, enter a version number in any format.
- In the Name* field, enter a release name.
- In the Notes field, enter any notes or comments.
- From the Client* drop-down, select the environment.
- From the Environment* drop-down, select the target environment level.
After making selections, the page displays the most recent release in that environment and all available app elements.
Step 2: Select Applications and Data Collections
The tool promotes the newest version of all selected modules.
If an application has more than 125 modules, a warning displays. Reorganize the promotion into smaller applications, as applications with more than 125 modules can cause timeouts and promotion failures.
Use the Applications table to locate applications and Data Collections to include. The table shows 10 entries at a time.
| Filter | Description |
|---|---|
| Workspace | Enter a workspace name. |
| Application | Enter an application name. |
| Last Promotion | Enter a time or date to filter by. |
| Promoted By | Enter a team member name. |
| Modified | Enter the full word exclamation to filter for modified app elements. |
For each application or Data Collection to include:
-
Click Select Elements.
-
In the dialog, select the modules to include. Click View Diff to review a module's revisions in the Module Revisions Dashboard.
-
Click Add.
Review selections using the Applications Selected, Modules Selected, and Data Collections Selected tabs. Selecting all modules creates a Full release; selecting specific modules creates a Partial release.
Before finalizing, scroll to the bottom to review the Modules Without Applications and Data Collections Without Applications panels. These show items excluded from the release.
Step 3: Finalize the Release
Confirm that applications have been submitted for a configuration analysis before promoting. Use the Config Analysis Dashboard to submit a request.
Click Create New Release, then click OK in the confirmation dialog.
Promoting a Release
After creating the release, the Release Dashboard reloads with the new release at the top.
Versioned applications cannot be promoted using this tool. See Application Versioning for version-controlled promotions.
To promote the release:
-
Click View to the right of the release.
-
In the Options section, click Promote, then click OK in the confirmation dialog.
-
Click Finish.
Promotion moves through Unqork environments in sequential order. Only one target environment level is available at a time. Keep the release name consistent across versions to avoid confusion.
After promoting, confirm that applications match in both the source and target environment levels. This is especially important for login, logout, header, and footer modules.
Promoting a New Version
When changes are ready to promote, follow the same steps in Creating a Release with a new version number. Unqork recommends using a new version number each time. Avoid reusing a version number from a previous release. Consider keeping the release name consistent with the previous version for organizational purposes.
After creating the release, follow the same steps in Promoting a Release.
Rolling Back a Release
If an application breaks in Production, roll back to a previous known-good release to keep the application available while resolving the issue.
Only complete applications can be rolled back. A warning displays if associated modules are not selected. Workflows and Data Collections cannot be rolled back.
To roll back:
-
Use the Release Dashboard's filters to locate the release and click View.
-
Click Rollback, then click OK in the confirmation dialog.
Troubleshoot and repromote when ready.
Restoring a Release
Restore returns a previous release version in the current environment level. Use this as a last resort when a serious issue occurs. Rolling back is typically the preferred option. After making fixes, repromote the changes.
Only applications can be restored to a previous release version. Data Collections cannot be restored.
To restore:
-
Use the Release Dashboard's filters to locate the release and click View.
-
Click Restore, then click OK in the confirmation dialog.
-
When the restore completes, click Finish.
Changelog
| Date | Change |
|---|---|
| 2026-07-21 | Restructured article — removed v1 links, collapsed Making Changes into a short cross-reference, combined sequential dialog steps, replaced pop-up modal with dialog throughout, removed tutorial framing. |
| 2026-07-16 | Editorial pass: fixed banned words, em dashes, See Also descriptions, and link paths. |
| 2026-04-28 | Editorial update: style guide compliance, fixed metadata, added H1, fixed alt text, removed tab list placeholders, added See Also and Changelog. |