You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.
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) |
|
blueriq.scheduler-quartz.advanced-scheduler | Property to enable the advanced scheduler Default: false |
| |
blueriq.migrate.displaynames.endpoint.enabled | Activates the migration endpoint for processing and updating the cases and tasks display names |
| |
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 |
| |
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 . |
| |
blueriq.processengine.worklist.limit | Limit of amount of items shown in the worklist Default: 1000 |
| |
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 |
| |
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. |
| |
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. |
| |
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. |
| |
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. |
| |
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. |
| |
blueriq.processlist.default-app-id-ignore-mode |
| ||
blueriq.processlist.app-id-ignore-modes.[app-id] |
| ||
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 |
|