how to configure History cleanup through config

Camunda 8 Topics
,
1

Hi,

we are doing POC on camunda8 saas, but actively we are using camunda7 and their features. In POC i pickedup History cleanup activity task, In C7 we are doing this activity using generic properties, like as below
camunda:
bpm:
generic-properties:
properties:
historyCleanupBatchWindowStartTime:
historyCleanupBatchWindowEndTime:
historyCleanupStrategy:
historyTimeToLive:
batch-jobs-per-seed:
invocations-per-batch-job-by-batch-type:
historic-instance-deletion:
historic-decision-instance-deletion:

when i used C8 shared config properties, but nothing happend

Application: Springboot, C8
Depemdancy: camunda 8.2.4

could you please share your input, how can i do this same activity through C8?

2

Hi @Sanket, welcome to the forums! You can view documentation about data cleanup and retention in our documentation (linked below). That should help get you started!

3

Hi @nathan.loding

I tried with both the properties but not working in my system.
could you please look and update
Currently i am just using below dependancy

io.camunda.spring spring-boot-starter-camunda 8.2.4

PBS SS:

image
image1126×632 40.4 KB

image
image1913×946 132 KB

4

Hi @Sanket - apologize, I misread your post! I thought you were working with a Self-Managed installation, not the SaaS product. The links I provided are for configuring cleanup/data retention in a self-managed install. I do not believe this is something you can automatically do with SaaS. With 8.3 we support deleting finished instances through Operate.

Can you share a bit more about why you want to clean the history in the SaaS product? Are you just working to implement from your C7 setup? I’d love to send some feedback to the product team if you can share some more details!