100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
Previously searched by you
Previously searched by you
logo
Guidewire Best Practices Exam study guide 2024 $12.99
Add to cart
Quickly navigate to
Preview
  2.  
  3. Wire .
  4.  
  5. Wire .

Exam (elaborations)

Guidewire Best Practices Exam study guide 2024
 0 purchase
  • Course
  • Wire .
  • Institution
  • Wire .

Avoid using internal path for your classes -Correct Answer wire.* 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 -Correct Answer Use TC_TYPECO...

[Show more]

Preview 3 out of 16  pages

Document information

  • November 1, 2024
  • 16
  • 2024/2025
  • Exam (elaborations)
  • Questions & answers

Subjects

  • guidewire
  • guidewire best practices exam study guide 2024
  • guidewire best practices exam study guide
  • guidewire best practices exam

Written for

  • Wire .
  • Wire .

Seller

avatar-seller
PossibleA

Reviews received

Content preview

Guidewire Best Practices Exam study guide



Guidewire Best Practices Exam study
guide 2024
Avoid using internal path for your classes -Correct 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 -Correct Answer ✔Use TC_TYPECODE instead of "typecode",
example: LossCause.TC_REAREND instead of "rearend"

Use the text for logical operators instead of the symbols -Correct Answer ✔Use
"and","or", and "not" instead of "&&", "||", and "!"

Code placement -Correct 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 -Correct Answer ✔Guidewire will
eventually remove deprecated classes and methods.

Turn on and run Studio Inspections -Correct Answer ✔These analyze configuration
resources

Use whitespace effectively -Correct 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 -Correct 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 -Correct 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


Guidewire Best Practices Exam study guide

,Guidewire Best Practices Exam study guide



Package naming conventions -Correct 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 -Correct Answer ✔Use UpperCamelCase
Do not add _Ext to classes within customer package spaces

Function naming conventions -Correct 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 -Correct 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 -Correct Answer ✔Add suffix _Ext too all new display
keys
Do not modify automatically generated display keys

Logging is -Correct Answer ✔The process of recording application actions and state to
a secondary interface

Logging is used for -Correct Answer ✔Application maintenance and troubleshooting
Creating statistics relating to application usage
Auditing by capturing significant events

Typical events to log are -Correct Answer ✔Success / Failure - a transaction or action
has succeeded or failed
Recovery - a system went down or connection failed, retried, and recovered
Identification - any large functional areas such as integration, rating, reinsurance, and
rules

Logging components - Logger -Correct Answer ✔has a category and level, sends
content to an Appender

Logging components - Appender -Correct Answer ✔is an output destination (server
console or rolling file)



Guidewire Best Practices Exam study guide

, Guidewire Best Practices Exam study guide


Logging components - Layout -Correct Answer ✔defines the format of the content sent
to an appender

Logging Level - Trace -Correct Answer ✔Description: Fine-grained informational events
When to use: Log method entry and exit

Logging Level - Debug -Correct Answer ✔Description: Detailed informational events
When to use: Log important steps and calculations for diagnosing problems

Logging Level - Info -Correct Answer ✔Description: Coarse-grained informational
messages of progress
When to use: Log the occurrence or result of an important event

Logging Level - Warn -Correct Answer ✔Description: Indicate a potential problem
When to use: The user experience has not been affected

Logging Level - Error -Correct Answer ✔Description - Indicate definite problems
When to use: The user experience has been affected

There are 2 ways to initialize a logger in Gosu -Correct 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 -Correct Answer ✔a standard format to simplify analysis of
large logs

Guarded Logging should be used -Correct Answer ✔To test log level before logging
costly messages (those with expensive expressions)

Typically used with the DEBUG level
Format is - if (_logger.DebugEnabled) { <log statement content>}
Not required for parameterized expressions lacking expensive operations, as in:

var hello = "Hello"
var world = "world"
_logger.debug("{}, {}!", hello, world)




Guidewire Best Practices Exam study guide

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

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

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

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 PossibleA. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy these notes for $12.99. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

68175 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy study notes for 15 years now

Start selling
$12.99
  • (0)
Add to cart
Added