Versions Compared

Key

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

...

Concerns: Change in name likely would impact our tis service , The need for notification on name change

Process map:

EPIC Link:

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

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

Legacy Revalidation

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

TIS

User Management

TSS

NDW

ESR

...