Changes for page TRKToXML
Last modified by Outhman Moustaghfir on 2022/12/29 10:42
<
>
edited by Outhman Moustaghfir
on 2022/12/27 11:32
on 2022/12/27 11:32
edited by Outhman Moustaghfir
on 2022/12/27 11:33
on 2022/12/27 11:33
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -31,10 +31,14 @@ 31 31 * **Output FileName** : The name of your output file. 32 32 * **//Condition //**: This field allows you to add a condition to execute the processing step only if the condition is met. 33 33 34 -== __**Example:**__ == 34 +== __**Example 1:**__ == 35 35 36 -You will find in this part an example of an input file with the correct format and the output file. 37 37 37 + __**[[image:scenarioTrackingToXml.png]]**__ 38 + 39 + 40 +You will find in this part an example of an input file with the correct format and an output file. 41 + 38 38 === __input File:__ === 39 39 40 40 <iXDoc> ... ... @@ -56,12 +56,9 @@ 56 56 </iXDoc> 57 57 58 58 59 -1. trackingType: it refers to type of tracking wanted. (eg : order , IXEnvironment, baseArticle ...) 60 -1. keys: it can handle 2 values, "trkID" or keys separated by ';' (eg: 'orderNumber;City;Phone') if the key contains '_' at the first character, it means we look for metadata (_statusTracking, _creationDate ...) 61 -**NB:** all metadata will be explained in detail in another paragraph. 62 -1. values: the values must be ordered the same as 'keys'. if we're searching by 'trkID', 'values' should contain trkIDs separated by space ' '. eg : '121ee 123DD 55evr om432' 63 -In the other case where we use values depending on keys, they must be separated by ';' as shown below : 64 -if we take the last example in 'keys' param, 'orderNumber;City;Phone' , 'values' will be by example '1243;Paris;06070706053' . 63 + 64 +1. trackingType: it refers to type of tracking wanted. (eg : order , IXEnvironment, baseArticle ...). 65 +1. TrKIDs :it refers the trkID of tracking wanted . 65 65 1. limit: it defines the max number of tracking to retrieve. **it's optional.** 66 66 1. order: whether you want to order the list of trackings in a descending way or not by a certain key order. The default value is 'trkID' and it's optional as long as you fill the limit value. 67 67 ... ... @@ -92,6 +92,7 @@ 92 92 93 93 </iXDoc> 94 94 96 +as you can see in the output file we get the tracking 95 95 96 96 = Paragraph 2 = 97 97