Data archiving for Problem and its related records

[prashu]

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 · Accepted solution]

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?

[prashu]

Hi Anurag,

Thanks for your response Anurag.

I meant and implemented the same. It works fine.

Thanks

Prashanthi

[rlatorre]

Are attachments archived automatically or does each rule need a related record entry for attachments like the following?

[rlatorre]

Does this statement mean no related record entry is needed?

"For attachment you don't really need to do anything. How irt works in the background is, the reference to the task on sys_attachment table is updates with the sys_id of the archived record. Hence the attachment shows up in the archived record."

[Anurag Tripathi]

Hi,

So attachment is really not archived, but the link of the attachment that earlier pointer to the record on the main table, is now changed and it points to the archived record.

In other words, same attachment(record on sys_attachment table) is just repointed to the archived record.

Hope that clears this up.

-Anurag