Guidewire Best Prac ces Exam study guide With
complete solu on RATED A+ 2025/2026 NEW
Avoid using internal path for your classes - Ans com.guidewire.* should be avoided. These can
always be poten ally changed or replaced during an upgrade.
When referencing typecodes, use the sta c property on the typelist class instead of the string
representa on - Ans Use TC_TYPECODE instead of "typecode", example:
LossCause.TC_REAREND instead of "rearend"
Use the text for logical operators instead of the symbols - Ans Use "and","or", and "not"
instead of "&&", "||", and "!"
Code placement - Ans 1) Avoid placing code within the CODE tab of a PCF. Create a UI helper
class instead
2) Avoid extending en ty enhancements with code suppor ng UI opera ons
Avoid using deprecated classes and methods - Ans Guidewire will eventually remove
deprecated classes and methods.
Turn on and run Studio Inspec ons - Ans These analyze configura on resources
Use whitespace effec vely - Ans Add spaces around operators
Do not add spaces between parentheses and operators
Indent logical blocks of code by two spaces only
Add a blank line a;er code blocks
,Add two blank lines a;er methods, including the last method in a class
Comments and Annota ons - Ans Document new classes and func ons with Javadoc-style
comments
Use single-line comments within func ons and methods when you need to clarify the intent of
the code
Use GoseDoc annota ons which are included when genera ng GosuDoc
"Upgrade-Safe" naming conven ons: Add the suffix _Ext to - Ans Columns added to exis ng
en es
Typecodes added to exis ng typelists
The name of custom en es
The name of custom typelists
New PCF files
Script parameters
Package naming conven ons - Ans Use the format
customer.applica on.featurecategory.feature
Customer - company name abbrevia on
Applica on- InsuranceSuite applica on code (pc, bc, cc, suite)
Feature Category - major feature (delinquency, configura on, integra on)
Feature - feature (ra ng, catastrophe, authen ca on)
Example: si.suite.integra on.authen ca on
Class naming conven ons - Ans Use UpperCamelCase
Do not add _Ext to classes within customer package spaces
, Func on naming conven ons - Ans Use lowerCamelCase
Use a verb that describes that the func on is doing i.e. verifyAddress
Do not add _Ext suffix to private func ons or enhancements in customer package spaces
Variable naming conven ons - Ans Member variable names use lowerCamelCase with a
leading underscore i.e. _pluginCallbackHandler
Local variable names use lowerCamelCase short names that describe the purpose i.e.
latestPolicyRevision
Display key naming conven ons - Ans Add suffix _Ext too all new display keys
Do not modify automa cally generated display keys
Logging is - Ans The process of recording applica on ac ons and state to a secondary interface
Logging is used for - Ans Applica on maintenance and troubleshoo ng
Crea ng sta s cs rela ng to applica on usage
Audi ng by capturing significant events
Typical events to log are - Ans Success / Failure - a transac on or ac on has succeeded or failed
Recovery - a system went down or connec on failed, retried, and recovered
Iden fica on - any large func onal areas such as integra on, ra ng, reinsurance, and rules
Logging components - Logger - Ans has a category and level, sends content to an Appender
Logging components - Appender - Ans is an output des na on (server console or rolling file)
Logging components - Layout - Ans defines the format of the content sent to an appender
complete solu on RATED A+ 2025/2026 NEW
Avoid using internal path for your classes - Ans com.guidewire.* should be avoided. These can
always be poten ally changed or replaced during an upgrade.
When referencing typecodes, use the sta c property on the typelist class instead of the string
representa on - Ans Use TC_TYPECODE instead of "typecode", example:
LossCause.TC_REAREND instead of "rearend"
Use the text for logical operators instead of the symbols - Ans Use "and","or", and "not"
instead of "&&", "||", and "!"
Code placement - Ans 1) Avoid placing code within the CODE tab of a PCF. Create a UI helper
class instead
2) Avoid extending en ty enhancements with code suppor ng UI opera ons
Avoid using deprecated classes and methods - Ans Guidewire will eventually remove
deprecated classes and methods.
Turn on and run Studio Inspec ons - Ans These analyze configura on resources
Use whitespace effec vely - Ans Add spaces around operators
Do not add spaces between parentheses and operators
Indent logical blocks of code by two spaces only
Add a blank line a;er code blocks
,Add two blank lines a;er methods, including the last method in a class
Comments and Annota ons - Ans Document new classes and func ons with Javadoc-style
comments
Use single-line comments within func ons and methods when you need to clarify the intent of
the code
Use GoseDoc annota ons which are included when genera ng GosuDoc
"Upgrade-Safe" naming conven ons: Add the suffix _Ext to - Ans Columns added to exis ng
en es
Typecodes added to exis ng typelists
The name of custom en es
The name of custom typelists
New PCF files
Script parameters
Package naming conven ons - Ans Use the format
customer.applica on.featurecategory.feature
Customer - company name abbrevia on
Applica on- InsuranceSuite applica on code (pc, bc, cc, suite)
Feature Category - major feature (delinquency, configura on, integra on)
Feature - feature (ra ng, catastrophe, authen ca on)
Example: si.suite.integra on.authen ca on
Class naming conven ons - Ans Use UpperCamelCase
Do not add _Ext to classes within customer package spaces
, Func on naming conven ons - Ans Use lowerCamelCase
Use a verb that describes that the func on is doing i.e. verifyAddress
Do not add _Ext suffix to private func ons or enhancements in customer package spaces
Variable naming conven ons - Ans Member variable names use lowerCamelCase with a
leading underscore i.e. _pluginCallbackHandler
Local variable names use lowerCamelCase short names that describe the purpose i.e.
latestPolicyRevision
Display key naming conven ons - Ans Add suffix _Ext too all new display keys
Do not modify automa cally generated display keys
Logging is - Ans The process of recording applica on ac ons and state to a secondary interface
Logging is used for - Ans Applica on maintenance and troubleshoo ng
Crea ng sta s cs rela ng to applica on usage
Audi ng by capturing significant events
Typical events to log are - Ans Success / Failure - a transac on or ac on has succeeded or failed
Recovery - a system went down or connec on failed, retried, and recovered
Iden fica on - any large func onal areas such as integra on, ra ng, reinsurance, and rules
Logging components - Logger - Ans has a category and level, sends content to an Appender
Logging components - Appender - Ans is an output des na on (server console or rolling file)
Logging components - Layout - Ans defines the format of the content sent to an appender
