Task Pruning Best Practice

Which IIQ version are you inquiring about?

Version 8.2

Share all details related to your problem, including any error messages you may have received.

We need to explore how to keep the task results longer then 60 days. We are currently looking to extend the Days before task result deletion from 60 to 720. However, doing this will increase our database size significantly. Is there any alternative solutions we can use to retrieve older task results?

Alternative solution which I have come across is to host a database and basically capture the taskresults older than 60 days and store it there and leverage in-house scripting to retrieve the details from the task results.

The last way which I have come across is to have the task results sent out as an email with the results converted to jasper reports as an attachment and keep that mailbox(DL in most cases) active.

Will be looking forward for any other alternatives.

@amansingh

Also, you can create a custom report to obtain any columns of data you like of TaskResult older than 90 days.

Charles-

You could export these taskResults to a separate debase if you upgrade to IdentityIQ 8.4. The export functionality is quite robust in this release.

Additionally, you might consider a third-party plugin like this object exporter plugin that will write those taskResult XML objects to your local filesystem in a structure compatible with SSB.

https://community.sailpoint.com/t5/Professional-Services/IdentityIQ-Object-Exporter-Plugin/ta-p/190179

Finally, here’s a pruning best practices guide from our docs team that provides some archiving suggestions:

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.