| ... |
... |
@@ -4,7
+4,7 @@ |
| 4 |
4 |
|{{formcloud/}}|{{formcycle/}} on a cloud, allowing you to edit and manage your forms online.| |
| 5 |
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 |
|
-|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]] |
|
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:Main.Inbox.WebHome]] |
| 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]] |
| 9 |
9 |
|Client|Clients are the top level instance with their own forms, users, user groups, inboxes etc. Different divisions of a company can use the same {{formcycle/}} system with a different client for each division.|[[Client>>doc:MandantenMenue]] |
| 10 |
10 |
|{{mserver/}}|A {{mserver/}} can be used as a stand-alone and provides all of {{formcycle/}}'s functionality. When {{fserver number="plural"/}} are used, the {{mserver/}} is also responsible for managing the connection to each {{fserver/}}.|[[{{mserver/}}and {{fserver/}}>>doc:Frontend- und Masterserver]], [[Server communications overview>>doc:Kommunikationsuebersicht]] |
| ... |
... |
@@ -12,9
+12,9 @@ |
| 12 |
12 |
|Variable|Sometimes it becomes necessary to use the value of certain form fields within {{formcycle/}}. For example, you might want to send a mail to the address the user entered in the form. Variables can be used within fields supporting them. They will be replaced by the corresponding value by the system.|[[Placeholder>>doc:Platzhalter]], [[Alias>>doc:Aliasnamen und Elemente ]] |
| 13 |
13 |
|Plugin (client)|Plugins extend the {{formcycle/}} by providing custom functionality. Client plugins are available only to the client who uploaded them. Plugins are written in Java.|[[Client plugin>>doc:Mandant-Plugins]] |
| 14 |
14 |
|Plugin (system)|Plugins extend the {{formcycle/}} by providing custom functionality. System plugins are available only to all clients. Plugins are written in Java.|[[System Plugins>>doc:System-Plugins]] |
| 15 |
|
-|General inbox|An inbox containing form records of different forms. Data columns cannot be customized.|[[General inbox>>doc:Postfaecher]], [[Inbox>>doc:Inbox]] |
| 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]] |
|
15 |
+|General inbox|An inbox containing form records of different forms. Data columns cannot be customized.|[[General inbox>>doc:Postfaecher]], [[Inbox>>doc:Main.Inbox.WebHome]] |
|
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:Main.Inbox.WebHome]] |
| 17 |
17 |
|Role|A role is assigned to each user, controlling the permissions of that user.|[[Roles>>doc:Rollen]] |
| 18 |
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 |
|
-|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 ]]. |
|
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:Main.Inbox.WebHome]], [[Workflow processing>>doc:Status und Aktionsverarbeitung ]]. |