From version < 28.1 >
edited by nlo
on 21.05.2019, 17:00
To version < 29.1 >
edited by nlo
on 06.08.2019, 14:23
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,6 +8,7 @@
8 8  The dialog for editing the access and availability configurations of a form (see [[figure>>||anchor="fig_form_access_dialog"]]) can be opened by clicking the //Access// button {{ficon name="user"/}} in the [[form menu>>doc:Formcycle.UserInterface.MyForms.WebHome||anchor="form_menu"]].
9 9  
10 10  == General settings ==
11 +
11 11  === Availability ===
12 12  
13 13  The //online// checkbox lets you switch the form on-/offline. When set to offline, the form cannot be viewed or submitted. Use this for example when you wish to perform maintenance operations.
... ... @@ -17,6 +17,7 @@
17 17  * {{litem title="Frontend server"}}By default the form can be accessed on the [[master server>>doc:Terminology.WebHome||ancher="master_server"]]. The form may be made available on a [[frontend server>>doc:Formcycle.UserInterface.Client.FrontendServer.WebHome]] as well, if one has been configured for the client. If no frontend server is selected the form is only accessible on the master server.{{/litem}}
18 18  
19 19  === Login protection ===
21 +
20 20  This fieldset allows you to restrict access to the form only to a selected group of users.
21 21  
22 22  * {{litem title="Accessible by"}}Only [[users>>doc:Formcycle.UserInterface.UserSettings.User.WebHome]] that are members of the selected groups will have access to the form (open, fill out, submit, ...). If no user group is selected, no restriction applies and all users may view the form. If a restriction to certain user groups is set, a login screen is shown when trying to open the form ([[HTML templates>>doc:Formcycle.UserInterface.FilesAndTemplates.HTML.WebHome]]).{{/litem}}
... ... @@ -24,11 +24,13 @@
24 24  * {{litem title="Auto login (SSO)"}}When this options is activated, the form can be opened only with a valid domain login. Available only for licenses with the option [[NTLM>>doc:Formcycle.SystemSettings.UserInterface.SingleSignOn.WebHome]].{{/litem}}
25 25  
26 26  === Password protection ===
29 +
27 27  In order to limit access to the form one can also set a **form password**. This password must be entered everytime to view, fill out and submit the form.
28 28  
29 29  === Editing protection ===
30 30  
31 -Only users belonging to the selected user groups may edit this form in the {{designer/}}. An [[error message>>doc:Formcycle.UserInterface.FilesAndTemplates.HTML.WebHome]] is displayed when an unauthorized user attempts to open the form. If no user group is selected, all user may edit the form.
34 +{{info}}Client administrators can always edit the form, regardless of their user group.{{/info}}
35 +Only users belonging to the selected user groups may edit this form in the {{designer/}}. An [[error message>>doc:Formcycle.UserInterface.FilesAndTemplates.HTML.WebHome]] is displayed when an unauthorized user attempts to open the {{designer/}}. Only users belonging to the selected user group have access to the configuration screens of the [[form menu>>Formcycle.UserInterface.MyForms||anchor="form_menu"]]. If no user group is selected, all user may edit the form.
32 32  
33 33  === Data protection ===
34 34  
... ... @@ -35,6 +35,7 @@
35 35  When the option **anonymize** is activated, the user name of the user who submitted the form is not logged in the system's [[protocol>>doc:Formcycle.UserInterface.Protocol.WebHome]].
36 36  
37 37  {{id name="duplicate_data_sets"/}}
42 +
38 38  === One-time submission ID ===
39 39  
40 40  Some forms may only be sent once per user or mail address. This forms allows you to configure an ID template that should contain [[variables>>doc:Formcycle.UserInterface.Variables.WebHome]], so that submitted forms with the same generated ID as already existing form records are rejected.
Copyright 2000-2024