Valid configuration for History Clean up


#1

Anyone have a valid set of properties to schedule process history clean up? We used to do it inside processes.xml, however we are now using the spring configuration to just auto scan.


#2

Hi,

The configuration properties are the same. If you create the engine via Spring, you would set them as properties in the Spring XML as in https://docs.camunda.org/manual/7.9/user-guide/spring-framework-integration/configuration/#configure-an-application-managed-process-engine.

Cheers,
Thorben


#3

I am having some difficulty translating that into yaml, as this config does not seem to schedule the clean up

camunda:
bpm:
admin-user:
id: admin
password: admin
database:
type: mysql
history-level: full
application:
delete-upon-undeploy: false
scan-for-process-definitions: true
deploy-changed-only: true
historyCleanupBatchWindowStartTime: 02:00
job-execution:
deployment-aware: true


#4

Perhaps I cannot configure via Yaml? I see no configuration here:

https://docs.camunda.org/manual/latest/user-guide/spring-boot-integration/configuration/


#5

Sorry, I didn’t notice you use Spring Boot and assumed you use plain Spring.

Yeah, I think you’ll have to configure it programmatically, e.g. by creating a ProcessEnginePlugin bean.

Cheers,
Thorben


#6

Alright, i’ll wire it in via the bean instead. Thanks