Skip to Content

Changes for page Platzhalter

From version 37.1
edited by sas
on 16.02.2023, 14:44
Change comment: There is no comment for this version
To version 34.1
edited by jdr
on 22.07.2021, 17:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sas
1 +XWiki.jdr
Content
... ... @@ -40,22 +40,6 @@
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 -
59 59  === Special form elements ===
60 60  
61 61  There are some special variables available:
... ... @@ -67,8 +67,6 @@
67 67  
68 68  === System variables ===
69 69  
70 -{{id name="system"/}}
71 -
72 72  {{panel monospace="true" title="Syntax"}}
73 73  [%$<Name>%]
74 74  {{/panel}}
... ... @@ -77,10 +77,6 @@
77 77  
78 78  ; [%$CLIENT_ID%]
79 79  : The client ID of the client of the current form.
80 -; [%$DEFAULT_MAIL_SENDER%] {{version major="7" minor="0" patch="4"/}}
81 -: Returns the e-mail sender (system) for the configured mail server. If a separate mail server is configured under Client > Settings, these configuration will be used, otherwise the system e-mail server.
82 -; [%$DEFAULT_MAIL_SENDERNAME%] {{version major="7" minor="0" patch="4"/}}
83 -: Returns the sender name (system) for the configured mail server. If this is not configured, an empty string is returned.
84 84  ; [%$FORM_LINK%]
85 85  : The URL of the current form.
86 86  ; [%$FORM_PROCESS_LINK%]
... ... @@ -93,8 +93,6 @@
93 93  : Returns the inbox link the form record currently resides in.
94 94  ; [%$FORM_INVITE_LINK%]
95 95  : Returns the invitation link of the form.
96 -; [%$FORM_HISTORY_HTML%] {{version major="7" minor="2" patch="0"/}}
97 -: Returns the the history of a form record as (HTML) table.
98 98  ; [%$PROCESS_ID%]
99 99  : The current process ID of the form record.
100 100  ; [%$PROJECT_ALIAS%]
... ... @@ -128,8 +128,8 @@
128 128  : The name of the task where the action of the event is located.
129 129  ; [%$TRIGGER.triggerName%]
130 130  : The name of the event where the action of the event is located.
131 -; [%$COUNTER_CLIENT.<name of the counter>%]
132 -: The current value of a client [[counter>>doc:Formcycle.UserInterface.Data.Counter]].
107 +; [%$COUNTER_CLIENT.<counterName>%]
108 +: The current value of a client counter.
133 133  
134 134  ==== System variables with parameters ====
135 135  
... ... @@ -157,12 +157,6 @@
157 157  {{/html}}
158 158  
159 159  
160 -
161 -{{html wiki="true"}}
162 -<div class='xm-figure xm-float-right xm-clear-h2' data-alt='Using user variables to prefill form fields with data of the logged in user.'><div class='xm-figure-inner' style='width:310px'>{{lightbox image='prefill_user_variables_en.png' width='300' group='$height' group='$group' title='Using user variables to prefill form fields with data of the logged in user.'/}}<div class='xm-figure-caption'>Using user variables to prefill form fields with data of the logged in user.</div></div></div>
163 -{{/html}}
164 -
165 -
166 166  User variables may be used in [[actions>>doc:Formcycle.Designer.Workflow.Actions.WebHome]], [[templates>>doc:Formcycle.UserInterface.FilesAndTemplates.WebHome]], [[data base queries>>Formcycle.UserInterface.Data.DBQueries.WebHome]] or directly in [[form elements>>Formcycle.Designer.Form.FormElements.WebHome]] for prefilling the form (see [[figure>>||anchor="fig_prefill_user_variables"]]).
167 167  
168 168  {{panel monospace="true" title="Syntax"}}
... ... @@ -286,8 +286,6 @@
286 286  
287 287  === Action variables ===
288 288  
289 -{{id name="action"/}}
290 -
291 291  {{panel monospace="true" title="Syntax"}}
292 292  [%$&lt;actionName&gt;.&lt;returnValue&gt;%]
293 293  {{/panel}}
... ... @@ -298,21 +298,17 @@
298 298  
299 299  ; [%$<actionName>.SUCCESS%]
300 300  : Whether the action could be processed successfully. Evaluates to a boolean, ie. true or false.
269 +; [%$<actionName>.COUNT%]
270 +: This variable is not supported in the new workflow.
271 +: The number of results. Evaluates to an integer value.
301 301  ; [%$<actionName>.RESULT%]
302 302  : A single return value. Evaluates to a string value.
303 303  ; [%$<actionName>.RESULT[<Index>].<Identifier>%]
304 304  : 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.
305 305  
306 -The following action variables are __not__ supported in the old workflow:
277 +These action variables are not supported in the old workflow:
307 307  
308 308  ; [%$<actionName>.ERROR_CODE%]
309 309  : In case of error the thrown error code of the action.
310 310  ; [%$<actionName>.ERROR_MESSAGE%]
311 311  : In case of error the thrown error message of the action.
312 -
313 -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()%]**
314 -
315 -The following action variable is __only__ supported in the old workflow:
316 -
317 -; [%$<actionName>.COUNT%]
318 -: The number of results. Evaluates to an integer value.