Atoti Limits
Overview
These are the properties used to configure your Atoti Limits Server. Note that we provide all
properties that can be used, but you are only required to set limits.autoconfiguration.service-principal.
This is because we expect you to use your own security configuration and thus your own users.
note
We inherit many properties from Spring related to the datasources. We define some, but not all of them. We have listed all that will be registered by Spring on startup. For more information on the different datasources, see Atoti Limits datasources. For more information on specific properties, see the Spring docs.
Module properties
| Key | Description | Default value |
|---|---|---|
| activeviam.apps.workflow-service.settings.allowed-file-upload-extensions | The file types allowed to be uploaded as attachments in the workflow. | [pdf jpeg png csv xls xlsx doc docx txt ppt pptx eml msg md] |
| activeviam.apps.workflow-service.settings.file-storage-path | The path where the workflow attachment files are stored. Please ensure users have access to this folder. | ./limits/workflow/attachments |
| application.datasource.driver-class-name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.embedded-database-connection | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.generate-unique-name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.allow-pool-suspension | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.auto-commit | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.catalog | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.connection-init-sql | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.connection-test-query | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.connection-timeout | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.credentials | ||
| application.datasource.hikari.data-source-class-name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.data-source-j-n-d-i | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.data-source-properties | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.driver-class-name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.exception-override | ||
| application.datasource.hikari.exception-override-class-name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.health-check-properties | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.idle-timeout | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.initialization-fail-timeout | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.isolate-internal-queries | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.jdbc-url | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.keepalive-time | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.leak-detection-threshold | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.login-timeout | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.max-lifetime | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.maximum-pool-size | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.metrics-tracker-factory | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.minimum-idle | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.password | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.pool-name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.read-only | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.register-mbeans | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.scheduled-executor | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.schema | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.transaction-isolation | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.username | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.hikari.validation-timeout | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.jndi-name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.password | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.type | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.url | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.username | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.xa.data-source-class-name | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| application.datasource.xa.properties | Spring inherited property used when configuring the Atoti Limits workflow datasource. | |
| limits.activiti.mail.breach-url | The URL to link when configuring the mail server for breach notifications. | |
| limits.activiti.mail.from | The email address to use when configuring the mail server for breach notifications. | |
| limits.activiti.mail.host | The host to use when configuring the mail server for breach notifications. | |
| limits.activiti.mail.password | The password to use when configuring the mail server for breach notifications. | |
| limits.activiti.mail.port | The port to use when configuring the mail server for breach notifications. | 0 |
| limits.activiti.mail.ssl | True if using SSL when configuring the mail server for breach notifications. | false |
| limits.activiti.mail.tls | True if using TLS when configuring the mail server for breach notifications. | false |
| limits.activiti.mail.username | The username to use when configuring the mail server for breach notifications. | |
| limits.alert-task.sample-rate-cron | Cron expression for the Intraday Alert task’s cron job. | |
| limits.application.datasource.driver-class-name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.embedded-database-connection | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.generate-unique-name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.allow-pool-suspension | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.auto-commit | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.catalog | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.connection-init-sql | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.connection-test-query | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.connection-timeout | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.credentials | ||
| limits.application.datasource.hikari.data-source-class-name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.data-source-j-n-d-i | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.data-source-properties | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.driver-class-name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.exception-override | ||
| limits.application.datasource.hikari.exception-override-class-name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.health-check-properties | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.idle-timeout | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.initialization-fail-timeout | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.isolate-internal-queries | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.jdbc-url | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.keepalive-time | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.leak-detection-threshold | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.login-timeout | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.max-lifetime | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.maximum-pool-size | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.metrics-tracker-factory | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.minimum-idle | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.password | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.pool-name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.read-only | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.register-mbeans | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.scheduled-executor | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.schema | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.transaction-isolation | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.username | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.hikari.validation-timeout | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.jndi-name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.password | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.type | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.url | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.username | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.xa.data-source-class-name | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.application.datasource.xa.properties | Spring inherited property used when configuring the Atoti Limits application datasource. | |
| limits.auto-migration.legacy-workflow-history-limit-value-json-converter-enabled | True if the configuration to migrate Activiti histories created prior to Atoti Limits version 4.2.0 should be enabled. The configuration is in LegacyActivitiWorkflowHistoryLimitValueMigrator. False if the configuration should be disabled. We recommend leaving this property enabled if you have workflow histories created prior to version 4.2.0 of Atoti Limits. You can disable this property if you don’t have workflow histories AND you are only using new workflows, not legacy workflows. | true |
| limits.autoconfiguration.service-principal | The name of the user authenticated to perform machine-to-machine requests from Atoti Limits to the connected Atoti Servers, if using JWT Authentication. | |
| limits.cube.format.double-format | Format value for double measures. | DOUBLE[#,##0.00] |
| limits.cube.format.integer-format | Format value for integer measures. | INT[#,###] |
| limits.cube.format.kpi-goal | Format value for KPI Goal values | #,##0.# |
| limits.cube.kpi-filters-enabled | True if cube filters are enabled for Limits KPIs, false otherwise. | true |
| limits.cube.scope-hierarchies-enabled | True if the scope hierarchies are enabled in the Limits cube, false otherwise. This may be disabled to improve performance for clients with large numbers of limits and in particular a high cardinality of scopes. | false |
| limits.data-access-control.servers | Stores the permissions available to each role, per server | |
| limits.data.jpa.repository.packages-to-scan | List of packages to scan for Entity classes to be managed by the JPA repositories. | |
| limits.data.mode | The mode used to load data into Atoti Limits. | csv |
| limits.discovery-manager.polling-delay | How long a Discovery’s refresh is valid for. | 30000 |
| limits.incident.evaluation.error.include-stacktrace | If true, the stack trace will be available in the evaluation response to the UI. | false |
| limits.incident.evaluation.include-passes | If true, evaluations resulting in a pass will be persisted to the datastore. | false |
| limits.incident.evaluation.parallel-tasks | Thread pool size for the evaluation task executors. | 10 |
| limits.incident.output-data-dir | The directory where the alert data is written to. | |
| limits.initial-load.file-path-matchers.as-of-date | The PathMatcher built from a regex or glob pattern to match the as-of-date files. | glob:**/*as_of_date*.csv |
| limits.initial-load.file-path-matchers.incidents | The PathMatcher built from a regex or glob pattern to match the incidents files. | glob:**/incident/**/*incident*.csv |
| limits.initial-load.file-path-matchers.limit-structures | The PathMatcher built from a regex or glob pattern to match the limit structures files. | glob:**/*limit_structures*.csv |
| limits.initial-load.file-path-matchers.limits | The PathMatcher built from a regex or glob pattern to match the limits files. | glob:**/*limits_approve*.csv |
| limits.initial-load.root-dir | The root directory for Limits data. | ./src/main/resources/data |
| limits.notification.evaluation-completed-notification-user-role | The role required to receive the evaluation completed notification. | |
| limits.notification.server-started-notification-user-role | The role required to receive the server started notification. | ROLE_ADMIN |
| limits.realtime.emitter-timeout | The timeout on each Event Source that a client opens to receive real-time updates on Limits statuses. | 8h |
| limits.scope.auto-fill-unambiguous-level-paths | If true, allows Limits to automatically fill in missing parent levels with Wildcards | true |
| limits.scope.force-unambiguous-level-paths | If true, this forces that a level be Unambiguous at load time | false |
| limits.scope.using-explicit-scope-matching | If true, limits will only be shown and applied to the exact location their Scope is defined on | true |
| limits.structure.templates | Stores the LimitStructureTemplates by templateName to ensure each one is unique | |
| limits.task-scheduler.thread-pool-size | The quantity of threads allotted to the TaskScheduler | 4 |
| limits.workflow.enable-bulk-activiti-transactions | True when users want to execute activiti transactions in bulk, false when they should be executed sequentially | true |
| limits.workflow.exception-workflows | A Map of the exception workflow name to the workflow configuration properties. These properties only apply to legacy workflows and will be removed in a future release. | |
| limits.workflow.incident-business-functions | Maps the business functions available for incident workflows. | [Incidents] |
| limits.workflow.limit-business-functions | Maps the business functions available for limits workflows. | [Limit Changes] |
| limits.workflow.limit-workflow-action-statuses.evaluable | The list of limit statuses that are eligible for evaluation. | [APPROVED] |
| limits.workflow.limit-workflow-action-statuses.inactive | Statuses that represent a limit that is longer active and should not be considered during the validation of other limits | [EXPIRED DELETED REJECTED] |
| limits.workflow.limit-workflow-action-statuses.kpi-visible | The list of limit statuses that are eligible to be shown in KPIs in the business cube. The EXPIREDstatus is included by default to allow for historical analysis of limit KPIs. ThePENDING, EDIT, and PENDING_DELETION` statuses are included because they represent limits that were previously approved so the approved values are still relevant for KPI purposes. |
[APPROVED EXPIRED PENDING EDIT PENDING_DELETION] |
| limits.workflow.limit-workflow-action-statuses.pending | The list of limit statuses that are considered pending. These statuses will be excluded when the business cube refreshes its cache of limits. | [INITIALIZED PENDING EDIT PENDING_DELETION] |
| limits.workflow.limit-workflows | A Map of the limit workflow name to the workflow configuration properties. These properties only apply to legacy workflows and will be removed in a future release. | |
| limits.workflow.roles | List of roles for a given workflow. | |
| limits.workflow.structure-deletion-workflows | List of workflows where structure deletion is enabled. | |
| limits.workflow.workflow-rules.can-approver-be-same-as-creator | If true, the creator of a limit may also approve it. | false |
| limits.workflow.workflow-status-fetched-with-limit | When set to true, retrieving limit structures also updates the limit status with the current workflow status. | true |