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 連接器分類.
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？.

Feature/Functionality	Support details
Supported Qlik Talend Data Integration projects	Data pipeline projects and Replication projects.
目標更新方法	Landing tasks: Change data capture (CDC) using Change Tables Reload and compare Replication tasks: Full load Change data capture (CDC) using Change Tables Change data capture (CDC). Using this method, changes are directly applied to the target. Landing data in a data lake tasks: Change data capture (CDC) using Change Tables Reload
管理中繼資料	Manual metadata generation is required.
結構描述演進	Not supported
Replication of LOB columns (NCLOB, CLOB, and BLOB)	Determined by the task type: Landing tasks: Supports limited LOB size only Replication tasks: Supports unlimited LOB
Scheduled CDC	Only required when accessing data sources without Data Movement gateway.
Notifications	Fully supported 設定變更進行時的通知
Monitoring	Fully supported 監控個別資料任務
Automatic denesting of JSON column payloads	Fully supported

Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

確認您使用的帳戶可讀取您要擷取的表格。

如需詳細資訊，請參閱連線到 SaaS 應用程式。

Connection settings
Setting	Description
Data gateway	如您的使用情況有需要，選取 Data Movement gateway。資訊備註此欄位無法用於 Qlik Talend Cloud 啟動器訂閱，因為不支援 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.

The following datasets are supported.

若您發現此頁面或其內容有任何問題——錯字、遺漏步驟或技術錯誤——請告知我們！