Upgrade Validator
  • 04 Apr 2024
  • 2 Minutes to read
  • Dark
    Light

Upgrade Validator

  • Dark
    Light

Article Summary

This project conducts scans within an environment to identify any known or potentially disruptive issues that might arise from an upgrade. The primary objective is to provide users with the confidence to proceed with upgrades while minimizing the likelihood of encountering significant problems. This initiative aims to enhance the overall upgrade experience and promote smoother transitions to new versions by systematically identifying and addressing issues before the upgrade process. Access guidance on installing accelerators for further insights.

Note that presently not all possible Breaking Changes can be found with this Accelerator. Visit the Release Notes for a particular version to make sure there are not any issues. 


Glossary of Terms

TermDescription
Scan IssueThis is a Flow configured to check if the current server contains an issue. Unless the state specifies so, this does not inherently indicate that your server has an issue before the upgrade.
Breaking IssueThis is a change in a version that is intentional and will cause functionality to break. This often comes from redesigning or removing a particular feature.
Known IssueThis is an unintentional bug that was discovered after a version was released. These may persist across multiple versions of the software.

Supported Versions

Not every version of Decisions is supported in the Upgrade Validator. No version prior to v8.13 is supported. The list of supported versions is below.

VersionRelease DateSupport
v8.193/27/24No breaking changes
v8.181/31/24Yes
v8.1712/13/23No
v8.1611/7/23No
v8.1510/13/23Yes
v8.149/6/23Yes
v8.138/11/23Yes

Configuration

Permissions

The default Administrator group included in all Decisions installations possesses the capacity to both download new scan issues and perform server scans to identify potential upgrade-related problems.

Setup

  1. Following installation, proceed to the Workflow Catalog, expand the Administration Service section, and select the Known Issues Scanner.
  2. Select the Import Latest Release action on the right-hand side of the screen. 
  3. A Form will appear displaying importable items. By default, all items should be pre-selected.
  4. Confirm the selection of all records and proceed by selecting Continue.
  5. Upon successful import, finalize the process by clicking Done.

Known Issue Scanner

Scanning the Server

Before Scanning
Ensure that you follow the Setup steps for every new Decisions release to ensure that your scans are all up to date.
  1. Access the Workflow Catalog and expand the Administration Service section.
  2. Choose the Known Issues Scanner located within the Administration Service folder.
  3. Select the Scan Server action on the top left corner of the Page.
  4. Once the scan is complete, the Scannable Issues Report will be updated for review.

Viewing Scan Results

Scan results will appear in the Scannable Issues Report. Each scan will result in one of the following states:

StateDescription
UnscannedThis signifies the server has not undergone scanning for this particular problem yet.
Not ApplicableDenotes that the server is exempt from this scan due to its current version; thus, no concern is needed.
Issues FoundHighlights problems anticipated during the upgrade to the version linked with the scan issue. Developers must adjust the server, rescan, and address these problems.
No Issues FoundConfirms the absence of the scanned problem in the server, ensuring a seamless transition to the specified version without complications.

Downloading Flow Issues

After scanning the server, a CSV file of Flows that contain a Scan Issue can be downloaded.

  1. Select the Download Release Issues action on the top left corner of the Dashboard.
  2. The Download Form provides a preview of the CSV file. On the Form, click Download CSV to save the file.

    The CSV file provides the following information:
    ItemDescription
    Release VersionThe version number that the issue applies to.
    Issue The ID of the Scan Issue.
    Flow NameThe name of the Flow where the issue was detected.
    Flow IDThe ID of the Flow where the issue was detected.
    Step NameThe name of the step that is causing the issue.
    Step TypeThe type of step that is causing the issue.

Was this article helpful?