nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Clean history periodically

pred05

Hi,
i am sure to have seen somewhere in the userguide that we can configure a periodical clean of the historic. Or a time to keep the history's data before clean.

I have found some topic about the query for clean the history. If it isn't possible to configure it, i think i'm going to make a job which execute these query.

Have a nice day,
Thanks for help.

Find more posts tagged with

Comments

martin_grofcik

Hi,

i am sure to have seen somewhere in the userguide that we can configure a periodical clean of the historic. Or a time to keep the history's data before clean.

I am not aware of it.

I have found some topic about the query for clean the history. If it isn't possible to configure it, i think i'm going to make a job which execute these query.
I would prefer archive. Why do you want to clean up history - If you do not need history why do you collect history data?

Regards
Martin

pred05

Ok thanks you. So i'm mistaken, i think i confuse with an other thing.
I have to use multiple database for handle several workflow. In each database i want to enable history. But i will have a lot of instance so i fear about the database performance. Also, i want to have a unique database which contain all history of each workflow to ease the post processing on this data (to visualize with several chart some data like the time's average to complete a process for example).

trademak

Right, we have defined all historic tables without foreign keys, to make it easy to move or copy any data.
But there's not specific logic doing that, it has to be created per use case.

Best regards,