Gosu - InsuranceSuite Developer Fundamentals

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/200

flashcard set

Earn XP

Description and Tags

Last updated 6:48 PM on 6/12/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No analytics yet

Send a link to your students to track their progress

201 Terms

1
New cards

Gosu

Guidewire’s programming language

2
New cards

Java

Gosu is based off of this other popular programming language

3
New cards

True

(True/False) Java code is entirely compatible with Gosu

4
New cards

Gosu Rules

Apply specific programming logic for testing a condition and performing an actionE

5
New cards

Enhancement

Extend entity functionality with programming logic as entity methods

6
New cards

Entity Name

Programming logic that defines how to display a name for an entity instance

7
New cards

Class

Encapsulate data and code for a specific purpose or function

8
New cards

Workflow

Runs custom business processes asynchronously, optionally with multiple states that transition over time

9
New cards

var

Gosu keyword for defining a variable

10
New cards

=

Gosu simple assignment operator

11
New cards

+=

Gosu operator that adds the left variable to the right side value and assigns the result to the left side variable

12
New cards

-=

Gosu operator that subtracts the right side value from the left variable, then assigns the result to the left side variable

13
New cards

*=

Gosu operator that multiplies the left variable with the right side value and assigns the result to the left side variable

14
New cards

and

Gosu operator for AND

15
New cards

or

Gosu operator for OR

16
New cards

not

Gosu operator for NOT

17
New cards

Text

(Text/Symbol) Is it preferred to use text or symbols for logical operators AND, OR, and NOT in Gosu?

18
New cards

2

How many spaces should you use to indent for best practices?

19
New cards

False

(True/False) The best practice is to put spaces around operators and parentheses in Gosu.

20
New cards

True

(True/False) The best practice is to put blank lines before and after code blocks in Gosu.

21
New cards

True

(True/False) The best practice is to add spaces around operators in Gosu.

22
New cards

True

(True/False) The best practice is to surround all logical blocks with curly braces in Gosu, even when they aren’t necessarily needed, such as for a single line if statement.

23
New cards

True

(True/False) The opening brace of a function should go on the same line that starts in, like in Java

24
New cards

gwb gosudoc

The console command used to generate Gosu documentation in CC/build/gosudoc/index.html

25
New cards

in

Which operator fills in the blank for the following Gosu for loop construction?
for ([variable] ______ [expression])

26
New cards

hasMatch()

Method used to return true/false for whether an array possesses an element that meets a given condition

27
New cards

firstWhere()

Method used to return a single element of an Array that matches a given condition

28
New cards

where()

Method used to return a new Array consisting of elements of an original Array which all match a given condition

29
New cards

countWhere()

Method used to return the number of elements in an Array that match a given condition

30
New cards

EN

File extension for an entity name file which contains at least one default entity name type definition

31
New cards

DisplayName

The property of an entity for the default entity name definition

32
New cards

True

(True/False) Using the DisplayName property for an entity without an entity name type definition will result in a list of fields

33
New cards

False

(True/False) Using the DisplayName property for an entity without an entity name type definition will print its denormalized class name only

34
New cards

GR

The file extension for a Gosu Rule class

35
New cards

True

(True/False) Gosu rules are all formatted in an if-then format

36
New cards

Root Entity

The input parameter for a Gosu rule

37
New cards

Condition

The portion of a Gosu rule that evaluates to either true or false and determines whether the rule is run

38
New cards

Action

The portion of a Gosu rule consisting of code to be run, provided the condition is true

39
New cards

False

(True/False) Gosu Rules code is still executed even if the condition is false

40
New cards

EventMessage

The type of Gosu rule that performs event processing and generates messages about events that have already occurred

41
New cards

Preupdate

The type of Gosu rule that provides domain logic that must happen before the entity is committed

42
New cards

Validation

The type of Gosu rule that verifies the saved data of the entity that must come before the entity is committed to ensure it is valid

43
New cards

True

(True/False) Gosu Rules can have child rules

44
New cards

False

(True/False) If a parent rule condition fails, the child rule is still evaluated

45
New cards

True

(True/False) If a parent Gosu rule is true, the program executes the parent’s action before executing its children

46
New cards

Execute All

The Gosu rule execution strategy where Guidewire executes all rules in the ruleset in hierarchy order

47
New cards

Exit after first action

The Gosu rule execution strategy where Guidewire executes rules in the ruleset until an exit() function is hit

48
New cards

actions.exit()

The function used to stop the processing of further Gosu rules

49
New cards

Validatable

Entities must have this property in the entity metadata in order to be able to trigger a preupdate rule

50
New cards

Logging

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

51
New cards

Logger

The element which encapsulates a logging category with a logical file nameA

52
New cards

Appender

The output point or destination for a logger, such as an app console or specific log file

53
New cards

Layout

The logging element which defines the log entry format instructions

54
New cards

Trace

The log level for fine-grained informational events at method entry/exit

55
New cards

Debug

The log level for detailed informational events used to diagnose problems

56
New cards

Info

The log level for coarse-grained informational messages of progress during important events or occurrences

57
New cards

Warn

The log level set to indicate potential problems where the user experience has not been affected

58
New cards

Error

The log level set to indicate definite problems where the user experience has been affected

59
New cards

True

(True/False) Loggers inherit the properties of their parent loggers, but can still overwrite them if needed

60
New cards

Structured

Guidewire’s common standard uses a (Regular/Intentional/Structured) logger as the basis

61
New cards

False

(True/False) All exceptions logged are considered errors

62
New cards

Info

In the production environment, the log level is set to ______

63
New cards

False

(True/False) It is acceptable to include sensitive information in logs, such as passwords or tokens, to help diagnose the issue

64
New cards

Common Logging Format

CLF abbreviation stands for

65
New cards

JSON

The de facto standard for message passing, often used alongside loggers

66
New cards

Unicode

The file encoding of JSON format, which makes it universally accesible

67
New cards

Common Logging Format (CLF)

Defines the correct usage of logging in Guidewire Cloud

68
New cards

True

(True/False) Common Logging Format (CLF) is platform-agnostic, meaning it works with both Log4j2 and Structured Logger

69
New cards

True

(True/False) Use of the Common Logging Format (CLF) is mandatory for Guidewire Cloud implementations and upgrades

70
New cards

True

(True/False) The timestamp is required for log messages

71
New cards

True

(True/False) The log level is required for log messages

72
New cards

True

(True/False) The contextMap is required for log messages

73
New cards

Error

The exceptionMessage is required for log messages at the ______ level or higher

74
New cards

False

(True/False) The operation is required for log messages

75
New cards

True

(True/False) The structured logger automatically converts objects into log entries using toString

76
New cards

1

What is the ideal number of lines each log entry should take up?

77
New cards

UTF-8

The ideal encoding of log messages under Guidewire’s best practices

78
New cards

True

(True/False) It is better to log too much than to log too little, according to Guidewire’s best practices

79
New cards

gsrc

All Gosu code packages are locted under the ../configuration/_________ folder

80
New cards

public

The Gosu access modifier keyword that makes the field fully accessible

81
New cards

protected

The Gosu access modifier keyword that makes the field accessible only by types with the same package and subtypes

82
New cards

internal

The Gosu access modifier keyword that makes the field accessible only within the same package

83
New cards

private

The Gosu access modifier keyword that makes the field accessible only by the declaring type or class that defines it

84
New cards

override

The Gosu modifier keyword that declares that this subtype overwrites and replaces the implementation of an identically-named method or property inherited from its parent

85
New cards

abstract

The Gosu modifier keyword that indicates a type is intended only to be a base type to be extended or inherited by other types

86
New cards

final

The Gosu modifier keyword that specifies that the value of this property cannot be modified after the initial value is assigned

87
New cards

static

The Gosu modifier keyword that specifies that this method or variable is defined once per Gosu class rather than once per instance of the class

88
New cards

False

(True/False) The final modifier can be combined with the abstract modifier

89
New cards

True

(True/False) The final modifier can be combined with the static modifier

90
New cards

GS

The file extension for a Gosu class

91
New cards

False

(True/False) You should add the _Ext suffix to new class names in customer packages

92
New cards

True

(True/False) You should add the _Ext suffix if you add a new class to a Guidewire package space

93
New cards

False

(True/False) Internal classes under the com.guidewire.* namespace are safe to use as they won’t be changed in future versions

94
New cards

function

The Gosu keyword to declare a code method

95
New cards

True

(True/False) You should add the _Ext suffix to enhancement methods created on Guidewire entities

96
New cards

True

(True/False) You should add the _Ext suffix to methods added directly into Guidewire base application classes

97
New cards

False

(True/False) You should add the _Ext suffix to private methods you create

98
New cards

False

(True/False) Properties and fields created as enhancement properties are persisted to the database

99
New cards

True

(True/False) Subtypes and subclasses will automatically inherit all elements from the entity enhancement made to their parent class / supertype

100
New cards

Getter

A property or method used to calculate a derived value and return it