Summary

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

Details

Page properties

Parent

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

Author

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

Content

...	...	@@ -1,5 +3,3 @@
1		-{{toc/}}
2		-
3	3	= __Introduction__ =
4	4
5	5
...	...	@@ -70,8 +70,8 @@
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		-== ==
	71	+(% class="wikigeneratedid" id="H" %)
	72	+When you change the environment, make sure to verify that the variable iXSwitchEnv has the value true.
75	75
76	76	== __Local variables__ ==
77	77
...	...	@@ -82,10 +82,17 @@
82	82
83	83
84	84	{{code language="XML"}}
85		-<xsl:value-of select=" ixf:SetVar('newVar', 'var Number 1')"></xsl:value-of>
	83	+<xsl:value-of select=" ixf:SetVar('newVar', 'var Number 1','false')"></xsl:value-of>
86	86
87	87	{{/code}}
88	88
	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	+
89	89	The call of this new variable in the scenario is similar to previous system variables:  **${newVar}.**
90	90
91	91	To get 'newVar' inside an XSL file :
...	...	@@ -95,7 +95,6 @@
95	95	<xsl:value-of select="ixf:getVar('newVar')"></xsl:value-of>
96	96	{{/code}}
97	97
98		-(% class="wikigeneratedid" %)
99	99	= __How to call the variables? :__ =
100	100
101	101
...	...	@@ -113,6 +113,7 @@
113	113	===== __**1^^st^^ Example:**__ =====
114	114
115	115
	120	+
116	116	)))
117	117
118	118	We set a simple example of a scenario to illustrate how to use variables.
...	...	@@ -133,11 +133,11 @@
133	133	* iXSession : ID session
134	134	* path : the path of BpmnFile in FileListener1.
135	135
136		-
137	137	* (((
138	138	===== __**2^^nd^^ Example**__ =====
139	139
140	140
	145	+
141	141	)))
142	142
143	143	This is an example to charge the call scenario variables:
...	...	@@ -148,11 +148,10 @@
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**"
	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**"
154	154
155		-(% class="wikigeneratedid" %)
156	156	= =
157	157
158	158	= __String Class__ =