Entering a Delete Rule
DeleteArchiveRules, including three columns the product documentation does not mention.
DeleteArchiveRules follows the same column pattern as the other rules tables, plus DeleteInstruction and three columns that appear in no shipped documentation.
| Column | Purpose |
|---|---|
DeleteInstruction | Archive or iManageANDArchive — see article 401 |
| HardDelete | Undocumented. Confirm the behaviour with GDSI before setting it. |
| SkipCheckedOutDocuments | Undocumented. Leaves checked-out documents in place. |
| SkipDeclaredDocuments | Undocumented. Leaves records-declared documents in place. |
Note The two Skip columns are operationally significant — they decide whether a deletion quietly leaves content behind. Establish what your build does with them before running a delete rule against anything that matters.
Safe entry
Identical to the other rules tables, and more important here than anywhere else. Set Disable = 1 on every row until the rule is complete, or stop the service while you type. A half-entered delete rule scoped to a client is the worst outcome the product can produce.
The API alternative
A third-party system can create delete rules through the Archive API rather than writing to the table directly. GDSI supplies a Postman collection with the endpoint. Authentication uses ApiClientId and ApiClientSecret with Basic authentication.