Summary

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

Details

Page properties

Parent

...	...	@@ -1,1 +1,1 @@
1		-User Guide.The iXPath BPMN.WebHome
	1	+Documentation.iXPath.User Guide.The iXPath BPMN.WebHome

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.omoustaghfir
	1	+XWiki.achmiti

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,56 +68,29 @@
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		-(% class="wikigeneratedid" id="H" %)
72		-When you change the environment, make sure to verify that the variable iXSwitchEnv has the value true.
	73	+== Local variables ==
73	73
74		-== __Local variables__ ==
75		-
76		-
77	77	Local variable is a type of variable that can be newly created and used for a certain need.
78	78
79	79	So as to create a local variable "newVar" with a value equals to "var number 1", we should write this piece of XSL code :
80	80
81		-
82	82	{{code language="XML"}}
83		-<xsl:value-of select=" ixf:SetVar('newVar', 'var Number 1','false')"></xsl:value-of>
	80	+<xsl:value-of select=" ixf:SetVar('newVar', 'var Number 1')"></xsl:value-of>
84	84
85	85	{{/code}}
86	86
87		-=== Explanation: ===
88		-
89		-* ixf:SetVar: Presumably a custom function or extension function that sets a variable.
90		-* 'newVar': The name of the variable being created.
91		-* 'var Number 1': The value assigned to the variable.
92		-* 'false': The third argument determining whether the variable is global (true) or local (false). if the variable is true so this meaning we can get the variable from the parent scenario.
93		-
94	94	The call of this new variable in the scenario is similar to previous system variables:  **${newVar}.**
95	95
96	96	To get 'newVar' inside an XSL file :
97	97
98		-
99	99	{{code language="XML"}}
100	100	<xsl:value-of select="ixf:getVar('newVar')"></xsl:value-of>
101	101	{{/code}}
102	102
103		-= __How to call the variables? :__ =
	92	+= Examples =
104	104
105		-
106		-To call a variable inside a connector, we should put it inside ${}. Eg: for a variable named ‘Var’, it can be called as ${Var}.
107		-
108		-For the condition in the connector's property, to check if the variable verify the condition, we can use " VarName== 'Value' " or " VarName!='Value' ".
109		-
110		-To call a variable in an xsl file, we should use the local variables SetVar ou GetVar.
111		-
112		-= __Examples__ =
113		-
114		-
115		-
116	116	* (((
117	117	===== __**1^^st^^ Example:**__ =====
118		-
119		-
120		-
121	121	)))
122	122
123	123	We set a simple example of a scenario to illustrate how to use variables.
...	...	@@ -138,11 +138,9 @@
138	138	* iXSession : ID session
139	139	* path : the path of BpmnFile in FileListener1.
140	140
	116	+
141	141	* (((
142	142	===== __**2^^nd^^ Example**__ =====
143		-
144		-
145		-
146	146	)))
147	147
148	148	This is an example to charge the call scenario variables:
...	...	@@ -153,16 +153,12 @@
153	153
154	154	As shown in the mail body, we called 3 variables which are :
155	155
156		-* **iXEnv**: the Environment when the new scenario exists
157		-* **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'"
158		-* **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**"
159	159
160		-= =
	133	+= String Class =
161	161
162		-= __String Class__ =
163		-
164		-
165		-
166	166	in java language, The String class represents character strings. It contains a lot of functions to handle String object.
167	167
168	168	you can discover all these functions on the following URL :