You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
| Subject | Property | Explanation | Example | |
|---|---|---|---|---|
| Misc | blueriq.production.shortcuts-only | Only possible to start flows with shortcut (instead of 'dash start url') |
| |
| blueriq.fileupload.maxuploadsize | maximum request size for the built-in file upload container, in bytes. Note: this is per request, so if you upload multiple files in one go, the total size of those files is validated against this property. Since 16.1 defaults to 10MB |
| # set the max upload size to 10 MB blueriq.fileupload.maxuploadsize=10485760 | |
| blueriq.fileupload.detect-content-type | Guesses the content type of uploaded files based on the actually uploaded data, instead of using the content type as present in the request. From a security perspective, it is advised that this option is enabled to reject malicious uploads. Available since R12.10, defaults to true. |
| ||
| blueriq.fileupload.validate-content-type | If enabled, the content type of the file is used to determine the supposed extension that is then validated against the list of allowed extensions. From a security perspective, it is advised that this option is enabled to reject malicious uploads. Available since R12.10, defaults to true. | |||
| blueriq.license | the license for blueriq (content of the license file). Property is optional. One should set either this property or place a license file in the |
| The property blueriq.license=0MtWfrubLL4Rq6TH/4TfNleRJqJHtSQIYe070... | |
| blueriq.cache.timeout | This property is used to specified the timeout that has to pass before the data in the aggregate / Process statistics container is considered not up to date and has to be reloaded. |
| ||
| blueriq.runtimekeys.enabled | The element keys created by the Runtime that are send to the browser to build the HTML are now containing the element name prefixed by the page ID. E.g. P108-C0-C0-F0 is now P108_Person_Firstname_1. This way, the pagemodel which is used to build the HTML is more stable and in turn leads to a more predictable way of testing. This functionality is enabled by default. |
| ||
| blueriq.webservices.create-empty-elements-for-unknowns | Controls whether generating empty elements for unknown relations should be enabled. This property is available in Blueriq 14. Use the Legacy Property in earlier versions. |
| ||
| blueriq.webservices.structured-input-validation | The webservice responses can be returned by Blueriq in a more structured way when input validations are triggered so those can be used in the model of the receiver. When this functionality is enabled, the error message returned for an invalid request is split up in such a way that validation messages can be handled separately and indicate the exact instance which is not valid. When this functionality is disabled, the error message is one string containing the validation message. This functionality only applies to REST services based on domain schemas. This functionality is disabled by default. |
|
Overview
Content Tools