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 Conexión a aplicaciones SaaS.
For more information about Lite connectors, see Clasificaciones para conectores de aplicaciones SaaS.
Depending on your use case, you might need to install Pasarela Data Movement to move data from SaaS applications. For more information, see ¿Cuándo es obligatorio Pasarela Data Movement?.

Supported update methods

For more information, see Una vista general de los métodos de actualización del destino.

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.

Make sure that the account you use has read access to the tables you want to fetch.

Creating the connection

For more information, see Conexión a aplicaciones 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.

Connection settings
Setting	Description
Data gateway	Seleccione una Pasarela Data Movement si su caso de uso así lo requiere. Nota informativa Este campo no está disponible con la suscripción Qlik Talend Cloud Starter porque Pasarela Data Movement no se admite. Si tiene otro nivel de suscripción y no desea utilizar Pasarela Data Movement, seleccione Ninguna. Para obtener información sobre las ventajas de Pasarela Data Movement y los casos de uso que lo requieren, consulte Pasarela de datos de Qlik - Data Movement.
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

¿Esta página le ha sido útil?

No dude en indicarnos en qué podemos mejorar si encuentra algún problema en esta página o su contenido, como, por ejemplo, errores tipográficos, pasos que falta o errores técnicos.

Deje aquí sus comentarios