Data archiving for Problem and its related records

prashu · ‎09-08-2016

Hi All,

We have a requirement to implement data archiving for problem and problem related records.

We have implemented the below functionality.

Problem:

I have created an archive rule and its archive related records for the following

Below are the archive related records which does not have the reference field so I used dot-walking for archiving the following related records.

PTASK Ticket
Related changes
Related CSI

->It works fine but need to confirm whether it is a best Practice or not? and also wanted to know from where the reference field choices comes from?

And below are the archive related records which already had a reference so I used the existing one.

Attachments
SLA's

Problem Subtask:

->We also need to archive the Problem subtask related records as well. Can we achieve it using the same archive rule or need to create a new archive rule?

Any suggestions/ideas. Please guide me on this.

Thanks in advance,

Prashanthi

Anurag Tripathi · ‎09-12-2016

This is from wiki

The Archive action updates the Document ID of the related record to point to the archived table. For example, if you select the Table sys ID Attachment(sys_attachment)* reference, the related record rule updates the attachment record to change the Document ID to refer to the archived table record.

Attachment is not actually archived, but it shows up on the archived record same way as it was on the main record. Only the reference on the sys_attachment table gets updated. If this is not happening in your case automatically then contact HI.

Or you don't want the above scenario and you are trying to achieve something else?

-Anurag

View solution in original post

nikhil_001 · ‎05-19-2017

Hi Anurag,

If we increase the batch_size to 2000. How much impact can it have on the performance?

glide.db.archive.batch_size	Controls how many records an archive rule processes per batch job.	Integer	2000
glide.db.archive.sleep_time	Controls how long each archive rule batch job runs, in seconds.	Integer	1
glide.db.archive.max_iterations	Controls the maximum number of batch jobs to run within an hour.	Integer	10

Thanks & Regards,

Nikhil jain