| ... |
... |
@@ -10,10
+10,10 @@ |
| 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]] |
| 11 |
11 |
|NTLM|NTLM can be used for authenticating users of a form. This is commonly used for internal forms of a company to identify the employees using the form, allowing the form to access the user's data via NTML. |[[NTLM >>doc:NTLMMenue]] |
| 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:Main.Administration.Placeholder]], [[Alias>>doc:Main.Administration.Aliases]] |
| 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]] |
|
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:Main.Administration.Modules.Client.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 |
15 |
|General inbox|An inbox containing form records of different forms. Data columns cannot be customized.|[[General inbox>>doc:Main.Administration.Modules.Inboxes]], [[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]] |
|
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:Main.Administration.Modules.MyForms.Inbox]], [[Inbox>>doc:Main.Inbox.WebHome]] |
| 17 |
17 |
|Role|A role is assigned to each user, controlling the permissions of that user.|[[Roles>>doc:Main.Administration.Modules.UserSettings.Roles]] |
| 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:Main.Administration.Modules.Data.DBQueries]], [[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//.|\\ |