Changes for page Platzhalter

From 16.1 to 15.1 From 38.2 to 38.1

From version 38.1

edited by sas
on 16.02.2023, 14:44

Change comment: There is no comment for this version

To version 16.1

edited by gru
on 29.06.2021, 14:33

Change comment: Renamed back-links.

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.sas
++XWiki.gru

Content

@@ -40,22 +40,6 @@
  Example: The variable {{code language="none"}}[%tfEmail%]{{/code}} will take the value of the [[input field>>doc:Formcycle.Designer.Form.FormElements.Input]] named //tfEmail//.
--=== Question element variables ===
--
--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:
--
--{{table}}
--|= - |= A1 |= A2 |= A3
--|Q1|☑|☐|☐
--|Q2|☑|☑|☐
--|Q3|☑|☑|☑
--{{/table}}
--
--Then:
--
--* //[%sel1%]// resolves to //A1;A1,A2;A1,A2,A3//
--* //[%sel1_0%]// resolves to //A1//, //[%sel1_1%]// resolves to //A1,A2//, and //[%sel1_2%]// resolves to //A1,A2,A3//
--
  === Special form elements ===
  There are some special variables available:
@@ -67,8 +67,6 @@
  === System variables ===
--{{id name="system"/}}
--
  {{panel monospace="true" title="Syntax"}}
  [%$&lt;Name&gt;%]
  {{/panel}}
@@ -77,10 +77,6 @@
  ; [%$CLIENT_ID%]
  : The client ID of the client of the current form.
--; [%$DEFAULT_MAIL_SENDER%] {{version major="7" minor="3"}}{{/version}}
--: 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.
--; [%$DEFAULT_MAIL_SENDERNAME%] {{version major="7" minor="3"}}{{/version}}
--: Returns the sender name (system) for the configured mail server. If this is not configured, an empty string is returned.
  ; [%$FORM_LINK%]
  : The URL of the current form.
  ; [%$FORM_PROCESS_LINK%]
@@ -88,30 +88,17 @@
  ; [%$FORM_VERIFY_LINK%]
  : The URL to confirm Double opt in. Can only be used once.
  ; [%$FORM_INBOX_NAME%]
--: Returns the inbox name the form record currently resides in.
--; [%$FORM_INBOX_LINK%]
--: Returns the inbox link the form record currently resides in.
--; [%$FORM_INVITE_LINK%]
--: Returns the invitation link of the form.
--; [%$FORM_HISTORY_HTML%] {{version major="7" minor="2" patch="0"/}}
--: Returns the the history of a form record as (HTML) table.
++: {{version major="6" minor="1"/}}Returns the inbox name the form record currently resides in.
  ; [%$PROCESS_ID%]
  : The current process ID of the form record.
--; [%$PROJECT_ALIAS%]
++; [%$PROJECT_ALIAS%]"}}
  : The alias of the current form.
  ; [%$PROJECT_ID%]
  : The form ID of the current form.
--; [%$PROJECT_TITLE%]
--: As of version 7, [%$PROJECT_NAME%] is now called [%$PROJECT_TITLE%] .
--: The title of the current form.
++; [%$PROJECT_NAME%]
++: The name of the current form.
  ; [%$RECORD_ID%]
  : The ID of the current form record.
--; [%$RECORD_READ%]
--: Whether the current form record was read. Evaluated as a Boolean, i.e. true or false.
--; [%$RECORD_UNREAD%]
--: Whether the current form record was not read. Evaluated as a Boolean, i.e. true or false.
--; [%$RECORD_ATTR.<customAttrKey>%]
--:   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.
  ; [%$SOURCE_SERVER%]
  : The name of the server that has provided the current form, either the name of the {{fserver/}} or the local server.
  ; [%$SOURCE_SERVER_URL%]
@@ -120,16 +120,6 @@
  : The ID of the current state.
  ; [%$STATUS_NAME%]
  : The name of the current state.
--; [%$STATUS_TYPE%]
--: The type of the current state. These four values are possible: //RECEIVED// , //SAVED//, //ERROR// and //CUSTOM// (Custom status created by user).
--; [%$TRIGGER.actionName%]
--: The name of the action of the providing event.
--; [%$TRIGGER.taskName%]
--: The name of the task where the action of the event is located.
--; [%$TRIGGER.triggerName%]
--: The name of the event where the action of the event is located.
--; [%$COUNTER_CLIENT.<name of the counter>%]
--: The current value of a client [[counter>>doc:Formcycle.UserInterface.Data.Counter]].
  ==== System variables with parameters ====
@@ -138,15 +138,15 @@
  {{/panel}}
  ; [%$DATE("<format>", <lang>)%]
--: Current date. The parameters are optional. When no parameter is specified, the date will be returned in default format. You can specify a custom date format with the first parameter, see the [[java.text.SimpleDateFormat>>https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html]] for more info on the date format string. The second parameter specifies the language, which affects the names of weekdays and months. Example: {{code language="none"}}[%$DATE("yyyy/MM/dd", en-GB)%]{{/code}}
++: {{version major="6" minor="0" patch="5"/}} Current date. The parameters are optional. When no parameter is specified, the date will be returned in default format. You can specify a custom date format with the first parameter, see the [[java.text.SimpleDateFormat>>https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html]] for more info on the date format string. The second parameter specifies the language, which affects the names of weekdays and months. Example: {{code language="none"}}[%$DATE("yyyy/MM/dd", en-GB)%]{{/code}}
  ; [%$FORM_DATE_CREATED("<format>", <lang>)%]
--: Creation date of the form record. The parameters are optional. When no parameter is specified, the date will be returned in default format. You can specify a custom date format with the first parameter, see the [[java.text.SimpleDateFormat>>https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html]] for more info on the date format string. The second parameter specifies the language, which affects the names of weekdays and months. Example: {{code language="none"}}[%$FORM_DATE_CREATED("yyyy/MM/dd", en-GB)%]{{/code}}
++: {{version major="6" minor="0" patch="5"/}} Creation date of the form record. The parameters are optional. When no parameter is specified, the date will be returned in default format. You can specify a custom date format with the first parameter, see the [[java.text.SimpleDateFormat>>https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html]] for more info on the date format string. The second parameter specifies the language, which affects the names of weekdays and months. Example: {{code language="none"}}[%$FORM_DATE_CREATED("yyyy/MM/dd", en-GB)%]{{/code}}
  ; [%$FORM_DATE_MODIFIED("<format>", <lang>)%]
--: Available with FORMCYCLE version 6.0.5~{~{/info}} Last change date of the form record. The parameters are optional. When no parameter is specified, the date will be returned in default format. You can specify a custom date format with the first parameter, see the [[java.text.SimpleDateFormat>>https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html]] for more info on the date format string. The second parameter specifies the language, which affects the names of weekdays and months. Example: {{code language="none"}}[%$FORM_DATE_MODIFIED("yyyy/MM/dd", en-GB)%]{{/code}}
++: {{version major="6" minor="0" patch="5"/}} Available with FORMCYCLE version 6.0.5~{~{/info}} Last change date of the form record. The parameters are optional. When no parameter is specified, the date will be returned in default format. You can specify a custom date format with the first parameter, see the [[java.text.SimpleDateFormat>>https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html]] for more info on the date format string. The second parameter specifies the language, which affects the names of weekdays and months. Example: {{code language="none"}}[%$FORM_DATE_MODIFIED("yyyy/MM/dd", en-GB)%]{{/code}}
  {{id name="sec_user_variables"/}}
--=== User variables ===
++=== User variables {{version major="6" minor="4" patch="0"/}} ===
  {{id name="fig_prefill_user_variables"/}}
  {{figure image="prefill_user_variables_en.png"}}Using user variables to prefill form fields with data of the logged in user.{{/figure}}
@@ -157,30 +157,6 @@
  {{/html}}
--
--{{html wiki="true"}}
--<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>
--{{/html}}
--
--
--
--{{html wiki="true"}}
--<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>
--{{/html}}
--
--
--
--{{html wiki="true"}}
--<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>
--{{/html}}
--
--
--
--{{html wiki="true"}}
--<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>
--{{/html}}
--
--
  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"]]).
  {{panel monospace="true" title="Syntax"}}
@@ -250,7 +250,7 @@
  {{id name="sec_appointment_variables"/}}
--=== Appointment variables ===
++=== Appointment variables {{version major="6" minor="5" patch="0"/}} ===
  Appointment variables can be used when [[appointments>>doc:Formcycle.Designer.Form.FormElements.Appointment.WebHome]] are booked with the form.
@@ -304,8 +304,6 @@
  === Action variables ===
--{{id name="action"/}}
--
  {{panel monospace="true" title="Syntax"}}
  [%$&lt;actionName&gt;.&lt;returnValue&gt;%]
  {{/panel}}
@@ -316,21 +316,9 @@
  ; [%$<actionName>.SUCCESS%]
  : Whether the action could be processed successfully. Evaluates to a boolean, ie. true or false.
++; [%$<actionName>.COUNT%]
++: The number of results. Evaluates to an integer value.
  ; [%$<actionName>.RESULT%]
  : A single return value. Evaluates to a string value.
  ; [%$<actionName>.RESULT[<Index>].<Identifier>%]
  : 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.
--
--The following action variables are __not__ supported in the old workflow:
--
--; [%$<actionName>.ERROR_CODE%]
--: In case of error the thrown error code of the action.
--; [%$<actionName>.ERROR_MESSAGE%]
--: In case of error the thrown error message of the action.
--
--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()%]**
--
--The following action variable is __only__ supported in the old workflow:
--
--; [%$<actionName>.COUNT%]
--: The number of results. Evaluates to an integer value.