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 資料移動閘道 to move data from SaaS applications. For more information, see 何時需要 資料移動閘道？.
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.
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.
| Setting | Description |
|---|---|
| Data gateway |
如您的使用情況有需要，選取 資料移動閘道。 資訊備註
此欄位無法用於 Qlik Talend Cloud 啟動器 訂閱，因為不支援 資料移動閘道。若您有另一個訂閱層級且不想使用 資料移動閘道，選取無。 如需關於 資料移動閘道 福利的資訊以及需要此項的使用案例，請參閱 Qlik 資料閘道 - 資料移動。 |
| 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