Versions Compared

Old Version 6

changes.mady.by.user ramtin.hosseini

Saved on

compared with

New Version Current

changes.mady.by.user Yong Guan (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Release Summary

This release implemented several new features like allow to add new attachments for complete requests and some attachments to a completed request. Improved performance to the website by parallelization and refactoring code. and addition of numerous bug fixes.

New Features and Improvements

ID

Items

146418

Refactor Work Management Service to combine multiple API calls into a single call from UI

146422

Refactor UI to use caching on LOV values and requests

146416

Update LOV service (TK version) - Remove DB Exist Check

138797

User can add attachments to a completed request

140355

Vessel Registry admins can also assign requests to any user

135175

Allow .doc and .docx files as attachments

Bug Fixes

ID

Items

145838

Web site performance can be improved by adding parallelization of calls to LoV service (Refactor)

140350

Work Management Service does not automatically generate auditable information

143463

Queue Message Processing Service logging environment variable should be set to pcp not Development

147883

Could not attach more than one certificate documents

Application Changes

Name

Version

DB change

Data Migration

LOV change

Description

Work Management

1.20

No

No

 

Internal Website

1.20

 

 

Yes

Add word document type for attachment

LOV API service

1.1

No

No

Release Processes

Estimated downtime: less then 1 min - due to server restarts.

...

Set configuration: ASPNETCORE_ENVIRONMENT to pcp from Development for pcpsafsecsurapp-service-bus-processing-service.

Re-Deploy WorkManagementService(WMS) api on APIM as a new method(GetWorkItemsByParams) was added to the api controller.

  • Rollout plan

    • Execute deployment pipeline to build and deploy a commit from Master branch that's tagged MVP1.2

    • 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

    • Swap the staging deployment slot to production deployment slot

  • Backout plan

    • 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