Wiki source code of Zugriff

Hide last authors

version	line-number	content
1.1	1	{{content/}}
	2
13.1	3	{{figure image="form_access_dialog_en.png" clear="global"}}
	4	{{id name="fig_form_access_dialog" /}}
	5	The configuration dialog //Access// with various settings for permissions and the form's availability.
	6	{{/figure}}
1.1	7
13.1	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"]].
1.1	9
13.1	10	== General settings ==
10.6	11
13.1	12	=== Availability ===
10.7	13
13.1	14	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.
1.1	15
13.1	16	* {{litem title="Availability window"}}This lets you limit the form's availability to a certain time range. When the form is not available, it can neither be viewed nor submitted. When no limit is set for //available from// and //Available until//, no restriction applies.{{/litem}}
1.1	17
13.1	18	* {{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}}
1.1	19
13.1	20	{{figure image="offline_process_en.png" width="300"}}
	21	Configure the behaviour of an process for forms that are offline.
	22	{{/figure}}
10.2	23
13.1	24	If the availability of the form is set to offline, it is possible to define the behaviour of a process for the end user and inbox user. It can be decided whether the process is never available, whether it can be opened or whether it can be opened and submited.
10.4	25
1.1	26	{{id name="form_login"/}}
	27
13.1	28	=== Form login ===
1.1	29
13.1	30	This configuration area allows you to provide different methods with which users can or must log in to the form. Information of the logged in user can be accessed within the form & the workflow processing using [[user variables>>doc:Formcycle.UserInterface.Variables.WebHome\|\|anchor="sec_user_variables"]].
	31	If no settings are made in this area, the form is public and can be accessed by any user without login.
1.1	32
13.1	33	; Authenticators (external users)
	34	: Here you can enable configured external users, system, NTLM or Kerberos logins. The selected login methods are available when the form is called.
1.1	35
13.1	36	; Accessible by
	37	: Only the users of the selected group have access to the form. This restriction applies only to users who have logged in to the form by system login, NTLM or Kerberos. If no user group is selected, there is no restriction for these login types.
1.1	38
13.1	39	; form password
	40	: To restrict access to the form, a form password can also be entered.
1.1	41
13.1	42	; Without login
	43	: If users are to be able to access the form without logging in, this checkbox must be activated. This option is only available if one of the login options above is activated.
1.1	44
	45	{{id name="admin_restriction"/}}
	46
13.1	47	=== Administrative protection ===
1.1	48
	49	{{info}}
13.1	50	Client administrators can always edit the form, regardless of their user group.
1.1	51	{{/info}}
	52
13.1	53	This section lets you configure which users are allowed access to the forms. It consists of two parts:
1.1	54
13.1	55	; Only editable by
	56	: Here you can choose which user groups may access the {{designer/}} and the change the settings in the configuration pages available from the [[form menu>>Formcycle.UserInterface.MyForms\|\|anchor="form_menu"]]. When no user groups are selected, all users of the [[client>>doc:Formcycle.UserInterface.Client.WebHome]] are allowed to make changes to the form's configuration.
	57	; Only visible for
	58	: Here you can choose which user groups can see the form on the form overview page. When a user is allowed to edit the form, they can see it even if not explicitly configured by this setting. When no user groups are selected, all users of the [[client>>doc:Formcycle.UserInterface.Client.WebHome]] can see the form.
1.1	59
13.1	60	=== Data protection ===
1.1	61
13.1	62	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]].
1.1	63
	64	{{id name="duplicate_data_sets"/}}
	65
13.1	66	=== One-time submission ID ===
1.1	67
13.1	68	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.
1.1	69
13.1	70	{{figure image="access2_en.png"}}
	71	The error message displayed when attempting to submit a form with the same one-time submission ID twice. Customize this error message by editing the corresponding [[HTML system template>>doc:Formcycle.UserInterface.FilesAndTemplates.HTML.WebHome]] {{enquote text="One-time submission error"/}}.
1.1	72	{{/figure}}
	73
13.1	74	Assuming a form contains an input field //tfMail//, the following one-time submission ID can be used to limit form submissions to distinct mail addresses.
1.1	75
	76	{{code language="none"}}
	77	[%tfMail%]
	78	{{/code}}
	79
13.1	80	Every time a form is submitted, the one-time submission ID is generated from the value of the input field //tfMail//. If there exists a form record with this ID already, the submission is rejected and an error message is displayed. This error message can be customized by editing the [[HTML system template>>doc:Formcycle.UserInterface.FilesAndTemplates.HTML.WebHome]] //One-time submission error//.
1.1	81
13.1	82	Available variables are form value variables and template variables.
1.1	83
13.1	84	In case the generated one-time submission ID is empty after all variables were replaced, the check is skipped and the form submission is not rejected. It is recommended you mark all form fields for the one-time submission ID as required.
1.1	85
13.1	86	The one-time submission ID must not be longer than 1024 characters. If possible, set a length restriction on the corresponding form fields in the {{designer/}}.
1.1	87
13.1	88	When changing the one-time submission ID template, you can update all existing form records with the button to the top left. In case this result in duplicate IDs, the update process is aborted and all conflicting form records are shown. If the ID template is empty and an update is performed, all existing IDs are removed.
1.1	89
13.1	90	== Settings per state ==
1.1	91
13.1	92	These settings can be configured separately for each state.
1.1	93
13.1	94	=== Advanced options: deletion & review ===
1.1	95
13.1	96	; Process-Link without login
	97	: When this option is enabled, form records with this state may be viewed by anonymous users, assuming they have got a link to the form with the process ID.
	98	When this option is disabled, users need to sign in in order to gain access to form records.
	99
	100	; Form record deletable
	101	: Whether a form record with this state can be deleted in the [[inbox>>doc:Inbox]].