Release v1.0.0 - April 28th, 2023

Owned by Magdalene Schifferer (Unlicensed)
Last updated: Jun 12, 2023
13 min read

 

ROFs MVP Release Schedule - Complete

Sprint

Due Date

Activity

Team Member(s)

Status

Sprint

Due Date

Activity

Team Member(s)

Status

February 2022 - Sprint 28

February 2022 - present

Projected completion date: Monday March 27th

Grace - WLM permissions for testing

Jugraj / MAACE

No longer required

  • Told we would have access by March 17

  • Update a/o March 22 - MAACE group is completing sync work before we can get access

  • New projected completion date March 27th - Jugraj will follow-up Tuesday March 28th. If not complete, we will escalate. We need the credentials to access.

  • April 3 - Permissions are in place, but waiting for a few extra columns to be added for Grace to be able to access

  • April 11 - Columns added. Grace and Jugraj will check together to test her access.

  • April 18th - Update: MAACE has noted that SCED is their #1 priority, and they will work on this issue after SCED is released.

  • April 20th - Update: MAACE team has put a priority one effort on releasing SCED to prod, and this work has been put on the backburner. Not sure when we can expect this to be completed by the MAACE team. Ticket has been put back into the backlog for future prioritization.

Sprint 27

Wednesday March 15th - Tuesday March 28th

Sprint 27

ROFs Team

Complete

Sprint 27

Wednesday March 15th - Tuesday March 29th

UAT Testing (with users)

Steve, Grace

Complete

Sprint 27 - 29

March 19th - present

SCED set-up (Secure Cloud Enablement and Defense)

Jugraj / MAACE

Complete

  • MAACE has provided four endpoints

  • SCED Performance issues have been sorted out with the MAACE team, and is working as expected when tested in SCED dev - a/o April 3rd

  • Meeting with MAACE team for March 29th to discuss missing endpoints (see activity “Meeting with MAACE team to discuss missing SCED endpoints” for more meeting details)

  • Will had a discussion with Walter on Friday March 31st, and will follow-up with him this week

  • Thursday April 6th - Walter noted that the MAACE team will start to build out prod starting Tuesday April 11th. Their focus is “ensuring that all common services and databases are on SCED as well as any supporting resources, this includes  WLM, LOV, DMS.   This will allow all new application to deploy to SCED and anyone else that is ready to go to SCED now.”

  • Tuesday April 11th - Meeting with Walter and the cloud team. We discussed the following:

    • MAACE team will finish SCED development by Friday April 14th. They have a commitment to build out the environment for new apps going to SCED. They will onboard one app at a time going forward.

    • ROF will be able to test the SCED endpoints from Monday April 17th - Friday April 21st. The MAACE team will be available for troubleshooting.

    • If needed, we can set up a chat 1-2 times a week with MAACE team to get updates or troubleshoot.

    • ROF does not need an ATO, so this is not a blocker for us.

    • Using a combination of SCED and non-SCED is not a option, as it does not provide any value for us.

    • When SCED is up and running, we need to flip the deployment slots in prod. If non-SCED works, then SCED is predicted to work without issue.

    • RSIG can submit a new SMGS package the week before release.

  • Jugraj notes that there will be minimal impact to RSIG. RSIG is only using one endpoint, which mainly affects the pop-up window. It should be easy to test. No new builds are required if there is a problem. May also want to test in Citrix. So test:

    • RSIG pop-up window

    • Citrix environment - test pop-up window

  • April 17th update:

    • DSD Tech Advisor Standup: SCED should be ready for us to test April 18th or April 19th. Xia will provide daily updates in the morning.

  • April 18th update:

    • MAACE team is running into some issues, as they need to transfer 60,000 documents overall (not only ROF). Jugraj can transfer himself, but will check with MAACE team to make sure it is ok.

    • ROF - we are planning to test SCED endpoints in ACC by Friday April 21st

  • April 20th update:

    • Jugraj’s issues were logged in MAACE DevOps board. They are as follows:

      • 259787 - received response “Internal Server Error” when trying to create a work item in SCED dev and test environments

      • 259730 - got message “Bad request” when attempting to get work items by lob id

      • 259801 - got error "Npgsql.PostgresException (0x80004005): 42703: column v2.RECEIPT_NUMBER does not exist" when attempting to update work item n WLM SCED ACC

  • April 26th update: SCED is confirmed working in both ROF and RSIG

Sprint 27

Monday March 20th

Troubleshoot and test URL

Jugraj / Cloud Team

Complete

  • URL fixed March 20th

  • Jugraj has tested and it is working for him

  • Jugraj suggests that we can test URL during smoke testing

Sprint 27

Tuesday March 21st

ACC / Prod API permissions

Jugraj / MAACE

Complete

  • Permissions granted March 21st

Sprint 27

Monday March 27th

ROFs ACC environment set-up to RSIG SCED endpoints

Jugraj / Shu Zi (endpoint set-up on RSIG side)

No longer applicable

  • March 27th - ran into issues, and could not give RSIG SCED endpoints

  • Need to update in dev and test environments as well to be in sync

  • See activity “Hook up WLM SCED endpoints to RSIG” for updated timeline (approx.)

Sprint 27 - 28

Monday March 27th - Wednesday March 30th

 

Possible required testing in RSIG when we give RSIG SCED.

RSIG ACC Testing

RSIG - Entai, Honglei and Ewa

Complete

  • RSIG ACC deployment of desktop and Citrix are complete a/o March 22nd

  • Xu needs to add current UAT user list to ACC (not real email addresses for RSIs)

  • Estimated time to test

    • ACC - 2 days

    • Citrix - 0.5 days

Sprint 28

Wednesday March 29th to Tuesday April 11th

Sprint 28

ROFs Team

Complete

Sprint 28

Wednesday March 29th

Meeting with MAACE team to discuss missing SCED endpoints

Jugraj, Maggie, MAACE Team

Complete

  • Wednesday Meeting with MAACE team to discuss progress. Meeting uncovered MAACE needs to move multiple lines of business to their db. They did not expect to need to move them during their planning. In order to make the transfer, they need permission at the director level to move them with a single ATO (Authentication to Operate).

Sprint 28

Wednesday March 29th - Tuesday April 11th

ACC / Prod API Testing

Jugraj

Complete

Sprint 28

March 27th to April 3

Jugraj & Henry to troubleshoot so it can be done automatically vs manually on March 27th

Jugraj

Complete

  • April 3rd - Jugraj and Henry troubleshooting to see if manual deployment on release day can be automatic vs. manual

  • April 3rd - Automated deployment in prod does not seems possible yet, the cloud team has things configured for Linux app service deployments, but nothing for Windows

  • Decided we will use manual deployment for the MVP, as automated deployment is not possible at this time. Jugraj will make a fake Linux environment for testing by Henry’s team in anticipation of supporting automated deployment in the future.

Sprint 28

March 30th - April 6th

ACC Ad-hoc testing - Frontend

Grace

Complete

Sprint 28

Friday March 31st

Code Freeze

ROFs Team

Complete

Sprint 28

Monday April 3rd

ACC Ad-hoc testing - Frontend and Backend

Ashiq

Complete

Sprint 28

Wednesday April 5th

ACC Ad-hoc testing - Frontend

Delwar

Complete

Sprint 28

Monday April 3rd - Wednesday April 5th

ACC testing - Backend

 

Jugraj

Complete

Sprint 28

Tuesday April 4 - Tuesday April 11th

ACC testing - Frontend

Grace

Complete

Sprint 28

Tuesday April 4 - Tuesday April 11th

ACC Ad-hoc testing - Frontend

Ewa

Complete

Sprint 28

Friday March 31st to April 14th

Prod Sanity Check - Backend

Jugraj

Complete

Sprint 28

Friday April 7th

Holiday - Good Friday

ROFs Team

Holiday

Sprint 28

Monday April 10th

Holiday - Easter Monday

ROFs Team

Holiday

Sprint 29

Wednesday April 12th -Tuesday April 25th

Sprint 29

ROFs Team

Complete

Sprint 29

Thursday April 13th - Friday April 14th

Update ROF architecture diagram and send to MAACE team

Jugraj

Complete

Sprint 29

Wednesday April 12th - Tuesday April 25th

Step 1: Prod sanity check - frontend

Grace

Complete

Sprint 29

Wednesday April 12th - Friday April 21st

Step 2: Create prod sanity check spreadsheet for release day

Grace

Complete

Sprint 29

Friday April 14th

Submit RSIG SGMS ticket

RSIG - Entai, Dave

Complete

  • Entai prepared ticket in advance

  • Dave will submit RSIG SGMS ticket

Sprint 29

Friday April 21st

Reach out to Andy Labelle on Teams and inquire about a) Does ROF need to submit an SGMS ticket b) If so, can RSIG SGMS ticket be reopened, and ROFs included in this ticket

Rationale for ROF submitting an SGMS ticket - if something goes wrong and we need their help, we may not get help in a timely manner, as we would need to submit a ticket first.

Maggie, Jugraj

Complete

  • To include in message to Andy:

    • Our upcoming release is a big one for RSIG, and we are

    • Let Andy know that ROF is under the RSIG umbrella, but is a separate piece of work. ROFs is cloud-based.

    • Does ROF need to submit a separate SGMS ticket?

    • If so, is it possible for us to roll back the RSIG ticket and include ROF, or should we open a separate ticket?

    • If so, in the future should ROF submit their own ticket, or can (we continue to) submit under RSIG ticket (if going this way).

  • Reference (if needed): RSIG Software release to Production: Create Service Manager Ticket

  • Completed RFC ticket on April 17th

Sprint 29

Monday April 17th - Thursday April 20th

Submit ROF RFC (Request for Change) ticket

Maggie, Jugraj, Will

Complete

  • April 17th - “Plan” tab did not appear. Perhaps it appears later in the process

Sprint 29

Monday April 17th - Tuesday April 21st

Hook up WLM SCED endpoints to RSIG ACC

ROFs - Jugraj, RSIG - Shu Zi

Complete

  • Does not require a prod release or database refresh to make the change in RSIG, as it is a database configuration issue (triple-checked with Shu Zi on March 31st). Change happens in WR203 system parameter endpoints.

  • Need to update in dev and test environments as well to be in sync

  • Need to wait until MAACE team development is complete before this can be implemented

Sprint 29

Tuesday April 18th - Friday April 21st

Test SCED endpoints in RSIG

RSIG - Honglei, Ewa

Complete

  • Test SCED endpoints in RSIG/ROF ACC by testing the following:

    • Desktop - Pop-up window

    • Citrix - Pop-up window

Sprint 30

Wednesday April 26th - April 28th

Sprint 30

ROFs Team

Complete

Sprint 30

Friday April 28th

Prod Release Day activities - Backend

Jugraj

Complete

Sprint 30

Friday April 28th

Step 3: Release day prod sanity check - frontend

Grace, Ewa, Ashiq

Complete

Sprint 30

Sunday April 30th

Step 4: Check if TSB occurrences from the weekend are being received from the overnight feed - database comparison

Jugraj

Complete

Sprint 30

Monday May 1st

Step 5: Check if TSB occurrences from the weekend are being received from the overnight feed - email comparison

Jugraj

Not Started

Sprint 30

Monday May 1st

Help Desk - Email / inform OPS users ROF is ready

Steve, Help Desk

No longer applicable

  • Email to OPS users, letting them know ROFs is released and ready for use

  • Update: not applicable for this release due to the strike

February - March 30th: UAT Testing - Complete

March 28th: RSIG ACC Testing - Complete

Morning

Meeting held with RSIG and ROFs team. RSIG team determined it was ok to give ROFs ACC non-SCED to RSIG ACC in the morning so they can start testing, and provide them with ROFs ACC SCED in the afternoon. We have been using ROFs ACC non-SCED to test in QA.

12:00pm (approx.)

Give RSIG team ROFs ACC non-SCED to RSIG ACC

Afternoon

Plan was to give RSIG team ROFs ACC SCED to RSIG ACC. We were unable to give them ROFs ACC SCED due to SCED issues.

From our understanding, the following was working in SCED:

  • Location mapping

  • Planned Location

  • Display ROFs data in pop-up window

  • RSIG workflow

The following is missing from SCED:

  • Letters - not working

    • A letter has been added to ROFs so workflow into RSIG can continue

March 29 to April 11: ACC / PROD API Testing (backend only) - Complete

Checklist: Reviewed with Jugraj, and marked as complete on March 29th

Test the following:

  • Roles have permissions

  • Workflows with different roles

  • Ad-hoc testing

March 30th to April 14th - ACC Testing - Complete

Tasks before ACC test begins:

  • We will test in our ACC environment, but switch connection to RSIG UAT

  • Ensure all emails outside of RSIG team are set to fake emails

April 3rd to April 6th: Backend testing - Complete

Checklist: Reviewed with Jugraj, and marked as complete on March 29th

  1. Check connection string in Key Vault

  2. Check correct groups in app settings

  3. Check if correct users are added to the groups - prod

  4. Check if all the API permissions are configured for the groups

  5. RSIG db - need to make sure the users main emails match with the Microsoft login emails

  6. Check the correct API endpoints are set up

March 30th - April 12th: Ad-hoc Frontend testing - Complete

  1. Devs and QA ad-hoc test various workflows in ACC environment

  2. Test in FR language

  3. Test different roles

  4. Time commitment 0.5-1 day

April 4th - 12th: Frontend testing - Complete

Checklist: Reviewed with Grace, and marked as complete on March 31st

  1. Task Dashboard:

    1. Check TSB occurrences from overnight feed appear in “Pending Review” tab at top of table (if still mapped to RSIG training)

    2. Run a date range search

    3. Run a few other ad-hoc searches

    4. Run a search in FR, searching for occurrences using FR translated criteria

  2. TSB Data:

    1. Check a few TSB occurrences to make sure correct TSB data is appearing (from Jeff’s morning email - if still mapped to RSIG UAT)

  3. Location Mapping:

    1. Search for yard, spur, subdivision, crossing in the search tab

    2. Map a few locations including search and select a few different location types

  4. Manager Review:

    1. Complete a few Manager Reviews including:

      1. No Action Required

      2. Assigning RSI

      3. Required by Manager

      4. Reopen

      5. Reassign

  5. Inspection Notification:

    1. Select a railway and railway officer

    2. Change railway and railway officer

    3. Create letter, add CC and appendix

    4. Send email - Caution: Double-check to make sure CC emails are not real

    5. Check letter received in email and make sure it can be edited

    6. Test letter pop-up window, download letter, Info Received pop-up window, Railway Officer pop-up window

    7. Test all fields in Inspection Notification tab

    8. Test validation and different scenarios

  6. TSB Planned Location

    1. Create Planned Location

    2. Test to make sure the Planned Location is going to the 2023-2024 fiscal year (or current fiscal year)

  7. Test Admin, Manager and RSI roles

  8. Test steps 1-6 in French

March 31st to April 28th: Prod Sanity Check -Backend and Frontend - Complete

RSIG Environments - Emails

QA

  • Real emails: RSIG/ROFs team members

  • Fake emails: All other RSIG contacts outside of RSIG/ROFs team members

  • ROFS is using [TR157_GEN_INDIV_EMAIL_ADDRESS_ROFS_ROFS] for authentication and users in this table have their real email listed

  • Fake email:  RSIG-PISF-test@tc.gc.cal

UAT

  • Real emails: RSIG/ROFs team members

  • Fake emails: All other RSIG contacts outside of RSIG/ROFs team members

  • ROFs is using [TR157_GEN_INDIV_EMAIL_ADDRESS] for authentication

  • RSIG has team members listed in [TR157_GEN_INDIV_EMAIL_ADDRESS]

  • Fake email:  RSIG-PISF-test@tc.gc.cal

  • Refer to DevOps ticket 252541

Required to start

  1. CC / Prod API permissions are granted and tested

  2. SCED endpoints are ready and tested

  3. Check to make sure live emails will not go out

Do not test

  1. Location Mapping

  2. Planned Location

  3. Send emails in Inspection Notification - DO NOT SEND EMAILS as they are live?

March 31st to April 14th: Backend Testing - Complete

Checklist: Reviewed with Jugraj, and marked as complete on March 29th

  1. Check connection string in Key Vault

  2. Check correct groups in app settings

  3. Check if correct users are added to the groups - prod

  4. Check if all the API permissions are configured for the groups

  5. RSIG db - need to make sure the users main emails match with the Microsoft login emails

  6. Check the correct API endpoints are set up

April 14th - April 28th: Frontend Testing - Complete

Checklist: Reviewed with Jugraj and Grace, and marked as complete on March 30th. Revised on April 14th to accommodate testing before release and on release day.

Step 1: April 14th - 25th - Complete

  1. Roles are deployed and functioning as expected

  2. Switch roles and confirm permission access

  3. User has a connection between ROF prod and db

    1. Test filters in “Search All Records” that connect with db

  4. Complete steps 1-3 in FR

Step 2: April 12th - 25th - Complete

  1. Create prod sanity check spreadsheet for team and external user to use on April 28th

    1. Example: RSIG Release 33 Smoke Test: https://docs.google.com/spreadsheets/d/1PVZJTDb89otTOUIQd1xXcPH20KENyeAPjPz6yGiv-4I/edit#gid=0

    2. Deliverable: RSIG Web (ROFS) MVP 1 Prod Sanity Check https://docs.google.com/spreadsheets/d/1xbTRMb-3hDvcRDIk10r5ptCmRm5As4FR/edit?usp=sharing&ouid=112575591080350658610&rtpof=true&sd=true

Step 3: April 28th - Complete

  1. Test URL

  2. Dashboard:

    1. Run a date range search

    2. Run a few other ad-hoc searches

    3. Open a few historical records

  3. TSB Data:

    1. Check a few TSB occurrences to make sure correct TSB data is appearing in TSB Data tab

  4. Location Mapping:

    1. Search for yard, spur, subdivision, crossing in the search tab

    2. Warning: Do not map a location!!!

  5. Manager Review:

    1. Test “Requested By”

      1. Select “No” for the first question and test “Requested By” dropdown menu

      2. Warning: Do not save!!!

  6. Test roles: Admin, Manager and RSI - test to see whether or not they have access to Location Mapping tab

  7. Warning: Do not map a location!!!

  8. Complete steps 2-6 in FR

Step 4: April 28th - Complete

  1. Remove Grace, Ewa, Ashiq and Jugraj from prod

Step 5: May 1st - Not Started

  1. Check TSB occurrences from Saturday and Sunday from the overnight feed appear in “Pending Review” - compare with daily email

  2. Warning: Do not complete Location Mapping or Manager Review

April 28th: Prod Release Day Activities - Complete

RSIG Release Day Activities - Dev Team: https://dev.azure.com/transport-canada/DSD-RAIL-RSIG/_wiki/wikis/DSD-RAIL-RSIG.wiki/4334/Release-34-Release-Day-Workflow-Dev-Team

Start Time (approx.)

Time to Complete

Activity

Team Member

Details

Status

Start Time (approx.)

Time to Complete

Activity

Team Member

Details

Status

1

9:00am

10 min

Switch connection string from training to prod

Jugraj

 

Complete

2

10:00am

15 min

Assign QA test roles in prod:

  • Grace - Admin

  • Ashiq - Manager

  • - RSI

Jugraj

 

Complete

3

10:30am

15 min

Re-upload document templates to SCED prod environment

Jugraj

  • One-time exercise required for SCED set-up

Complete

4

11:00am or earlier (confirm with RSIG)

20 min

Merge ACC branch with main branch

Jugraj

  • We can do our build after RSIG db is refreshed. Need to confirm with RSIG before proceeding.

  • Add contact ROF as part of RSIG release-day process

Complete

5

11:30am

20 min

Manually deploy from main branch to prod app service

Jugraj

 

Complete

6

1:00pm - 3:00pm

2 hours

Step 3: Prod Sanity Check on release day

Grace - test Admin role

Ashiq - test Manager role

-test RSI role

Jugraj - available for troubleshooting

Complete

7

3:00pm

15 min

Step 4: Remove Grace and Maggie from prod environment. Jugraj can remain in prod environment as Admin.

Jugraj

 

Complete

May 1st: RSIG Release day - Complete

Start Time (approx.)

Time to Complete

Activity

Team Member

Details

Status

Start Time (approx.)

Time to Complete

Activity

Team Member

Details

Status

1

8:30am

30 min

Step 5: Check to see if TSB Occurrences from Saturday and Sunday are coming in from the overnight feed - email check

Jugraj, Grace

Complete

2

Morning

15-30 min

Help Desk - Email / inform OPS users ROF is ready

Steve

  • Due to strike, no longer required for this release

No longer required