Archiving work queue items

[Dawid.Pekala]

Just like it is possible with process logs, it would be great to see an option to added to archive off work queue items.
It could be as simple as a tickbox within log archiving to include queue items or (even better) as an entire separate archiving subrouitne, so it can run on separate schedule.

[Anonymous]

Hello Dawid,

The only way i know to export the work queue items is throug the "export current view as report" function, and after that manually cleaning up, the work items processed. But i dont know an automated way to archive the work queue items

[MelanieGiuliani]

Hi Dawid,

Thanks so much for submitting your idea! We are moving it into the Under Consideration status while we route the idea through our internal review process. 

We will update you as your idea moves along the lifecycle.

Thank you!
Melanie 

[Stefan__Pappalardo]

The in product session log archiving function is also useful to delete not needed data. In my whole opinion there should be an in product function to manage all the database housekeeping tasks to avoid the database from growing infinitely. This would include the (archiving and) deletion of session logs, schedule logs, completed work queue items, unused work queue item tags.

Especially the work queue item housekeeping should adjustable for every wok queue in the work queue management area of the product.

[robert.nicklin]

Hello @Dawid.Pekala,

Can you confirm whether you want to archive work queue items (i.e. export and store the data in the item in a specific format with the option to later import it) or whether you're just looking for more flexibility on the maintenance/removal of items from within your work queues?

I'm going to mark this idea as Needs More Info awaiting your reply.

Regards,

Rob

[Dawid.Pekala]

Hi @robert.nicklin 

It's been a while, but gathering some old notes/thoughts from my team, the idea was to replicate what Session Logs archiving does, so:

1. be able to select (by dates and queues) queues to archive
2. the date used for archiving would be the 'last updated' date
3. archived queue items would be stored in similar fashion to how logs are (so under pre-defined folder, then YYYY/MM/DD/<Queue>)
4. archived queue items would be stored in a single file per date/queue
5. archived files would be encrypted with BP encryption key (as per Log files)
6. user would be able to re-import archived files (similarly to Log files, by selecting either individual files or any level of day/month/year structure)
7. auto archiving should be possible, with number of days specified after which queue items would be archived into pre-defined location (as per point c))

Although I must stress that the time passed since this idea somewhat diminished the priority/benefit of it. With some careful balancing of how much we delay the deletion old queue items and archiving logs off (combined with some improvement in business awareness, trust and ownership/response time) we have managed to avoid any situations where we'd need this functionality. 

So no rush 🙂

Regards

Dawid