Proper-case conversion¶
Proper-case conversion is a thin wrapper around the CorrectAddress vendor's proper-case operation. It exists so consuming applications can standardize the casing of free-text fields (for example, addresses assembled outside the main Address cleanse flow) without depending on the vendor proxy directly.
| Field | Value |
|---|---|
| Operation ID | OP-CA-03 |
| Trigger | Caller invokes clsCleanAddress.ConvertToProperCase(inString) |
| Inputs | inString — the string to convert |
| Outputs | Trimmed proper-case String |
| Primary components | clsCleanAddress.ConvertToProperCase, CleanAddressSvc.clsCAServices |
| Entry point | Services\SAIF.Services.CleanAddress\clsCleanAddress.vb |
Steps¶
- Create a new
CleanAddressSvc.clsCAServicesproxy instance and setAllowAutoRedirect = TrueandUseDefaultCredentials = True. - Call
ConvertToProperCase(inString)on the proxy. - Trim the returned value and return it to the caller.
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([Caller invokes ConvertToProperCase<br>with inString]) --> Proxy[Create clsCAServices proxy]
Proxy --> Call[Call vendor ConvertToProperCase]
Call --> Trim[Trim returned string]
Trim --> Return([Return normalized string])
Failure and edge-case behavior¶
- The vendor call is not wrapped in a
Try/Catch; a SOAP fault or transport error propagates to the caller unhandled, unlike Address cleanse.* - No null or empty-string guard is applied to
inStringbefore the call; behavior for null input depends entirely on the vendor service.**
Note: Statements marked with
*were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts. Statements marked with**could not be confirmed; treat as unknown until verified.
Related documentation¶
Sources¶
Services\SAIF.Services.CleanAddress\clsCleanAddress.vbServices\SAIF.Services.CleanAddress\Web References\CleanAddressSvc\Reference.vb