Common\ProcessState\JobHistory\IsToExport

Hi Alan,

What version are you running?

The benefit of using a HDb is that historical data is stored in a separate DB from your main DB, and therefore not using up valuable space in your database.

Historical data can be viewed when the HDB is configured as part of the overall implementation.

It really depends on whether keeping historical data is important to you or not.  More on this here:

https://support.oneidentity.com/technical-documents/identity-manager/8.2.1/data-archiving-administration-guide#TOPIC-1796972

Trevor

Trevor - Thank you for the reply - I understand how the history Databases works - My question was specifically about the JobHistory - Does anyone find sending this to History rather than deleting it usefull and if they do send to history is it just stored in the HistoryJob table waiting for someone to run a query against it - i.e no out of the box tools actually look at this table in HDB

Hi,

I'm afraid it is sadly true that there is no OOB UI that you can just use to look at the information in HistoryJob.  I have been asking for this enhancement for quite some time now.  You can view it using JobQueueInfo that is configured against your HDB but you first have to copy the entries from HistoryJob to JobHistory (I did it and set the XTouched to a known value that I could use in a filter and for deletion).

Regards, B.

Hi,

I'm afraid it is sadly true that there is no OOB UI that you can just use to look at the information in HistoryJob.  I have been asking for this enhancement for quite some time now.  You can view it using JobQueueInfo that is configured against your HDB but you first have to copy the entries from HistoryJob to JobHistory (I did it and set the XTouched to a known value that I could use in a filter and for deletion).

Regards, B.

Bary, we are having something in the backlog for that area but I cannot give a timeframe or release when a UI solution is coming, But it is on our radar.

Good to know. Thanks.