Which one is preffered Archieving or Deleting a process model in Data management .
Any use case for the both ?
Discussion posts and replies are publicly visible
My $.02, doing both Dev and O&M long term on all of my projects, I default to deleting process instances after 30 days. System processes, and more mature processes, I will delete after 7. This generally gives enough time for debugging, and to resolve our most common "Help, we accidentally denied/ended the process and do not want to bother the prior approvers again" (request to restart at a given step). If any high-priority bug occurs, we certainly will know about it within a month's time, and you can edit the instance to add/activate a dummy rule node (or something of the sort) to keep it from archiving if you need more time to debug.
We've archived millions of processes in the past (early theory), while never having to unarchive 1. They just eat server resources, and processes should be designed to save as much audit type information (history, etc) to the DB for reporting. Archiving was more of a potential decision in the original "Portal" days.
If I were doing O&M and received issues on processes that had been deleted after 0 or 1 day, I would certainly start heating up fish!!
The only other note on deletion settings, which I haven't confirmed is still an issue, is it used to be the best practice for asynchronous sub processes to delete at 1 day instead of 0 to prevent a system race condition.
That race condition is a fun one. I bet that was fun to figure out (assuming you know about it the hard way).
Those are always "fun"! If I recall, I learned about it the easy way a while back (from Eduardo during his tenure with Appian). We hadn't run many subs as asynchronous in the legacy Portal/Apps environment, but we do so more now with Tempo and shorter lived processes - and if they are set to delete, do so after 1 day. No one needs more issues