Guidewire ClaimCenter
Guidewire ClaimCenter manages the process of reporting, verifying, and making payments on claims against policies.
For more information about the API, see Guidewire Cloud API Documentation.
-
For more information about connecting to SaaS applications, see Connessione alle applicazioni SaaS.
-
For more information about Lite connectors, see Classificazioni per i connettori delle applicazioni SaaS.
-
Depending on your use case, you might need to install Gateway di Data Movement to move data from SaaS applications. For more information, see Quando è richiesto il Gateway di Data Movement?.
Supported update methods
For more information, see Una panoramica dei metodi di aggiornamento della destinazione.
Landing tasks:
-
Change data capture (CDC)
-
Reload and compare
Replication tasks:
-
Change data capture (CDC) using Change Tables
-
Full load
Landing data in a data lake tasks:
-
Change data capture (CDC)
-
Reload
Preparing for authentication
To access your Guidewire data, you need to authenticate the connection with your account credentials.
Creating the connection
For more information, see Connessione alle applicazioni SaaS.
- Fill in the required connection properties.
-
Provide a name for the connection in Connection name.
-
Select Open connection metadata to define metadata for the connection when it has been created.
-
Click Create.
Setting | Description |
---|---|
Data gateway |
Selezionare un Gateway di Data Movement se richiesto dal proprio caso di utilizzo. Nota informatica
Questo campo non è disponibile con la sottoscrizione a Avvio Qlik Talend Cloud, poiché non supporta il Gateway di Data Movement. Se si dispone di un altro livello di sottoscrizione e non si desidera utilizzare il Gateway di Data Movement, selezionare Nessuno. Per informazioni sui vantaggi del Gateway di Data Movement e quando è richiesto, vedere Qlik Data Gateway - Spostamento dati. |
JWT Payload | JSON Web Token payload is a set of claims. Each claim is a key/value pair that represents information that the bearer of the token claims to be true. |
Signing Algorithm | The algorithm to sign the JWT. |
Private Key | The private key to sign the JWT. |
Token URL | Token URL. |
Token Request Body | The body to send to the Token URL. Use <signed> as a variable for the signed JWT Payload.
Example: grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=<signed> |
Base URL | The base URL for this source. This is the common part of the endpoints preceding /bc/rest/. |
User Context | User context.
The contents of this field will be base64-encoded and included as GW-User-Context header. If a user context is not needed, leave the field empty. For more information, see JWTs for services with user context. |
Supported datasets
The following datasets are supported.
-
Service Requests
-
Activities
-
Batch Processes
-
Database Consistency Checks