Summary

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

Details

Page properties

Content

...	...	@@ -1,8 +1,7 @@
1	1	{{toc/}}
2	2
3		-= __Introduction__ =
	3	+= Introduction =
4	4
5		-
6	6	Variable is a container that holds a value and can be called in the iXPath Scenario. The importance of
7	7
8	8	variables is to make flexibility in using some values without referring to their origins.
...	...	@@ -12,8 +12,9 @@
12	12	* System variables
13	13	* Local variables
14	14
15		-== __System variables__ ==
	14	+To call a variable, we should put it inside ${}. Eg: for a variable named ‘iXVar’, it can be called as ${iXVar}.
16	16
	16	+== System variables ==
17	17
18	18	System variables define some default values in the system, and they can be called by users several times.
19	19
...	...	@@ -70,17 +70,12 @@
70	70	1**. **iXEnv**: used especially when the developper wants to switch the environment and use another scenario in another environment. It is a variable that precise the name of the new environment
71	71	1**. [[image:1649942613906-103.png]]
72	72
73		-(% class="wikigeneratedid" %)
74		-== ==
	73	+== Local variables ==
75	75
76		-== __Local variables__ ==
77		-
78		-
79	79	Local variable is a type of variable that can be newly created and used for a certain need.
80	80
81	81	So as to create a local variable "newVar" with a value equals to "var number 1", we should write this piece of XSL code :
82	82
83		-
84	84	{{code language="XML"}}
85	85	<xsl:value-of select=" ixf:SetVar('newVar', 'var Number 1')"></xsl:value-of>
86	86
...	...	@@ -90,29 +90,14 @@
90	90
91	91	To get 'newVar' inside an XSL file :
92	92
93		-
94	94	{{code language="XML"}}
95	95	<xsl:value-of select="ixf:getVar('newVar')"></xsl:value-of>
96	96	{{/code}}
97	97
98		-(% class="wikigeneratedid" %)
99		-= __How to call the variables? :__ =
	92	+= Examples =
100	100
101		-
102		-To call a variable inside a connector, we should put it inside ${}. Eg: for a variable named ‘Var’, it can be called as ${Var}.
103		-
104		-For the condition in the connector's property, to check if the variable verify the condition, we can use " VarName== 'Value' " or " VarName!='Value' ".
105		-
106		-To call a variable in an xsl file, we should use the local variables SetVar ou GetVar.
107		-
108		-= __Examples__ =
109		-
110		-
111		-
112	112	* (((
113	113	===== __**1^^st^^ Example:**__ =====
114		-
115		-
116	116	)))
117	117
118	118	We set a simple example of a scenario to illustrate how to use variables.
...	...	@@ -136,8 +136,6 @@
136	136
137	137	* (((
138	138	===== __**2^^nd^^ Example**__ =====
139		-
140		-
141	141	)))
142	142
143	143	This is an example to charge the call scenario variables:
...	...	@@ -148,17 +148,12 @@
148	148
149	149	As shown in the mail body, we called 3 variables which are :
150	150
151		-* **iXEnv**: the Environment when the new scenario exists
152		-* **iXScenario**: ='**error_sc_out_trk_and_statut**'. It means that the current scenariowhere the **connector CallScenario** will be changed to "error_sc_out_trk_and_statut'"
153		-* **iXSwitchEnv**: ='**true**'. It means that the current env will be switched to "**Danone**"
	129	+* **iXEnv**: the Environment when the new scenario exists
	130	+* **iXScenario**: ='**error_sc_out_trk_and_statut**'. It means that the current scenariowhere the **connector CallScenario** will be changed to "error_sc_out_trk_and_statut'"
	131	+* **iXSwitchEnv**: ='**true**'. It means that the current env will be switched to "**Danone**"
154	154
155		-(% class="wikigeneratedid" %)
156		-= =
	133	+= String Class =
157	157
158		-= __String Class__ =
159		-
160		-
161		-
162	162	in java language, The String class represents character strings. It contains a lot of functions to handle String object.
163	163
164	164	you can discover all these functions on the following URL :