📘 Guidewire Tools – Full Syllabus (Basic to Advanced)

1. Insurance Domain Fundamentals (Pre-requisite)

 Basics of General Insurance (P&C Insurance)

 Policy Lifecycle (Quote → Bind → Issue → Renewal → Cancel → Reinstate)

 Claims Lifecycle (FNOL → Adjudication → Settlement → Subrogation → Recovery)

 Billing lifecycle (Invoice → Payment → Write-off → Refund)

 Roles: Agent, Broker, Underwriter, Claims Adjuster

 Regulatory concepts in Insurance (compliance, risk management)

2. Guidewire Introduction

 Overview of Guidewire Software

 Guidewire Architecture (PolicyCenter, ClaimCenter, BillingCenter, Digital)

 Product Suite Components:

o PolicyCenter (PC) – Policy administration

o ClaimCenter (CC) – Claim management

o BillingCenter (BC) – Billing and payments

o DataHub & InfoCenter

o Digital Portals (Agent, Customer, Producer)

 Deployment models (On-Premise vs. Guidewire Cloud)

3. Guidewire Basics

 Guidewire Studio & IDE Overview

 Configuration vs. Integration vs. Gosu Programming

 Data Model in Guidewire (Entities, Typelists, Extensions)

 Gosu Programming Language:

o Syntax, Variables, Loops, Collections

o Classes, Interfaces, Enhancements

o Exception Handling

o Gosu Templates
  Guidewire UI Basics (PCF – Page Configuration Files)

4. Guidewire Configuration

 Understanding Configuration Layer

 Data Model Configuration:

o Entities, Entity Extensions

o Typelists, Localizations

 UI Configuration:

o PCF files

o Widgets & Panels

o Menus & Navigation

 Business Rules:

o Validation Rules

o Pre-update Rules

o Post-update Rules

o Workflow Rules

 Gosu Enhancements (adding business logic)

5. Guidewire Integration

 Introduction to Integration Layer

 Messaging:

o Events, Destinations, Message Transport

o Messaging Plugins

 Web Services:

o SOAP APIs

o REST APIs

 Integration Plugins:

o Pre-update & Post-update plugins

o Messaging Plugins

o Authentication Plugins

 Batch Processes & Schedulers

  Using JMS, MQ for integration

 File-based Integration (CSV, XML, JSON import/export)

6. Guidewire PolicyCenter (PC)

 Policy Lifecycle in detail

 Product Model:

o Lines of Business

o Coverages, Modifiers, Risk Locations

 Rating Engine Configuration

 Jobs in PolicyCenter:

o Submission

o Renewal

o Cancellation

o Rewrite

o Policy Change

 Underwriting Rules & Referrals

 Integration with BillingCenter & ClaimCenter

7. Guidewire ClaimCenter (CC)

 Claims Lifecycle in detail

 FNOL (First Notice of Loss) Setup

 Exposure, Reserve, Recovery, Subrogation

 Claim Assignment & Activities

 Workflow Configuration in ClaimCenter

 Catastrophe Management

 Claim Fraud Detection (rules and workflows)

 Integration with external systems

8. Guidewire BillingCenter (BC)

 Billing lifecycle overview

 Accounts, Invoices, Payments, Write-offs

  Billing Methods (Direct, Agency, Broker)

 Payment Instruments (Check, EFT, Credit Card)

 Integration with PolicyCenter for Premium Billing

 Delinquency & Collections

 Commission Calculation & Payments

9. Guidewire Digital Applications

 Digital Portals (Agent Portal, Customer Portal, Vendor Portal)

 Guidewire Edge API

 Guidewire Jutro (React-based design system)

 Configuring Digital Portals

 Omni-channel Experiences (Web, Mobile)

10. Guidewire Data & Analytics

 Guidewire DataHub

 Guidewire InfoCenter (Reporting & BI)

 Data Model for DataHub

 ETL Processes in Guidewire

 Integration with external Data Warehouse

 Guidewire Predictive Analytics

11. Advanced Guidewire Topics

 Guidewire Cloud Platform (GCP)

o SaaS Model

o Cloud-native tools

o CI/CD pipelines for Guidewire

 Security in Guidewire (SSO, Authentication, Authorization)

 Performance Tuning

 Logging & Monitoring

 Guidewire Upgrade & Versioning

 Agile DevOps Practices in Guidewire projects

12. Practical & Project Work

 End-to-end Implementation Project:

o Configure a new Line of Business in PolicyCenter

o Integrate PC with BC & CC

o Create custom workflows

o Build & consume REST APIs

o Configure Digital Agent Portal

 Real-time Case Studies:

o Fraud detection with rules

o Premium calculation integration

o Payment gateway integration

==================================================================================
==================================================================================

🔹 1. Insurance Domain Basics

👉 Before touching Guidewire, you must know the Insurance world, because Guidewire is 100%
domain-driven.

📝 Key Concepts

 Insurance = Risk transfer. Customers pay Premiums to protect against Losses.

 🧒 Child Level Explanation

 Insurance = A promise.

 Example: If your phone breaks tomorrow, and you bought insurance today → Company
pays you money to fix it.

 You pay small money regularly (premium) to insurance company → they help in big losses
(accident, fire, flood).

 🏠 Real Life Example

 Kanhu buys Bike Insurance.

 He pays ₹2000 every year (premium).

 After 6 months → accident → repair cost ₹50,000.

 Insurance company pays (claims settlement).

👉 So, paying small money protects you from huge loss.
  Policy Lifecycle (Real-time flow):

1. Quote – Customer requests insurance → System calculates premium.

2. Bind – Customer accepts quote & signs → Coverage becomes active.

3. Issue – Policy document is generated & sent to customer.

4. Endorsement/Change – Modify policy (e.g., add a driver to car insurance).

5. Renewal – Policy extended for another term.

6. Cancellation/Reinstatement – Terminate or reactivate policy.

🧒 Child Level Explanation

Insurance Lifecycle (Simple Version)

1. Quote → “How much do I need to pay?” (Like asking shopkeeper “price please”).

2. Bind → Customer says “Okay, I’ll buy it.”

3. Issue → Official policy document given to customer.

4. Renewal → Continue policy after expiry.

5. Cancel → Stop policy if customer doesn’t want.

6. Claim → When accident/loss happens, customer asks for money.

👉 This flow is exactly what Guidewire automates.

 Claims Lifecycle:

1. FNOL (First Notice of Loss) – Customer reports accident.

2. Adjudication – Insurance company investigates.

3. Settlement – Payment to customer or repair vendor.

4. Subrogation – Recovery from another party (e.g., accident caused by third party).

 Billing Lifecycle:

o Invoice → Payment → Refunds/Write-offs.

o Modes: Direct Billing, Agency Billing, Broker Billing.

💡 Real-Time Example

Imagine Kanhu buys Car Insurance:

 He submits an online application (PolicyCenter).

 System calculates premium ₹20,000 based on age, car model, driving history.
  Kanhu pays first installment in BillingCenter.

 After 6 months, he meets with an accident → claim is raised in ClaimCenter.

 Adjuster validates claim & approves ₹1,00,000 for repairs.

👉 This entire flow = Guidewire ecosystem.

🔹 2. Guidewire Introduction

What is Guidewire?

Guidewire is a comprehensive core insurance platform offering three major applications —

PolicyCenter, ClaimCenter, and BillingCenter. It provides flexibility with configuration and extension
using Gosu, integration with external systems (via web services, messaging), and a strong data
model. Insurance companies use it to increase efficiency, reduce claim processing time, and
provide better customer service.
OR
Or

Guidewire is a software suite used by insurance companies to manage policies, claims, and billing.
It helps automate insurance processes and reduces manual work.

👉 Imagine one giant software system made only for Insurance Companies.
Banks have Core Banking Software,
Hospitals have Hospital Management Software,
Insurance companies have Guidewire.

📝 Why Guidewire?

 Core Insurance Operations (Policy, Claims, Billing).

 Used by Top P&C companies worldwide.

 Reduces manual work by automation & rules.

 Supports cloud & digital portals for customers & agents.

Guidewire Product Suite

1. PolicyCenter (PC): Policy lifecycle management.

2. ClaimCenter (CC): Claim handling, FNOL to Settlement.

3. BillingCenter (BC): Premium invoices, payments, commissions.

4. Digital Portals: Self-service for Agents, Customers.

5. DataHub & InfoCenter: Data warehouse + BI reporting.

 🧒 Child Level Explanation

Guidewire is like a school with 3 departments:

 PolicyCenter (PC) = Admission Department (Creating & Managing Policies)

 BillingCenter (BC) = Fees Department (Invoices, Payments)

 ClaimCenter (CC) = Exam Department (Handling claims when accidents happen)

Other small departments:

 Digital Portal = Website where students/parents login

 DataHub/InfoCenter = Report card system (analytics & BI reports)

🔄 Guidewire Architecture

 Configuration Layer:

o For Business Analysts / Configurators.

o Modify data model, PCF (UI), rules, workflows.

 Integration Layer:

o For Developers.

o APIs, Plugins, Messaging, Batch processing.

 Gosu Language:

o Guidewire’s own programming language.

o Used for rules, business logic, integration.

🧒 Child Level Explanation

Guidewire Architecture (Simple Words)

 Configuration Layer → Like setting rules in a game (e.g., pass mark = 35).

 Integration Layer → Like connecting school to outside world (SMS parents, Online Fees).

 Gosu Language → Like English used in school. All rules are written in this language.

💡 Real-Time Example

 If an Underwriter wants to add a new coverage option (e.g., “Natural Disaster Coverage”),
 o Config team creates new typelist & coverage entity in PolicyCenter.

o Integration team updates rating engine service to calculate premium.

o Gosu rules check eligibility (e.g., coverage not allowed in high-risk zones).

How to run guidewiregwb studio

Automatically after sometimes below page will open

Type in URL http://localhost:8180/pc

It wiil open below page

Username :su

Password :gw
Sub-folders within configuration

These folders contain the specific types of customizations and configurations:

1. config: Contains environment-specific configuration files, such as database

connection details (datasource.groovy), server settings, logging configuration
(log4j.xml), and other parameters that differ between development, testing, and
production environments.

2. Entity Names: Used to define custom names for entities (database tables) that are
different from the default names generated by Guidewire. This is often used for
integration with existing corporate database standards.

3. Extensions: One of the most important folders. This is where developers place
custom Java code that extends the core functionality of PolicyCenter. This is the
recommended way to add new features without modifying the base product code.

4. Integration: Contains configuration files for integrating PolicyCenter with external

systems. This includes things like Web Service (SOAP/WSDL) definitions, messaging
(JMS) setups, and other external interface configurations.

5. Localizations: Holds files for translating the application into different languages and
for region-specific configurations (like date formats, address formats, etc.).

6. Messaging: Configures the internal messaging system, which allows different parts of
the application to communicate asynchronously. Defines destinations, listeners, and
publishers.

7. Metadata: Contains XML files that define the application's data model. This includes
custom fields added to standard entities (like adding a "Hobby" field to a Person
entity).

8. Page Configuration: Defines the layout, content, and behavior of the user interface
(UI) screens. Developers can hide fields, add new ones, rearrange panels, and create
new screens here.

9. Plugins: Used for adding or configuring plugins that provide additional functionality
to the Guidewire platform, such as specific authentication providers or third-party
libraries.

10. Rule Sets: Extremely important for business logic. Contains .pcf files that define
business rules using Guidewire's proprietary rule language. These rules automate
underwriting, validation, pricing, and other policy-related decisions.

11. Security: Configures user authentication, authorization, and permissions. Defines

which users and roles can access specific parts of the application and perform certain
actions.

12. Workflows: Configures the business process automation. Defines the steps,
approvals, and tasks required for processes like "New Business," "Endorsement," or
"Renewal."
Other Visible Files and Folders

o addressbook: Likely a legacy or custom folder for contact management configuration,

though standard contact info is usually handled by core entities.

o apd.model.generate.xml: A key file used during the build process. It defines how the
application's data model is generated from the underlying metadata and creates the
necessary Java classes and database scripts.

o batchprocess: Configuration for automated background jobs (batch processes), such

as generating reports, sending expiration notices, or processing payroll deductions.

o currencies: Defines the currencies supported by the application and their exchange
rates.

o datadistribution: Related to distributing data between different Guidewire

environments or systems.

o datatypes: Allows for the creation of custom data types beyond the standard ones
(e.g., Text, Integer, Date) provided by the platform.

o dbupgrade: Contains scripts and configuration for upgrading the database schema
when deploying a new version of the application or its configurations.

o fieldvalidators: Houses custom validation logic for data entered into fields on the UI,
beyond the standard validations.

o geodata: Stores data for geocoding and validating addresses.

o import: Configuration for bulk importing data into the system from external files
(e.g., CSV, XML).

o inbound: Configuration for "listening" to incoming integration messages from

external systems.

13. org: Typically contains configuration related to organizational structure, such as internal
departments, teams, or cost centers within the insurance company.

14. outbound: The counterpart to the inbound folder. This configures how PolicyCenter sends (or
"produces") messages to external systems, like sending confirmation emails or submitting
data to a reinsurance company.

15. phone: Contains configuration for telephone number formats, validation rules, and
potentially integration with telephony systems.

16. registry: Often used for a service registry or to define and manage reusable components and
their configurations.

17. reporting: Configuration files for built-in reports and integration with external reporting
tools.

18. resources: A common directory for non-code files used by the application, such as custom
images, CSS files for UI theming, or template documents (e.g., for policy documents).
19. runtimeproperties: Contains .properties files that define variables used by the application at
runtime. These can be environment-specific (e.g., URLs for external services) and are often
injected by the deployment process.

20. sampledata: Holds scripts or XML files used to populate the database with sample or test
data for development and demo environments.

21. scheduler: Configures jobs that run on a specific cron-like schedule (e.g., "run this process
every night at 2 AM").

22. search: Configuration for the application's search functionality, often integrated with Apache
Solr (as seen elsewhere in the list). Defines what data is indexed and how it can be queried.

23. servlet: Configuration for custom servlets or HTTP endpoints that extend the application's
web layer.

24. smoketests / statetests / tests / waitintests: These directories contain different types of
automated tests.
* smoketests: Basic tests to verify a new deployment starts correctly and core functions
work.
* statetests: Likely tests for state-specific insurance rules.
* tests: General unit and integration tests.
* waitintests: Likely a misspelling of integrationtests for more complex end-to-end
integration tests.

25. solr: Configuration files for Apache Solr, the search platform that PolicyCenter uses for its
advanced and quick search features. This includes schema definitions and index settings.

26. startup: Contains scripts or configuration that are executed when the application server is
starting up.

27. suite: Related to test suites, which are groups of tests that can be run together.

28. templates: Houses templates for documents, emails, or UI snippets that are dynamically
populated with data.

29. tools: Contains scripts and utilities used for development, build, and deployment tasks (e.g.,
data migration scripts, code generation tools).

30. typelists.mapping: Defines mappings for "TypeLists" (static reference data

like ReasonCode or CoverageType) to external codes or values, crucial for integration.

31. workqueue: Configures the Work Queue system, which manages the assignment and
processing of internal work items (e.g., assign this claim to an adjuster, send this
underwriting task to a queue).

32. xsd: Contains XML Schema Definition (.xsd) files. These define the structure of XML
documents used for integration, ensuring that messages sent to and received from other
systems are valid.
Key Configuration Files

 config.xml: A primary configuration file for the application, often defining high-level settings
and linking to other config files.

 config-service.yml: A YAML configuration file, typically used for modern microservice-style

configuration, possibly for a specific service within the PolicyCenter architecture.

 database-config.xml: Defines settings related to the database connection pool, transaction

management, and other persistence-layer parameters.

How to create Entity :

------------------------------
Create all required Attributes
Then search PolicyPeriod - double click shift  open a search barSearch PolicyPeriod

Select PolicyPeriod.etx-add foregin key

Then create .pcf file inside pageconfiguration/pcf/--right click
Search text input -and drag it

Click inputset - go to --required variables

add required RequiredVaribles by click + button

go to page configuration -like below fill all details

Like that we have to fills all details

Then create detailview in automobile folder

Click ok then search inputset ref- drag it to detail view

Click Dvgo to Requird varibles--add value

Then click go to pageconfiguration- call given/created inputset(automobilesInputSet(automobile))

Then now create screen inside pcf /automobiles

Search panelref --drag it to screen -go to Required Varibales-add like below

Then if go to pageconfigurationcall createdDv (automobilesDV(automob))

How to create New Submission ?

Select PersonalAuto
Click Next
🔹 3. Gosu Basics (Guidewire’s Programming Language)

👉 Think of Gosu = mix of Java + scripting flexibility.

 Statically typed (like Java).

 Object-oriented.

 Has enhancements (like C# extensions).

📝 Gosu Syntax Essentials

Variables

var customerName : String = "Kanhu"

var premiumAmount : int = 20000

Conditional

if(premiumAmount > 15000) {

print("High Premium")

} else {

print("Standard Premium")

Looping

for(i in 1..5) {
 print("Installment " + i)

Collections

var coverages = {"Fire", "Theft", "Flood"}

for(c in coverages) {

print("Coverage Included: " + c)

Classes & Methods

class Policy {

var policyNumber : String

var premium : int

function displayPolicy() {

print("Policy No: " + policyNumber + " | Premium: " + premium)

var p = new Policy()

p.policyNumber = "POL123"

p.premium = 20000

p.displayPolicy()

🔹 Enhancements (Special Gosu Feature)

👉 Used to add new behavior to existing classes (like extension methods).

Example: Adding a utility function to String

enhancement StringEnhancement : String {

function toPolicyFormat() : String {

return this.toUpperCase() + "-POLICY"

}
print("kanhu".toPolicyFormat()) // Output: KANHU-POLICY

💡 Real-Time Example (Phase 1)

 When a Customer applies for policy, we need to check eligibility.

function isEligible(age : int) : boolean {

if(age < 18) {

return false

} else {

return true

print(isEligible(16)) // false

print(isEligible(25)) // true