Changes for page Platzhalter


From version 34.3
edited by gru
on 26.07.2021, 15:39
Change comment: There is no comment for this version
To version 36.2
edited by awa
on 24.05.2022, 16:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.gru
1 +XWiki.awa
Content
... ... @@ -40,6 +40,22 @@
40 40  
41 41  Example: The variable {{code language="none"}}[%tfEmail%]{{/code}} will take the value of the [[input field>>doc:Formcycle.Designer.Form.FormElements.Input]] named //tfEmail//.
42 42  
43 +=== Question element variables
44 +
45 +To access the values of [[select elements>>doc:Formcycle.Designer.Form.FormElements.Selection]] displayed as questions, you can use the following variables. Assume the select element is named //sel1//, has got 3 questions Q1, Q2, Q3 and 3 answers A1, A2, A3, and also assume these answers are selected:
46 +
47 +{{table}}
48 +|= - |= A1 |= A2 |= A3
49 +|Q1|☑|☐|☐
50 +|Q2|☑|☑|☐
51 +|Q3|☑|☑|☑
52 +{{/table}}
53 +
54 +Then:
55 +
56 +* //[%sel1%]// resolves to //A1;A1,A2;A1,A2,A3//
57 +* //[%sel1_0%]// resolves to //A1//, //[%sel1_1%]// resolves to //A1,A2//, and //[%sel1_2%]// resolves to //A1,A2,A3//
58 +
43 43  === Special form elements ===
44 44  
45 45  There are some special variables available:
... ... @@ -51,6 +51,8 @@
51 51  
52 52  === System variables ===
53 53  
70 +{{id name="system" /}}
71 +
54 54  {{panel monospace="true" title="Syntax"}}
55 55  [%$<Name>%]
56 56  {{/panel}}
... ... @@ -59,6 +59,10 @@
59 59  
60 60  ; [%$CLIENT_ID%]
61 61  : The client ID of the client of the current form.
80 +; [%$CLIENT_MAIL_SENDER%] {{version major="7" minor="0" patch="4" /}}
81 +: Returns the mail sender address of the client. If none has been set then an empty string will be returned.
82 +; [%$CLIENT_MAIL_SENDERNAME%] {{version major="7" minor="0" patch="4" /}}
83 +: Returns the mail sender name of the client. If none has been set then an empty string will be returned.
62 62  ; [%$FORM_LINK%]
63 63  : The URL of the current form.
64 64  ; [%$FORM_PROCESS_LINK%]
... ... @@ -104,8 +104,8 @@
104 104  : The name of the task where the action of the event is located.
105 105  ; [%$TRIGGER.triggerName%]
106 106  : The name of the event where the action of the event is located.
107 -; [%$COUNTER_CLIENT.<counterName>%]
108 -: The current value of a client counter.
129 +; [%$COUNTER_CLIENT.<name of the counter>%]
130 +: The current value of a client [[counter>>doc:Formcycle.UserInterface.Data.Counter]].
109 109  
110 110  ==== System variables with parameters ====
111 111  
... ... @@ -256,6 +256,8 @@
256 256  
257 257  === Action variables ===
258 258  
281 +{{id name="action" /}}
282 +
259 259  {{panel monospace="true" title="Syntax"}}
260 260  [%$&lt;actionName&gt;.&lt;returnValue&gt;%]
261 261  {{/panel}}
... ... @@ -278,6 +278,8 @@
278 278  ; [%$<actionName>.ERROR_MESSAGE%]
279 279  : In case of error the thrown error message of the action.
280 280  
305 +In the new workflow, the number of elements of JSON arrays can be queried from variable values with //.length()//, e.g.: **[%$Database query.RESULT.rows.length()%]**
306 +
281 281  The following action variable is __only__ supported in the old workflow:
282 282  
283 283  ; [%$<actionName>.COUNT%]