...
This release implemented several new features like allowing user . Among them, it allows users to postpone a request, to attach a cover letter and multiple certificates to completed requests, and it also fixed some bugs.
This release provides enhancements for VR staff to further manage service requests (ie. postpone request until later date, etc) and capture additional vessel or owner details (ie. and also some bug fixes.such as fields for hull ID and Pleasure Craft License Number, etc.)
New Features and Improvements
...
ID | Items |
|---|---|
Change clear filters icon to text "Clear filters" on request board | |
Address should not show anything if not selected | |
Request Board - 'add request' button should be blue | |
Time Received defaults to GMT | |
Application randomly open in/switches to French | |
Official number field does not accept NF as a province code | |
Date received resets when entering time received | |
User cannot view or download an attachment that has a long hyphen in the name | |
Putting a status in pending should hide "time until deadline", follow up should reset the time |
User application roles for assign requests
...
Application Changes
Name | Version | DB change | Data Migration | LOV change | Description |
|---|---|---|---|---|---|
Work Management | 1.10 | Yes | No | Added phone extension to contact | |
Internal Website | 1.10 | Yes | New features and bug fixes |
Release Processes
Estimated downtime: less then 1 min - due to server restarts.
Communication required: inform business users in advance.
Users need to sign out and sign in again after the release to see the proper assign to user list base on the application roles.
Rollout plan
Run database update script (non-breaking change, a field gets added to WorkItem table)
Execute deployment pipeline to build and deploy a commit from Master branch that's tagged MVP1.1
Verify the staging deployment slot has been updated with the docker image built from the pipeline
Verify the Vessel Registry internal website and Work Management service on staging deployment slot works normally
Update List Of Values by using LOV service and update json file (non-breaking change)
Swap the staging deployment slot to production deployment slot
Backout plan
Database update rollback not required (change is backwards compatible)
Revert service and frontend web application container instances to their last version prior to update by swaping back the deployment slot to original production deployment slot