Guidewire is a comprehensive property and casualty (P&C) insurance carrier

software suite. It o ers a range of tools and solutions to streamline various aspects
of insurance operations, including:

Core Products:
• PolicyCenter: Manages the entire policy lifecycle, from policy creation and
underwriting to renewals and cancellations.
• ClaimCenter: Handles the claims process, from initial reporting to
settlement and payment.
• BillingCenter: Manages billing, invoicing, and payment processing.

Additional Modules and Services:

• Guidewire Analytics: Provides advanced analytics and reporting
capabilities to gain insights into business performance.
• Guidewire Marketplace: O ers a variety of third-party solutions and
integrations to extend the functionality of the Guidewire platform.
• Guidewire Cloud: Provides cloud-based deployment options for Guidewire
software, o ering scalability and exibility.

Key Bene ts:

• Improved E ciency: Automates many manual processes, reducing errors
and speeding up operations.
• Enhanced Customer Experience: Provides tools to improve customer
service and satisfaction.
• Increased Agility: Enables faster response to market changes and
regulatory requirements.
• Data-Driven Decision Making: Provides valuable insights through
advanced analytics.
fi
ff
ffi
ff
ff
fl
Flow-Charts
Task -> Create a screen like the attached Photo Below:

Main Steps:
step-1: Creating Entities
step-2: Creating pcf les
step-3: Linking Entity Values to pcf les
fi
fi
Step-1:Creating Entities

1. Create an Entity at the path con guration/con g/Extensions/entity, as shown in the image
below.

2. Give the name to the Entity.

fi
fi
3. Add a column for a eld that represents customerId in the CustomerDetails
database table.

4. If we add a varchar type column, we must specify its size. To do this, we

select the column that needs a column parameter and provide the column
parameter as shown below.
fi
5. Please use the “date only” type for date inputs such as Date of Birth (DOB),
Date of Joining (DOJ), From Date, and To Date.
 6. To add the address to the CustomerDetails table, we need to create another
PCF le. This is necessary because the address contains multiple elds. We
will create the address entity as a generic entity, which can be used wherever
an address is required.

7. Please add a foreign key to the AddressGeneric entity to link it to the

CustomerDetails table, as demonstrated below.
fi
fi
8. Add an Array type to the CustomerDetails entity, as a customer may have
multiple addresses. We will implement a list of addresses following the
instructions provided below.
9. Please create a TypeList for the category of Gender. This TypeList should only
accept inputs that are explicitly included within it. To ensure clarity, please
follow these instructions when creating the TypeList: include all relevant
options and limit the list to the speci ed entries.

fi
10. Add a type key to the CustomerDetails Entity and link the GenderList TypeList
to it, as shown below.
11. To link customer details to the Base Entity Account, add a foreign key in the
account entity, as shown below.
**Step 2: Creating PCF Files**
**Step 3: Linking Entity Values to PCF Files**

These steps involve the processes of creating PCF les and

establishing connections between entity values and those les.
fi
fi
Creating Pages, screens, detailed Views, List
views and card views.

1. Create a new PCF folder for better organisation, allowing us to store all
individual PCF groups in one place.
2. Create a new PCF le in the folder.

3. We are creating a new page to display all customer details. Please follow the
instructions shown below and ensure you understand the syntax as
demonstrated in the example images.
fi
4. Once the page has been created, if it shows errors, read all the displayed
errors and follow the instructions as shown in the images.

5. We need to add a variable to the page that represents the account, as it is the
root entity or table in which all customer details are saved as foreign keys.
This will allow us to access the customer details from the account entity.
Additionally, wherever you see an entry point, we should provide only the
necessary variables, excluding any that are not required. Please refer to the
attached image example for clari cation.
fi
6. Please include the entry point as demonstrated below.
7. It is necessary to provide the required mandatory values for the page
properties.

8. To link the page to a location, follow these steps:

9. Open the web page where you want to add the location.
10. Press Alt + Shift + E to open the current PCF le.
11. Double-click on the "Location" menu.
12. You should see an interface similar to the image shown below.
13. Drag the "LocationRef" from the toolbox to add a new location.
14. Finally, provide an ID and title for the location, which should be set as the
page (CustomDetails).
fi
15. The property location reference should match the signature mentioned in the
entry point on the page pcf.

16. Add a screen and follow the syntax when creating PCF for better uniformity
and organisation.
17. Please add the necessary variables to the screen, as demonstrated below.

18. Add a screen reference to the page and de ne it as stated below.

fi
19. Let’s check if the location we added to the location groups in the account is
correctly included. To do this, log in, select the account, and run the server.
We will then review the results for the created PCF on the new page for
customer details.

20. Create a detailed view for CustomerDetails, as shown below, and review the
requirements to correct the errors displayed in the image.
21. Add an input column in the Data View (DV) and include the necessary variable
in the DV.
22. Include a text input eld that accepts both string values, along with the
appropriate properties for the text input, as shown below.

23. Text input defaults to the string type, so the CustomerId, which is an Integer,
must be converted from a String to an Integer, as shown below.
fi
24. Include a date input type from the toolbox to allow users to enter dates.

25. Take typekey input to create a dynamic dropdown with a prede ned list of
values from which the user can select.
fi
26. Add a Panel Reference to link the CustomerDetailsScreen with the created
CustomerDetailsDv and provide the de nition.

27. Let’s check if the data is populated by reloading PCF. We can see that the
labels are shown, but they are not editable. To address this, we need to add
edit buttons. Let’s do that rst.
fi
fi
28. Add edit buttons from the toolbox on the screen, and ensure all components
are set to editable as true.

29. We can edit the button now. Click it and add the required details. Update, and
we can see that the data is populated on the screen.
30. The next task is to add addresses to the screen. To create a more
aesthetically pleasing view, we will arrange the list of addresses in card
format, as shown below. To add a card, take one from the toolbox and place it
on the screen. Then, assign an ID and title to the card.
31. Please create a new Customer Address Data View (CustomerAddressDV) as
outlined below.

32. Please remember the following steps:

33. As we have done before, add the required variables to the Data View (DV).
Next, create an input column, and within that column, we need to add a
ListView. In the ListView, incorporate a Row Iterator. After adding the Row
Iterator, insert the necessary rows. Finally, resolve all the errors that are shown
in the attached images below.
34. Add an ID and element name for the row iterator. The element name acts as a
variable, allowing us to access the data in the row.

35. Add a toolbar in the list view input. It helps sort data in a table on the
webpage, and we can add buttons like edit buttons and iterator buttons.
36. Please add the required text cell to the row and provide the necessary values
for it, as indicated below. Check the data type; if it is an integer, convert it
from a string to an integer, as we have done previously. If the row requires a
date cell or type key cell, you can add those from the toolbox.

37. To add iterator buttons to the toolbar, start by dragging them from the
toolbox. Next, right-click on the mouse and select the link widgets as
demonstrated below. Be sure to assign the iterator values for the iterator
buttons as shown. The row iterator ID should match the iterator value
assigned to the iterator buttons.
38. Let’s reload the page and check if we received the card and list view for the
address as expected.

39. Click edit, add a new row, provide the required data for the table, and update
it.
Creating a List-detailed view to display policies by
the Customer and allowing the addition of new
policies.

1. Create a typelist for listing available policy types for customers to select from
a dropdown, including all required elds.

2. Create a new entity for customer policies and add required elds such as type
keys and foreign keys correctly, as shown below.
fi
fi
3. Add an array of customer policies in CustomerDetails, as a customer can hold
more than one policy.

4. To display all the policies taken by the customer and to add new policies in
one place for uniformity and better visibility on the webpage, we need to
create a card. This card will contain the policy details. Please follow the
procedure below and provide the values as shown.
5. Add a list detail panel from the toolbox. It holds the value (policy type). When the
user clicks on a policy in the list, the List-detail panel displays the data of the
clicked policy.

6. Assign values to the List-detail panel using the selectionName and

selectionType values to display data.
7. Add all components required to display the data, like list view, row, row
iterator, and card panel, to display the selected policy details.

8. Please provide the mandatory values required for the card panel, as shown
below.
9. We should add text cells to display customer policies more clearly. Currently,
we only show the policy ID and customer name. Whenever a user selects a
policy from the list, detailed policy information should be displayed based on
that selection.

10. Please provide the required values for the text cells.
11. Add the necessary text cells, date cells, and type key cells to display
customer policy information.

12. We can verify the webpage by running the server or reloading the PCF les.
We will see that the new card has appeared in the customer details.
fi
Creating a popup to add new policies.

**Requirement**: When a user intends to take out a new policy, a label will be
displayed that says “Add New Policy.” Upon clicking this label, the user will
be directed to a new page where they can enter details for the policy
enrollment. This information can be submitted on the popup page.

1. Create a new PCF popup for AddNewPolicy and read the errors, resolving
them by following the procedures shown in the images below.

2. Please provide the variables and entry points for the popup. Add the screen
into the popup PCF le as demonstrated below.
fi
3. Please create a new AddNewPolicyDV with the speci ed variables as outlined
below.
fi
4. Create a new function called AddNewPolicyLV and give the required variables.
5. Add a row iterator to the list view and provide all required values to the row
iterator.

6. Add rows to the row iterator and include all necessary cells for user input to
gather the required data for the new policy.
 7. Add the list view input from the toolbox to the detailed view and assign the
de nition value that refers to the AddNewPolicyLV.pcf le.

8. Add an iterator button and link it to the row iterator as we did previously.
Below are images to show how to do it.
fi
fi
9. Please add a panel reference to the screen to link the DV to it.
10. Add edit buttons to create or update data. Ensure all components are editable
to allow edits in this popup.

11. Please add a text input eld labeled “Add New Policy.” Ensure that this eld is
set to non-editable. Additionally, provide an action value that will route the
user to a new popup page for adding a policy when they click on the label.
fi
fi
12. Reload the PCF le and check if the page displays as expected. Also, add
policies and verify if the checklist detailed view is working correctly.
fi