Changes for page Anwendungseinstellungen


From version 7.7
edited by awa
on 29.09.2022, 16:04
Change comment: There is no comment for this version
To version 5.2
edited by awa
on 02.02.2022, 13:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -95,15 +95,11 @@
95 95  
96 96  {{table dataTypeAlpha="0" preSort="0-asc" caption="Various settings regarding the application"}}
97 97  |= Property|= Default value|= Explanation
98 -|bot.field.name|x-i-m-a-5536-required|Name of the hidden input field [[for detecting bots>>doc:Formcycle.SystemSettings.ErrorMessageTemplates]]. Since V7, the field name is automatically renewed when the form is opened.
99 -|{{version major="7" minor="1"/}} bot.field.autocomplete|new-password|Value for the //autocomplete// attribute of the bot field. When this property is not present, it defaults to //new-password//. When the value is empty, the //autocomplete// attribute is not set. Any other value is used for the //autocomplete// attribute.
98 +|bot.field.name|x-i-m-a-5536-required|Name of the hidden input field [[for detecting bots.>>doc:Formcycle.SystemSettings.ErrorMessageTemplates]]
100 100  |defaults.systemeinstellung.loginName|sadmin|Login name for the super administrator of the system.
101 101  |defaults.systemeinstellung.passwort|hash(admin)|Login name for the super administrator of the system. Should be changed after installing the application. The password is stored hashed, it should not be set manually in the configuration file, but only via the user interface.
102 102  |cluster.implementation|jgroups|The implementation used for [[clustering>>doc:Formcycle.SystemSettings.UserInterface.Cluster.WebHome]]. Allowed options are [[jgroups>>http://www.jgroups.org/||target="_blank"]] and [[shoal>>https://javaee.github.io/shoal/||target="_blank"]].
103 103  |system.server.id |(generated)|Unique ID of the server which can be included in the HTTP header and attached to the submit URL of a form for the use of load balancers. See //HTTP//.
104 -|{{version major="7" minor="1"/}} monitoring.enabled|false|Whether the [[frontend server monitoring URL>>doc:Formcycle.SystemSettings.Monitoring]] is enabled.
105 -|{{version major="7" minor="1"/}} monitoring.allowed.hosts|(empty)|List of host, that are allowd to access the [[frontend server monitoring URL>>doc:Formcycle.SystemSettings.Monitoring]] . localhost (loopback) is always granted access.
106 -|defaults.http.use_system_properties {{version major="7" minor="2"/}}|true|When //true//, uses settings from JVM system properties to configure HTTP requests. The following system properties are read: //https.protocols//, //https.cipherSuites//, //http.keepAlive//, //http.maxConnections//, //http.agent//. In addition, when a proxy was configured for the JVM, that proxy is used unless an explicit proxy server was configured within {{formcycle/}}. Finally, when attempting to access protected resources, the default system credentials provider is also queried for credentials.
107 107  {{/table}}
108 108  
109 109  == Limits ==
... ... @@ -115,7 +115,7 @@
115 115  |defaults.upload.max_fieldsize|0|Maximum size in bytes when retrieving columns of type //character// (eg. char or varchar) or //binary//. Set to {{code language="none"}}0{{/code}} to disable.
116 116  {{/table}}
117 117  
118 -== Frontend server ==
114 +== Frontend Server ==
119 119  
120 120  These settings control the connection to the {{fserver/}}. They should be edited [[via the user interface>>doc:Formcycle.SystemSettings.UserInterface.FrontendServer]].
121 121  
... ... @@ -146,7 +146,7 @@
146 146  |http.header.referer|same-origin|The referre policy for HTTP responses. You can also change this setting [[in the system settings menu >>doc:Formcycle.SystemSettings.UserInterface.General.WebHome]].
147 147  |http.header.hsts.max|(empty)|The value for the //max-age// of the HTTP Strict Transport Security. You can also change this setting [[in the system settings menu >>doc:Formcycle.SystemSettings.UserInterface.General.WebHome]].
148 148  |http.header.hsts.sub|false|Whether the HTTP Strict Transport Security should be applied to sub domains as well. You can also change this setting [[in the system settings menu >>doc:Formcycle.SystemSettings.UserInterface.General.WebHome]].
149 -|http.header.serverid.name |(not available)|Specifies the header name with which the //system.server.id// is written to all requests. If this entry exists but is empty the corresponding header will not be set. If the entry does not exist the default //XFC-Server-Id// is used.
145 +|http.header.serverid.name |(not available)|Specifies the header name with which the //system.server.id// is written to all requests. If this entry exists but is empty the corresponding header will not be set. If the entry does not exist the default //XFC-Server-Id// is used.
150 150  |http.param.serverid.name |(not available)|Specifies the name of the URL parameter used to append the //system.server.id// to the form submission URL. If the value is empty or not available, no parameter will be appended.
151 151  {{/table}}
152 152  
... ... @@ -175,68 +175,3 @@
175 175  |mail.smtp.connectiontimeout {{version major="7" minor="0" patch="4" /}}|300000|SMTP Socket connection timeout value in milliseconds.
176 176  |mail.smtp.timeout {{version major="7" minor="0" patch="4" /}}|300000|SMTP Socket I/O timeout value in milliseconds.
177 177  {{/table}}
178 -
179 -== Workflow ==
180 -
181 -The following properties can be used to selectively enable or disable certain events or actions of the new workflow.
182 -
183 -The properties for events share the following pattern:
184 -
185 -{{code language="text"}}
186 -trigger.<technical_name_of_the_event>.enable=false
187 -{{/code}}
188 -
189 -The properties for actions share the following pattern:
190 -
191 -{{code language="text"}}
192 -processing.<technical_name_of_the_action>.enable=false
193 -{{/code}}
194 -
195 -The technical event names are as follows:
196 -
197 -* //fc_catch_error//: Workflow error
198 -* //fc_doi_verified//: Double opt-in confirmed
199 -* //fc_form_submit_button//: Technical name
200 -* //fc_invitation_error//: Invitation failed
201 -* //fc_invitation_sent//: Invitation sent
202 -* //fc_manual//: Custom
203 -* //fc_qualified_form_submit_button//: Submit button
204 -* //fc_state_timer//: After state change
205 -* //fc_time_point//: Date and time
206 -
207 -The technical action names are as follows:
208 -
209 -* //fc_change_form_availability//: Change availability
210 -* //fc_change_form_value//: Change form values
211 -* //fc_change_state//: Set state
212 -* //fc_compress_as_zip//: Compress files
213 -* //fc_copy_form_record//: Copy form record
214 -* //fc_counter//: Change counter
215 -* //fc_create_text_file//: Create text file
216 -* //fc_delete_form_record//: Delete form record
217 -* //fc_doi_init//: Send double opt-in email
218 -* //fc_email//: Email
219 -* //fc_empty//: Empty statement
220 -* //fc_experiment//: Handle errors
221 -* //fc_export_to_persistence//: Export to persistence file
222 -* //fc_export_to_xml//: Export as XML
223 -* //fc_fill_pdf//: Fill PDF document
224 -* //fc_fill_word//: Fill word document
225 -* //fc_import_form_value_from_xml//: Import from XML
226 -* //fc_ldap_query//: LDAP query
227 -* //fc_move_form_record_to_inbox//: Move to inbox
228 -* //fc_multiple_condition//: Condition (Check value)
229 -* //fc_post_request//: HTTP request
230 -* //fc_provide_resource//: Provide file
231 -* //fc_queue_task//: Queue custom event
232 -* //fc_redirect//: Redirect
233 -* //fc_renew_process_id//: Create new process ID
234 -* //fc_return//: Stop processing chain
235 -* //fc_return_file//: File download
236 -* //fc_save_to_file_system//: Save to file system
237 -* //fc_set_saved_flag//: Save
238 -* //fc_show_template//: HTML response page
239 -* //fc_sql_statement//: Database query
240 -* //fc_throw_exception//: Throw error
241 -* //fc_write_form_record_attributes//: Set server attribute
242 -* //sequence//: Block statement