tm/ticket-service

The duration in minutes for incident ticket after it is created/accepted to calculate its due date. The due date of an incident ticket will be Created_Time/First_Accepted_Time + TS_INCIDENTDEADLINEINMINUTES.

No

10

The default time-interval in milliseconds for each schedule job, like the escalation scheduling job.

No

600000

The initial delay in milliseconds for the ACL-Reload-Scheduler to wait to be triggered.

No

30000

How often in milliseconds the ACL-Reload-Scheduler will be run.

No

120000

Flag indicating whether the scheduler to reload the device master data from MDM should be enabled.

No

true

Shedlock configuration to prevent multiple service instances to run the scheduling job.

No

PT15M

Shedlock configuration to lock the triggering of escalations at least for the duration of TS_SCHEDULER_LOCK_ESCALATION_MINDURATION.

No

PT10M

Shedlock configuration to lock the triggering of escalations at most for the duration of TS_SCHEDULER_LOCK_ESCALATION_MAXDURATION.

No

PT15M

[DEPRECATED - use API instead] Starting with IAS release 26.01.01, changing these values will have no impact. The fine-grained access values configured before IAS release 26.01.01 will be automatically migrated

The facility type Ids for "Custom Product Line" and "Customer Area", for which dynamic resources should be registered. Each tenant can have his own list by defining the variable: TS_FACILITYTYPESTOREGISTERRESOURCE_<REPLACE_HERE_WITH_YOUR_TENANT_ID> e.g. TS_FACILITYTYPESTOREGISTERRESOURCE_7311ea8c-5d48-43fe-acf9-980eedf24b6c.
Manual reload of device master data has to be triggered for the affected tenants when changing this variable’s value.

No

A list: - E14CAB2A-2113-441C-A4A1-FCC6AF91861D

[DEPRECATED - use API instead] Starting with IAS release 26.01.01, changing these values will have no impact. The fine-grained access values configured before IAS release 26.01.01 will be automatically migrated

Define a list of facility types for which the dynamic resource should be deleted in MACMA. Each tenant can have his own list by defining the variable: TS_FACILITYTYPESTODELETERESOURCE_<REPLACE_HERE_WITH_YOUR_TENANT_ID> e.g. TS_FACILITYTYPESTODELETERESOURCE_7311ea8c-5d48-43fe-acf9-980eedf24b6c.

No

-

Cached Token introspection result fallback expiry time. Used in case parsing 'riexp' claim fails.

No

300

Cached Token introspection result initial capacity.

No

100

Cached Token introspection result maximum size.

No

500

Cached User Groups expiry time.

No

300

Cached User Groups initial capacity.

No

30

Cached User Groups maximum size.

No

100

Instance id of the ticket service, displayed in the custom health endpoint.

No

ticket-service@tm

Enables/disables the heartbeat for the websocket communication

No

true

Specifies the maximum size of an attachment in MB (i.e. 5MB). However, not allowed to specify more than 10MB, as there is currently a maximum request body size validation on nginx server of 10MB.

No

10MB

Specifies the maximum number of attachments for a ticket

No

5

Specifies the maximum length of the attachment filename. Longer names are abbreviated in the middle. The maximum filename length must be configured to be at least 15, otherwise the file cannot be uploaded.

No

256

Specifies the allowed extensions for attachment files.

No

A list:

Specifies the forbidden extensions for attachment files, according to the security guideline. Be careful with changing this list.

No

A list:

Specifies the default time (in days) after which closed tickets/archived tickets are automatically anonymized. This time is used only when no specific anonymization configuration exists for a tenant.

No

90

Specifies the default time (in days) after which closed tickets are automatically archived. This time is used only when no specific archive configuration exists for a tenant.

No

30

Enables the ticket anonymization scheduler task.

No

true

Cron value (in Spring CronExpression format: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/scheduling/support/CronExpression.html) for the ticket anonymization scheduler task. (value must be kept in sync with ticketAnonymizationSchedulerLockMinDuration and ticketAnonymizationSchedulerLockMaxDuration)

No

0 0 1 * * *

Minimum duration for the database lock used by the ticket anonymization scheduler task. The lock makes sure that there is only one instance executing the task at a time. (value must be kept in sync with ticketAnonymizationSchedulerCron)

No

PT24H

Maximum duration for the database lock used by the ticket anonymization scheduler task. The lock makes sure that there is only one instance executing the task at a time. (value must be kept in sync with ticketAnonymizationSchedulerCron)

No

PT25H

Specifies how often the scheduler for processing anonymization jobs should run (in milliseconds). Default: 60000 (1 minute)

No

60000

Minimum duration for the database lock used by the anonymization job scheduler task. The lock makes sure that there is only one instance executing the task at a time. Default: PT1M (value must be kept in sync with anonymizationJobSchedulerDelayInMilliSeconds)

No

PT1M

Maximum duration for the database lock used by the anonymization job scheduler task. The lock makes sure that there is only one instance executing the task at a time. Default: PT10M

No

PT10M

Enables the ticket archiving scheduler task.

No

true

Cron value (in Spring CronExpression format: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/scheduling/support/CronExpression.html) for the ticket archiving scheduler task. (value must be kept in sync with archivingSchedulerLockMinDuration and archivingSchedulerLockMaxDuration)

No

0 0 2 * * *

Minimum duration for the database lock used by the ticket archiving scheduler task. The lock makes sure that there is only one instance executing the task at a time. (value must be kept in sync with ticketArchivingSchedulerCron)

No

PT24H

Maximum duration for the database lock used by the ticket archiving scheduler task. The lock makes sure that there is only one instance executing the task at a time. (value must be kept in sync with ticketArchivingSchedulerCron)

No

PT25H

Enables the failed master data reload scheduler task.

No

true

Delay (in minutes) after application startup when the master data reload scheduler for fetching devices and facilities should be started.

No

5

Scheduled period (in hours) when the master data reload scheduler for fetching devices and facilities should be executed.

No

24

Minimum duration for the database lock used by the failed master data reload scheduler task. The lock makes sure that there is only one instance executing the task at a time. (value must be kept in sync with failedMasterDataReloadingSchedulerFixedDelayInHours)

No

PT24H

Maximum duration for the database lock used by the failed master data reload scheduler task. The lock makes sure that there is only one instance executing the task at a time. (value must be kept in sync with failedMasterDataReloadingSchedulerFixedDelayInHours)

No

PT25H

Enables the deviation processing reaction scheduler to retry resolving actions in deviation processor for closed tickets.

No

true

Specifies when and how often the deviation processing reaction scheduler should run to resolve actions for closed tickets in deviation processor in CronExpression format (https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/scheduling/support/CronExpression.html). Value must be kept in sync with deviationProcessingReactionSchedulerLockMinDuration and deviationProcessingReactionSchedulerLockMaxDuration.

No

* * 6/6 * * *

Minimum duration for the database lock used by the deviation processing reaction scheduler task. The lock makes sure that there is only one instance executing the task at a time. (value must be kept in sync with deviationProcessingReactionSchedulerCron)

No

PT6H

Maximum duration for the database lock used by the deviation processing reaction scheduler task. The lock makes sure that there is only one instance executing the task at a time. (value must be kept in sync with deviationProcessingReactionSchedulerCron)

No

PT7H

Maximum number of retries for resolving actions in deviation processor for closed tickets. With every attempt of the scheduler to update deviation processing reaction state it decreases this number. If the counter is 0 the scheduler will not trigger an update request anymore.

No

4

Maximum number of context attribute values per domain when filtering tickets. Filtering with multiple values can seriously impact performance. The default value is 10.

No

10

Timeout in seconds for the shutdown of any phase (group of SmartLifecycle beans with the same 'phase' value), when the shutdown mode is set to graceful

No

45

Whether the executor should wait for scheduled tasks to complete on shutdown, when the shutdown mode is set to graceful

No

true

Maximum time in seconds the executor should wait for remaining tasks to complete, when the shutdown mode is set to graceful

No

45

Whether the scheduler should wait for scheduled tasks to complete on shutdown, when the shutdown mode is set to graceful

No

true

Maximum time in seconds the scheduler should wait for remaining tasks to complete, when the shutdown mode is set to graceful

No

15