This page described all the properties that can be set for the runtime.

The message properties are not in these lists because of the self explanatory properties in these files (default and language variants) and the sheer amount of them.

But to give you an idea, here is an example of a messages*.properties file: messages_en-GB.properties.

All properties

Subject	Property	Default	Explanation	Property file	Additional information
Aggregates	blueriq.customerdata-client.list.record.limit	10	Maxiumum results of the search.	`application.properties`
	blueriq.customerdata-client.url		Url for the customerdata service	`application.properties`
	blueriq.customerdata-client.username		Username used for authentication against the customerdata service	`application.properties`
	blueriq.customerdata-client.password		Password used for authentication against the customerdata service	`application.properties`
	blueriq.customerdata-client.preemptive-authentication	true	Use preemptive authentication	`application.properties`	since 11.8

Subject	Property	Default	Explanation	Property file
Service call type: AQ_MailService	blueriq.mail.dkim.domain_alias.name		Specifies the domain name for dkim.	`application.properties`
	blueriq.mail.dkim.domain_alias.enabled	false	Enable/disable dkim.	`application.properties`
	blueriq.mail.dkim.domain_alias.selector		Specifies the DNS selector for dkim.	`application.properties`
	blueriq.mail.dkim.domain_alias.private-key-file		Specify the path to the private key file used for dkim in signing email messages.	`application.properties`

Properties

Subject	Property	Default	Explanation	Property file
Cluster	blueriq.session.session-manager		Configures the type of session manager used. The session manager can be 'memory', 'external' or a custom implemented bean.	`application.properties`
Cluster	blueriq.session.request-ward-enabled	false	Toggle to enable request wards	`application.properties`

Messages

Subject	Key	Explanation
Cluster	request-ward.invalid.title	The title of the error message when request ward validation fails
Cluster	request-ward.invalid.message	The error message when request ward validation fails

Subject	Property	Explanation
CMIS	blueriq.cmis.user	The username needed for the cmis connection.	`application-cmis-client.properties`
	blueriq.cmis.password	The password needed for the cmis connection.	`application-cmis-client.properties`
	blueriq.cmis.services-url	The serviceURL of the cmis connection.	`application-cmis-client.properties`
	blueriq.cmis.repository-id	The repository on the filesystem the cmis connection connects to.	`application-cmis-client.properties`
	blueriq.cmis.objectType-id	The kind of objectType the file is.	`application-cmis-client.properties`
	blueriq.cmis.binding-type	The type of communication you desire. Currently the only supported value is `atompub`	`application-cmis-client.properties`
	blueriq.cmis.authProviderClassName	The classname of the authProvider	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration.jwt.ks.fileUrl	URL pointing to key store containing RSA private/public keys for JWT signing	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration.jwt.ks.password	Key store password	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration. jwt.ks.blueriqKeyAlias	Alias of key that Blueriq should use for JWT signing	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration. jwt.ks.blueriqKeyPassword	Password for key that Blueriq should use for JWT signing	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration.jwt.claims.iss	Standard 'issuer' claim to put in Json Web token	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration.jwt.claims.aud	Standard 'audience' claim to put in Json Web token	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration.jwt.claims.sub	Standard 'subject' claim to put in Json Web token	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration.jwt.claims.idp	Custom claim to put in Json Web token	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration. jwt.blueriqUser.id.claimName	JWT claim name to put the Blueriq user id in	`application-cmis-client.properties`
	blueriq.cmis.authProviderConfiguration. jwt.cmisConnector.id.claimName	JWT claim name to put the CMIS connector id in	`application-cmis-client.properties`

Subject	Property	Explanation
Connections	blueriq.connection.[name].sql.type	The type of sql connection (ie. jdbc)	`application.properties`
	blueriq.connection.[name].sql.url	The url of the datasource which should be connected to.	`application.properties`
	blueriq.connection.[name].sql.driver	The driver that needs to be used to connect to the datasource	`application.properties`
	blueriq.connection.[name].sql.username	The username to login to the datasource	`application.properties`
	blueriq.connection.[name].sql.password	The password to login to the datasource	`application.properties`
	blueriq.connection.[name].filesystem.path	The path of the filesystem	`application.properties`
	blueriq.connection.[name].memory	Name of a memory connection.	`application.properties`
	blueriq.connection.names	A comma-separated list of connection names, which are later defined using connection.<name>.	`application.properties`
	blueriq.connection.headers	A comma-separated list of http-header names which will be send as header on a outgoing request. More info here.	`application.properties`	@since 11.6
	blueriq.connection.[name].http.url	The URL of the REST web service.	`application.properties`
	blueriq.connection.[name].http.username	The username for basic authentication.	`application.properties`
	blueriq.connection.[name].http.password	The password for basic authentication.	`application.properties`
	blueriq.connection.[name].http.headerNames	A comma-separated list of http-header names which will be send as header on a outgoing request for this connection. Overrides blueriq.connection.headers. More info here.	`application.properties`	@since 11.6
	blueriq.connection.[name].http.timeout	The timeout in milliseconds.	`application.properties`
	blueriq.connection.[name].http.authentication	If the Runtime authentication is set to openid-connect, then setting this property to 'openid-connect' will make the webservice send along a bearer Authorization header. Since Blueriq 13.12, it is also possible to set this property to 'oauth2' for Oauth2 authentication. The next 5 properties will configure Oauth2.	`application.properties`
	blueriq.connection.[name].http.oauth2-token-endpoint	The URL of the OAuth2 authentication server, where tokens can be requested(required)	`application.properties`	@since 13.12
	blueriq.connection.[name].http.oauth2-client-id	The id of the client that a token should be requested for (required)	`application.properties`	@since 13.12
	blueriq.connection.[name].http.oauth2-client-secret	The secret key of the client where a token should be requested for (required)	`application.properties`	@since 13.12
	blueriq.connection.[name].http.oauth2-grant-type	The value of the grant type parameter when requesting a token	`application.properties`	@since 13.12
	blueriq.connection.[name].http.oauth2-scope	The scope that we want to request a token for	`application.properties`	@since 13.12
	blueriq.connection.[name].soap.url	The URL of the SOAP web service.	`application.properties`
	blueriq.connection.[name].soap.username	The username for basic authentication.	`application.properties`
	blueriq.connection.[name].soap.password	The password for basic authentication.	`application.properties`
	blueriq.connection.[name].soap.security.implementations	A comma separate list of security implementations (defined using the blueriq.soap.security.* properties)	`application.properties`
	blueriq.connection.[name].soap.timeout	The timeout in milliseconds.	`application.properties`
	blueriq.connection.[name].soap.headers	A comma-separated list of http-header names which will be send as header on a outgoing request for this connection. Overrides blueriq.connection.headers. More info here.	`application.properties`	@since 11.6
	blueriq.connection.[name].email.smtp	The hostname of the SMTP server.	`application.properties`
	blueriq.connection.[name].email.smtpport	The port of the SMTP server.	`application.properties`
	blueriq.connection.[name].email.username	The username to use when connecting to the SMTP server.	`application.properties`
	blueriq.connection.[name].email.password	The password to use when connecting to the SMTP server.	`application.properties`
	blueriq.connection.[name].email.usetls	Indicates if the SMTP server should be contacted using TLS.	`application.properties`
	blueriq.connection.[name].email.fromaddress	An email address from which to send the email.	`application.properties`
	blueriq.connection.[name].email.toaddress	An email address to which to send the email.	`application.properties`
	blueriq.connection.[name].email.ccaddresses	Addresses to put in cc.	`application.properties`
	blueriq.connection.[name].email.bccaddresses	Addresses to put in bcc.	`application.properties`
	blueriq.connection.[name].resource.path	Defines a path to a resource.	`application.properties`
	blueriq.connection.[name].external-flow.project	The REQUIRED name of the project that contains the flow to be started	`application.properties`
	blueriq.connection.[name].external-flow.version	The REQUIRED version of the project that contains the flow to be started, e.g. 0.0-Trunk	`application.properties`
	blueriq.connection.[name].external-flow.flow	The REQUIRED name of the flow to be started	`application.properties`
	blueriq.connection.[name].external-flow.channel	The OPTIONAL name of the channel be started	`application.properties`
	blueriq.connection.[name].external-flow.baseurl	The OPTIONAL URL of the external host where the target project is on (if omitted the same server is assumed).	`application.properties`

For the Blueriq Runtime there are two types of datasources that you can define in your properties: jndidatasources or externaldatasources. You can only enable one type by providing the type in the property spring.profiles.active.

Datasource configuration for the Customerdata Service can be found here: Customerdata service#Configuration

Subject	Property	Default	Explanation	Property file spring.profiles.active= `externaldatasources`	Property file spring.profiles.active= `jndidatasources`
Datasources	blueriq.datasource.[name].url		The url of the datasource which should be connected to.	`application-externaldatasources.properties`	Only available when you have `externaldatasources` enables instead of `jndidatasources`.
	blueriq.datasource.[name].username		The username to login to the datasource	`application-externaldatasources.properties`	Only available when you have `externaldatasources` enables instead of `jndidatasources`.
	blueriq.datasource.[name].password		The password to login to the datasource	`application-externaldatasources.properties`	Only available when you have `externaldatasources` enables instead of `jndidatasources`.
	blueriq.datasource.[name].driverClassName		The driver that needs to be used to connect to the datasource	`application-externaldatasources.properties`	Only available when you have `externaldatasources` enables instead of `jndidatasources`.
	blueriq.datasource.[name].jndiName		The name of the jndi datasource connection.	Only available when you have `jndidatasources`instead of `externaldatasources`.	`application-jndidatasources.properties`
	blueriq.hibernate.[name].hbm2ddl.auto	validate	When starting server (SessionFactory) create/update/create-drop/validate	`application-externaldatasources.properties`	`application-jndidatasources.properties`
	blueriq.hibernate.[name].dialect		The dialect that hibernate should use.	`application-externaldatasources.properties`	`application-jndidatasources.properties`
	blueriq.hibernate.[name].use_nationalized_character_data	true	Enable nationalized character support on all string / clob based attributes ( string, char, clob, text etc ). Note that this property by defaults to true because 'hibernate.use_nationalized_character_data' is set in application.properties that is packaged in the default runtime WAR. When using H2 this property should be set to 'false' because H2 does not have specific nationalized data types. For more information about it's usage see: UTF8 support.	`application-externaldatasources.properties`	`application-jndidatasources.properties`

The development properties only apply when the profile development-tools is added to the Spring.active.profiles

Since Blueriq 13.13 the development tools have been updated. The new toolset, which has been available to activate for a long time, has now been made the default.

We still support the old toolset, switching between the two version is described on page Switching between development toolsets

Subject	Property	Explanation	Example
Development	logging.file.name=C:/Deployments/logs/runtime.log	The file in which to write the log		`application.properties`
	blueriq.development.sessionStore.dir=C:/Deployments/SessionStore/	Path to where the sessionstore file can be found.(if property is present, it will be enabled by default)		`application-development-tools.properties`
	blueriq.development.showToolbar=true	Development Toolbar on/off. default is true		`application-development-tools.properties`
	blueriq.development.usePasswordEncryption=true	When editing properties encrypt passwords before saving them.		`application-development-tools.properties`
	blueriq.development.settingsExternallyManaged=false	When properties can not be managed by the Blueriq 'development-tools' this can disable the settings menu and reload settings button.		`application-development-tools.properties`
	blueriq.external.themes.[name].baseUrl	URL where the external theme is can be reached. When using a custom made them which is not configured via the Runtime using an STG, but rather via a CDN or reverse proxy. An external theme can be configured so that the development dashboard can create URL's to the corresponding targets.	https://example.com/	`application-development-tools.properties`
	blueriq.external.themes.[name].template.flow	RFC-6570 URI template for creating a start flow request. By combining the baseUrl and template.flow properties a full URL is formed. The variables which can be used in the URI template are: flow - name of the flow to start project - name of the project to use version - project version to use languageCode - code of the language to use testPath - name of the test path to use The combined URL will be expanded in development dashboard.	/flow/{project}/{flow} /{version}/{languageCode} With test path: /flow/{project}/{flow} /{version}/{languageCode}{?testPath}	`application-development-tools.properties`
	blueriq.external.themes.[name].template.shortcut	RFC-6570 URI template for creating a start shortcut request. By combining the baseUrl and template.shortcut properties a full URL is formed. The variables which can be used in the URI template are: shortcut - name of the shortcut to start The combined URL will be expanded in development dashboard.	/shortcut/{shortcut}	`application-development-tools.properties`
	blueriq.external.themes.[name].template.session	RFC-6570 URI template for creating a continue session request. By combining the baseUrl and template.session properties a full URL is formed. The variables which can be used in the URI template are: sessionId - id of the session to continue The combined URL will be expanded in development dashboard.	/session/{sessionId}	`application-development-tools.properties`

Subject	Property	Explanation
Domain Schema	blueriq.domainschema.infinite-loop-detection-limit	Sets the limit for loops in case of domain schema in domain schema relations.	`application.properties`

Subject	Property	Explanation
Exports	blueriq.exports.enabled	Boolean to enable usage of exports. Default is false.	`application.properties`
	blueriq.exports.description	The group name of all the exports shown in the dev dashboard	`application.properties`
	blueriq.exports.prefix	The prefix in front of the export project when started.	`application.properties`
	blueriq.exports.folder	The folder in the configuration folder where the exports are.	`application.properties`
	blueriq.exports.files	Direct location of (an) export file(s). Comma seperated.	`application.properties`

Subject	Property	Explanation
Exports	blueriq.exports-r8.enabled	Boolean to enable usage of R8 type (Blueriq 8 - 11) exports. Default is false.	`application.properties`
	blueriq.exports-r8.description	The group name of all the R8 type (Blueriq 8 - 11) exports shown in the dev dashboard	`application.properties`
	blueriq.exports-r8.prefix	The prefix in front of the R8 type (Blueriq 8 - 11) export project when started.	`application.properties`
	blueriq.exports-r8.folder	The folder in the configuration folder where the exports R8 type (Blueriq 8 - 11) are.	`application.properties`
	blueriq.exports-r8.files	Direct location of (an) export R8 type (Blueriq 8 - 11) file(s). Comma seperated.	`application.properties`

With Blueriq 11.0 we introduced legacy properties that will be available for one major version and are immediately deprecated from the moment of introduction. The properties should therefore preferably not be used but may help during a transitioning period towards the new behavior.

Subject	Property	Explanation	Default	Introduced in	Removed in
XML in Web Services	blueriq.legacy.create-empty-elements-for-unknowns	Controls whether the legacy behaviour of generating empty elements for unknown relations should be enabled.	false	Blueriq 11.6	Changed to feature toggle in Blueriq 14.0: blueriq.webservices.create-empty-elements-for-unknowns	`application.properties`
Datamapping when cancel task	blueriq.legacy.execute-datamapping-on-cancel-task	Controls whether the legacy behavior of executing the datamapping when cancelling a task is enabled.	false	Blueriq 12.12.1	Blueriq 14.0	`application.properties`
Flow transaction rollback	blueriq.legacy.rollback-unknown-relation-to-empty-list	Controls whether previously unknown multi value relations should be rolled back to an empty list instead of unknown on transaction failure	false	Blueriq 12.13.19 and Blueriq 13.9	Blueriq 14.0	`application.properties`
Container type: AQ_InstanceList	blueriq.legacy.single-field-instance-list-pagination	Controls whether the legacy behavior of using a single Field for pagination in the AQ_InstanceList should be enabled. NB: the new behavior adds a Container which contains two text Assets and a Field for pagination.	false	Blueriq 13.13	Blueriq 15.0	`application.properties`
Process Engine	blueriq.legacy.use-legacy-case-unlocking	With the legacy behavior, checking if a case is locked and unlocking a case is done in Hibernate. This in contrast with acquiring a lock, which is done directly on the database. The new behavior is to check/unlock directly in the database as well and also throw an exception when a case is unlocked that was not locked.	false	Blueriq 13.13.17 Blueriq 14.10.1	Blueriq 16.0	`application.properties`

Subject	Property	Explanation		Example
Misc	blueriq.production.shortcuts-only	Only possible to start flows with shortcut (instead of 'dash start url')	`application.properties`
	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.	`application.properties`	# 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.	`application.properties`
	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.documents.base-folder	The base directory for documents resources. . For example `D:/yourlocation/documents/`. You only need to set this property when the /documents folder is not located in the `spring.config.additional-location`	`application.properties`
	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 `spring.config.additional-location` folder , behaviour is undefined if both are set.	`application.properties`	The property `blueriq.license` should contain the contents of the license file, not the path to the license file. The value should be something like: 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.	`application.properties`
	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.	`application.properties`
	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.	`application.properties`
	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.	`application.properties`

Model Preloading properties

Note: these properties were introduced in Blueriq 13.8

Subject Property Explanation Default value Property file Example

Model preloading

blueriq.modelpreload.enabled

If true, preloading of configured application models during Runtime startup is enabled

false

application.properties

blueriq.modelpreload.before-requests

If false, preload the application models after the Runtime is ready to accept HTTP requests. Otherwise the models will be preloaded before HTTP requests are accepted.

true

application.properties

blueriq.modelpreload.models

A map of application models (name and versions) to preload. Only application models that are in this list will preloaded if preloading is enabled.

application.properties

blueriq.modelpreload.models.MyApp1=0.0-Trunk,0.0-FeatureX,0.0-FeatureY

blueriq.modelpreload.models.MyApp2=0.0-Trunk

Subject Property Default Explanation Property file

Multi-tenacy

blueriq.multi-tenancy.enabled

false

Toggle to enable multi-tenancy.

application.properties

blueriq.multi-tenancy.allowed-tenants

List of comma separated tenant names. Tenant names can contain letters, digits and '-' (dashes).

For example:

blueriq.multi-tenancy.allowed-tenants=google,apple

application.properties

blueriq.multi-tenancy.http-header

The name of the HTTP header which the Runtime can retrieve the tenant name

application.properties

Subject	Property	Explanation
MVC UI - deprecated	blueriq.mvc.development-mode	Turning mvc development mode on or off.	`application.properties`
	blueriq.mvc.themes.[theme].template-group-file	Path to where the stg file can be found.	`application.properties`
	blueriq.mvc.themes.[theme].template-name	Name of the mvcui template.	`application.properties`
	blueriq.mvc.active-themes	The themes that are active in the Runtime. The theme names listed here (as a comma separated list) must match the theme names that are used with the properties above. Not all defined themes need to be active. Only the active ones will be shown in the development dashboard. This is useful for overriding the default styling that is packaged with Blueriq.	`application.properties`
	spring.mvc.dispatch-options-request	This is a spring mvc property that enables the dispatcher to listen to OPTIONS request methods.	`application.properties`

Example

blueriq.mvc.themes.bootstrap3.template-group-file=UI/mvc/v2/bootstrap3.stg
blueriq.mvc.themes.bootstrap3.template-name=main
blueriq.mvc.active-themes=bootstrap3

Subject	JAVA Property	Explanation
OpenID Connect	blueriq.security.openid-connect.use-discovery	Boolean property which enables Blueriq to read identity provider specific properties from an specific exposed location if the value is true, or to read them from application.properties if the value is false. Default: false.	`application.properties`
	blueriq.security.openid-connect.keys-endpoint	Location from where Blueriq loads the public keys. In order to work, blueriq.security.openid-connect.use-discovery must be true. Example for Keycloak: http://<server>:<port>/auth/realms/<realm name>/protocol/openid-connect/certs Note: this property was introduced in 11.4 and removed in 11.5 with the introduction of the discovery feature.	`application.properties`
	blueriq.security.openid-connect.public-keys.<key id>	Defines the <key id, public key> mappings that are loaded by Blueriq if blueriq.security.openid-connect.use-discovery is false.	`application.properties`
	blueriq.security.openid-connect.client-id	The client-id of the Runtime, as defined at the identity provider.	`application.properties`
	blueriq.security.openid-connect.client-secret	The client secret of the Runtime, as defined at the identity provider. This value is used, for example, to complete the OpenID Connect Authorization Code Flow, when exchanging the authorization code for ID and access tokens.	`application.properties`
	blueriq.security.openid-connect.scopes	The OpenID Connect scopes used when starting the Authorization Code flow. The scopes must include the value "openid" in order for the identity provider to recognize that the OpenID Connect Authorization Code flow must be initiated. If "openid" is not specified as a scope, the identity provider may instead initiate the OAuth2 Authorization Code flow (depends on the identity provider in use). Multiple scopes can be specified separated with coma.	`application.properties`
	blueriq.security.openid-connect.token-endpoint	the URL of the endpoint where access codes can be exchanged for ID and access tokens. Example for Keycloak: http://<host>:<port>/auth/realms/<realm name>/protocol/openid-connect/token	`application.properties`
	blueriq.security.openid-connect.token-endpoint-parameters.<name>=<value>	Additional custom parameters to be sent to the token endpoint. For example; blueriq.security.openid-connect.token-endpoint-parameters.audience=https://example.eu.auth0.com/api/v2/	`application.properties`
	blueriq.security.openid-connect.authorization-endpoint	the URL where the OpenID Connect Authorization Code flow can be started. Example for Keycloak: http://<host>:<port>/auth/realms/<realm name>/protocol/openid-connect/auth	`application.properties`
	blueriq.security.openid-connect.authorization-endpoint-parameters.<name>=<value>	Additional custom parameters to be sent to the authorization endpoint. For example; blueriq.security.openid-connect.authorization-endpoint-parameters.audience=https://example.eu.auth0.com/api/v2/	`application.properties`
	blueriq.security.openid-connect.token-issuer	The expected issuer in the "iss" claim of JWT tokens. A received JWT which does not have this exact, case-sensitive value in its "iss" claim will be rejected as invalid.	`application.properties`
	blueriq.security.openid-connect.roles-path	The comma-separated path to the roles claim in the JWT body. For example if the JWT body contains the following claims: { ... other claims ... "realm_access": [ "roles": ["role1", "role2"] ] ... other claims ... } then this property should be set to "realm_access,roles" in order to indicate that the roles claim nested within the realm_access claim represents the user's roles.	`application.properties`
	blueriq.security.openid-connect.teams-path	The comma-separated path to the teams claim in the JWT body. See roles-path above for an example.	`application.properties`
	blueriq.security.openid-connect.role-mapping.<role-claim>	Maps a role claim to zero, one or multiple Blueriq roles. If a role claim does not have a mapping, it is considered to have an implicit identity mapping. Example: blueriq.security.openid-connect.role-mapping.employee=authenticated_user,vu_employee (all users which have the employee role at the identity provider will have the authenticated_user and vu_employee roles in Blueriq)	`application.properties`
	blueriq.security.openid-connect.team-mapping.<team-claim>	Maps a team claim to zero, one or multiple Blueriq teams. If a team claim does not have a mapping, it is considered to have an implicit identity mapping. Example: blueriq.security.openid-connect.team-mapping.amsterdam=europe,netherlands (all users which have the amsterdam team at the identity provider will have the europe and netherlands teams in Blueriq)	`application.properties`
	blueriq.security.openid-connect.check-audience	Boolean indicating whether the audience claim should be checked. If true, the audience claim must contain the Runtime's client-id. All JWTs which do not contain the Runtime's client-id in the audience claim are rejected as invalid. When false, the audience claim is not checked. Default: false.	`application.properties`
	blueriq.security.openid-connect.sso-logout	Boolean indicating whether when logging out of Blueriq the user should be logged out of the Single-Sign-On session as well. Default: false	`application.properties`
	blueriq.security.openid-connect.end-session-endpoint	When sso-logout is true, the Runtime redirects to this URL at the identity provider in order to log out of the Single-Sign-On session.	`application.properties`
	blueriq.security.openid-connect.username-path	The comma-separated path to the username claim in the JWT body. For example if the JWT body contains the following claims: { ... other claims ... "realm_access": [ "nickname": "username" ] ... other claims ... } then this property should be set to "realm_access,nickname" in order to indicate that the `nickname` claim nested within the `realm_access` claim represents the username. Auth0 will include the claim `nickname` in the JWT body when the scope `profile` is added to the list of scopes. We suggest to set this property to "nickname" when using Auth0. If no value is specified, the default value is used: `preferred_username`.	`application.properties`
	blueriq.security.openid-connect.user-info-endpoint	the URL of the OpenID Connect UserInfo endpoint. This endpoint provides information about the user associated with an access token. It is used when the access token is not a JWT.	`application.properties`
	blueriq.security.openid-connect.user-info-endpoint-parameters.<name>=<value>	Additional custom parameters to be sent to the user info endpoint. For example; blueriq.security.openid-connect.user-info-endpoint-parameters.audience=https://example.eu.auth0.com/api/v2/	`application.properties`

The property retain-required-tasks has been added

Subject	JAVA Property	Explanation
Processes and DCM	blueriq.timer.interval	Timer interval of when to check timed tasks - (values must now be MINUTE, HOUR or NEVER, caps are required)	`application.properties`
	blueriq.scheduler-quartz.advanced-scheduler	Property to enable the advanced scheduler Default: false	`application.properties`
	blueriq.migrate.displaynames.endpoint.enabled	Activates the migration endpoint for processing and updating the cases and tasks display names	`application.properties`
	blueriq.processengine.cancel-started-tasks	Will cancel all started tasks when the runtime starts. This property does not work as intended for production environments where the runtime is installed on multiple nodes. Starting a new (or restarting a running node) might cancel tasks that are in use. For that scenario we recommend to use the Reopening Tasks endpoint exposed by the CancelAllStartedTasks from the Scheduler Maintenance REST API or the Backend REST API V1 Default: false	`application.properties`
	blueriq.processengine.retain-required-tasks	If true, ad-hoc tasks for which the precondition becomes false will not be automatically canceled (pre R11 behaviour). Defaults to `false`.	`application.properties`
	blueriq.processengine.worklist.limit	Limit of amount of items shown in the worklist Default: 1000	`application.properties`
	blueriq.processengine.caselist.limit	Limit of amount of items shown in the caselist Default: 1000
	blueriq.processengine.default-app-id-ignore-mode	To influence the behavior of models that normally make use of the application Id for whole server (Control applicationId behavior) Default: none	`application.properties`
	blueriq.processengine.app-id-ignore-modes.[app-id]	To influence the behavior of models that normally make use of the application Id, but per project.	`application.properties`
	blueriq.processengine.default-ignore-unknown-attributes	Indicates whether attributes stored in the process database which are no longer in the model should be ignored. By default, these attributes are not ignored and an error is raised when such an attribute is found in the database. To ignore the attributes, set this property to true.	`application.properties`
	blueriq.processengine.ignore-unknown-attributes.[app-name]	Same as blueriq.processengine.default-ignore-unknown-attributes, but allows enabling this setting on a per-application basis. The application-specific setting takes precedence over the global setting.	`application.properties`
	blueriq.processengine.default-ignore-unknown-entities	Indicates whether entity instances stored in the process database which are no longer in the model should be ignored. By default, these entity instances are not ignored and an error is raised when such an entity instance is found in the database. To ignore the entity instances, set this property to true.	`application.properties`
	blueriq.processengine.ignore-unknown-entities.[app-name]	Same as blueriq.processengine.default-ignore-unknown-attributes, but allows enabling this setting on a per-application basis. The application-specific setting takes precedence over the global setting.	`application.properties`
	blueriq.processlist.default-app-id-ignore-mode		`application.properties`
	blueriq.processlist.app-id-ignore-modes.[app-id]		`application.properties`
	blueriq.process-sql-store.oracle.case-insensitive-search-enabled	This property enables case insensitive searching for oracle. For more information see: How to enable case insensitive search on case data for Oracle	`application.properties`

Subject	Property	Explanation
Publisherclient	blueriq.hibernate.publisher-client.main.hbm2ddl.auto=validate	Specifies the hibernate property for publisherclient connection.	`application-publisher-client.properties`
	blueriq.hibernate.publisher-client.dialect=org.hibernate.dialect.Oracle12cDialect	Example: blueriq.hibernate.publisherclient.dialect=org.hibernate.dialect.Oracle12cDialect	`application-publisher-client.properties`
	blueriq.datasource.publisher-client.database.url=jdbc:oracle:{host}:{port}:{servicename}	The url of the publisher database.	`application-publisher-client.properties`
	blueriq.datasource.publisher-client.database.driverClassName=oracle.jdbc.driver.OracleDriver	The driverclassname of the publisher database.	`application-publisher-client.properties`
	blueriq.datasource.publisher-client.database.username={Username}	The username to log in the database.	`application-publisher-client.properties`
	blueriq.datasource.publisher-client.database.password={password}	The password to log in the database.	`application-publisher-client.properties`
	blueriq.publisher-client.environmentName=Test		`application-publisher-client.properties`

Subject	Property	Explanation
Runtime API	blueriq.oauth2.client-id	The username (id) so a oAuth user can login to the REST API.	`application.properties`
	blueriq.oauth2.secret	The password so a oAuth user can login to the REST API.	`application.properties`
	blueriq.runtime.name	name of the runtime in the REST API	`application.properties`

Subject	Property	Explanation
Security LDAP	blueriq.security.auth-providers.ldap01.type	What type of provider is used, in this case it always is 'ldap'	`application.properties`
	blueriq.security.auth-providers.ldap01.connectionUrl	The connection url to the LDAP server	`application.properties`
	blueriq.security.auth-providers.ldap01.userDn	The userDn to connect with the ldap; format should look something like 'cn=LDAP reader,ou=something,dc=company,dc=nl'	`application.properties`
	blueriq.security.auth-providers.ldap01.password	Password to connect to the LDAP	`application.properties`
	blueriq.security.auth-providers.ldap01.useTls	boolean to either use TLS or not for the LDAP connection; this setting is not required	`application.properties`
	blueriq.security.auth-providers.ldap01.tls.trustStoreUrl	Only required if useTls is true; the location to the truststore file	`application.properties`
	blueriq.security.auth-providers.ldap01.tls.trustStorePassword	Only required if useTls is true; The password used to login to the keystore	`application.properties`
	blueriq.security.auth-providers.ldap01.tls.trustStoreType	Only required if useTls is true; what type of keystore is used, like 'jks' or 'pkcs12'	`application.properties`
	blueriq.security.auth-providers.ldap01.referralStrategy	Can be 'ignore' or 'follow'	`application.properties`
	blueriq.security.auth-providers.ldap01.searchSubtree	Used for searching in LDAP; boolean value if set to true, not only the current directory will be search, but also underlaying directories.	`application.properties`
	blueriq.security.auth-providers.ldap01.userSearchBaseDn	Used for searching in LDAP; Should look something like 'OU=Gebruikers,DC=company,DC=nl'; points to the directory to where the user search should happen.	`application.properties`
	blueriq.security.auth-providers.ldap01.userSearchAttribute	Used for searching in LDAP; What attribute to use to iddentify as a user, common use is : 'sAMAccountName'	`application.properties`
	blueriq.security.auth-providers.ldap01.groupSearchBaseDn	Used for searching in LDAP; Should look something like 'OU=Groepen,DC=company,DC=nl'; points to the directory to where the group search should happen. Important for the roles for the user	`application.properties`
	blueriq.security.auth-providers.ldap01.groupSearchFilterAttribute	Used for searching groups in ldap; What attribute to use to to filter groups on; This property is not required	`application.properties`
	blueriq.security.auth-providers.ldap01.groupSearchFilterPattern	Used for searching groups in ldap; What pattern to use to to filter groups on;This property is not required; Should look something like this: 'BQ_, EVE_,PRO - ,PRO -' Results in: ((<attribute>=BQ_)(<attribute>=EVE_)(<attribute>=PRO -*))	`application.properties`
	blueriq.security.auth-providers.ldap01.role-mapping	Used for mapping LDAP groups to Blueriq roles, in the form ..role-mapping.<ldap group 1>=<blueriq role 1>[,<blueriq role 2>,...,<blueriq role n>] ..role-mapping.<ldap group n>=<blueriq role 1>[,<blueriq role 2>,...,<blueriq role n>]	`application.properties`

Subject	JAVA Property	Explanation
Security	blueriq.security.click-jacking-protection.enabled	Turning clickjack protection on/off. For more information go to Security: Clickjacking protection	`application.properties`
	blueriq.security.click-jacking-protection.content-security-policy.default-src	Set the location where content can be loaded from, if no more specific value (for example font for where fonts can be loaded from) is given there is a fallback to this value. For more information see Security: Clickjacking protection.	`application.properties`
	blueriq.security.click-jacking-protection.content-security-policy.script-src	Set the location where scripts can be loaded from. For more information see Security: Clickjacking protection.	`application.properties`
	blueriq.security.click-jacking-protection.content-security-policy.style-src	Set the location where stylesheets can be loaded from. For more information see Security: Clickjacking protection.	`application.properties`
	blueriq.security.click-jacking-protection.content-security-policy.font-src	Set the location where fonts can be loaded from. For more information see Security: Clickjacking protection.	`application.properties`
	blueriq.security.csrf-protection.enabled	Turning Cross Site Request Forgery protection on/off. For more information go to Security: Cross-site scripting protection	`application.properties`
	blueriq.security.strict-transport-protection.enabled	Turning strict transport protection protection on/off. For more information go to Security: HTTP Strict Transport Security	`application.properties`
	blueriq.security.x-content-type-protection.enabled	Turning x-content type protection protection on/off. For more information go to Security: Content sniffing protection	`application.properties`
	blueriq.security.xss-protection.enabled	Turning cross site scripting protection protection on/off. For more information go to Security: Cross-site scripting protection	`application.properties`
	blueriq.security.xss-protection.header.enabled	Turns the X-XSS-Protection HTTP header on/off.	`application.properties`
	blueriq.security.xss-protection.request-validation.enabled	Turns cross site scripting validator filter on request body on/off.	`application.properties`
	blueriq.security.xss-protection.blacklist.enabled	Turns the XSS blacklist on/off.	`application.properties`
	blueriq.security.xss-protection.whitelist.enabled	Turns the XSS whitelist on/off.	`application.properties`
	blueriq.security.xss-protection.whitelist.allowed-protocols=http,https	Sets the whitelisted protocols in URI attributes.	`application.properties`
	blueriq.security.xss-protection.whitelist.allowed-tags=b,img	Sets the whitelisted HTML tags.	`application.properties`
	blueriq.security.xss-protection.whitelist.allowed-global-attributes=class,title	Sets the whitelisted attributes allowed on any whitelisted HTML tag.	`application.properties`
	blueriq.security.xss-protection.whitelist.allowed-attributes.<tag>=<attr1>,<attr2>	Sets the whitelist attributes allowed on a specific whitelisted HTML tag	`application.properties`
	blueriq.security.xss-protection.whitelist.uri-attributes.<tag>=<attr1>,<attr2>	Marks which attributes are URI attributes and are subject to the allowed protocols rule. In Java, URI attributes can be defined per tag. In .NET, URI attributes can be defined only globally.	`application.properties`
	blueriq.security.xss-protection.whitelist.max-loop-count=5	Defines a limit on the number of sanitization iterations.
	blueriq.security.http.restricted-methods=head,options	Specifies the methods that should not be allowed while doing HTTP calls. For more information go to Security: Block HTTP Methods	`application.properties`
	blueriq.security.http.interactions.enabled	This property if true enables the default secured access to the runtime interactions.	`application.properties`
	blueriq.security.auth-providers.ldap01.url
	blueriq.security.login-type	Defines the login type used in Blueriq. Possible values: form-login, openid-connect, kerberos. This property is not mandatory and default value is form-login. If openid-connect is chosen, openid-connect properties have to be defined as well.	`application.properties`
	blueriq.security.redirect-url-whitelist	Defines a whitelist of URLs where the user can be redirected to. If the `redirect_uri` (for OpenIdConnect login/logout) or the `error-redirect` (for render document/page and file download) are not in this list, the Runtime will return 400. If the list is empty, any URL is accepted.	`application.properties`
	blueriq.security.keystore.location	The path to the keystore file to be used as repository for security certificates	`application.properties`
	blueriq.security.keystore.password	The password of the keystore	`application.properties`
	blueriq.security.truststore.location	The path to the trust store containing the public keys/certificates of external hosts that should be trusted	`application.properties`
	blueriq.security.truststore.password	The password for the truststore file.	`application.properties`
	blueriq.security.bcrypt-strength	Defines the BCrypt strength for password hashing. BCrypt is the default encoder in Blueriq. Default value : 10 Applicable values : number between 4-30 Performance impact The higher the number the higher the hashing complexity but also the work to calculate the hash. Each increment is twice as much work. Introduced in version 12.13	`application.properties`
	blueriq.security.session-fixation-protection.enabled	Turns session fixation on/off. For more information, see Security: Session Fixation protection Default value: false Introduced in 13.13.18	`application.properties`

Subject	Property	Explanation	Property file
Shortcuts	blueriq.shortcut.[name].flow	The flow of the project that is started	`application.properties`
	blueriq.shortcut.[name].languageCode	The languagecode of the project that is started	`application.properties`
	blueriq.shortcut.[name].project	The name project that is started	`application.properties`
	blueriq.shortcut.[name].theme	The theme of the project that is started	`application.properties`
	blueriq.shortcut.[name].ui	The ui of the project that is started	`application.properties`
	blueriq.shortcut.[name].version	The version of the project that is started	`application.properties`
	blueriq.shortcut.[name].channel	The device channel of the project that is started
	blueriq.shortcut.[name].privateAccess	This property indicates if the project reference that is specified in the shortcut is private or not. Read also Security: Shortcuts and AQ_GetRequestParameters	`application.properties`

Subject	Property	Explanation	Property file
Studio	blueriq.studio.description	Description of the studio	`application-development-tools.properties`
	blueriq.studio.prefix	The prefix in front of the studio project when started.	`application-development-tools.properties`
	blueriq.studio.domain	Network domain where the studio is in.	`application-development-tools.properties`
	blueriq.studio.url	The url of the studio in the network	`application-development-tools.properties`
	blueriq.studio.authentication	Method of authentication (NTLM/custom/kerberos/etc) that the studio uses Authentication can be KERBEROS, KERBEROS_CUSTOM, NTLM, NTLM_CUSTOM or BASIC	`application-development-tools.properties`
	blueriq.studio.username	Username for the studio management service	`application-development-tools.properties`
	blueriq.studio.password	Password for the studio management service	`application-development-tools.properties`

Subject	Property	Default	Explanation	Property file
Webresources	blueriq.web-resources.source-location		The location (URL) of additional or overridden web resources. For example `file:///d:/resources/webresources/`. If not set only web resources from the classpath will be available	`application.properties`
	blueriq.web-resources.cache-key-seed		The seed used to generate a cacheKey for static resources. Set this property if you want to be responsible for invalidating the cache. This probably means you must change the cacheKeySeed every time you change one or more of your custom web resources. Please note that when this property is not set, the cacheKey is changed every time the Blueriq Runtime is restarted	`application.properties`
	blueriq.web-resources.cache-period-seconds	31536000	The cache period for all static web resources. When null, default behavior is to rely only on 'Last-Modified' header. When 0, caching is disabled. When > 0 is number of seconds to cache a resource client-side (browser). (31536000 seconds = 365 days)	`application.properties`

Subject	Property	Default	Explanation	Property file	Additional information
External Flow Component	blueriq.external-flow.store-type	memory	The data store type, having two possible values: memory and redis. memory is the default one.	`application-external-flow.properties`
	blueriq.external-flow.redis-store.database	0	The Database index used by the connection factory.	`application-external-flow.properties`
	blueriq.external-flow.redis-store.host	localhost	The REQUIRED DNS name or IP address of the Redis server.	`application-external-flow.properties`	No default before 13.4
	blueriq.external-flow.redis-store.port	6379	The REQUIRED port on which to connect to Redis.	`application-external-flow.properties`	Default before 13.4: -1
	blueriq.external-flow.redis-store.ssl	false	Whether to enable SSL support	`application-external-flow.properties`	Since 13.4
	blueriq.external-flow.redis-store.password		The password used to connect to Redis, can be left empty if no password is required.	`application-external-flow.properties`
	blueriq.external-flow.redis-store.read-timeout-millis	10000	Timeout (ms) for read operations	`application-external-flow.properties`	Since 12.8 Removed in 13.4
	blueriq.external-flow.redis-store.connect-timeout-millis	10000	Timeout (ms) for connect operations	`application-external-flow.properties`	Since 12.8 Removed in 13.4
	blueriq.external-flow.redis-store.timeout	2000	Timeoud (ms) for connect and read operations	`application-external-flow.properties`	Since 13.4
	blueriq.external-flow.redis-store.client-name		Client name to be set on connections. Can be left empty.	`application-external-flow.properties`
Redis pool configuration	blueriq.external-flow.redis-store.pool.maxIdle	8	Maximum number of "idle" connections in the pool. Use a negative value to indicate an unlimited number of idle connections.	`application-external-flow.properties`	Removed in 13.4
	blueriq.external-flow.redis-store.pool.minIdle	0	Target for the minimum number of idle connections to maintain in the pool. This setting only has an effect if it is positive.	`application-external-flow.properties`	Removed in 13.4
	blueriq.external-flow.redis-store.pool.maxActive	8	Maximum number of connections that can be allocated by the pool at a given time. Use a negative value for no limit.	`application-external-flow.properties`	Removed in 13.4
	blueriq.external-flow.redis-store.pool.maxWait	-1	Maximum amount of time a connection allocation should block before throwing an exception when the pool is exhausted. Use a negative value to block indefinitely.	`application-external-flow.properties`	Removed in 13.4
	blueriq.external-flow.redis-store.jedis.pool.maxIdle	8	Maximum number of "idle" connections in the pool. Use a negative value to indicate an unlimited number of idle connections.	`application-external-flow.properties`	Since 13.4
	blueriq.external-flow.redis-store.jedis.pool.minIdle	0	Target for the minimum number of idle connections to maintain in the pool. This setting only has an effect if it is positive.	`application-external-flow.properties`	Since 13.4
	blueriq.external-flow.redis-store.jedis.pool.maxActive	8	Maximum number of connections that can be allocated by the pool at a given time. Use a negative value for no limit.	`application-external-flow.properties`	Since 13.4
	blueriq.external-flow.redis-store.jedis.pool.maxWait	-1	Maximum amount of time a connection allocation should block before throwing an exception when the pool is exhausted. Use a negative value to block indefinitely.	`application-external-flow.properties`	Since 13.4
	blueriq.external-flow.redis-store.jedis.pool.timeBetweenEvictionRuns		Time between runs of the idle object evictor thread. When positive, the idle object evictor thread starts, otherwise no idle object eviction is performed. Can be left empty.	`application-external-flow.properties`	Since 13.4

This component is part of an ongoing effort to separate the Process Engine from the Runtime. As this component is still in active development, it's not ready for use in production scenarios. Behavior and interfaces are subject to change.

Subject	Property	Explanation	Property file	Additional information
Case Engine Client Component - under development	blueriq.dcm.rabbitmq.host	Settings for the RabbitMQ instance used to communicate with the Case Engine.	`application.properties`
	blueriq.dcm.rabbitmq.port
	blueriq.dcm.rabbitmq.username
	blueriq.dcm.rabbitmq.password
	blueriq.dcm.rabbitmq.exchangeName			Exchange to which events to the Case Engine should be published
	blueriq.dcm.rabbitmq.queueNames			Queue from which events from the Case Engine should be consumed
	blueriq.dcm.rabbitmq.virtualHost
	blueriq.dcm.case-engine.url	URL and credentials for the Case Engine.	`application.properties`
	blueriq.dcm.case-engine.username
	blueriq.dcm.case-engine.password

Common used properties

server.servlet.contextPath=/runtime

# do not use spring default multipart configuration
spring.http.multipart.enabled=false
spring.cloud.config.overrideSystemProperties=false

hibernate.use_nationalized_character_data=true

Java Third Party properties

For part of the features we rely on third party libraries. These library's have their own properties like: logging.level.com.aquima=DEBUG. you can find an overview or the Spring properties here: spring-common-application-properties.

Space shortcuts

Page tree

All properties

Properties

Messages

Model Preloading properties

Example

Common used properties

Java Third Party properties

Space shortcuts

Page tree

Reference Guide: Properties

All properties

Properties

Messages

Model Preloading properties

Example

Common used properties

Java Third Party properties