25th January 2019
This release includes upgrades to all the applications in the CDS infrastructure, a result of which mitigates some of the notification issues seen previously. In the interests of transparency, please note that some underlying issues within the applications remain under investigation and re-test. It is still possible there may be some notification issues that require a restart as a temporary workaround.
TTM6.0.0 deployment end-to-end was tested by submitting our XML sample messages into CDS from v2.0 of the API and all expected notifications were received.
The Following functionality is available:
The inventory linking unhappy path defects are not in this release. This release does, however, correct the defect with the ROE values in the declaration status notifications. These now correctly return ROE = 6, indicating that risking has taken place with no controls.
TTM6.0.0 Scenarios – this provides a high-level summary of the test scenarios enabled by this release. This is a new format based on feedback that scope documentation did not provide enough detail about the test scenarios available within the functional areas. If you have any further comments on the scope documentation, please let us know.
TTM6.0.0 Test Data Cover Sheet– please note that the test data used in CDS Trade Test has now changed due to the introduction of authorisation validation rules. Please refer to the TTM6.0.0 Test Data Cover Sheet for a library of the test data available and please be sure to use the correct authorisation ID number for the EORI used in all happy path tests submitted during TTM6.0.0.
XML Samples – new XML samples have been produced for TTM6.0.0 alongside updated versions of the samples from previous milestones.
C_Sample_TC01_Payload_v3.3 C_Sample_TC01_Scenario_v3.3 C_Sample_TC01_DMSACC_v3.3 C_Sample_TC01_DMSROG_v.3.3 C_Sample_TC01_DMSACC_v3.3 C_Sample_TC01_DMSROG_v.3.3 C_Sample_TC01_Payload_v3.3 C_Sample_TC01_Scenario_v3.3 C_Sample_TC01_DMSROG_v.3.3 C_Sample_TC01_Payload_v3.3 C_Sample_TC01_Scenario_v3.3 C_Sample_TC01_DMSACC_v3.3
IVL_Sample_Scenario_TC01_v1.2 IVL_Sample_TC01_DeclarationStatusNotification_1_v1.2 IVL_Sample_TC01_DeclarationStatusNotification_2_v1.2 IVL_Sample_TC01_DeclarationStatusNotification_3_v1.2 IVL_Sample_TC01_DMSACC_v.1.2 IVL_Sample_TC01_DMSRCV_1_v.1.2 IVL_Sample_TC01_DMSRCV_2_v1.2 IVL_Sample_TC01_DMSRES_DMSROG_v1.2 IVL_Sample_TC01_Goods_Arrival_Message_v.1.2 IVL_Sample_TC01_Payload_v1.2 IVL_Sample_TC01_ValidateMovementRequest_1_v.1.2 IVL_Sample_TC01_ValidateMovementRequest_2_v.1.2 IVL_Sample_TC01_ValidateMovementResponse_1_v.1.2 IVL_Sample_TC01_ValidateMovementResponse_2_v.1.2
Z_Sample_TC01 has been temporarily removed due to a defect found that impacts this scenario in this phase of Trade Test. Additionally, the structure of the cancellation message has changed. Please see the Known Error Log section for more information about these defects. Once they have been resolved, Z_Sample_TC01 will be added back into the Trade Test XML sample messages with any relevant updates and an updated version of Cancellation_Sample_TC01 will be issued.
TTM6.0.0 Known Error Log (KEL) – an updated version of the KEL is expected to be issued on Monday, 28/01, at the latest.
This document is being updated to remove the errors from TTM5.1 that are resolved in this release, as well as to include new errors identified through our testing of TTM6.0.0. This new KEL will also be added to the online forum. Please refer to the online forum for the latest updates against the Trade Test known errors.
There are two key defects which have impacted the XML samples and may impact your testing in TTM6.0.0. These will also be included on the next published KEL.
Improvements to the Pull Notification API – TTM6.0.0 also introduces a set of improvements to the Pull Notifications API. While the use of these enhancements are entirely optional they do provide significant benefit when retrieving notifications.
The capability to repeatedly retrieve the same notification in the event of that notification being lost or not successfully received or processed is now in place. Rather than deleting the notification once pulled, the API now retains pulled notifications. All notifications are kept for a maximum of 14 days from when they are first sent, after which time they cannot be retrieved.
Currently the Pull Notifications API works as follows:
The current implementation does not allow for a failure scenario where a notification needs to pulled more than once in the event of a client side failure to process the notification. To rectify this the Pull Notifications API has been extended by adding the following new endpoints to the API:
Improvements to the Pull Notifications API:
(For software houses that are not testing inventory linking, this is for information only)
There are some limitations to the inventory linking functionality that is available in CDS Trade Test. This information will remain documented on the Known Error Log (KEL), but we wanted to bring a few specific elements to your attention.
TTM5.1 is limited to ‘happy path’ responses to the inventory match request only. While we have resolved the defect in our core product that was preventing ‘unhappy path’ journeys following an inventory mismatch, a defect was found late in our test cycle which impacts the outbound notifications in this scenario. This therefore remains out of scope for this phase of Trade Test.
There will be two elements to the ‘unhappy path’ which will be released into CDS Trade Test once resolved:
Additionally, the following workarounds will be in place during TTM5.1. Once the underlying issue causing each workaround is resolved, a fix will be released into Trade Test and communicated:
We recognise that unhappy path testing is a key journey for your development and that these workarounds impact your ability to develop and test against the end-state solution. However, the programme has taken the decision to move forwards with this release. We are currently impacting a defect fix release into Trade Test that focuses specifically on inventory linking by addressing the unhappy path and the workarounds that are currently in place.
The CSP-specific XML sample pack (IVL_Sample_TC01) includes the following:
CDS Trade Test is still a test system so if you do encounter any issues, please continue to raise these via the SDST keeping in mind that trade test is currently supported from 9am to 5pm Monday to Friday, excluding UK bank holidays.