From 42e599b0c125952873e2b454ec9ea40bd39875b8 Mon Sep 17 00:00:00 2001 From: ManithaSrinivasa Date: Thu, 24 Jul 2025 18:16:34 +0100 Subject: [PATCH 1/2] added additionalspace --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 7ba779b8d..8441c04e9 100644 --- a/README.md +++ b/README.md @@ -545,6 +545,7 @@ What are the links of the supporting systems? #### Tracing Change events and requests Correlation Id + To be able to track a change event and the change requests it can become across systems a common id field is present on logs related to each event. The id is generated in `Profile Editor` (NHS UK) which is then assigned to the `correlation-id` header of the request send to our (DoS Integration) endpoint, for a given change event. The `correlation-id` header is then used throughout the handling of the change event in `DoS Integration`. If a change event does result in change requests being created for `DoS` then the change requests have a `reference` key with the value being the correlation id. From 445a770361be362b2a35f689ce7584bf2cadc81b Mon Sep 17 00:00:00 2001 From: ManithaSrinivasa Date: Thu, 24 Jul 2025 23:52:36 +0100 Subject: [PATCH 2/2] added additional space --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8441c04e9..cfa691126 100644 --- a/README.md +++ b/README.md @@ -206,7 +206,7 @@ This includes: - Correct data types and data returned from function - All paths tested of the application -This testing is generally done by a developer +This testing is generally done by a developer. To run unit tests run the following commands @@ -545,7 +545,6 @@ What are the links of the supporting systems? #### Tracing Change events and requests Correlation Id - To be able to track a change event and the change requests it can become across systems a common id field is present on logs related to each event. The id is generated in `Profile Editor` (NHS UK) which is then assigned to the `correlation-id` header of the request send to our (DoS Integration) endpoint, for a given change event. The `correlation-id` header is then used throughout the handling of the change event in `DoS Integration`. If a change event does result in change requests being created for `DoS` then the change requests have a `reference` key with the value being the correlation id. @@ -623,3 +622,4 @@ The runbooks for this project can be found on the DI confluence. - Ways of working +