Skip to content

Provider address maintenance

This operation adds or updates a provider's address in Guidewire ContactManager/AddressBook through ProviderDataApiClient, and is the one write path in this library that does not verify the response status.

Field Value
Operation ID OP-SDG-06
Trigger Caller invokes the provider address add or update method
Inputs Provider id, ProviderAddressRequest
Outputs Unverified HTTP response
Primary components ProviderDataApiClient
Entry point Data/SAIF.Data.Guidewire/Clients/ProviderDataApiClient.cs

Steps

  1. Resolve the client's base URL (ab.providerdata.api.url.v1) and Basic-auth header (cc.providerdataapi.gwcreds).

Origin: Step 1 is implemented in Resolve base URL and authenticate (SAIF.Data.Guidewire) and executed on behalf of this operation. 2. To add an address: POST provider/{id}/address with the ProviderAddressRequest payload. 3. To update an address: PUT provider/{id}/address with the ProviderAddressRequest payload. 4. The response status is not checked and the result is unused. (SDG-BR-014) - Whether this silent-failure behavior is intentional is unknown.**

Process flow

The following diagram visualizes this operation's control flow.

flowchart TD
    Start(["Caller invokes address<br>add/update method"]) --> S1["Resolve base URL and<br>Basic-auth header"]
    S1 --> Which{"Add or update?"}
    Which -->|Add| S2["POST provider/{id}/address"]
    Which -->|Update| S3["PUT provider/{id}/address"]
    S2 --> S4(["Return without checking<br>response status"])
    S3 --> S4

Failure and edge-case behavior

  • The response status of the add/update call is never inspected, so a failed request produces no observable error to the caller (SDG-BR-014).

Note: Statements marked with ** could not be confirmed; treat as unknown until verified.

Sources

  • Data/SAIF.Data.Guidewire/Clients/ProviderDataApiClient.cs
  • Data/SAIF.Data.Guidewire/Models/ProviderDataApi/ProviderAddressRequest.cs