Consumption¶

A consumer references SAIF.Claims.Intake.Client, copies the ClaimIntakeBasic client endpoint into its own configuration file, constructs a ClaimIntakeGateway with that endpoint name, calls Submit or GetStatus, and disposes the gateway. The gateway wraps a svcutil-generated ClaimIntakeClient. It applies a 30-second send timeout, performs no retry, and is not safe for concurrent use.

Reference style¶

Field	Value
Mechanism	Service Reference (svcutil)
Declared in	`src/SAIF.Claims.Intake.Client/Service References/ClaimIntakeReference/Reference.svcmap`
Generated artifacts	`src/SAIF.Claims.Intake.Client/Service References/ClaimIntakeReference/Reference.cs`
Target framework	.NET Framework 4.8
Regeneration command	Visual Studio "Update Service Reference"

Reference.cs has no hand edits, so a refresh does not discard any repository change.

Construction¶

public ClaimIntakeGateway(string endpointConfigurationName)
{
    _client = new ClaimIntakeClient(endpointConfigurationName);
    _client.ClientCredentials.Windows.AllowedImpersonationLevel = TokenImpersonationLevel.Identification;
}

Step	Requirement
Endpoint address	Read from the `<client><endpoint name="ClaimIntakeBasic">` element of the consuming application's configuration file, selected by the `endpointConfigurationName` constructor argument
Binding	Named binding configuration `ClaimIntakeBasic`
Credentials	Windows transport credential of the calling process, with an impersonation level of `Identification`
Initialization	Single-constructor

Endpoint configuration¶

Setting	Value	Source	Changeable without a rebuild
Endpoint address	`http://claims-intake-dev.saif.example/ClaimIntake.svc`	`src/SAIF.Claims.Intake.Client/app.config`	Yes
Binding configuration	`ClaimIntakeBasic`	`src/SAIF.Claims.Intake.Client/app.config`	Yes
Security mode	`TransportCredentialOnly` (`clientCredentialType="Windows"`)	`src/SAIF.Claims.Intake.Client/app.config:14`	Yes

A class library's own app.config is not read at run time. The consuming application must copy the <client> and <bindings> sections into its own configuration file, which is also where each environment sets its address.

Resilience¶

Concern	Finding	Configurable by consumer	Source	Tech debt
Timeout	30 seconds	Yes (`sendTimeout`)	`src/SAIF.Claims.Intake.Client/app.config:12`	No
Retry	None configured	No	-	Yes
Circuit breaking	None configured	No	-	Yes
Thread safety	Not safe - one channel is shared by every call on a gateway instance	-	`src/SAIF.Claims.Intake.Client/ClaimIntakeGateway.cs:21`	Yes
Cancellation	Not supported - no cancellation on any call site	-	-	No
Message size limits	None set - binding defaults apply	Yes (`maxReceivedMessageSize`)	-	No

A consumer that needs retry must wrap each call in its own policy and create a new gateway for each attempt, because a faulted channel cannot be reused. A consumer that needs circuit breaking must provide it outside the package. A consumer that calls from several threads must construct one gateway per thread. The retry, circuit breaking, and thread safety findings are recorded in Tech debt.

Disposal¶

Aspect	Finding
Disposal performed	`Close()`
Faulted channel handled	No - a faulted channel throws from disposal and masks the original failure
Wrapper responsibility	`ClaimIntakeGateway` disposes the proxy
Source	`src/SAIF.Claims.Intake.Client/ClaimIntakeGateway.cs:78`

public void Dispose()
{
    _client.Close();
}

Error handling for consumers¶

Failure	Surfaces as	Consumer action
Service unreachable	`EndpointNotFoundException`†	Treat as transient, check the configured address, and retry with a new gateway
SOAP fault returned	`FaultException<ClaimValidationFault>`† for a failed validation on `SubmitClaim`, `FaultException`† for any other failure	Read `Detail.Code` and `Detail.FieldErrors` from the typed fault; treat the generic fault as a service error and do not retry blindly
Timeout exceeded	`TimeoutException`†	Retry with a new gateway, because the channel is faulted after a timeout
Response larger than the message size limit	`CommunicationException`†	Raise `maxReceivedMessageSize` in the consuming application's binding configuration
Empty or absent output message	`null` from `GetStatus`	Treat as "claim not found or status unavailable"; the service also returns null when its own lookup fails

Usage examples¶

// Submit a claim, then read its status
using (var gateway = new ClaimIntakeGateway("ClaimIntakeBasic"))
{
    ClaimReceipt receipt = gateway.Submit(submission);
    ClaimStatusResult status = gateway.GetStatus(receipt.ClaimNumber);
}

// Handle a validation failure
try
{
    gateway.Submit(submission);
}
catch (FaultException<ClaimValidationFault> ex)
{
    Assert.Equal("INJURY_DATE_FUTURE", ex.Detail.Code);
}

Scenario	Operations used	Notes
Submit a claim and read its status	`SubmitClaim`, `GetClaimStatus`	Taken from `tests/SAIF.Claims.Intake.Client.IntegrationTests/GatewayTests.cs:18`
Handle a validation failure	`SubmitClaim`	Taken from `tests/SAIF.Claims.Intake.Client.IntegrationTests/GatewayTests.cs:41`

Lifecycle guidance¶

Question	Answer
Construct once or per call	Per unit of work - every integration test constructs a gateway inside a `using` block and disposes it after one or two calls
Disposable	Yes (`IDisposable`)
Safe to share across threads	No - see the Thread safety row in Resilience

Client index
Overview
Architecture
Contract
Operation map
Client reference
Dependencies
Tech debt

Note: Statements marked with † were retrieved from dependency library documentation via the Legends CLI RAG service. They describe inherited behavior from the indicated origin library and should be verified if the dependency version changes.

Sources¶

src/SAIF.Claims.Intake.Client/ClaimIntakeGateway.cs
src/SAIF.Claims.Intake.Client/Service References/ClaimIntakeReference/Reference.svcmap
src/SAIF.Claims.Intake.Client/Service References/ClaimIntakeReference/Reference.cs
src/SAIF.Claims.Intake.Client/app.config
tests/SAIF.Claims.Intake.Client.IntegrationTests/GatewayTests.cs