Guidewire Best Practices Exam study guide
Avoid using internal path for your classes - answerwire.* 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
represent...
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
When to use: The user experience has been affected
There are 2 ways to initialize a logger in Gosu - answer✔Integration: PLLoggerCategory.INTEGRATION
Plugin: PLLoggerCategory.PLUGIN
Use sub-level of existing logging category to maintain structure.
Example: PLUGIN.MotorVehicleRecord
static var _motorVehiclePluginLogger =
LoggerFactory.getLogger(PLLoggerCategory.PLUGIN."MotorVehicleRecord")
Logging Format should be - answer✔a standard format to simplify analysis of large logs
Guarded Logging should be used - answer✔To test log level before logging costly messages (those with
expensive expressions)
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 Thebright. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $11.49. You're not tied to anything after your purchase.
