INSURANCE SUITE DEVELOPER FUNDAMENTALS COMPREHENSIVE EXAM SCRIPT
COMPLETE QUESTIONS VERIFIED SOLUTIONS
● Custom field name suffix. Answer: Every custom field name in an
extension must end with "_Ext" to protect Guidewire upgrade tooling
and ensure a clean, non-colliding namespace for customer changes.
● Array vs Foreign-key relationship. Answer: Use an array when one
entity must point to many instances of another (1-to-many), but you do
not want a join table; for many-to-many, create a versionable link entity
instead.
● Super-type data format in database. Answer: Stores all subtype fields
in a single denormalised table and adds a typelist column indicating the
subtype row.
● Referencing subtype-specific field in Gosu. Answer: Cast first, then
access: `(someContact as ABPerson).TaxID`.
● Three container tiers in PCF hierarchy. Answer: Primary (Detail View,
List View, Input Set) → Secondary (Card View, List Detail View) →
Top-level (Screen).
, ● Location types that can directly contain Screens. Answer: **Page**,
**Wizard**, **Worksheet**, **Popup**. (Location Groups own Pages;
Forwards & ExitPoints redirect.)
● Best practice for making a List View editable. Answer: 1) Toolbar
with Edit/Update/Cancel. 2) Iterator Buttons widget wired via `toAdd /
toRemove`. 3) RowIterator `editable="true"`.
● validationExpression. Answer: Fires client-side when the widget loses
focus.
● requestValidationExpression. Answer: Evaluates server-side on every
request, common for submissions.
● postOnChange. Answer: Set to true to trigger an AJAX call and
rerender the UI when a drop-down changes.
● Dynamic widget properties. Answer: Examples include visible and
editable.
● Static widget properties. Answer: Examples include id and valueType.
● isEmpty(). Answer: Issues SELECT 1 ... FETCH FIRST 1 ROW,
which is cheaper than using .Count.
COMPLETE QUESTIONS VERIFIED SOLUTIONS
● Custom field name suffix. Answer: Every custom field name in an
extension must end with "_Ext" to protect Guidewire upgrade tooling
and ensure a clean, non-colliding namespace for customer changes.
● Array vs Foreign-key relationship. Answer: Use an array when one
entity must point to many instances of another (1-to-many), but you do
not want a join table; for many-to-many, create a versionable link entity
instead.
● Super-type data format in database. Answer: Stores all subtype fields
in a single denormalised table and adds a typelist column indicating the
subtype row.
● Referencing subtype-specific field in Gosu. Answer: Cast first, then
access: `(someContact as ABPerson).TaxID`.
● Three container tiers in PCF hierarchy. Answer: Primary (Detail View,
List View, Input Set) → Secondary (Card View, List Detail View) →
Top-level (Screen).
, ● Location types that can directly contain Screens. Answer: **Page**,
**Wizard**, **Worksheet**, **Popup**. (Location Groups own Pages;
Forwards & ExitPoints redirect.)
● Best practice for making a List View editable. Answer: 1) Toolbar
with Edit/Update/Cancel. 2) Iterator Buttons widget wired via `toAdd /
toRemove`. 3) RowIterator `editable="true"`.
● validationExpression. Answer: Fires client-side when the widget loses
focus.
● requestValidationExpression. Answer: Evaluates server-side on every
request, common for submissions.
● postOnChange. Answer: Set to true to trigger an AJAX call and
rerender the UI when a drop-down changes.
● Dynamic widget properties. Answer: Examples include visible and
editable.
● Static widget properties. Answer: Examples include id and valueType.
● isEmpty(). Answer: Issues SELECT 1 ... FETCH FIRST 1 ROW,
which is cheaper than using .Count.
