GUIDEWIRE BEST PRACTICES EXAM 2024-2025
ACTUAL EXAM 120 QUESTIONS AND CORRECT
DETAILED ANSWERS WITH RATIONALES
(VERIFIED ANSWERS)
Terms in this set (115)
Avoid using internal path com.guidewire.* should be avoided. These can always be
for your classes potentially changed or replaced during an 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
Indent logical blocks of code by two spaces only
Use whitespace 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 methods
Comments and Annotations
when you need to clarify the intent of the 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 suffix
The name of custom typelists
_Ext to
New PCF files
Script parameters
Use the format
customer.application.featurecategory.feature
Customer - company name abbreviation
Application- InsuranceSuite application code (pc, bc, cc,
Package naming
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
Variable naming leading underscore i.e. _pluginCallbackHandler
conventions Local variable names use lowerCamelCase short 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 state
Logging is
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 Appender
Logger
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
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller THEALPHANURSE. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $14.49. You're not tied to anything after your purchase.
