Every rule below is enforced in the executable; the argument container enforces none, because it declares no arguments. Three additional rules are inherited from SAIF.Framework.Windows and are included for completeness even though two of them are not reachable by this application.
BR-OBKS-001 Asynchronous or synchronous update mode¶
Field
Value
Statement
Updates are sent to OnBase asynchronously or synchronously according to OnBaseKeywordSync.onbaseasync; only the synchronous path yields a document handle.
BR-OBKS-004 Document count gates whether a record is sent¶
Field
Value
Statement
When document counting is enabled, a record is sent only if it has at least one document to update; when disabled, every record is sent without a count check.
Trigger
Per record
Enforcement
KeywordUpdater.PerformUpdate
Origin
application
Outcome
Send or skip decision with a logged reason
Source
OnBaseKeywordSync/Services/KeywordUpdater.cs
BR-OBKS-005 Equal prior and new values are not sent¶
Field
Value
Statement
A record whose prior and new values are equal (case-insensitive) is not sent to OnBase.
Trigger
Per record, when the document-count branch does not already return true
Enforcement
KeywordUpdater.PerformUpdate
Origin
application
Outcome
Logged "No updates will be sent to onbase because prior value and new value are the same". Ordering finding: because the document-count branch is evaluated first, a record whose values are identical is still sent when document counting is on and documents exist — this equality short-circuit only applies when document counting is off or no documents exist*
Source
OnBaseKeywordSync/Services/KeywordUpdater.cs
BR-OBKS-006 Trigger type and query keyword derived by precedence¶
Field
Value
Statement
A keyword sync's trigger type and OnBase query keyword are derived by precedence: claim number, then person id, then policy number, then agency number, then group acronym.
Three keywords are translated to Y/N flags: CLAIM EXPOSURE FLAG is Y when the value is not "0"; CLAIM SECURED FLAG is Y when the value is R or T; POLICY SECURED FLAG is Y when the value is non-blank. All other keywords pass through unchanged.
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.