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,3 +1,5 @@
	1	+{{toc/}}
	2	+
1	1	= __Introduction__ =
2	2
3	3
...	...	@@ -68,8 +68,8 @@
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	+(% class="wikigeneratedid" %)
	74	+== ==
73	73
74	74	== __Local variables__ ==
75	75
...	...	@@ -80,17 +80,10 @@
80	80
81	81
82	82	{{code language="XML"}}
83		-<xsl:value-of select=" ixf:SetVar('newVar', 'var Number 1','false')"></xsl:value-of>
	85	+<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 :
...	...	@@ -100,6 +100,7 @@
100	100	<xsl:value-of select="ixf:getVar('newVar')"></xsl:value-of>
101	101	{{/code}}
102	102
	98	+(% class="wikigeneratedid" %)
103	103	= __How to call the variables? :__ =
104	104
105	105
...	...	@@ -117,7 +117,6 @@
117	117	===== __**1^^st^^ Example:**__ =====
118	118
119	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,11 @@
138	138	* iXSession : ID session
139	139	* path : the path of BpmnFile in FileListener1.
140	140
	136	+
141	141	* (((
142	142	===== __**2^^nd^^ Example**__ =====
143	143
144	144
145		-
146	146	)))
147	147
148	148	This is an example to charge the call scenario variables:
...	...	@@ -153,10 +153,11 @@
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**"
	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**"
159	159
	155	+(% class="wikigeneratedid" %)
160	160	= =
161	161
162	162	= __String Class__ =