Creating UI Pages and Widgets in Guidewire

 Guidewire provides a robust development environment for building insurance applications. Its UI layer, built using Gosu, PCF (Page Configuration Files), and widgets, enables developers to create responsive, efficient, and intuitive interfaces. Whether you’re customizing ClaimCenter, PolicyCenter, or BillingCenter, understanding how to create UI pages and widgets is key to delivering a user-friendly experience.


Understanding PCF (Page Configuration Files)

PCF files are XML-based and define the structure and components of UI pages in Guidewire applications. Each PCF file corresponds to a specific screen or panel in the user interface.

Located in: resources/config/web/pcf

Editable using: Guidewire Studio or any XML editor

Tied to entities and data models via UI metadata


Creating a New UI Page

To create a new page:

  • Open Guidewire Studio and navigate to the PageConfiguration tab.
  • Right-click the PCF folder (e.g., web/pcf/claim) and select New > PCF File.
  • Name your page (e.g., MyCustomPage.pcf) and specify the page type (Screen, PanelSet, Popup).
  • Use the visual designer or XML view to add layout containers, input fields, and widgets.


Adding Widgets to UI Pages

Widgets are reusable UI components like input fields, buttons, checkboxes, lists, etc.


Common Widgets:

<TextInput> – for text entry

<SelectInput> – dropdown selection

<Button> – for actions like Save or Submit

<ListView> – to display tabular data

<Checkbox> – for boolean input


Example:

<TextInput id="MyTextInput" label="Enter Name:" value="MyEntity.Name"/>

<Button id="SaveButton" label="Save" action="MySaveAction"/>

Each widget is tied to a data field from an entity or a variable and can be configured with properties like:

  • value
  • label
  • action
  • disabled
  • visible


Using PanelSets and Tabs

PanelSets help in structuring complex pages with multiple sections. You can use TabBar and DetailViewPanel for organizing data in a user-friendly layout.

<PanelRef panel="MyTabPanel" />

<TabBar>

  <Tab label="Details" panel="DetailsPanel" />

  <Tab label="Documents" panel="DocsPanel" />

</TabBar>


Best Practices

  • Use existing templates as references to maintain consistency.
  • Follow naming conventions for widgets and IDs.
  • Use permissions and visibility expressions to control access.
  • Test UI pages in different modes (view, edit, create) and roles.


Conclusion

Creating UI pages and widgets in Guidewire requires a good grasp of PCF structures, widget configuration, and data binding. With the right approach, you can build powerful, user-friendly interfaces that streamline insurance processes and improve user productivity across Guidewire applications.

Learn Guidewire Training in Hyderabad

Read More:

Creating Entities and Typelists in Guidewire

Guidewire Studio IDE: Tools and Usage

Building a Quote-to-Issue Flow in PolicyCenter

Guidewire Plugin Development: A Step-by-Step Guide

Visit our IHub Talent Training Institute

Get Direction

 

Comments

Post a Comment

Popular posts from this blog

Tosca Installation and Environment Setup

 Tosca by Tricentis is a powerful tool for model-based test automation. It supports testing across various technologies like web, mobile, API, and enterprise applications. Setting up Tosca correctly is the first step towards building reliable and scalable test cases. In this blog, we’ll guide you through the Tosca installation process and the essential environment setup required to get started. System Requirements Before installing Tosca, ensure your system meets the following minimum requirements: Operating System: Windows 10 (64-bit) or later RAM: 8 GB (16 GB recommended) Disk Space: At least 10 GB free space .NET Framework: Version 4.7.2 or higher Microsoft SQL Server: Express, Standard, or Enterprise (for shared repositories) Downloading Tosca Visit the Tricentis Support Portal or Tricentis Official Website. Log in or create an account. Navigate to the Downloads section and select Tosca Testsuite. Choose the latest stable version and download the installer (typically in .exe fo...
Read more

Tosca Reporting: Standard and Custom Reports

Tosca by Tricentis offers powerful test automation capabilities, and one of its key strengths lies in its reporting features. Effective reporting helps QA teams analyze results, track test coverage, and communicate findings with stakeholders. Tosca provides both Standard Reports for out-of-the-box insights and Custom Reports for tailored analysis. ✅ Standard Reports in Tosca Standard Reports are built-in and generated automatically during test execution. These reports provide essential insights into test case execution status, errors, and execution logs. 🔹 Key Types of Standard Reports: Execution Logs Shows step-by-step execution of each test case Includes Passed/Failed status, actual vs. expected values, and screenshots (if enabled) ExecutionLists Overview Summarizes the status of all test cases in an execution list Categorized as Passed, Failed, or Not Executed Log Info Details Provides detailed logs with timestamps, test steps, test data used, and error messages Dashboard View (in ...
Read more

Creating Entities and Typelists in Guidewire

 Guidewire is a leading platform for core insurance operations, including policy administration, claims management, and billing. In Guidewire, entities and typelists are essential components used to define the data model and control business logic. Whether you're customizing ClaimCenter, PolicyCenter, or BillingCenter, understanding how to create and use these elements is key. ✅ What Are Entities and Typelists? Entities represent database tables and define the structure of business objects (like Policy, Claim, Contact). Typelists define enumerated values (like policy statuses, claim types, or user roles) and are used in drop-down fields and business rules. 🧱 Creating Entities in Guidewire 1. Define the Entity in Data Model XML Entities are defined in the XML files located in: config\extensions\entity\YourEntityName.etx Example: Creating a Custom Entity VehicleInfo <entity   name="VehicleInfo"   entityExtends="EffDated"   tableName="vehicle_info"   ...
Read more