Guidewire Insurance Suite Analyst – Complete Guide
Impact of UI changes that are consistent with base product architecture
1. Ensure consistent look and feel
2. Simplify new user learning experience
3. Reduce development time
4. SImplify maintenance and upgrades
5. Reduce likelihood of performance impacts
5 Common UI areas of all InsuranceSuite products
Screen area, sidebar, tab bar, info bar, workspace
Sidebar
Menu links
Tab bar
Tabs, unsaved work, option menu, QuickJump box
Info bar
Icons, text descriptions
Widgets
Elements that make up the UI
Interrogate location information
ALT + SHIFT + I
Interrogate widget information
ALT + SHIFT + W
Why is it important for non-developers to understand the basics of the UI architecture and
components
So they can request changes to the UI that are consistent with the base product architecture and
communicate effectively with developers
Components of a PCF
Card, list view, button, text input, contact picker, radio button, checkbox
What do non-developers define business logic requirements for
UI functionality, rule conditions and actions, application processing flow
Two types of rules
Gosu rules and Business rules
,Gosu Rules
1. Created and maintained by devs
2. Managed in Guidewire studio
3. Written in Gosu language
4. Available for many business purposes and business objects
5. Capable of handling complex logic
Business Rules
1. Created and maintained by non-devs
2. Managed in Business rules AI screens
3. Available for limited business purposes and business objects
4. Meant for simpler logics
Approval rules
Gosu rules triggered by creation or update of a financial translation
Assignment rules
Gosu rules triggered by creation of an activity, claim, exposure, matter, service, or subrogation
Validation rules
Gosu rules triggered by creation or update of activity, claim, contact, exposure, and so on
Gosu rules consist of:
1. A business object or root object
2. A condition that evaluates to T/F
3. An action that executes if the solution is true, nothing happens if the condition is false
Non-dev Gosu responsibility
1. Determine business requirements for condition and action logic
2. Communicate requirements to devs
Dev Gosu responsibility
1. Determine correct category for rule
2. Code and test the rule logic
Business rules are used to create
1. Activities
2. Exposures
3. Reserves
Business Rule Components
1. Basic Information
, 2. Applicability criteria
3. Rule conditions
4. Rule actions
Logic that can be configured in PCFs
1. Field behavior - visibility, availability, editability
2. Screen behavior - add buttons, links, and menu items
Logic that can be configured in classes
1. New computed values or business logic
2. Non-dev document requirements for calculations or formatting changes
3. Dev writes code to implement requirement and tests it
What are Gosu classes based on?
Business objects
What are utility classes based on?
Common, reusable tasks and calculations
Integration mechanisms
1. Predefined plugins (authentication/geocoding)
2. Web services - xml based information exchange system
3. Messaging - exchanging messages between systems
4. Startable plugins - listens for requests from external systems
5. Batch processes - completes work without user input
What is the purpose of integration?
Assist with documenting requirements including data mapping between the two systems and UI changes
and communicate the requirements to devs
Name some common examples of InsuranceSuite Integrations
Address verification, User authentication
What tasks are commonly performed by non-devs for integrations?
Data mapping documents and screen mockups
a __________ defines what the business will do to realize their business objectives
Business Strategy what is ultimately the best measurement of project success?
strategic objectives are met what is the typical output of
a strategic value workshop?
strategic value map
Impact of UI changes that are consistent with base product architecture
1. Ensure consistent look and feel
2. Simplify new user learning experience
3. Reduce development time
4. SImplify maintenance and upgrades
5. Reduce likelihood of performance impacts
5 Common UI areas of all InsuranceSuite products
Screen area, sidebar, tab bar, info bar, workspace
Sidebar
Menu links
Tab bar
Tabs, unsaved work, option menu, QuickJump box
Info bar
Icons, text descriptions
Widgets
Elements that make up the UI
Interrogate location information
ALT + SHIFT + I
Interrogate widget information
ALT + SHIFT + W
Why is it important for non-developers to understand the basics of the UI architecture and
components
So they can request changes to the UI that are consistent with the base product architecture and
communicate effectively with developers
Components of a PCF
Card, list view, button, text input, contact picker, radio button, checkbox
What do non-developers define business logic requirements for
UI functionality, rule conditions and actions, application processing flow
Two types of rules
Gosu rules and Business rules
,Gosu Rules
1. Created and maintained by devs
2. Managed in Guidewire studio
3. Written in Gosu language
4. Available for many business purposes and business objects
5. Capable of handling complex logic
Business Rules
1. Created and maintained by non-devs
2. Managed in Business rules AI screens
3. Available for limited business purposes and business objects
4. Meant for simpler logics
Approval rules
Gosu rules triggered by creation or update of a financial translation
Assignment rules
Gosu rules triggered by creation of an activity, claim, exposure, matter, service, or subrogation
Validation rules
Gosu rules triggered by creation or update of activity, claim, contact, exposure, and so on
Gosu rules consist of:
1. A business object or root object
2. A condition that evaluates to T/F
3. An action that executes if the solution is true, nothing happens if the condition is false
Non-dev Gosu responsibility
1. Determine business requirements for condition and action logic
2. Communicate requirements to devs
Dev Gosu responsibility
1. Determine correct category for rule
2. Code and test the rule logic
Business rules are used to create
1. Activities
2. Exposures
3. Reserves
Business Rule Components
1. Basic Information
, 2. Applicability criteria
3. Rule conditions
4. Rule actions
Logic that can be configured in PCFs
1. Field behavior - visibility, availability, editability
2. Screen behavior - add buttons, links, and menu items
Logic that can be configured in classes
1. New computed values or business logic
2. Non-dev document requirements for calculations or formatting changes
3. Dev writes code to implement requirement and tests it
What are Gosu classes based on?
Business objects
What are utility classes based on?
Common, reusable tasks and calculations
Integration mechanisms
1. Predefined plugins (authentication/geocoding)
2. Web services - xml based information exchange system
3. Messaging - exchanging messages between systems
4. Startable plugins - listens for requests from external systems
5. Batch processes - completes work without user input
What is the purpose of integration?
Assist with documenting requirements including data mapping between the two systems and UI changes
and communicate the requirements to devs
Name some common examples of InsuranceSuite Integrations
Address verification, User authentication
What tasks are commonly performed by non-devs for integrations?
Data mapping documents and screen mockups
a __________ defines what the business will do to realize their business objectives
Business Strategy what is ultimately the best measurement of project success?
strategic objectives are met what is the typical output of
a strategic value workshop?
strategic value map
