Archiving - Reference field options - where do they come from?

Sue Frost
Giga Guru

I'm trying to understand the archive process so that I can solve a problem with ours.

I'm looking at the Archive Related Records and trying to figure out where the values in the Reference field are coming from. Some appear to be out-of-the-box but a few are most definitely custom. I've tracked this field to a Glide Object - Reference Field, but there's nothing similar on the sys_glide_object.list.

Here's the field:

6-16-2016 10-47-59 AM.png

Where do I find the entries to add / update them?

Thanks!

1 ACCEPTED SOLUTION

Michael Fry1
Kilo Patron

On your archive rule you set a table. Any table that Extends from the table you set in the rule, including those that Extend from any Extended table should be in the list of related records.


View solution in original post

3 REPLIES 3

Michael Fry1
Kilo Patron

On your archive rule you set a table. Any table that Extends from the table you set in the rule, including those that Extend from any Extended table should be in the list of related records.


That's starting to make sense. If I could restate ... the Reference field displays a list of all the defined relationships / references that extend from the selected table.



If so, that gets me closer to a solution for my initial problem. Thank you!



----


Initial Problem as FYI.


We have a custom application which contains:


  • CASE table (extends Task)
  • COMMUNICATION table (extends Task)
  • ATTACHMENTS (no extension)


Cases have related Communications which have related Attachments.



We turned on archiving earlier this year but have just discovered that the Attachments are not being archived. Confusion arises because attachments can't be located in the archive (to be restored) and the records in the live Attachments table show as having a blank Task field - so no relationship.


Fortunately, once the Case and Communications are restored, the relationship to the Attachment is rebuilt. (The alternative - thousands of orphaned records - is very unpleasant to contemplate.)



I was able to create a second archive rule which is a child of the first one. The second rule will archive the Attachments related to the Communication. As a child rule, it is automatically dependant on, an inherits the filter criteria from, the parent rule which runs against Case and archives cases closed 14 months ago.


How to setup a rule both tables in the archive .



For an example :   cmdb_ci is parent table which is all other cmdb_server , cmdb_ci_comp tables are extend table


I cant setup both in archive rule at same time



how to do taht