Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • 1649942613906-103.png
  • 1649943564529-130.png

Details

Page properties

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		-To call a variable, we should put it inside ${}. Eg: for a variable named ‘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
...	...	@@ -25,10 +25,10 @@
25	25	1*. env: name of the environment.
26	26	1*. inputFile: this variable collect all input files in one list.
27	27	1. For a **mail listener : **
28		-1*. iXFrom: refers to the sender of the mail.
29		-1*. iXSubject: refers to the mail subject.
	26	+1*. iXFrom: refers to the sender of the mail that we are listening on.
	27	+1*. iXSubject: refers to the Subject of the mail that we are listening on.
30	30	1. For an **AS2 listener **:
31		-1*. iXFrom: return the value of the AS2 sender.
	29	+1*. iXFrom: return the value of the source of the AS2 that we are listening on.
32	32	1. All connectors declare a system variable of type BpmnFile, the connector variable uses a bunch of functions to handle the list of BpmnFiles that will be detailed in the table below :
33	33	1*. (((
34	34	(% style="width:884px" %)
...	...	@@ -58,13 +58,28 @@
58	58	${XmlToXml1.get(1).type()}
59	59	)))
60	60	)))
	59	+1. Variables used to charge the connectors properties in the xsl file without charging them in the scenario manually. Those variables helps reduce time consuming and avoid reputation in the scenario elements:
	60	+1*. For the SendFTP et SendSFTP, there are 3 variables:
	61	+1**. __**i​​XTo**__: used to charge the property **Destination **of the connector in the XSL file.
	62	+1**. __**iXServerConfig**__: used to charge the property **Server Config** of the connector in the XSL file.
	63	+1**. __**iXDirectory**__: used to charge the property **Folder** of the connector in the XSL file.
	64	+1**. [[image:SendFtp.png]]
	65	+1*. For the CallScenario Connector, there are 3 variables:
	66	+1**. **iXScenario**: used to charge the property **Scenario **of the connector in the XSL file.
	67	+1**. **iXSwitchEnv**: is a boolean variable used to charge the checkbox property **switch environnement** of the connector in the XSL file.
	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	+1**. [[image:1649942613906-103.png]]
61	61
62		-== Local variables ==
	71	+== ==
63	63
	73	+== __Local variables__ ==
	74	+
	75	+
64	64	Local variable is a type of variable that can be newly created and used for a certain need.
65	65
66	66	So as to create a local variable "newVar" with a value equals to "var number 1", we should write this piece of XSL code :
67	67
	80	+
68	68	{{code language="XML"}}
69	69	<xsl:value-of select=" ixf:SetVar('newVar', 'var Number 1')"></xsl:value-of>
70	70
...	...	@@ -74,12 +74,31 @@
74	74
75	75	To get 'newVar' inside an XSL file :
76	76
	90	+
77	77	{{code language="XML"}}
78	78	<xsl:value-of select="ixf:getVar('newVar')"></xsl:value-of>
79	79	{{/code}}
80	80
81		-= Examples =
	95	+= __How to call the variables? :__ =
82	82
	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	+* (((
	109	+===== __**1^^st^^ Example:**__ =====
	110	+
	111	+
	112	+
	113	+)))
	114	+
83	83	We set a simple example of a scenario to illustrate how to use variables.
84	84
85	85	We want to receive a file by a FileListener and send it by mail that contains a message body.
...	...	@@ -98,8 +98,31 @@
98	98	* iXSession : ID session
99	99	* path : the path of BpmnFile in FileListener1.
100	100
101		-= String Class =
	133	+* (((
	134	+===== __**2^^nd^^ Example**__ =====
102	102
	136	+
	137	+
	138	+)))
	139	+
	140	+This is an example to charge the call scenario variables:
	141	+
	142	+
	143	+[[image:1649943564529-130.png]]
	144	+
	145	+
	146	+As shown in the mail body, we called 3 variables which are :
	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**"
	151	+
	152	+= =
	153	+
	154	+= __String Class__ =
	155	+
	156	+
	157	+
103	103	in java language, The String class represents character strings. It contains a lot of functions to handle String object.
104	104
105	105	you can discover all these functions on the following URL :

1649942613906-103.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+20.3 KB

Content

1649943564529-130.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+41.2 KB

Content