Skip to Content
Last modified by Nico Lemaire on 2025/05/06 15:49
From version 18.1
edited by Robin Huisman
on 2024/04/05 16:21
Change comment: There is no comment for this version
To version 18.4
edited by Luca de Laat
on 2024/04/10 11:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.RobinHuisman
1 +XWiki.LucadeLaat
Content
... ... @@ -4,6 +4,7 @@
4 4  = Digital Lab Exchange process =
5 5  
6 6  The flow diagram gives a small overview of what the data flow of a lab assignment is. Every green block shows a step of the lab assignment process. From top to bottom these steps are:
7 +~==> nle what green blocks?
7 7  
8 8  1. Showing the laboratory and all the analyses that can be requested as an option to the user.
9 9  1. The user creating a lab assignment and sending it to the lab trough TerraIndex.
... ... @@ -17,7 +17,14 @@
17 17  
18 18  [[image:1712326520488-924.png||height="312" width="632"]]
19 19  
21 +
22 +(% class="wikigeneratedid" element-id="1884" %)
23 +~==> nle Perhaps add option download labcertificate
24 +
20 20  (% element-id="1884" %)
26 += =
27 +
28 +(% element-id="1884" %)
21 21  = (% element-id="1883" %)Firewall IP-Addresses of TerraIndex(%%) =
22 22  
23 23  (% element-id="1882" %)
... ... @@ -95,6 +95,9 @@
95 95  
96 96  (% element-id="1752" %)
97 97  Besides SIKB 13.4.0, TerraIndex also supports 9.0.0/8.0.0 etc.
106 +
107 +(% element-id="1752" %)
108 +~==> nle Do you want to mention these old versions?
98 98  )))|(% element-id="1751" %)
99 99  (% element-id="1749" %)|(% element-id="1748" %)6|(% element-id="1747" %) |(% element-id="1745" %) |(% element-id="1743" %)Reveives a request to create a labdelivery file in a certain version of SIKB. It will generate the file.|(% element-id="1742" %) |(% element-id="1740" %) |(% element-id="1738" %)
100 100  (% element-id="1736" %)|(% element-id="1735" %)7|(% element-id="1734" %) |(% element-id="1732" %)<=|(% element-id="1731" %)Sends back the SIKB file, as a Base64 encoded string, with or without using a zipstream.|(% element-id="1730" %)ResultCode (),
... ... @@ -473,7 +473,7 @@
473 473  
474 474  
475 475  (% element-id="1366" %)
476 -Therefor we call a Webserice for ValidCredentials Check:
487 +Therefore we call a Webserice for ValidCredentials Check:
477 477  
478 478  
479 479  (% class="table-hover" element-id="1363" %)
... ... @@ -692,12 +692,12 @@
692 692  == (% element-id="1202" %)Solution/Design(%%) ==
693 693  
694 694  (% element-id="1201" %)
695 -For this we create a Webserice for CreateOrder to create the order in the lab system.
706 +For this we create a Webservice for CreateOrder to create the order in the lab system.
696 696  After the creation, we would like to show an order overview of the laboratory in the future in PDF. The user can see the prices and can confirm or cancel.
697 697  Depending on the user's choice at the laboratory, to support this or not, TerraIndex calls the ApproveOrder or the CancelOrder.
698 698  
699 699  (% element-id="0" %)
700 -For default we assume that we cannot do this yet, and TerraIndex sends needsApprovalIsSupported = false. If this becomes true in the future, the Lab can indicate whether or not it is necessary in the NeedsApprove field.
711 +For default we assume that we cannot do this yet, and TerraIndex sends needsApprovaIsSupported = false. If this becomes true in the future, the Lab can indicate whether or not it is necessary in the NeedsApprove field.
701 701  
702 702  
703 703  (% class="table-hover" element-id="1195" %)
... ... @@ -1239,7 +1239,7 @@
1239 1239  = (% element-id="653" %)Get Order status and Results(%%) =
1240 1240  
1241 1241  (% element-id="652" %)
1242 -== (% element-id="651" %)Soluion/Design(%%) ==
1253 +== (% element-id="651" %)Solution/Design(%%) ==
1243 1243  
1244 1244  (% element-id="650" %)
1245 1245  TerraIndex will request per license/customer which results are ready. These are queried if the latest changes are newer than the last check. This way we never download too much unnecessarily and it can always be requested again.