---
title: SAIF.Data.Guidewire operations and processes
summary: Business and technical operations supported by this library.
status: draft
owner: SAIF.Core documentation team
last_reviewed: 2026-09-24
library: SAIF.Data.Guidewire
reference_type: package
---

# SAIF.Data.Guidewire operations and processes

This page is the operation catalog and cross-operation hub for this library. Each operation's detailed, step-by-step logic lives in its own page under `operations/`.

## Operation catalog
| Operation | Intent | Trigger | Inputs | Outputs | Rules |
| --- | --- | --- | --- | --- | --- |
| [Resolve base URL and authenticate](operations/resolve-base-url-and-authenticate.md) | Resolve a client's base URL and Basic-auth header, and execute cached requests | Client construction / first request | `UrlKey`, `AuthKey`, `IDataClientConfiguration` | Configured `HttpClient` with `BaseAddress` and `Authorization` header | [SDG-BR-001](business-rules.md#sdg-br-001-base-url-resolved-from-environment-configuration), [SDG-BR-002](business-rules.md#sdg-br-002-basic-credentials-read-from-secure-configuration), [SDG-BR-003](business-rules.md#sdg-br-003-responses-cached-unless-caching-is-disabled) |
| [Create claim activity](operations/create-claim-activity.md) | Post a new activity request against a Guidewire claim | Caller invokes `CreateActivityRequest` | Claim id, `Activity` | HTTP 2xx or thrown exception | [SDG-BR-010](business-rules.md#sdg-br-010-null-activity-properties-omitted-from-serialized-request), [SDG-BR-011](business-rules.md#sdg-br-011-non-success-responses-throw-with-status-and-content) |
| [Claim data retrieval](operations/claim-data-retrieval.md) | Retrieve claim, MCO, condition, contact, financial, vocational, and legacy-claim data | Caller invokes a `ClaimDataApiClient` method | Claim id or number, financial query options | `ClaimData`/related DTOs | [SDG-BR-003](business-rules.md#sdg-br-003-responses-cached-unless-caching-is-disabled), [SDG-BR-012](business-rules.md#sdg-br-012-empty-bulk-claim-request-short-circuits) |
| [Create check or recovery](operations/create-check-or-recovery.md) | Post a new check or recovery financial transaction | Caller invokes `CreateCheckAsync` / `CreateRecoveryAsync` | Claim id, `CheckFinancialData` / `RecoveryFinancialData` | HTTP 2xx or thrown exception | [SDG-BR-011](business-rules.md#sdg-br-011-non-success-responses-throw-with-status-and-content) |
| [Payment and check lookup](operations/payment-and-check-lookup.md) | Retrieve payments by invoice number or issue date, or a check by number | Caller invokes a `FinancialDataApiClient` lookup method | Invoice number, issue date, zero-pay flag, check number | `PaymentsResponse` / `CheckFinancialData` | [SDG-BR-013](business-rules.md#sdg-br-013-zero-pay-payments-included-only-when-requested) |
| [Provider address maintenance](operations/provider-address-maintenance.md) | Add or update a provider's address in Guidewire ContactManager | Caller invokes the provider address method | Provider id, `ProviderAddressRequest` | Unverified HTTP response | [SDG-BR-014](business-rules.md#sdg-br-014-provider-address-changes-are-fire-and-forget) |
| [Worker retrieval](operations/worker-retrieval.md) | Retrieve a worker, worker claims, or run a claim search | Caller invokes a `WorkerDataApiClient` method | Worker/claim id, `FindClaimsSearchCriteria` | `ClaimSummary`/`ClaimSummaries` or `null` | [SDG-BR-011](business-rules.md#sdg-br-011-non-success-responses-throw-with-status-and-content), [SDG-BR-015](business-rules.md#sdg-br-015-null-or-0-worker-id-short-circuits-lookup) |

## Process flow diagram
The following diagram visualizes the shared resolution/authentication/caching pipeline that every operation runs through before reaching a Guidewire endpoint.

```mermaid
flowchart TD
	Start([Caller invokes a client method]) --> Resolve[Resolve base URL and authenticate]
	Resolve --> Cached{"Cached GET/POST?"}
	Cached -->|Yes| Policy[Execute through Polly cache policy]
	Cached -->|No| Direct[Execute request directly]
	Policy --> GW["Call Guidewire ClaimCenter /<br>ContactManager API"]
	Direct --> GW
	GW --> Status{"Non-success status?"}
	Status -->|Yes, ensure-success call| Throw([Throw with status and content])
	Status -->|No| Return([Return deserialized response])
```

## Failure and edge-case behavior
- A non-success HTTP status on an ensure-success call (activity creation, check/recovery creation, worker retrieval) throws with the status code and response content ([SDG-BR-011](business-rules.md#sdg-br-011-non-success-responses-throw-with-status-and-content)).
- Provider address add/update does not check the response status, so a failed request is silently unverified by the caller ([SDG-BR-014](business-rules.md#sdg-br-014-provider-address-changes-are-fire-and-forget)).
- A null or `"0"` worker/claim id short-circuits to `null` without an HTTP call ([SDG-BR-015](business-rules.md#sdg-br-015-null-or-0-worker-id-short-circuits-lookup)).
- An empty bulk claim id list short-circuits to an empty result without an HTTP call ([SDG-BR-012](business-rules.md#sdg-br-012-empty-bulk-claim-request-short-circuits)).

## Related documentation
- [Index](index.md)
- [Overview](overview.md)
- [Architecture](architecture.md)
- [Dependencies](dependencies.md)
- [Configuration](configuration.md)
- [Business rules](business-rules.md)
- [API reference](api/index.md)

## Sources
- `Data/SAIF.Data.Guidewire/Clients/HttpClientBase.cs`
- `Data/SAIF.Data.Guidewire/Clients/ActivityDataApiClient.cs`
- `Data/SAIF.Data.Guidewire/Clients/ClaimDataApiClient.cs`
- `Data/SAIF.Data.Guidewire/Clients/FinancialDataApiClient.cs`
- `Data/SAIF.Data.Guidewire/Clients/ProviderDataApiClient.cs`
- `Data/SAIF.Data.Guidewire/Clients/WorkerDataApiClient.cs`