Deletion periods – processes that retire themselves
Many processes rightly do not run forever: an application, an incident, a support case – after processing, the run belongs in the rule handling or in the recycle bin, depending on your rules. linqi provides the “Set deletion period” action for this: within the process, you define after how many days an individual process run should be deleted. The period is set per run – also derived from process values, for example via a placeholder – and starts running from the point where the action stands in the flow. After that, linqi takes care of it itself: a background service checks the running deletion periods and removes expired processes.
The flow remains documented: every deletion is part of a deletion protocol regulation that you maintain in linqi. So you can see not only that a process was deleted, but that you can trace the flow of the deletion – when the period was set, when it expired, and when the run was removed. In addition, the retention behavior is configurable: from the time spent in the recycle bin to the time until deletion, to the retention of the deletion protocol itself. This turns the deletion period into more than a technical timer: it becomes a documented, rule-based retirement of your processes.
Retirement that documents itself
The “Set deletion period” action is deliberately kept small: it stands as a step in the process and sets a period in days. What it achieves in combination is larger: processes clean up after themselves with it. An application that expires after 30 days, an incident that should be stored for 90 days after processing, a support case that leaves the run after 7 days – all of this can be defined per process, instead of checking manually. The deletion itself runs via a service in the background that checks the periods and removes the expired runs. Together with the deletion protocol, this creates a clean, rule-based flow: defined in the process, executed in the background, documented in the protocol.
Frequently asked questions about deletion periods
How is the deletion period set?
Via the “Set deletion period” action in the process: it sets the period in days per process run – also as a value from the process, for example via a placeholder.
Who deletes the process?
A background service checks the running deletion periods regularly and removes expired processes – the flow runs without manual intervention.
Is the deletion traceable?
Yes. Via the deletion protocol, the deletion is documented – you can trace the flow of the deletion.
Can the period vary per process?
Yes. The period is set per run and can be derived from process values – different processes can use different storage periods.