Changes for page 3. Variables
Last modified by Outhman Moustaghfir on 2024/01/23 13:58
Change comment:
There is no comment for this version
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.WebHome1 +User Guide.The iXPath BPMN.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.a chmiti1 +XWiki.omoustaghfir - Content
-
... ... @@ -1,6 +1,5 @@ 1 - {{toc/}}1 += __Introduction__ = 2 2 3 -= Introduction = 4 4 5 5 Variable is a container that holds a value and can be called in the iXPath Scenario. The importance of 6 6 ... ... @@ -11,9 +11,8 @@ 11 11 * System variables 12 12 * Local variables 13 13 14 - Tocall a variable, weshould putit inside${}. Eg:for avariablenamed ‘iXVar’, it can be called as${iXVar}.13 +== __System variables__ == 15 15 16 -== System variables == 17 17 18 18 System variables define some default values in the system, and they can be called by users several times. 19 19 ... ... @@ -70,29 +70,51 @@ 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 -== Local variables == 71 +(% class="wikigeneratedid" id="H" %) 72 +When you change the environment, make sure to verify that the variable iXSwitchEnv has the value true. 74 74 74 +== __Local variables__ == 75 + 76 + 75 75 Local variable is a type of variable that can be newly created and used for a certain need. 76 76 77 77 So as to create a local variable "newVar" with a value equals to "var number 1", we should write this piece of XSL code : 78 78 81 + 79 79 {{code language="XML"}} 80 -<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> 81 81 82 82 {{/code}} 83 83 87 +=== === 88 + 84 84 The call of this new variable in the scenario is similar to previous system variables: **${newVar}.** 85 85 86 86 To get 'newVar' inside an XSL file : 87 87 93 + 88 88 {{code language="XML"}} 89 89 <xsl:value-of select="ixf:getVar('newVar')"></xsl:value-of> 90 90 {{/code}} 91 91 92 -= Examples =98 += __How to call the variables? :__ = 93 93 100 + 101 +To call a variable inside a connector, we should put it inside ${}. Eg: for a variable named ‘Var’, it can be called as ${Var}. 102 + 103 +For the condition in the connector's property, to check if the variable verify the condition, we can use " VarName== 'Value' " or " VarName!='Value' ". 104 + 105 +To call a variable in an xsl file, we should use the local variables SetVar ou GetVar. 106 + 107 += __Examples__ = 108 + 109 + 110 + 94 94 * ((( 95 95 ===== __**1^^st^^ Example:**__ ===== 113 + 114 + 115 + 96 96 ))) 97 97 98 98 We set a simple example of a scenario to illustrate how to use variables. ... ... @@ -113,9 +113,11 @@ 113 113 * iXSession : ID session 114 114 * path : the path of BpmnFile in FileListener1. 115 115 116 - 117 117 * ((( 118 118 ===== __**2^^nd^^ Example**__ ===== 138 + 139 + 140 + 119 119 ))) 120 120 121 121 This is an example to charge the call scenario variables: ... ... @@ -126,12 +126,16 @@ 126 126 127 127 As shown in the mail body, we called 3 variables which are : 128 128 129 -* 130 -* 131 -* 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**" 132 132 133 -= StringClass=155 += = 134 134 157 += __String Class__ = 158 + 159 + 160 + 135 135 in java language, The String class represents character strings. It contains a lot of functions to handle String object. 136 136 137 137 you can discover all these functions on the following URL :