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,16 +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
71		-== ==
	73	+== Local variables ==
72	72
73		-== __Local variables__ ==
74		-
75		-
76	76	Local variable is a type of variable that can be newly created and used for a certain need.
77	77
78	78	So as to create a local variable "newVar" with a value equals to "var number 1", we should write this piece of XSL code :
79	79
80		-
81	81	{{code language="XML"}}
82	82	<xsl:value-of select=" ixf:SetVar('newVar', 'var Number 1')"></xsl:value-of>
83	83
...	...	@@ -87,29 +87,14 @@
87	87
88	88	To get 'newVar' inside an XSL file :
89	89
90		-
91	91	{{code language="XML"}}
92	92	<xsl:value-of select="ixf:getVar('newVar')"></xsl:value-of>
93	93	{{/code}}
94	94
95		-= __How to call the variables? :__ =
	92	+= Examples =
96	96
97		-
98		-To call a variable inside a connector, we should put it inside ${}. Eg: for a variable named ‘Var’, it can be called as ${Var}.
99		-
100		-For the condition in the connector's property, to check if the variable verify the condition, we can use " VarName== 'Value' " or " VarName!='Value' ".
101		-
102		-To call a variable in an xsl file, we should use the local variables SetVar ou GetVar.
103		-
104		-= __Examples__ =
105		-
106		-
107		-
108	108	* (((
109	109	===== __**1^^st^^ Example:**__ =====
110		-
111		-
112		-
113	113	)))
114	114
115	115	We set a simple example of a scenario to illustrate how to use variables.
...	...	@@ -130,11 +130,9 @@
130	130	* iXSession : ID session
131	131	* path : the path of BpmnFile in FileListener1.
132	132
	116	+
133	133	* (((
134	134	===== __**2^^nd^^ Example**__ =====
135		-
136		-
137		-
138	138	)))
139	139
140	140	This is an example to charge the call scenario variables:
...	...	@@ -145,16 +145,12 @@
145	145
146	146	As shown in the mail body, we called 3 variables which are :
147	147
148		-* **iXEnv**: the Environment when the new scenario exists
149		-* **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'"
150		-* **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**"
151	151
152		-= =
	133	+= String Class =
153	153
154		-= __String Class__ =
155		-
156		-
157		-
158	158	in java language, The String class represents character strings. It contains a lot of functions to handle String object.
159	159
160	160	you can discover all these functions on the following URL :