Release Summary

Usability Enhancement

ECR Framework

Know the Status of a Workitem in the Timesheet eForm View

The Virtual eForm, Timesheet eForm View, has a column `Status’ that helps you know the status of the timesheet – whether it is routed, rejected, closed, etc. Now, we have introduced a new column “Item Status” to help you know the status of the workitem- whether it is open or closed. This new column will help you customize the application behavior based on the workitem status as per the business need.

Story Mapping

Automatic Linking of Child Card to Parent Card

The Story Mapping board consists of 3 levels that help you break down work from a high level to a granular level that can be planned across releases/sprints. For example, one can break down an Epic into Features and then eventually into User Stories. Currently, when a card Feature is created at level 2, it would automatically be linked as a child card to the Epic at level 1. Now the same behavior has been extended to cards created at level 3. So, when a User Story is created (at level 3) under an Epic (at level 2), it will automatically link the User Story to the Epic as a child card.

NOTE: The Story Mapping feature is graduated from Beta to general availability.

Defects Addressed

Platform

Deliverables

Annexure 1: Release Compatibility

Release Compatibility: SwiftEnterprise 9.0.0 and above means, while upgrading an existing customer installation of SwiftEnterprise, you will consider following –

Upgrading the database component

1. If your current release is prior to SwiftEnterprise 9.0.0, then you must upgrade the database by running DB.EXE for all the interim releases up to SwiftEnterprise 9.0.0.
2. Once you have reached 9.0.0 version, you can directly run SwiftEnterprise 9.2.0 DB.EXE
3. If your current release is SwiftEnterprise 9.0.0 or above, you can directly run SwiftEnterprise 9.2.0 DB.EXE

Upgrading the WildFly component

1. Make deployment as mentioned in the ReadME.pdf, present in the SwiftEnterprise 9.2.0 release folder.
2. If your current release is SwiftEnterprise 9.1.0, then follow the deployment impact present in this release document.
3. If your current releaseis prior to SwiftEnterprise 9.1.0, you must apply the deployment impacts mentioned in all the interim releases up to SwiftEnterprise 9.1.0. Once that is done, then follow the deployment impact present in this release document.

MSP Plugin Version

The MSP Plugin Version is not tied to release compatibility. It is changed whenever there are fixes or enhancements in the plugin code. The MSP plugin version is mentioned in the Release Summary section of the Release Notes. We append ‘updated’ tag to the version number if there is a change in the plugin version shipped in the previous SwiftEnterprise release.