Skip to Content

Changes for page Erstellen von Formularen

From version 4.1
edited by jdr
on 20.07.2021, 16:05
Change comment: There is no comment for this version
To version 4.2
edited by jdr
on 06.09.2021, 14:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,10 +16,10 @@
16 16  : Opens a selection dialog through which previously [[exported forms>>doc:.Export.WebHome]] can be imported. See [[form import>>||anchor="sec_form_import"]]. There are two different mechanisms for importing forms. Which import mechanism is used depends on the {{formcycle/}} version where you exported the form.
17 17  
18 18  ; Using form templates
19 -: Already existing forms can be saved as templates via the [[form menu>>doc:Formcycle.UserInterface.MyForms.WebHome||anchor="form_menu"]]. These templates may be used as a quick start for form creation. The settings of the form template will be preserved. This includes the [[form files>>doc:Formcycle.UserInterface.MyForms.Files.WebHome]], the [[workflow processing>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.WebHome]], [[double opt-in>>doc:Formcycle.UserInterface.MyForms.DoubleOptIn.WebHome]], [[inbox>>doc:Formcycle.UserInterface.MyForms.Inbox.WebHome]] and [[data table settings>>doc:Formcycle.UserInterface.MyForms.DataTables.WebHome]].
19 +: Already existing forms can be saved as templates via the [[form menu>>doc:Formcycle.UserInterface.MyForms.WebHome||anchor="form_menu"]]. These templates may be used as a quick start for form creation. The settings of the form template will be preserved. This includes the [[form files>>doc:Formcycle.UserInterface.MyForms.Files.WebHome]], the [[workflow>>doc:Formcycle.Designer.Workflow.WebHome]], [[double opt-in>>doc:Formcycle.UserInterface.MyForms.DoubleOptIn.WebHome]], [[inbox>>doc:Formcycle.UserInterface.MyForms.Inbox.WebHome]] and [[data table settings>>doc:Formcycle.UserInterface.MyForms.DataTables.WebHome]].
20 20  
21 21  ; Using plugin templates
22 -: Form templates (with [[workflow processing>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.WebHome]]) can also be added by plugins. If plugin templates are installed, they will show up here.
22 +: Form templates (with [[workflow>>doc:Formcycle.Designer.Workflow.WebHome]]) can also be added by plugins. If plugin templates are installed, they will show up here.
23 23  
24 24  {{id name="sec_form_import"/}}
25 25  
... ... @@ -70,7 +70,7 @@
70 70  A form dependency could not be resolved automatically. Every dependency will be listed with its name (1) and a description (2) of where the dependency is needed within the form. Here the CSS template used as the form theme exists already, but is not identical with the one in the form export file. You now have the option to either override the existing template (3), create a new template (4) or ignore this dependency altogether (5).
71 71  {{/figure}}
72 72  
73 -//Form dependencies// are [[files & templates>>doc:Formcycle.UserInterface.FilesAndTemplates.WebHome]], [[inboxes>>doc:Formcycle.UserInterface.Inboxes.WebHome]], [[data source>>doc:Formcycle.UserInterface.Data.Sources.WebHome]], etc. that are used by the form. These dependencies may be used by the form (e.g. for [[select elements>>doc:Formcycle.Designer.Form.FormElements.Selection]]), by the form's settings or in the [[workflow configuration>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.WebHome]] of the form (e.g. configuration of an action). Depending on the type of the form dependency, the following options are available to resolve the dependency (see [[figure>>doc:||anchor="fig_form_import_dep_exisiting"]]):
73 +//Form dependencies// are [[files & templates>>doc:Formcycle.UserInterface.FilesAndTemplates.WebHome]], [[inboxes>>doc:Formcycle.UserInterface.Inboxes.WebHome]], [[data source>>doc:Formcycle.UserInterface.Data.Sources.WebHome]], etc. that are used by the form. These dependencies may be used by the form (e.g. for [[select elements>>doc:Formcycle.Designer.Form.FormElements.Selection]]), by the form's settings or in the [[workflow>>doc:Formcycle.Designer.Workflow.WebHome]] of the form (e.g. configuration of an action). Depending on the type of the form dependency, the following options are available to resolve the dependency (see [[figure>>doc:||anchor="fig_form_import_dep_exisiting"]]):
74 74  
75 75  ; {{icon name="refresh"/}} Override
76 76  : An element may be overridden if it exists already within the system. This option is not available for inboxes and user groups.