| ... |
... |
@@ -2,7
+2,7 @@ |
| 2 |
2 |
|Cluster|{{formcycle/}} can be run on multiple servers, called {{mserver number="plural"/}} and {{fserver number="plural"/}}. When one server fails, another server can take over and replace that server. All servers connected to each other this way are called a cluster.|[[Cluster>>doc:ClusterMenue]], [[{{mserver/}} and {{fserver/}}>>doc:Frontend- und Masterserver]], [[Server communications overview>>doc:Kommunikationsuebersicht]] |
| 3 |
3 |
|{{designer/}}|Form editor for creating forms.|[[{{designer/}}>>doc:Main.FormDesigner.WebHome]] |
| 4 |
4 |
|{{formcloud/}}|{{formcycle/}} on a cloud, allowing you to edit and manage your forms online.| |
| 5 |
|
-|Form|A form is a web page where users can enter and submit data, such as a contact form, order form, or support request form.|[[Forms>>doc:Formulare]], [[Form settings>>doc:Main.FormDesigner.Formulareinstellungen]] |
|
5 |
+|Form|A form is a web page where users can enter and submit data, such as a contact form, order form, or support request form.|[[Forms>>doc:Formulare]], [[Form settings>>doc:Main.FormDesigner.FormProperties]] |
| 6 |
6 |
|{{fserver/}}|A {{fserver/}} provides users with access to forms and accepts or rejects forms that have been submitted. It does not handle management or administrative services, such as editing forms or viewing forms in the inbox.|[[{{mserver/}} and {{fserver/}}>>doc:Frontend- und Masterserver]], [[Server communications overview>>doc:Kommunikationsuebersicht]] |
| 7 |
7 |
|Inbox|Contains all forms that have been submitted, called form records. There are form specific inboxes containing only form records of a certain form, and general inboxes containing forms records of different forms.|[[Inbox>>doc:Inbox]] |
| 8 |
8 |
|LDAP|{{formcycle/}} allows you to create and manage users directly, but users can also be managed by connection to an LDAP (MS active directory).|[[LDAP>>doc:LDAP]] |
| ... |
... |
@@ -15,6
+15,6 @@ |
| 15 |
15 |
|General inbox|An inbox containing form records of different forms. Data columns cannot be customized.|[[General inbox>>doc:Postfaecher]], [[Inbox>>doc:Inbox]] |
| 16 |
16 |
|Form specific inbox|An inbox containing only form records of a specific form. Data columns can be customized. This allows you to view certain form fields without having to open the form.|[[Form specific inbox>>doc:Postfach]], [[Inbox>>doc:Inbox]] |
| 17 |
17 |
|Role|A role is assigned to each user, controlling the permissions of that user.|[[Roles>>doc:Rollen]] |
| 18 |
|
-|Servlet|Servlets are run on the server when requested by the client, and can return data from the system or make changes to the system.|[[IPluginServletAction>>doc:Main.PluginDevelopment.Types.IPluginServletAction]], [[Queries>>doc:Abfragen]], [[Working with form URLs>>doc:URL zum Aufruf von Formularen]] |
|
18 |
+|Servlet|Servlets are run on the server when requested by the client, and can return data from the system or make changes to the system.|[[IPluginServletAction>>doc:Main.PluginDevelopment.Types.IPluginServletAction]], [[Queries>>doc:Abfragen]], [[Working with form URLs>>doc:Main.FormDesigner.URLsForOpeningForms]] |
| 19 |
19 |
|State|When a form is submitted, is in the special system state //Received//. Other custom states can be defined by adding them in the workflow processing. For example, a job interview form might have the two additional states //Accepted// and //Rejected//.|\\ |
| 20 |
20 |
|Workflow processing|After a form has been submitted, workflow processing starts. Depending on the form's state, certain actions will be executed, such as generating PDF files, sending mails etc. State transitions can be performed manually in the inbox, or by the system.|[[Inbox>>doc:Inbox]], [[Workflow processing>>doc:Status und Aktionsverarbeitung ]]. |