Exam (elaborations)
Guidewire Best Practices Exam study guide Verified Questions And Answers -100-- Correct_.pdf
- Course
- Institution
Guidewire Best Practices Exam study guide Verified Questions And Answers -100-- Correct_.pdf
[Show more]
Seller
Follow
Content preview
8/23/24, 6:01 PMGuidewire Best Practices Exam study guide
Jeremiah
Practice questions for this set
Terms in this set (115)
com.guidewire.* should be avoided. These can always be potentially changed or
Avoid using internal path for your classes
replaced during an upgrade.
When referencing typecodes, use the static Use TC_TYPECODE instead of "typecode", example: LossCause.TC_REAREND instead of
property on the typelist class instead of the "rearend"
string representation
Use the text for logical operators instead of Use "and","or", and "not" instead of "&&", "||", and "!"
Guidewire Best Practices Exam study guide
the symbols
1/9
, 8/23/24, 6:01 PM
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 classes and Guidewire will eventually remove deprecated classes and methods.
methods
Turn on and run Studio Inspections These analyze configuration resources
Add spaces around operators
Do not add spaces between parentheses and operators
Use whitespace effectively 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
Document new classes and functions with Javadoc-style comments
Use single-line comments within functions and methods when you need to clarify the
Comments and Annotations
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 conventions: Add The name of custom entities
the suffix _Ext to The name of custom typelists
New PCF files
Script parameters
Use the format customer.application.featurecategory.feature
Customer - company name abbreviation
Application- InsuranceSuite application code (pc, bc, cc, suite)
Package naming 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. verifyAddress
Function naming 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 conventions
Local variable names use lowerCamelCase short names that describe the purpose i.e.
latestPolicyRevision
Add suffix _Ext too all new display keys
Display key naming conventions
Do not modify automatically generated display keys
Logging is The process of recording application actions and 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, retried, and recovered
Typical events to log are
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)
2/9
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 Denyss. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $7.99. You're not tied to anything after your purchase.
Can Stuvia be trusted?
4.6 stars on Google & Trustpilot (+1000 reviews)
78834 documents were sold in the last 30 days
Founded in 2010, the go-to place to buy study notes for 14 years now