This page documents every operation of ThirdPartyArchivalService† that repository source calls through HylandOutBoundContractClient. The contract declares one operation and it is documented here.
Endpoint address from the setting ProcessOB3PRetention.WSPEndPointUrl; binding from <client><endpoint name="BasicHttpBinding_HylandOutBoundContract"> in ProcessOB3PRetention/App.config; no timeout, no client credential. See Endpoint resolution
The long result of ArchiveDocumentResult is returned unchanged by OnBaseService.ProcessRetention. The caller logs it as OnBase Document ID: {onbaseId} and does not validate it for zero or negative values, nor persist it beyond the log line. What the value means inside OnBase is not stated in the WSDL**.
Once per batch, sequentially. Batch size comes from processob3pretention.processbatchsize, seeded 200 with a code fallback of 100 for an empty or invalid value; a missing key throws ApplicationException
The call is synchronous and blocking. The task-based overload the generator produced is not used.
No call is made when the batch source returns zero claims.
If the call succeeds and the following step that marks the batch as processed fails, the batch has been sent but is not recorded as processed, so a later run could resend the same claims*. See Business rules.
Note: Statements marked with † are derived from dependency library
documentation via the Legends CLI. Statements marked with * were inferred
from code structure or contextual evidence. Statements marked with ** could
not be confirmed; treat as unknown until verified.