From d6264b6c744c861452f7bfd44c07ab5e84763358 Mon Sep 17 00:00:00 2001 From: Carl De'ath <74620667+cda69@users.noreply.github.com> Date: Thu, 20 Mar 2025 17:41:44 +0000 Subject: [PATCH] 122Fixes --- .../Home/Core/1.2.2/Appointment-StandardPattern/toc.yaml | 2 +- .../Home/Core/1.2.2/BaRS-FHIR-Usage/toc.yaml | 2 +- .../Home/Core/1.2.2/Core-Functionality-Requirements/toc.yaml | 2 +- .../Receiver-DocumentReference.md | 1 + .../Sender-DocumentReference.md | 2 ++ .../Home/Core/1.2.2/DocumentReference-StandardPattern/toc.yaml | 2 +- .../Home/Core/1.2.2/End-to-end-workflow/toc.yaml | 2 +- .../1.2.2/EndpointCatalogue-StandardPattern/Endpoint-Data.md | 2 -- .../Core/1.2.2/EndpointCatalogue-StandardPattern/Interface.md | 1 + .../1.2.2/EndpointCatalogue-StandardPattern/Introduction.md | 3 ++- .../Core/1.2.2/EndpointCatalogue-StandardPattern/Sequences.md | 2 ++ .../Core/1.2.2/EndpointCatalogue-StandardPattern/index.page.md | 3 +++ .../Home/Core/1.2.2/EndpointCatalogue-StandardPattern/toc.yaml | 2 +- .../Failure-Scenarios-1.1.x/Bundle-Processing.page.md | 2 +- .../Failure-Scenarios-1.1.x/GET--Appointment.page.md | 2 +- .../Failure-Scenarios-1.1.x/GET--MessageDefinition.page.md | 2 +- .../Failure-Scenarios-1.1.x/GET--ServiceRequest.page.md | 2 +- .../Error-Handling/Failure-Scenarios-1.1.x/GET--Slots.page.md | 2 +- .../Failure-Scenarios-1.1.x/General-Failure-Scenarios.page.md | 2 +- .../Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/toc.yaml | 2 +- .../Home/Core/1.2.2/Error-Handling/toc.yaml | 2 +- .../Home/Core/1.2.2/Non-Functional-Requirements/toc.yaml | 2 +- .../Home/Core/1.2.2/Security-and-Authorisation/toc.yaml | 2 +- .../Core/1.2.2/Standard-Pattern-Composite-Messages/toc.yaml | 2 +- .../Home/Core/1.2.2/Transactional-integrity/toc.yaml | 2 +- guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/toc.yaml | 2 +- 26 files changed, 30 insertions(+), 22 deletions(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/toc.yaml index a63929b3..368719f9 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: index.page + filename: index.page.md - name: Introduction filename: Introduction.page.md - name: Initial Booking diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/BaRS-FHIR-Usage/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/BaRS-FHIR-Usage/toc.yaml index 83d2aa08..cb7ee837 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/BaRS-FHIR-Usage/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/BaRS-FHIR-Usage/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.page.md - name: Frameworks diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Core-Functionality-Requirements/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Core-Functionality-Requirements/toc.yaml index 9433b048..31db240a 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Core-Functionality-Requirements/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Core-Functionality-Requirements/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.page.md - name: All diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/Receiver-DocumentReference.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/Receiver-DocumentReference.md index cfbe1346..6b18c987 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/Receiver-DocumentReference.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/Receiver-DocumentReference.md @@ -104,3 +104,4 @@ A DocumentReference can be updated by performing a DELETE request with the resou +. \ No newline at end of file diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/Sender-DocumentReference.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/Sender-DocumentReference.md index c8349fa9..acad18ab 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/Sender-DocumentReference.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/Sender-DocumentReference.md @@ -111,3 +111,5 @@ Once you have retrieved the resource, you can process it according to your requi +. + diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/toc.yaml index 50a1b561..9ac19ca8 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/DocumentReference-StandardPattern/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: index.page + filename: index.page.md - name: Introduction filename: Introduction.page.md - name: DocumentReferences for Senders diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/End-to-end-workflow/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/End-to-end-workflow/toc.yaml index 131ba901..7b6ddaf8 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/End-to-end-workflow/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/End-to-end-workflow/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.page.md - name: Service Discovery diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Endpoint-Data.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Endpoint-Data.md index 8971b1c8..14bf3c1b 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Endpoint-Data.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Endpoint-Data.md @@ -12,8 +12,6 @@ Describing Endpoints will be facilitated by the Organization, HealthcareService * An Endpoint belongs to a HealthcareService. * Multiple Endpoints of the same type are not permitted for a HealthcareService - -
> Organization

diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Interface.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Interface.md index 141041ca..7303a205 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Interface.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Interface.md @@ -255,6 +255,7 @@ The Interface for managing the 3 resources relating to an "endpoint" is detailed This table describes the parameters currently defined for the Paths defined in the interface table above. + diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Introduction.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Introduction.md index 6fb4e709..7e970de5 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Introduction.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Introduction.md @@ -31,4 +31,5 @@ BaRS employs an endpoint catalogue to match Target Identifiers with a stored end The BaRS endpoints will utilise not only service ids and a physical endpoint, but data describing the healthcare service, the provider of that service and the organization which manages and/or supplies the endpoint in question. This information will be stored using 3 FHIR resources which appropriately describe [Endpoints](http://hl7.org/fhir/R4/endpoint.html), [HealthcareServices](http://hl7.org/fhir/R4/healthcareservice.html) and [Organizations](http://hl7.org/fhir/R4/organization.html). -BaRS will expose an interface to manage this information for each of these resources. Each resource will have a corresponding endpoint on the Proxy to assist in managing these endpoints. \ No newline at end of file +BaRS will expose an interface to manage this information for each of these resources. Each resource will have a corresponding endpoint on the Proxy to assist in managing these endpoints. + diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Sequences.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Sequences.md index bfbc878c..ca9f343f 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Sequences.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/Sequences.md @@ -25,3 +25,5 @@ Here a Receiving system is creating a resource related to an endpoint. Here a Receiving system is updating a resource related to an endpoint. + +. diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/index.page.md index 0be1d9e3..10ba6b26 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/index.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/index.page.md @@ -1,3 +1,6 @@ --- topic: core-StandardPattern-Endpoints-1.2.2 --- + + +. \ No newline at end of file diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/toc.yaml index f1655b38..82637464 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/EndpointCatalogue-StandardPattern/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.md - name: Interface diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/Bundle-Processing.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/Bundle-Processing.page.md index 8721a472..26a4902b 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/Bundle-Processing.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/Bundle-Processing.page.md @@ -23,7 +23,7 @@ Below is a simplified example of how how to handle the Transaction Integrity HTT ![BaRS FHIR API end-to-end process](https://raw.githubusercontent.com/NHSDigital/NHSDigital-FHIR-BookingAndReferrals/main/BaRS-Images/FailureScenarios/HTTP-Header-logic-1.0.0.svg) -| HTTP Status Code | HTTP Error Code | issue Code | Scenario | +| HTTP Status Code | HTTP Error Code | Issue Code | Scenario | |------------------|-----------------|------------|-------------------------------------------------------------------| | 400 | REC_BAD_REQUEST | invalid | The request headers are not valid. | | 400 | REC_BAD_REQUEST | required | The request headers are not present. | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--Appointment.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--Appointment.page.md index 7a0d4690..ea4e15df 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--Appointment.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--Appointment.page.md @@ -17,7 +17,7 @@ This section defines the failure scenarios for GET /Appointment. There are two w ### Errors by parameter **path id in GET /Appointment{id}** -| HTTP Status Code | HTTP Error Code | issue Code | Scenario | Source | +| HTTP Status Code | HTTP Error Code | Issue Code | Scenario | Source | |------------------|------------------|------------|-----------------------------------------------------------------------------------------------|----------| | 400 | SEND_BAD_REQUEST | required | The parameter value was not included in the request. | API | | 400 | REC_BAD_REQUEST | required | The parameter value was not included in the request. | Receiver | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--MessageDefinition.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--MessageDefinition.page.md index f0451263..6b8432ad 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--MessageDefinition.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--MessageDefinition.page.md @@ -13,7 +13,7 @@ Message definition includes only one additional parameter and therefore there ar **context** -| HTTP Status Code | HTTP Error Code | issue Code | Scenario | Source | +| HTTP Status Code | HTTP Error Code | Issue Code | Scenario | Source | |------------------|------------------|------------|--------------------------------------------------|----------| | 400 | SEND_BAD_REQUEST | required | no context parameter was given. | API | | 400 | REC_BAD_REQUEST | required | no context parameter was given. | Receiver | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--ServiceRequest.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--ServiceRequest.page.md index 3c680a59..0d49be8f 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--ServiceRequest.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--ServiceRequest.page.md @@ -17,7 +17,7 @@ This section defines the failure scenarios for GET /ServiceRequest. As with GET ### Errors by parameter **path id in GET /ServiceRequest{id}** -| HTTP Status Code | HTTP Error Code | issue Code | Scenario | Source | +| HTTP Status Code | HTTP Error Code | Issue Code | Scenario | Source | |------------------|------------------|------------|-----------------------------------------------------------------------------------------------|----------| | 400 | SEND_BAD_REQUEST | required | The parameter value was not included in the request. | API | | 400 | REC_BAD_REQUEST | required | The parameter value was not included in the request. | Receiver | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--Slots.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--Slots.page.md index 523dadc2..d40929f8 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--Slots.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/GET--Slots.page.md @@ -22,7 +22,7 @@ Get /Slots has added complexity compared to previous endpoints in this section. ### Errors by parameter **Schedule:actor:HealthcareService** -| HTTP Status Code | HTTP Error Code | issue Code | Scenario | Source | +| HTTP Status Code | HTTP Error Code | Issue Code | Scenario | Source | |------------------|-------------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------|------------------| | 400 | SEND_BAD_REQUEST / REC_BAD_REQUEST? | required | The parameter value was not included in the request. (This parameter is not currently marked as required. ) | API and Receiver | | 400 | REC_BAD_REQUEST | value / invariant | The parameter value was incorrect or wrong. | Receiver | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/General-Failure-Scenarios.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/General-Failure-Scenarios.page.md index 4e3683c6..bd03e6c7 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/General-Failure-Scenarios.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/General-Failure-Scenarios.page.md @@ -2,7 +2,7 @@ This section will define errors that could be seen in any given step and shared from function to function without context. All interactions MUST follow these rules as such they may be listed in different sections. -| HTTP Status Code | HTTP Error Code | issue.Code | Scenario | Source | +| HTTP Status Code | HTTP Error Code | Issue.Code | Scenario | Source | |------------------|-----------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| | 400 | SEND_BAD_REQUEST | required | Content invalid against the specification or a profile. For example a required parameter or header is not provided. | API | | 400 | REC_BAD_REQUEST | value | a header value or parameter is invalid. (these are defined in each specific scenario) | Receiver | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/toc.yaml index 31603d91..116448ef 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/Failure-Scenarios-1.1.x/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.page.md - name: Message Routing diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/toc.yaml index 948a1d2f..cf1fff38 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Error-Handling/toc.yaml @@ -1,7 +1,7 @@ - name: filename: Failure-Scenarios-1.1.x - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.page.md - name: Overview diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Non-Functional-Requirements/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Non-Functional-Requirements/toc.yaml index 03f9dd67..5e962e98 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Non-Functional-Requirements/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Non-Functional-Requirements/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.page.md - name: Requirements diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Security-and-Authorisation/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Security-and-Authorisation/toc.yaml index ad294581..3949edb7 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Security-and-Authorisation/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Security-and-Authorisation/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.page.md - name: Sender diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/toc.yaml index 0cac8f0f..66f49100 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/toc.yaml @@ -1,5 +1,5 @@ - name: index - filename: index.page + filename: index.page.md - name: Introduction filename: Introduction.page.md - name: Standard Pattern For Composites diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Transactional-integrity/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Transactional-integrity/toc.yaml index bc0f40f4..659624ab 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Transactional-integrity/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Transactional-integrity/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: Introduction filename: Introduction.page.md - name: Initial Request diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/toc.yaml index ac5eb14d..1e31e4e5 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/toc.yaml @@ -1,5 +1,5 @@ - name: Index - filename: Index.page + filename: Index.page.md - name: filename: End-to-end-workflow - name:
API Path