Basics
What a End User sees and interacts with.
What is the UI?
Screens throughout the InsuranceSuite are built as <blank>
What are Page Configuration Files (PCFs)?
These two things make up the data model.
What are entities and typelists?
The core technology of application logic
What is Gosu?
The three things that can be configured for integrations.
What are:
What data is passed to the external system
What data is received from the external system
Integration timing
Exchange of data or requests to perform work between two Systems
What are Integrations?
Shortcuts for Location Info window and Widget Info window
What are Alt + Shift + I and Alt + Shift + W?
Dynamic info that is held or stored about things like a person or claim
What are entities?
3 of the 5 places where Application Logic exists.
What are Gosu Rules, Business Rules, UI, Classes, Entity Names
Tasks performed by non-developers for integration implementation.
Data mapping Documents and Screen Mockus
The organization of the data stored by the application.
What is the Data Model?
The 5 common UI areas for all InsuranceSuite Products
What are the Screen Area, Sidebar, Tab Bar, Info Bar, and Workspace?
Static info used to define details about an entity
What is a typelist?
These are what can be configured and what those options entail in Application Logic.
What is:
Validation rules- specific rules for what data is required
Assignment rules- specific criteria for assigning objects to groups and users
Function rules- calculations
These are the sources of customer value for integrations (Name 2 of 3).
What are
Access services not provided by InsuranceSuite Products
Use services that were previously used in Legacy systems
Eliminates time and expense of building in house
The behavior and functionality of the application.
What is Application Logic?
2 reasons why it's important for non-developers to understand the basics of UI architecture and components
What is request changes to the UI that are consistent with base product architecture, and so they can communicate effectively with developers?
The different types of Data Model Keys and their definitions
What are:
Typekeys - Associated with a Typelist
ArrayKeys - Associates a set of rows in a different entity with the main entity
ForeignKeys - Stores a reference to a single row in a different entity
Examples of why a non-developer should have a basic understanding of Application logic (Name 2).
What are any of the following 2:
Most project require some changes to application logic
Non-developers define reqs for UI changes
Non-devs help define reqs for Gosu rules
Non-devs help define reqs for Business Rules
3 common examples of InsuranceSuite Integrations.
Reasons for a non-developer to understand the Technology stack (Name 2).
1. Determine what data is stored and if new reqs need additional data elements
2. Know how and where Data is used
3. Communicate what data may be needed beyond base configuration
4. Determine valid values or circumstances for new data.
All 7 components of a PCF
What are Card, ListView, Button, Text Input, Contact Picker, Radio Button, and Checkbox?
These things can be configured in the Data Model (Name 2)
What is:
Info that the base application doesn't store
Values for a Typelist
Data to support regulatory requirements
These are the two types of Application logic rules, who is responsible for them, and the key differences between the two.
Gosu rules are Dev responsibilities and consist of A business object or root object , a condition that evaluates that object to true or false, and An action that executes if true, and nothing if false, and are set in GW Studio.
Business Rules are Non-Dev responsibilities and contain Basic Information (like a rule name and description), a trigger Entity and Trigger Action, Applicability Criteria, Conditions that must be met for rule, and Actions to be performed when the condition is met. Created in Admin screens.
These are 4 of the 5 integration mechanisms and what they do.
What are any 4 of the following:
Predefined Plugins - Authentication and Geocoding
Web Services - XML based info exchange system
Messaging - exchanging messages between systems
Startable plugins - listens for requests from external systems
Batch Processes - Completes work without user input