The application enforces four rules of its own around the ArchiveDocument call: how claims are batched, when the call is skipped, how the request is built, and the order of archive and mark-processed. Rules enforced by the remote service are outside this repository and are not restated here.
Claim numbers are partitioned into batches of the configured size, and ArchiveDocument is called once per batch
Trigger
Evaluated in ThirdPartyRetentionProcessor.Execute before the first call
Enforcement
The size comes from the setting processob3pretention.processbatchsize; the key must exist — GetConfigSetting throws ApplicationException if it is absent — but once a value is returned, an empty, non-numeric, zero, or negative value falls back to 100
Origin
call site
Outcome
The seeded value is 200 on prod, entqa, and npuat per environmentSettings/settings.yml; a present-but-invalid value silently becomes 100, while a missing key fails the run (exit 5) before any claim is processed
BR-OBR-003 Build the request from a fixed placeholder document and the batch claim numbers¶
Field
Value
Statement
Every request carries the same placeholder text document and the batch's claim numbers as standalone keywords
Trigger
Each call to OnBaseService.ProcessRetention, before ArchiveDocument
Enforcement
Message construction in the wrapper; FileInfo.MIMEType and FileInfo.Base64FileStream are literals and Keywords.StandAlone.ClaimNumber_Collection is the supplied claim numbers
Origin
wrapper
Outcome
The remote service receives identical document content on every call, varying only by claim numbers