INSURANCESUITE ANALYST FUNDAMENTALS EXAM QUIZZES & ANSwers 2024

What is the core programming language for Guidewire?

Gosu

What does application logic control?

Detail behavior of the application

Code is used in....

Rules, Classes, Extensions

What can be configured?

Validation, Assignment, Function

Rules

Validation, assignment, approval routing

Classes

Functions that return calculated values & set values in fields

Extensions

Added functionality to entities

Validation

Specific rules for what data is required

Assignments

Specific criteria for assigning objects to groups and users

Function

Calculate the number of days since a loss date

How is configuration done by developers?

Through Guidewire Studio

What 5 common UI areas do all InsuranceSuite products share?

Screen Area, Sidebar, Tab Bar, Info Bar, Workspace

What does having a common UI architecture ensure?

Familiar look and feel & reduced training time

What area displays the business information?

Screen Area

What area provides navigational menu links?

Sidebar Area

QuickJump Box

Provides a fast way to navigate within the GW application

What determines the Tab Bar that a user sees?

User's permission

What the purpose Info Bar?

Shows summary information relevant to the user's currently selected item (combo of text and icons)

What is the Workspace used for?

Display info while keeping the Screen Area visible to display additional info

What is used to build the GW UI?

Widgets

Widgets

- Display app info to the user/render info into displayable format

- Support data entry

- Organize data into logical groupings

Different Functions/Types of Widgets

Data entry, Actions, Organize info, Containers

ListViews

Widget used to display a list of related data

How to find location info? (Keyboard shortcut)

ALT + SHIFT + I (Location Info window)

Why would you what to find the Location info?

To help the developers identify the file they will need to make changes to in order to satisfy Business requirements

How to find widget info? (Keyboard Shortcut)

ALT + SHIFT + W (Widget Inspector)

What is a developer's role in configuration/project implementation team?

To configure IS products to satisfy the customer's reqs by using the GW Studio tool

Why is it important for non-developers to understand the basics of the UI architecture and components?

So that they can request changes to the UI that are consistent with the base product architecture and communicate effectively with developers

Components of a PCF (name 3)

Card, Listview, Button, Text Input, Contact Picker, Radio button, Checkbox

End-to-End testing

Complete scripted testing of the day- to- day future-state business process.

Performance Testing

Confirm system performance under normal and high load. Done to test if the system can handle the expected load.

User Acceptance Testing (UAT)

Testing for End Users with real world scenarios.

What phases are User stories used in?

Pre-inception, Inception, Sprint 0, and Development

Story Elaboration

Conversations that occur between the users and the project team during the Inception to ensure that all requirements are understood.

What does INVEST stand for?

Well written user stories are Independent, Negotiable, Valuable, Estimable, small, and testable

Performance testing is done in which phase?

Development & Stabilization

Who are the three amigos?

Business Analyst, Developers, and Quality Analysts

What is the duration of sprint 0

1-4 weeks

What is the IS data model?

A collection of typelists and entities that organize and store IS data

Why is it important for a non-developer to understand the IS data model?

to make better decisions about configuration changes/how & where data can be stored

Entity

A set of fields/attributes related to an object and store/retrieve that data

(ie. attributes for Claims = claim description and loss date)

Typelist

droplist; A set of code/value pairs/typecodes that are valid for a field

What 2 main components make up the data model?

Entities and Typelists

Fields

Store atomic data about entity (i.e.. claim report date or WeatherRelated claim) (dates)

Type keys

Reference a single acceptable value in a typelist (i.e.. accident type or claim source) (dropdowns)

Array keys

a set of references to another entity (multiple rows) (i.e.. addresses or incidents) (lists)

Foreign keys

a single reference to another entity (single row) (i.e. catastrophe or assigned group) (codes/ account numbers)

Data field

Where a single value is stored; can be physically in the database or virtually created by Gosu code

Foreign Key Field

Stores a reference to a related object in the data model; unidirectional relationship ie. AssignedUser in Claim IS)

Array

Associates a set of related rows with the main entity; multidirectional relationship

What are the 3 main sections of the data dictionary?

Data Entities, Typelists and All Fields

What are the 2 specialized versions of Data Entities? And who are they used by?

- Database and Migration view

- Used by the implementation team

What does the Data Dictionary show?

- The meaning of a field

- What fields are available

- Where the field is used in GW UI

Type filter

Creates a subset of values valid for the type of claim; filter within type key within type list

What can an array key used for in ClaimCenter?

Linking several exposures with an incident (lost/damaged things), then linking several incidents with a claim

What is the purpose of the Data Dictionary?

To show the data elements that belong to entities and typelists

What are some relationships between entities?

Foreign Keys, Array Keys, and Type Keys

Application logic

Code written in Gosu that determines behavior and functionality within GW IS

When identifying new business logic requirements, what is important for non-developers to remember?

Business requirements/changes to the app logic should add value to the company implementation

How do requirements add value?

- Ensure compliance with fed or state regulations/reg requirements

- Maintain competitive advantage

- Improve business processes

What do non-developers define business reqs for?

- UI Functionality

- Rule conditions and actions

- App processing flow

Where is Gosu used?

-Gosu Rules

-Business Rules

-User Interface

-Classes

-Entity Names

What are the 2 types of rules?

Gosu Rules and Business Rules

Gosu Rules

Created in GW studio by developers; capable of handling more complex logic and cover a wider variety of business processes/objects; works on a specific business object/entity

Business Rules

Created in Business Rules admin screens by non-developers; meant for simpler logic

What are 3 categories that Gosu rules can be organized in?

- Approval

- Assignment

- Validation

Approval Rules

Triggered by creation or update of a financial transaction

Assignment Rules

Triggered by creation of business objects that can be assigned (ie. claims, activities, exposures)

Validation Rules

Triggered by creation or update of activity, claim, contact, exposure; different from assignment rules because it can be triggered by an update and even wider variety of business objects

What does a Gosu rule consist of?

A condition that is either true or false, and an action that is executed

Gosu Rules: Non-developer responsibilities

- Determine business reqs for condition and action logic

- Communicate requirements to developers

Gosu Rules: Developer responsibilities

- Determine correct category for rule

- Code and test the rule logic

How do non-developers use business rules?

Used to create Activities, Exposures, and Reserves

What are the 4 components of a Business rule?

-Basic info

-Applicability criteria

-Rule conditions

-Actions

Applicability criteria

Filter to limit the trigger entities this rule applies to; used to get more specific on what entities a BA wants this rule to apply to

What triggers an Exposure rule?

The creation of an incident

What triggers a Reserve rule?

The creation of an exposure

What are 3 things an activity rule can generate?

-new activity for the claim's workplan

-generate a history event

-set the value of a field

What logic can be configured in PCFs?

Simple logic can be used in the UI configuration of field and screen behavior; Screen behavior = Button, links, and menu items to change the screen and navigate the app

What logic can be configured in Classes? and what are the responsibilities of each role?

-New computed values or business logic

-Non-developer: documents reqs for calculations or formatting changes

-Developer: writes code, determines if the code applies to one or multiple objects, implements the req and tests it

How are Gosu classes determined?

They are based on Business objects

Utility classes

handle common, reusable tasks and calculations

How do GW apps use entity names?

To represent a business object as a text string

Entity names

Text displayed in the UI for business objects

Can entity names be modified?

Yes, if the insurance carrier wants to include different info. ONLY developers can create and modify entity names

How is logic configured into an entity name?

two or more information/logic fields can be combined to create an entity name (ie. order number of claim + los party + exposure type + claimant name)

How do you determine app logic changes?

-review the fields on each screen and identify any fields to be added or removed (Screen content)

-look at how a user would navigate through the screen(s) and see if you need to change anything (Screen navigation)

-consider what validations are needed when entering data and if a user should be warned when data is missing (Field Validation)

-review options for assigning work to users and document the reqs (Assignment options)

-when claims and exposures are created, are there activities that should be created (Initial workplan)

-should exposures be created when loss details are captured (Exposure creation)

-does sufficient history exist to create reserves for new exposures (Initial reserves)

Provide an example of why a non-developer should have a basic understanding of app logic?

- Most projects require some changes to the app logic

- Non-developers define reqs for Ui changes

- Non-developers help define reqs for Gosu rules

- Non-developers define reqs for business rules

Name 2 places where app logic exists

- Gosu rules

- Business rules

- UI

- Classes

- Entity names

What are the 2 types of rules and who is responsible for developing each?

- Business Rules; non-developers

- Gosu Rules; developers

Integration

The exchange of data or requests to perform work between two systems

What does integration allow insurers to do?

Integration allows insurers to continue using services used with their legacy systems with IS products while adding new capabilities

What is the value of Integration?

-Benefit from external applications maintained by industry specialists

-Outsource common tasks

-Eliminate time and expense of building in-house

What are common GW Integration points?

-Authentication systems

-Doc management systems

-Address book application systems

Why understand Integration?

-To assist with documenting reqs and communicating them to developers (Data mapping between systems)

-Integ. logic determines how IS apps communicate with external systems (written in Gosu)

-Timing

-Understanding what triggers the integration and triggers in general

IS Integration Mechanisms

-Predefined plugins

-Web Services

-Messaging

-Startable plugins

-Batch processes

Predefined plugins

Gosu classes that a GW app invokes to perform an action or calculate a result at a specific time in its business logic

Web Services

Define request-and-response APIs that let you call an API on a remote computer or get info from an remote computer; XML-based information exchange system; GW can both publish and consume internet web services

Messaging

GW app is programmed to send a message to an external system when an important event occurs. (ie. A change triggers and event that executes Gosu code)

External system only receives messages for successful events and sends an acknowledgement that the message was received in response

Startable plugins

Custom code that begins executing during server startup; not evoked by another code but can be stopped and started as required; listens for requests from an external system