Wiki source code of Aktualisieren

Hide last authors
jdr 39.1 1 {{figure image="form_menu_update_en.png" width="300" clear="h1"}}
2 Existing forms may be updated with form exports via the [[form menu>>doc:Formcycle.UserInterface.MyForms.WebHome||anchor="form_menu"]].
awa 1.1 3 {{/figure}}
4
5 {{info}}
jdr 39.1 6 **Attention!** Be aware that updating forms overrides all of its settings, including its [[workflow configuration>>doc:Formcycle.Designer.Workflow.WebHome]]. When you update a form that has already been used to collect data, make sure that data is compatible with the new form settings.
awa 1.1 7 {{/info}}
8
jdr 39.1 9 Form exports can be used to update existing forms or to transform them altogether.
awa 1.1 10
jdr 39.1 11 == Requirement ==
awa 1.1 12
jdr 39.1 13 In order to update a form, a form export is needed that has been exported by {{formcycle/}} version **6.2** or higher (either the [[default format>>doc:Formcycle.UserInterface.MyForms.Export.Form||anchor="li_default_format"]] or the [[compatibility format>>doc:Formcycle.UserInterface.MyForms.Export.Form||anchor="li_compatibilty_format"]] can be used).
awa 1.1 14
jdr 39.1 15 == Procedure ==
awa 1.1 16
jdr 39.1 17 After selecting {{icon name="refresh"/}}**Update** from the [[form menu>>doc:Formcycle.UserInterface.MyForms.WebHome||anchor="form_menu"]], a dialog opens which can be used to select a previously exported form file. To learn more about exporting forms, see [[here>>doc:Formcycle.UserInterface.MyForms.Export.Form]].
awa 1.1 18
jdr 39.1 19 The update process starts after a file has been selected. {{formcycle/}} then tries to automatically match states of the old form to states of the selected form export. This is not always possible. If a match could not be found for all states, you need to [[select a new state>>||anchor="subsec_state_mapping"]] [[manually>>||anchor="subsec_state_mapping"]].
awa 1.1 20
jdr 39.1 21 If no state selection was necessary or the state selection has been finished, you now have to decide what you want to do with the active form version (see [[form version>>||anchor="subsec_form_version"]]).
awa 1.1 22
jdr 39.1 23 If you do not have permission to view or edit the form from the form export, you will get the opportunity to adjust the [[form restrictions>>||anchor="subsec_access_config"]].
awa 1.1 24
jdr 39.1 25 After the form update is done, you then need to resolve all unresolved [[form dependencies>>doc:||anchor="subsec_dependencies"]].
awa 1.1 26
jdr 27.2 27 {{id name="subsec_state_mapping"/}}
28
jdr 39.1 29 === State mapping ===
jdr 27.2 30
jdr 39.1 31 {{figure image="form_update_state_mapping_en.png" clear="h1"}}
32 If {{formcycle /}} can not find a matching state, you will be prompted to select a new state from the form export.
jdr 27.2 33 {{/figure}}
34
jdr 39.1 35 A manual state mapping is required only if there are states that with form record in that state, and no matching state in the form export could be found (based on their name).
jdr 27.2 36
jdr 39.1 37 Every non-mapped state will be listed in the dialog along with the number of form records that are in that state. For each of these states, a new state needs to be selected from the list of available states of the form export. Form records that are in that state will be moved to the selected state.
jdr 27.2 38
awa 1.1 39 {{id name="subsec_form_version"/}}
40
jdr 39.1 41 === Form version ===
awa 1.1 42
jdr 39.1 43 {{figure image="form_update_form_version_en.png" clear="h1"}}
44 Before the form update begins, you need to decide whether the currently active form version should be overridden or if the form version of the form export should be created as a new form version.
awa 1.1 45 {{/figure}}
46
jdr 39.1 47 Before the form can be updated, you must decide whether the currently active form version should be overridden; or if the form version of the form export should be created as a new form version. This is particularly important when updating a form that has already been used to collect data.
awa 1.1 48
jdr 39.1 49 If a form has [[form records>>doc:Terminology.WebHome]] in the active form version, then it is recommended to create a new form version. This means that the form version of the form export will be created as a new form version. This also means that previously collected data can still be viewed in its original form version.
awa 1.1 50
jdr 39.1 51 Otherwise, if the active form version is overridden, then this may lead part of the collected data not being viewable anymore - as the names of the form elements can be completely different in both form versions.
awa 1.1 52
jdr 39.1 53 The form update starts after you have decided whether to override the active form version or to create a new one. During this process, {{formcycle/}} attempts to resolve all of the form's dependencies. If afterwards there are dependencies that could not be resolved automatically, you will have to resolve those dependencies manually (see [[form dependenices>>doc:||anchor="subsec_dependencies"]]).
awa 1.1 54
55 {{id name="subsec_access_config"/}}
56
jdr 39.1 57 === Access restriction ===
awa 1.1 58
jdr 39.1 59 {{figure image="form_update_access_config_en.png" width="300" clear="h1"}}
60 If the form of the form export has any access restrictions that might exclude the user, then the user can remove those restrictions.
awa 1.1 61 {{/figure}}
62
jdr 39.1 63 If the form of the form export has got any [[access restriction>>doc:Formcycle.UserInterface.MyForms.Access.WebHome||anchor="admin_restriction"]] to already 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.
awa 1.1 64
jdr 39.1 65 If a restriction exists for //form visibility// or //form editability,// you have the following options:
awa 1.1 66
jdr 39.1 67 ; {{icon name="user"/}} Join the user group
68 : This option only exists if 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 permission to edit or view the form.
awa 1.1 69
jdr 39.1 70 ; {{ficon name="trash-alt2"/}}Remove restriction
71 : There will not be any restriction anymore.
awa 1.1 72
jdr 39.1 73 ; {{ficon name="close-circle-outline"/}}Keep restriction
74 : 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}}
awa 1.1 75
76 {{id name="subsec_dependencies"/}}
77
jdr 39.1 78 === Form dependencies ===
awa 1.1 79
jdr 39.1 80 {{figure image="form_import_dep_exisiting_02_en.png"}}
awa 1.1 81 {{id name="fig_form_import_dep_exisiting" /}}
jdr 39.1 82 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 by form. Alternative existing CSS templates can be used, which are already created in the backend (3). 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. You now have the option to either override the existing template (4), create a new template (5) or ignore this dependency altogether (6).
awa 1.1 83 {{/figure}}
84
jdr 39.1 85 //Form dependencies// are [[files & templates>>doc:Formcycle.UserInterface.FilesAndTemplates.WebHome]], [[inboxes>>doc:Formcycle.UserInterface.Inboxes.WebHome]], [[data sources>>doc:Formcycle.UserInterface.Data.Sources.WebHome]], etc. that are used by the form. These dependencies may be used inside the form (e.g. for [[select elements>>doc:Formcycle.FormDesigner.FormElements.Selection.WebHome]]), in the form settings or in the [[workflow>>doc:Formcycle.Designer.Workflow.WebHome]] of the form (e.g. inside of action configurations). 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"]]):
awa 1.1 86
jdr 39.1 87 ; {{icon name="refresh"/}} Override
88 : An element may be overridden if it already exists within the system. This option is not available for inboxes or user groups.
awa 1.1 89
jdr 39.1 90 ; {{ficon name="plus-circle-outline"/}}Create
91 : The dependency will be created as a new element in the system. If necessary, the name of the element will be adjusted.
awa 1.1 92
jdr 39.1 93 ; {{icon name="chevron-down"/}} Use alternative
94 : Instead of creating the element, an alternative may be chosen.
awa 1.1 95
jdr 39.1 96 ; {{ficon name="close-circle-outline"/}}Ignore (not recommended)
97 : The form dependency will be ignored altogether. This may lead to issues in displaying and processing the form.
awa 1.1 98
jdr 39.1 99 === Worth to note ===
awa 1.1 100
jdr 39.1 101 ; Default inbox
102 : If a form dependency is the //default inbox// then it should be noted that all new form records will be placed in that inbox. To view those form records you need to have permission for this inbox. However, if that dependency is ignored, the system inbox //default inbox// will become 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.
awa 1.1 103
jdr 39.1 104 ; Form visibility / form editability
105 : If a form dependency is a user group for the //form visibility// or //form editability// and could not be resolved, 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 not a client admin either, you will not be able to see or edit the form until you are part of that user group. If the dependency is ignored, the access restriction is ignored as well. See [[form access configuration>>doc:Formcycle.UserInterface.MyForms.Access.WebHome||anchor="admin_restriction"]] for more information.