Avoid using internal path to your classes - ANScom.Guidewire.* need to be prevented. These
can usually be potentially modified or changed throughout an upgrade.
When referencing typecodes, use the static belongings at the typelist magnificence rather than
the string illustration - ANSUse TC_TYPECODE in place of "typecode", example:
LossCause.TC_REAREND as opposed to "rearend"
Use the textual content for logical operators instead of the symbols - ANSUse "and","or", and
"now not" as opposed to "&&", "setting code in the CODE tab of a PCF. Create a UI helper
elegance as a substitute
2) Avoid extending entity enhancements with code supporting UI operations
Avoid the use of deprecated instructions and strategies - ANSGuidewire will in the end cast off
deprecated instructions and methods.
Turn on and run Studio Inspections - ANSThese analyze configuration assets
Use whitespace effectively - ANSAdd spaces around operators
Do now not upload areas among parentheses and operators
Indent logical blocks of code by using two spaces simplest
Add a blank line after code blocks
Add two blank lines after techniques, which includes the last technique in a category
Comments and Annotations - ANSDocument new lessons and capabilities with Javadoc-fashion
comments
Use unmarried-line feedback within functions and methods when you want to clarify the purpose
of the code
Use GoseDoc annotations which are blanketed while producing GosuDoc
"Upgrade-Safe" naming conventions: Add the suffix _Ext to - ANSColumns introduced to
present entities
Typecodes introduced to current typelists
The call of custom entities
The name of custom typelists
New PCF documents
Script parameters
, Package naming conventions - ANSUse the layout
purchaser.Software.Featurecategory.Characteristic
Customer - company name abbreviation
Application- InsuranceSuite software code (laptop, bc, cc, suite)
Feature Category - most important function (delinquency, configuration, integration)
Feature - feature (rating, disaster, authentication)
Example: si.Suite.Integration.Authentication
Class naming conventions - ANSUse UpperCamelCase
Do now not add _Ext to training inside customer package areas
Function naming conventions - ANSUse lowerCamelCase
Use a verb that describes that the function is doing i.E. VerifyAddress
Do not upload _Ext suffix to non-public functions or upgrades in purchaser package deal spaces
Variable naming conventions - ANSMember variable names use lowerCamelCase with a
leading underscore i.E. _pluginCallbackHandler
Local variable names use lowerCamelCase quick names that describe the motive i.E.
LatestPolicyRevision
Display key naming conventions - ANSAdd suffix _Ext too all new display keys
Do no longer alter routinely generated show keys
Logging is - ANSThe procedure of recording utility movements and state to a secondary
interface
Logging is used for - ANSApplication preservation and troubleshooting
Creating facts relating to application usage
Auditing with the aid of taking pictures giant events
Typical occasions to log are - ANSSuccess / Failure - a transaction or motion has succeeded or
failed
Recovery - a machine went down or connection failed, retried, and recovered
Identification - any big useful areas along with integration, rating, reinsurance, and regulations
Logging additives - Logger - ANShas a class and stage, sends content to an Appender
Logging components - Appender - ANSis an output destination (server console or rolling report)
Logging additives - Layout - ANSdefines the layout of the content sent to an appender
Logging Level - Trace - ANSDescription: Fine-grained informational occasions
When to apply: Log approach 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 Legitexams. 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.
