Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,8 +1,8 @@
1		-= Introduction =
	1	+= Introduction =
2	2
3	3	In this section, we will go throw an XSL function to get trackings by trkID or using Keys/Values.
4	4
5		-= Parameters =
	5	+= Parameters =
6	6
7	7	GetTracking uses 5 params to help retrieve trackings in question.
8	8
...	...	@@ -12,11 +12,15 @@
12	12	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'
13	13	In the other case where we use values depending on keys, they must be separated by ';' as shown below :
14	14	if we take the last example in 'keys' param, 'orderNumber;City;Phone' , 'values' will be by example '1243;Paris;06070706053' .
15		-1. limit: it defines the max number of tracking to retrieve.
16		-1. order: whether you want to order the list of trackings in a descending way or not by a certain key order.
	15	+1. limit: it defines the max number of tracking to retrieve. **it's optional.**
	16	+1. order: whether you want to order the list of trackings in a descending way or not by a certain key order. it's optional as long as you didn't fill then
17	17
18	18	= Uses =
19	19
20		-In order to use
	20	+We suppose that we have a tracking type named Product. It has 3 data (Name, Brand, and Country).
21	21
	22	+if we want to get Product by key values
	23	+
	24	+ {{code language="XML"}}<xsl:value-of select="ixf:GetTracking('Product', 'Name;Brand' , 'Laptop;Dell')"></xsl:value-of>{{/code}}
	25	+
22	22