Skip to Content

Changes for page Platzhalter

From version 23.1
edited by jdr
on 21.07.2021, 08:51
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.jdr
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%]
... ... @@ -78,6 +78,7 @@
78 78  ; [%$PROJECT_ID%]
79 79  : The form ID of the current form.
80 80  ; [%$PROJECT_TITLE%]
103 +: As of version 7, [%$PROJECT_NAME%] is now called [%$PROJECT_TITLE%] .
81 81  : The title of the current form.
82 82  ; [%$RECORD_ID%]
83 83  : The ID of the current form record.
... ... @@ -85,6 +85,8 @@
85 85  : Whether the current form record was read. Evaluated as a Boolean, i.e. true or false.
86 86  ; [%$RECORD_UNREAD%]
87 87  : Whether the current form record was not read. Evaluated as a Boolean, i.e. true or false.
111 +; [%$RECORD_ATTR.<customAttrKey>%]
112 +: Read user-defined form record attributes (e.g. [%$RECORD_ATTR.loopCount%]). This allows values to be stored on the form record and accessed in any action.
88 88  ; [%$SOURCE_SERVER%]
89 89  : The name of the server that has provided the current form, either the name of the {{fserver/}} or the local server.
90 90  ; [%$SOURCE_SERVER_URL%]
... ... @@ -93,6 +93,16 @@
93 93  : The ID of the current state.
94 94  ; [%$STATUS_NAME%]
95 95  : The name of the current state.
121 +; [%$STATUS_TYPE%]
122 +: The type of the current state. These four values are possible: //RECEIVED// , //SAVED//, //ERROR// and //CUSTOM// (Custom status created by user).
123 +; [%$TRIGGER.actionName%]
124 +: The name of the action of the providing event.
125 +; [%$TRIGGER.taskName%]
126 +: The name of the task where the action of the event is located.
127 +; [%$TRIGGER.triggerName%]
128 +: The name of the event where the action of the event is located.
129 +; [%$COUNTER_CLIENT.<name of the counter>%]
130 +: The current value of a client [[counter>>doc:Formcycle.UserInterface.Data.Counter]].
96 96  
97 97  ==== System variables with parameters ====
98 98  
... ... @@ -243,6 +243,8 @@
243 243  
244 244  === Action variables ===
245 245  
281 +{{id name="action" /}}
282 +
246 246  {{panel monospace="true" title="Syntax"}}
247 247  [%$&lt;actionName&gt;.&lt;returnValue&gt;%]
248 248  {{/panel}}
... ... @@ -253,9 +253,22 @@
253 253  
254 254  ; [%$<actionName>.SUCCESS%]
255 255  : Whether the action could be processed successfully. Evaluates to a boolean, ie. true or false.
256 -; [%$<actionName>.COUNT%]
257 -: The number of results. Evaluates to an integer value.
258 258  ; [%$<actionName>.RESULT%]
259 259  : A single return value. Evaluates to a string value.
260 260  ; [%$<actionName>.RESULT[<Index>].<Identifier>%]
261 261  : Certain actions may return more than one result, corresponding to a //List<Map<String,String>>// in Java. The index and identifier is set by the corresponding action implementation and cannot be changed. This is used mostly by custom plugins when multiple values need to be returned.
297 +
298 +The following action variables are __not__ supported in the old workflow:
299 +
300 +; [%$<actionName>.ERROR_CODE%]
301 +: In case of error the thrown error code of the action.
302 +; [%$<actionName>.ERROR_MESSAGE%]
303 +: In case of error the thrown error message of the action.
304 +
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 +
307 +The following action variable is __only__ supported in the old workflow:
308 +
309 +; [%$<actionName>.COUNT%]
310 +: The number of results. Evaluates to an integer value.
311 +