Guidewire Best Practices Exam study guide
Questions with Correct Answers 2025 latest
update!!
Save
Terms in this set (115)
com.guidewire.* should be avoided. These can always
Avoid using internal path
be potentially changed or replaced during an
for your classes
upgrade.
When referencing Use TC_TYPECODE instead of "typecode", example:
typecodes, use the static LossCause.TC_REAREND instead of "rearend"
property on the typelist
class instead of the string
representation
Use the text for logical Use "and","or", and "not" instead of "&&", "||", and "!"
operators instead of the
symbols
1) Avoid placing code within the CODE tab of a PCF.
Create a UI helper class instead
Code placement
2) Avoid extending entity enhancements with code
supporting UI operations
Avoid using deprecated Guidewire will eventually remove deprecated classes
classes and methods and methods.
Turn on and run Studio These analyze configuration resources
Inspections
, Add spaces around operators
Do not add spaces between parentheses and
operators
Use whitespace
Indent logical blocks of code by two spaces only
effectively
Add a blank line after code blocks
Add two blank lines after methods, including the last
method in a class
Document new classes and functions with Javadoc-
style comments
Use single-line comments within functions and
Comments and
methods when you need to clarify the intent of the
Annotations
code
Use GoseDoc annotations which are included when
generating GosuDoc
Columns added to existing entities
Typecodes added to existing typelists
"Upgrade-Safe" naming
The name of custom entities
conventions: Add the
The name of custom typelists
suffix _Ext to
New PCF files
Script parameters
Use the format
customer.application.featurecategory.feature
Customer - company name abbreviation
Application- InsuranceSuite application code (pc, bc,
Package naming
cc, suite)
conventions
Feature Category - major feature (delinquency,
configuration, integration)
Feature - feature (rating, catastrophe, authentication)
Example: si.suite.integration.authentication
Use UpperCamelCase
Class naming conventions Do not add _Ext to classes within customer package
spaces
, Use lowerCamelCase
Use a verb that describes that the function is doing i.e.
Function naming
verifyAddress
conventions
Do not add _Ext suffix to private functions or
enhancements in customer package spaces
Member variable names use lowerCamelCase with a
leading underscore i.e. _pluginCallbackHandler
Variable naming
Local variable names use lowerCamelCase short
conventions
names that describe the purpose i.e.
latestPolicyRevision
Display key naming Add suffix _Ext too all new display keys
conventions Do not modify automatically generated display keys
The process of recording application actions and
Logging is
state to a secondary interface
Application maintenance and troubleshooting
Logging is used for Creating statistics relating to application usage
Auditing by capturing significant events
Success / Failure - a transaction or action has
succeeded or failed
Recovery - a system went down or connection failed,
Typical events to log are
retried, and recovered
Identification - any large functional areas such as
integration, rating, reinsurance, and rules
Logging components - has a category and level, sends content to an
Logger Appender
Logging components - is an output destination (server console or rolling file)
Appender
Logging components - defines the format of the content sent to an appender
Layout
Description: Fine-grained informational events
Logging Level - Trace
When to use: Log method entry and exit
Questions with Correct Answers 2025 latest
update!!
Save
Terms in this set (115)
com.guidewire.* should be avoided. These can always
Avoid using internal path
be potentially changed or replaced during an
for your classes
upgrade.
When referencing Use TC_TYPECODE instead of "typecode", example:
typecodes, use the static LossCause.TC_REAREND instead of "rearend"
property on the typelist
class instead of the string
representation
Use the text for logical Use "and","or", and "not" instead of "&&", "||", and "!"
operators instead of the
symbols
1) Avoid placing code within the CODE tab of a PCF.
Create a UI helper class instead
Code placement
2) Avoid extending entity enhancements with code
supporting UI operations
Avoid using deprecated Guidewire will eventually remove deprecated classes
classes and methods and methods.
Turn on and run Studio These analyze configuration resources
Inspections
, Add spaces around operators
Do not add spaces between parentheses and
operators
Use whitespace
Indent logical blocks of code by two spaces only
effectively
Add a blank line after code blocks
Add two blank lines after methods, including the last
method in a class
Document new classes and functions with Javadoc-
style comments
Use single-line comments within functions and
Comments and
methods when you need to clarify the intent of the
Annotations
code
Use GoseDoc annotations which are included when
generating GosuDoc
Columns added to existing entities
Typecodes added to existing typelists
"Upgrade-Safe" naming
The name of custom entities
conventions: Add the
The name of custom typelists
suffix _Ext to
New PCF files
Script parameters
Use the format
customer.application.featurecategory.feature
Customer - company name abbreviation
Application- InsuranceSuite application code (pc, bc,
Package naming
cc, suite)
conventions
Feature Category - major feature (delinquency,
configuration, integration)
Feature - feature (rating, catastrophe, authentication)
Example: si.suite.integration.authentication
Use UpperCamelCase
Class naming conventions Do not add _Ext to classes within customer package
spaces
, Use lowerCamelCase
Use a verb that describes that the function is doing i.e.
Function naming
verifyAddress
conventions
Do not add _Ext suffix to private functions or
enhancements in customer package spaces
Member variable names use lowerCamelCase with a
leading underscore i.e. _pluginCallbackHandler
Variable naming
Local variable names use lowerCamelCase short
conventions
names that describe the purpose i.e.
latestPolicyRevision
Display key naming Add suffix _Ext too all new display keys
conventions Do not modify automatically generated display keys
The process of recording application actions and
Logging is
state to a secondary interface
Application maintenance and troubleshooting
Logging is used for Creating statistics relating to application usage
Auditing by capturing significant events
Success / Failure - a transaction or action has
succeeded or failed
Recovery - a system went down or connection failed,
Typical events to log are
retried, and recovered
Identification - any large functional areas such as
integration, rating, reinsurance, and rules
Logging components - has a category and level, sends content to an
Logger Appender
Logging components - is an output destination (server console or rolling file)
Appender
Logging components - defines the format of the content sent to an appender
Layout
Description: Fine-grained informational events
Logging Level - Trace
When to use: Log method entry and exit
