Wiki source code of Erstellen von Formularen

Show last authors
1 {{figure image="form_create_en.png" clear="h1"}}
2 {{id name="fig_form_create" /}}
3 Choices for creating new forms. You can create empty forms or use a user (plugin) templates. Moreover, previously [[exported forms>>doc:Formcycle.UserInterface.MyForms.Export.WebHome]] can be imported as well.
4 {{/figure}}
5
6 {{content/}}
7
8 == Overview ==
9
10 The button //Create new form// {{ficon name="document-add"/}} on the [[dashboard>>doc:Formcycle.UserInterface.Dashboard.WebHome]] or on the [[form overview page>>doc:Formcycle.UserInterface.MyForms.WebHome]] opens the page or dialog for creating forms (see [[figure>>||anchor="fig_form_create"]]). There are serveral ways of creating new forms:
11
12 ; Empty form
13 : Creates a completely empty form and opens the [[{{designer/}}>>doc:Formcycle.FormDesigner.WebHome]] for editing.
14
15 ; Import form
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
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]].
20
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.
23
24 {{id name="sec_form_import"/}}
25
26 {{figure image="form_import_dep_exisiting_02_en.png"}}
27 {{id name="fig_form_import_dep_exisiting" /}}
28 A form dependency could not be resolved automatically. Every dependency will be listed with its (1) name and (2) a description of where the dependency is needed within the form. In this case the CSS template that is being used as the form theme already exists but is not identical with the one in the form export file. The user now has the option to either (3) override the exisiting template, (4) create a new template or (5) ignore this dependency alltogether.
29 {{/figure}}
30
31 == Form exports from {{formcycle/}} below version 6.2 ==
32
33 After selecting a form export file, the form will be imported. {{formcycle/}} attempts to resolve possible dependencies to [[files & templates>>doc:Formcycle.UserInterface.FilesAndTemplates.WebHome]], [[inboxes>>doc:Formcycle.UserInterface.Inboxes.WebHome]], [[data sources>>doc:Formcycle.UserInterface.Data.Sources.WebHome]], etc. during the import process. If no matching element is found, the dependency can not be resolved. You will need to edit the form and its settings manually.
34
35 {{id name="sub_sec_form_import_new"/}}
36
37 == Form exports from {{formcycle/}} since version 6.2 {{version major="6" minor="2" patch="0"/}} ==
38
39 The import of forms since {{formcycle/}} version 6.2 allows you to update or create existing or missing form dependencies. This means that [[files & templates>>doc:Formcycle.UserInterface.FilesAndTemplates.WebHome]], [[inboxes>>doc:Formcycle.UserInterface.Inboxes.WebHome]], [[data sources>>doc:Formcycle.UserInterface.Data.Sources.WebHome]], etc. can be updated or created during the import process. {{formcycle/}} tries to automate this process as much as possible, so that existing and unchanged dependencies will be resolved automatically. If a dependency could not be resolved automatically, you need to decide how the dependency should be resolved. After the form import, all non-resolved dependencies will be listed in a dialog (see [[figure>>||anchor="fig_form_import_dep_exisiting"]]).
40
41 === When you need to resolve a dependency? ===
42
43 If a form dependency does not exist yet; or it does exist but is not identical to the element in the export file, then you need to resolve this dependency manually. For example, if a missing client file is needed by a workflow action, you have the option to create that file.
44
45 === Access restriction ===
46
47 {{figure image="form_update_access_config_en.png" width="300" clear="h1"}}
48 If the form of the form export has any access restriction that might exclude the user, then the user can remove those restrictions.
49 {{/figure}}
50
51 If the form of the form export has any [[access restriction>>doc:Formcycle.UserInterface.MyForms.Access.WebHome||anchor="admin_restriction"]] to existing user groups and you are neither a client administrator nor part of these [[user groups>>doc:Formcycle.UserInterface.UserSettings.UserGroups.WebHome]], you have the opportunity to change the access restrictions.
52
53 If a restriction exists for //form visibility// or //form editability, //you have the following options:
54
55 ; {{icon name="user"/}} Join the user group
56 : This option only exists you have the necessary [[permission>>doc:Formcycle.UserInterface.UserSettings.Roles.WebHome]] to edit [[user groups>>doc:Formcycle.UserInterface.UserSettings.UserGroups.WebHome]]. By joining the selected user group, you will gain the needed permissions to edit or view the form.
57
58 ; {{ficon name="trash-alt2"/}}Remove restriction
59 : There will not be any restriction anymore.
60
61 ; {{ficon name="close-circle-outline"/}}Keep restriction
62 : The restriction will be unchanged. {{info}}This will lead to you being unable to view or edit the form after it has been updated.{{/info}}
63
64 {{id name="subsec_dependencies"/}}
65
66 === Form dependencies ===
67
68 {{figure image="form_import_dep_exisiting_02_en.png"}}
69 {{id name="fig_form_import_dep_exisiting" /}}
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 {{/figure}}
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.FormDesigner.FormElements.Selection.WebHome]]), 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"]]):
74
75 ; {{icon name="refresh"/}} Override
76 : An element may be overridden if it exists already within the system. This option is not available for inboxes and user groups.
77
78 ; {{ficon name="plus-circle-outline"/}}Create
79 : The dependency will be created as a new element in the system. If necessary, the element will be renamed.
80
81 ; {{icon name="chevron-down"/}} Use alternative
82 : This option is only available for user groups and inboxes. Instead of creating the element, an alternative may be chosen.
83
84 ; {{ficon name="close-circle-outline"/}}Ignore (not recommended)
85 : The form dependency will be ignored altogether. This may lead to issues in displaying and processing the form.
86
87 === Worth to note ===
88
89 ; Default inbox
90 : If a form dependency is the //default inbox,// please note that all new form records will be placed in that inbox. To view those form records, you need to have permission for the inbox. However, if the dependency is ignored, then the system inbox //default inbox// will be the default inbox of the form. See [[form inbox configuration>>doc:Formcycle.UserInterface.MyForms.Inbox.WebHome]] and [[inboxes>>doc:Formcycle.UserInterface.Inboxes.WebHome]] for more information.
91
92 ; Form visibility / form editability
93 : If a form dependency is a user group for the //form visibility// or //form editability// and could not be resolved, then only users of the selected or newly created user group may see or edit the form. This means that if you are not part of the selected user group and no client admin either, you will not be able to see or edit the form until you are a member of that user group. If the dependency is ignored, this access restriction is also ignored. See [[form access configuration>>doc:Formcycle.UserInterface.MyForms.Access.WebHome||anchor="admin_restriction"]] for more information .
Copyright 2000-2024