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 Questions| With Complete Solutions. CA$16.60   Add to cart
Quickly navigate to
Preview
  2.  
  3. Wire
  4.  
  5. Wire

Exam (elaborations)

Guidewire Best Practices Exam Study Guide Questions| With Complete Solutions.
 9 views  0 purchase
  • Course
  • Wire
  • Institution
  • Wire

Guidewire Best Practices Exam Study Guide Questions| With Complete Solutions. Avoid using internal path for your classes 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 in...

[Show more]

Preview 3 out of 16  pages

Document information

  • March 11, 2024
  • 16
  • 2023/2024
  • Exam (elaborations)
  • Questions & answers

Subjects

  • guidewire best practices exam study guide question

Written for

  • Wire
All documents for this subject (263)

Seller

avatar-seller
ACADEMICAIDSTORE

Reviews received

Content preview

Guidewire Best Practices Exam Study Guide
Questions| With Complete Solutions.
Avoid using internal path for your classes

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

Use TC_TYPECODE instead of "typecode", example: LossCause.TC_REAREND instead of "rearend"

Use the text for logical operators instead of the symbols

Use "and","or", and "not" instead of "&&", "||", and "!"

Code placement

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

Guidewire will eventually remove deprecated classes and methods.

Turn on and run Studio Inspections

These analyze configuration resources

Use whitespace effectively

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

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

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

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

Use UpperCamelCase
Do not add _Ext to classes within customer package spaces

Function naming conventions

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

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

Add suffix _Ext too all new display keys
Do not modify automatically generated display keys

Logging is

The process of recording application actions and state to a secondary interface

Logging is used for

Application maintenance and troubleshooting
Creating statistics relating to application usage
Auditing by capturing significant events

Typical events to log are

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

, has a category and level, sends content to an Appender

Logging components - Appender

is an output destination (server console or rolling file)

Logging components - Layout

defines the format of the content sent to an appender

Logging Level - Trace

Description: Fine-grained informational events
When to use: Log method entry and exit

Logging Level - Debug

Description: Detailed informational events
When to use: Log important steps and calculations for diagnosing problems

Logging Level - Info

Description: Coarse-grained informational messages of progress
When to use: Log the occurrence or result of an important event

Logging Level - Warn

Description: Indicate a potential problem
When to use: The user experience has not been affected

Logging Level - Error

Description - Indicate definite problems
When to use: The user experience has been affected

There are 2 ways to initialize a logger in Gosu

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

a standard format to simplify analysis of large logs

Guarded Logging should be used

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

Will I be stuck with a subscription?

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

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

75323 documents were sold in the last 30 days

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

Start selling
CA$16.60
  • (0)
  Add to cart