Guidewire Insurance Suite Analyst Exam (Study Guide) 2024/2025 Questions with 100% Correc, Exams of Business Administration

Download Guidewire Insurance Suite Analyst Exam (Study Guide) 2024/2025 Questions with 100% Correc and more Exams Business Administration in PDF only on Docsity!

Guidewire Insurance Suite Analyst Exam (Study Guide)

2024/2025 Questions with 100% Correct Verified

Answers Graded

Gosu Core programming technology Data Model The organization of the data stored by the application User Interface What the user sees and interacts with Application Logic The behavior and functionality of the application Page Configuration Formats Changes to the UI are made in these components Data Model Formula Entities + Typelists Entities Dynamic information which is held or stored about things such as a person or a claim Typelists static information used to define details about an entity such as gender, type of claimant, or severity of injury Rules Validation, assignment, approval, routing and so on

Classes Functions that return calculated values, set values in fields, and so on Functions ex. Calculate the number of days since a loss date Integration Mechanisms Exchange of data or requests to perform work between two systems Common Integration Systems exs. Authentication system, documents management system, address book application system Fields Atomic data stored about the entity (non-restricted values) Type Keys A single reference to a value in a typelist Array Keys A set of single references to another entity Foreign Keys A single reference to the id of another entity Fields ex. Description, ClaimReportDate, WeatherRelated Type Keys ex. AccidentType, ClaimSource, LossType Array Keys ex. AllAddresses, SecondaryAddresses Foreign Keys ex.

Catastrophe, AssignedGroup Data Dictionary Shows definitions of entities and typelists Typelist Field Predefined set of possible values Typekey Field Associated with a specific typelist 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
6. Created and maintained by non-devs
7. Managed in Business rules AI screens
8. Available for limited business purposes and business objects
9. 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
4. Determine business requirements for condition and action logic
5. Communicate requirements to devs Dev Gosu responsibility
6. Determine correct category for rule
7. Code and test the rule logic Business rules are used to create
8. Activities
9. Exposures
10. Reserves Business Rule Components
11. Basic Information
12. Applicability criteria
13. Rule conditions
14. Rule actions Logic that can be configured in PCFs
15. Field behavior - visibility, availability, editability
16. 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
4. Predefined plugins (authentication/geocoding)
5. Web services - xml based information exchange system
6. Messaging - exchanging messages between systems
7. Startable plugins - listens for requests from external systems
8. 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