Versions Compared

Version Old Version 15 New Version 16
Changes made by

Cai Willis

Yafang Deng

Saved on

Key

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

...

Aim: Migration system -27 March and go live day to be 1st April 2023

This is the follow-up from the GMC (16 February) – Holly Chadwick holly.chadwick@gmc-uk.org → GMC Operations Manager for Revalidation

  • Test at least two mergers as soon as possible (hopefully next week if that’s good for you).

  • We want to make the changes on the live environment on Monday 27 March.

  • We estimate minimal system outage. I’m meeting with team who will be updating the systems next week to get an estimation of how long it will take to get the new codes for you.

Planning:

Impact : ?Tis , revalidation(both 1 and 2), we currently do not have a DB code-

...

Service

Tasks/

Ticket(s)

Revalidation

  • Awaiting to receive new/modified Designated body name, code and RO details from GMC on stage.

  • Test new DBC by CURLing from STAGE-GREEN/BLUE

  • Add the new DBCs to parameter store to map to the Recommendation

  • Add the new DBCs to TIS-GMC-Client service

  • Add the new DBCs to tis-revalidation-connection service (probably parameter store like recommendations)

  • ALSO: For Revalidation API calls to work, the admin needs to have the correct DBC assigned in usermanagement/profile service And the RO for that DBC needs to be correct (wherever that comes from)

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4234

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4235

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4236

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4239

Legacy Revalidation

  • Find the location where we need to accomodate the new DBC changes

TIS

  1. TIS-Reference: update reference.DBC table

  2. TIS-Profile: update auth.UserDesignatedBody table

  3. TIS-TCS:

    1. update tcs.Programme , tcs.Post table

    2. update tcs.PersonOwner table by PersonOwnerRebuildJob in Sync service

    3. update class DesignatedBodyMapper

User Management

TSS

NDW

ESR

Hicom Leave Manager

  • Update TIS-Accent ETL to use the new Owner names

  • Confirm with Hicom the impact on their ETL and Accent Leave Manager system changing DBCs/Owners would have and identify mitigating actions

NDW-Tableau

  • Identify scripts in the NDW which are or are a dependency for Tableau data sources which use DBC/Owner to extract relevant data

  • Identify Tableau workbooks which use DBC/Owner to group, filter, etc