Anyone have a process or more than one process for good house keeping? dbcount

I recently reviewed our dbcount for all business classes in our production environment and was a little surprised by the numbers we have. I've already opened an incident with infor support but I was curious if anyone here is already doing house keeping cleaning up record counts on your systems either by IPA process or other processes.

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

cleverly

We periodically delete completed work units older than N months. (Process Server Administrator > Administration > Work Units > Ellipsis > Schedule Work Unit Deletion).

If you have any of your Async queues set to retain history it is a good idea to periodically delete/purge those records as well. (Async Administrator > Async Overview > (any queue) > Ellipsis > Delete Finished Triggers (or Delete Finished triggers in All Queues)).

Rebecca Derr

We evidently had no work unit purge processes set up during implementation and when I reviewed our pfi tables there were way too many unnecessary records. After reviewing with our team I set up three existing processes to run on a schedule. These can be found where Michael had noted (Process Server Administrator > Administration > Work Units > Ellipsis > ...).

ScheduleMoveToWorkUnitHistory
ScheduleNonUAWorkUnitDeletion
ScheduleWorkUnitDeletion

lrjurgen

I like this tactic, can I ask how did you choose the parameters? I'd like to do this for WU that are say 90 days old and older. Using this I assume, but 90 in the begin days and some arbitrary number (or blank) in the end days?

Noe Ramos

thank you all for your feedback. i have some managers here wanting to keep work units indefinitely but i can see a performance issue if we are creating 100,000 work units monthly. we are sitting at about 1.5 million work units sitting in our environment as we have not deleted anything since conversion. Is anyone aware of security reports that would generate the same audit information for work units that could be saved rather than saving the work unit itself?

one thought was to move work units to work unit history and save everything there indefinitely. i know it would remove some data compared to sitting in the normal work unit class.

another question - does anyone have their IPA configurations set to prune work unit data?

andy

Are your managers only concerned about losing work units for flows that include approvals? If so, maybe the ScheduleNonUAWorkUnitDeletion job is an acceptable compromise since it won't delete work units with User Actions or Action Requests.

Starting with moving work units to history might be the best first step since it just prevents the work units from appearing in the LiveWorkunits list. I don't believe it actually purges any data. I believe it just sets Archived flag to true on the work unit so it doesn't appear in the LiveWorkunits list. If after a month of moving work units to history and your managers haven't reported any issues, maybe you could then proceed to purging data?

don-kintzle

Have you reviewed KB Article 2266724 - IPA Maintaining Work Units? This has some good information regarding cleaning/maintaining work units. It specifically discusses how to clean up Work Units without losing the audit on the UserActions taken.

Copyright © 2025 Infor. All rights reserved.