Summary

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

Details

Page properties

Content

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