Guidewire PolicyCenter integrations — P&C insurer
- Period
- Dec 2024 – Present
- Sector
- Insurance (P&C)
- Engagement
- GFT Technologies engagement
Role Full-Stack Developer — Guidewire Integration Specialist
REST and SOAP connectors built in Integration Gateway between PolicyCenter and payment, CRM and document-management systems, across the motor policy lifecycle.
Client engagement: the code and implementation details are proprietary. This case study describes the architecture and technical decisions without exposing confidential information.
Context
Second phase of a transformation programme built on Guidewire PolicyCenter. The core insurance platform has to talk to external systems — payment platforms, CRM, document management — at every step of a motor policy lifecycle.
Challenge
Keep integration logic out of the core application: capture business events (issuance, endorsement, cancellation) without coupling PolicyCenter to downstream systems, guarantee faithful bidirectional mapping between heterogeneous data models, and make functional errors visible to business teams instead of silent in the logs.
Solution
Designed and maintained REST and SOAP connectors in Integration Gateway, fed by App Events capture and JMS messaging, with Apache Camel routes and bidirectional mapping. On the PolicyCenter side, activity patterns (XML) automatically create follow-up tasks when an integration fails functionally — the error becomes an assigned action, not a log line.
Outcome
The motor policy lifecycle flows are covered end to end, and integration failures reach business teams as traceable tasks. Alongside delivery: flow modelling with business analysts, downstream impact analysis, QA test datasets, Camel route debugging, integration unit tests and code reviews.
Highlights
- REST and SOAP connectors built in Integration Gateway towards payment, CRM and document management
- App Events capture on policy issuance, endorsement and cancellation
- JMS messaging and Apache Camel routes with bidirectional mapping
- PolicyCenter activity patterns (XML) turning integration errors into follow-up tasks
- Business-analyst support: integration flow modelling and downstream impact analysis
- QA support: test datasets, scenario walkthroughs, Integration Gateway log analysis