Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-$services.localization.render("PT.Main.Begriffserklaerung")
	1	+Terminology

Content

...	...	@@ -1,4 +2,3 @@
1		-{{table dataTypeAlpha="0" preSort="0-asc"}}
2	2	|=Term|=Description|=Links
3	3	|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]]
4	4	|{{designer/}}|Form editor for creating forms.|[[{{designer/}}>>doc:Designer]]
...	...	@@ -19,4 +19,3 @@
19	19	|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:Plugin-Entwicklung.IPluginServletAction]], [[Queries>>doc:Abfragen]], [[Working with form URLs>>doc:URL zum Aufruf von Formularen]]
20	20	|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//.|
21	21	|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 ]].
22		-{{/table}}