InsuranceSuite Developer Fundamentals Test Questions And Answers Verified 100% Correct

InsuranceSuite Developer Fundamentals Test Questions And Answers Verified 100% Correct How to Reference a Field of a Subtype - ANSWER -(object as subtype).field Define a Primary Container for Reusability - ANSWER -Define the container in its own file, and reference this file using a PanelRef List View Input Widget - ANSWER -Causes list view to behave as atomic widgets, allowing them to be stored in primary containers Iterator Buttons Widget - ANSWER -Contains add and remove buttons, which call the toAdd and toRemove functions of the row iterator Entity (display ) name - ANSWER -defines a function which returns a UI friendly name for the entity, use when field is not editable. accessible with entity.DisplayName Set Default Filter (List View) - ANSWER -use a hidden toolbar filter, selectOnEnter: true, visible: false Edit Buttons Widget - ANSWER -Usually contained in toolbar. Buttons: Edit: enters edit mode Update: commits changes Cancel: discards changes Row Iterator Widget - ANSWER -Takes an array or query results, can apply functions to this input View Entities use - ANSWER -To enhance performance and remove dot notation from column values. View Entities: Retrieve Items outside of entity - ANSWER -Extend the view entity with new fields for these items Entry Point - ANSWER -used by a widget to navigate to a location group, must define what object(s) the entry point takes in (can be none) Post on Change - ANSWER -Used for dynamic behavior, triggers onChange function when field is changed, as long as disablePostOnEnter evaluates to false Dynamic Behavior vs Dynamic Property - ANSWER -Dynamic behavior affects the UI while a change is being made, Dynamic property does not affect UI until after change is committed Property Types - ANSWER -Static and Dynamic (Immutable and Mutable) Dynamic Widget Properties - ANSWER -Label, Available, Editable, Required, Visible Modes - ANSWER -Set of PCF files, one is selected based on some conditional. Default is selected if no conditionals evaluate to true. Field-Level Validation Parts - ANSWER -Regular Expression (regex): defines the pattern the input must follow Input Mask (optional): displays watermark and guides user input Validation Expression - ANSWER -Logical Gosu expression associated with an atomic widget, if expression returns null (no error) field is saved Request Validation Expression - ANSWER -Like validation expression, but only updates on request to server (usually submission) Field-Level Validation: Implementation in UI vs Database - ANSWER -UI: Can change between PCFs, does not require round trip to DB to validate DB: Allows for custom error message, avoids retyping the same code Gosu Variable Declaration - ANSWER -var name : type = expression Gosu Array Declaration - ANSWER -var arr = new int[3], var arr = new int[] {1,2,3} hasMatch(condition) - ANSWER -determines if any element in the array matches condition countWhere(condition) - ANSWER -returns the number of elements that match the given condition firstWhere(condition) - ANSWER -retrieves the first element which matches condition where(condition) - ANSWER -returns an array which consists of all members that match the given condition Entity Enhancement - ANSWER -Add additional method onto Guidewire entity Gosu Rule - ANSWER -Gosu class with file extension .gr, executes an action if the condition evaluates to true. Rule Set - ANSWER -Logical grouping of rules specific to one business function, has one root entity Rule Set Category - ANSWER -Collection of rule sets, defines the type of event that will cause rule sets to be executed Child Rules - ANSWER -Rules can have child rules, which execute (evaluate condition) if the parent rule evaluates to true Ruleset Types - ANSWER -Validation: "execute all", all rules executed to ensure full validation of data Assignment: "exit after first action", rules evaluated until one successfully assigns a task