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 Подключение к приложениям SaaS.
For more information about Lite connectors, see Классификации для коннекторов приложений SaaS.
Depending on your use case, you might need to install Data Movement Gateway to move data from SaaS applications. For more information, see Когда требуется Data Movement Gateway?.

Supported update methods

For more information, see Обзор методов обновления цели.

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 Подключение к приложениям 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	Выберите шлюз Data Movement Gateway, если этого требует текущий сценарий использования. Примечание к информации Это поле недоступно при использовании подписки Qlik Talend Cloud Starter, так как она не поддерживает Data Movement Gateway. Если используется другой уровень подписки или не требуется использовать Data Movement Gateway, выберите Нет. Для получения информации о преимуществах Data Movement Gateway и о сценариях, требующих его использования, см. раздел Qlik Data Gateway — 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

Помогла ли вам эта страница?

Если вы обнаружили какую-либо проблему на этой странице и с ее содержанием — будь то опечатка, пропущенный шаг или техническая ошибка, сообщите нам об этом, чтобы мы смогли ее исправить!

Оставьте свой отзыв здесь