GUIDEWIRE BEST PRACTICES EXAM STUDY GUIDE |
115 QUESTIONS AND ANSWERS | 2025/2026 UPDATE
| GRADED A+
Avoid using internal path for your classes Answer - com.guidewire.* should be
avoided. These can always be potentially changed or replaced during an
upgrade.
When referencing typecodes, use the static property on the typelist class
instead of the string representation Answer - Use TC_TYPECODE instead of
"typecode", example: LossCause.TC_REAREND instead of "rearend"
Use the text for logical operators instead of the symbols Answer - Use
"and","or", and "not" instead of "&&", "||", and "!"
Code placement Answer - 1) Avoid placing code within the CODE tab of a PCF.
Create a UI helper class instead
2) Avoid extending entity enhancements with code supporting UI operations
Avoid using deprecated classes and methods Answer - Guidewire will
eventually remove deprecated classes and methods.
Turn on and run Studio Inspections Answer - These analyze configuration
resources
,Use whitespace effectively Answer - 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 after code blocks
Add two blank lines after methods, including the last method in a class
Comments and Annotations Answer - Document new classes and functions
with Javadoc-style comments
Use single-line comments within functions and methods when you need to
clarify the intent of the code
Use GoseDoc annotations which are included when generating GosuDoc
"Upgrade-Safe" naming conventions: Add the suffix _Ext to Answer - Columns
added to existing entities
Typecodes added to existing typelists
The name of custom entities
The name of custom typelists
New PCF files
Script parameters
Package naming conventions Answer - Use the format
customer.application.featurecategory.feature
Customer - company name abbreviation
Application- InsuranceSuite application code (pc, bc, cc, suite)
Feature Category - major feature (delinquency, configuration, integration)
Feature - feature (rating, catastrophe, authentication)
, Example: si.suite.integration.authentication
Class naming conventions Answer - Use UpperCamelCase
Do not add _Ext to classes within customer package spaces
Function naming conventions Answer - Use lowerCamelCase
Use a verb that describes that the function is doing i.e. verifyAddress
Do not add _Ext suffix to private functions or enhancements in customer
package spaces
Variable naming conventions Answer - 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 conventions Answer - Add suffix _Ext too all new display
keys
Do not modify automatically generated display keys
Logging is Answer - The process of recording application actions and state to a
secondary interface
Logging is used for Answer - Application maintenance and troubleshooting
Creating statistics relating to application usage
Auditing by capturing significant events
Typical events to log are Answer - Success / Failure - a transaction or action has
succeeded or failed
115 QUESTIONS AND ANSWERS | 2025/2026 UPDATE
| GRADED A+
Avoid using internal path for your classes Answer - com.guidewire.* should be
avoided. These can always be potentially changed or replaced during an
upgrade.
When referencing typecodes, use the static property on the typelist class
instead of the string representation Answer - Use TC_TYPECODE instead of
"typecode", example: LossCause.TC_REAREND instead of "rearend"
Use the text for logical operators instead of the symbols Answer - Use
"and","or", and "not" instead of "&&", "||", and "!"
Code placement Answer - 1) Avoid placing code within the CODE tab of a PCF.
Create a UI helper class instead
2) Avoid extending entity enhancements with code supporting UI operations
Avoid using deprecated classes and methods Answer - Guidewire will
eventually remove deprecated classes and methods.
Turn on and run Studio Inspections Answer - These analyze configuration
resources
,Use whitespace effectively Answer - 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 after code blocks
Add two blank lines after methods, including the last method in a class
Comments and Annotations Answer - Document new classes and functions
with Javadoc-style comments
Use single-line comments within functions and methods when you need to
clarify the intent of the code
Use GoseDoc annotations which are included when generating GosuDoc
"Upgrade-Safe" naming conventions: Add the suffix _Ext to Answer - Columns
added to existing entities
Typecodes added to existing typelists
The name of custom entities
The name of custom typelists
New PCF files
Script parameters
Package naming conventions Answer - Use the format
customer.application.featurecategory.feature
Customer - company name abbreviation
Application- InsuranceSuite application code (pc, bc, cc, suite)
Feature Category - major feature (delinquency, configuration, integration)
Feature - feature (rating, catastrophe, authentication)
, Example: si.suite.integration.authentication
Class naming conventions Answer - Use UpperCamelCase
Do not add _Ext to classes within customer package spaces
Function naming conventions Answer - Use lowerCamelCase
Use a verb that describes that the function is doing i.e. verifyAddress
Do not add _Ext suffix to private functions or enhancements in customer
package spaces
Variable naming conventions Answer - 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 conventions Answer - Add suffix _Ext too all new display
keys
Do not modify automatically generated display keys
Logging is Answer - The process of recording application actions and state to a
secondary interface
Logging is used for Answer - Application maintenance and troubleshooting
Creating statistics relating to application usage
Auditing by capturing significant events
Typical events to log are Answer - Success / Failure - a transaction or action has
succeeded or failed
