When I try to create a Clone Preserver on the table Update Sets (sys_update_set) the User Interface

[William David]

When I try to create a new Clone Preserver, as part of an existing Clone Profile, for the table "Update Sets" (sys_update_set), my entries in the Name and Table field get immediately erased when I move my cursor from the entry boxes. It is as if there is a rule preventing me from creating a Clone Preserver. Additionally, I CAN find and select the Update Sets table (sys_update_set) in the "Table" entry field, but as described above, that selection is immediately counteracted by this mysterious rule.

I am aware that there is a Clone Preserver Setting "No. of days of In-progress Global Update Sets to be preserved". Was the logic implemented behind this setting something that was implemented in place of allowing Users to create Clone Preservers on the Update Sets table (sys_update_set)? Additionally, how are the days selected by this setting related to the various Update Sets? Are the "number of days" calculated from the Update Set creation date, of from the Update Set modification date, or some other date associated with the Update Sets? If we cannot create our own custom Clone Preserver on the Update Sets table, then we'll need to understand this setting clearly, with regards to the phrase "no. of days", so that we can use it confidently in the place of a Clone Preserver.

[William David]

Posted to a Service Now Support Case and reposted here.

Based upon our analysis and testing, we have refined our question.

1. We wish to know if we can request that the Clone Preserver method for conserving In progress Update Sets (the Clone Preserver Setting "No. of days of In-progress Global Update Sets to be preserved") be extended to include custom Update Sets in custom Application scopes (in our case, "Realty Income Spoke"), in addition to the "Global" Application scope.
2. We desire to know exactly which Update Set field is used to determine the Clone Preserver Setting "No. of days of In-progress Global Update Sets to be preserved". This is important for ensuring we understand the logic that is preserving our VERY valuable custom Update Sets containing development work (which may represent many man-days of effort).