Bridge Specialty Suite

(1)

(2)

Introduction

Welcome to Insurity's Bridge Specialty Suite. The system provides a full workflow, from the administration of products and coverage, to the submission and management of individual policies.

Access to all features, options, and data are controlled by the settings in your user account. This guide is for users with product design rights, and details the creation of formulas for use in calculated fields. Calculated fields can be used for simple purposes such as dis-playing a basic system variable, or can perform a complex calculation pulling in a variety of fields and system information and gen-erating a result to be displayed on-screen, used in documentation, or even used in other calculated fields.

(7)

Building Formulas

Formulas are assembled using common logic and notation, and should be familiar for users experienced with formulas in spreadsheet and database applications.

Operators

The system uses the following symbols to represent common arithmetic operators. + Add - Subtract * Multiply / Divide ( Open bracket ) Close bracket

Simple Arithmetic Formulas

(8)

3 x 6 ÷ (5 + 15 – 0.3) x 0.6 Would be input into a calculated field as:

3*6/(5+15-.3)*.6

Note: Spaces are optional, but can be included for clarity. They will be ignored by the system.

Placeholders Within Formulas

The real power of calculated fields in the Bridge Specialty Suite is the ability to pull in information from the system and from the sub-mission or claims form itself. This is achieved using placeholders. When the system encounters a placeholder while resolving a for-mula, it replaces the placeholder with the current value from the system or workflow.

The placeholders are predefined, and are detailed in thePlaceholderssection. Placeholders for fields within the submission or claims form are made up of the Code for the field (defined in Field Management), enclosed in double square brackets [[ ]].

Example:

100 x The Number of Trucks - 50 Would be input into a calculated field as:

100*[[NumberOfTrucks]]-50

Where NumberOfTrucks is the Code for the field “The Number of Trucks”.

(9)

Defining String Data

Calculated fields are not restricted to using numerical values. Dates and text can also be manipulated using a selection of functions and features.

In some situations, however, the formatting of data could be mistaken for calculations. For example, the date format 5/15/2012 could be interpreted as 5 divided by 15 divided by 2012, or a policy number with dashes, such as 2012-12345 could be interpreted as 2012 minus 12345.

There are two methods for defining string data.

l The String: formatting notation can be used at the beginning of a calculated field formula, and causes the system to treat all

val-ues as text. No calculations are performed, and any operators, arithmetic expressions, and spaces are treated as text. Functions and placeholders still function normally, but the resulting data is treated as text.

Example:

String:[[field1]]/[[field2]]+[[field3]]

If the values of the three placeholders are 8, 4, and 2 respectively, the value of this calculated field would be 8/4+2, and would be displayed as such in the field and any documents or e-mails that pull in this calculated field.

l Any text, numbers, or symbols enclosed in quotes " will be treated as simple text. No calculations will be performed on content

within quotes, spaces in quotes will not be removed, and even functions and placeholders will be treated as text instead of being replaced with system information.

Example:

(10)

If the values of the three placeholders are 8, 4, and 2 respectively, the result of this calculated field would be: The value of 8/ 4 +2 equals 4

The first set of operators are treated as text and displayed in the output, while the second set are calculated and the result is displayed in the output. Note that the spaces within the quotes are kept, while the spaces outside of the quotes are

ignored.

Note: All quotes must be straight quotes " or they will not be recognized. Some word processing programs replace straight quotes with angled quotes or "Smart Quotes". These quotes must be replaced with straight quotes, either in the word processor, or within the system.

l If a field is used within an arithmetic expression that evaluates to null, the result is '0' (zero).

Concatenation (Combining Data)

If no Operators are used between placeholders and/or data entered directly in the formula, the system simply pulls in the placeholder data without any modifications.

This is useful for merging fields that are collected separately, but need to be used together.

Example: If a user's first name and last name are collected in separate fields, the following formulas could be used: String:[[FirstName]] [[LastName]] -or- [[FirstName]] " " [[LastName]]

(11)

Another example would be to assemble an address:

String:[[StreetAddress]], [[City]], [[Country]]. -or- [[StreetAddress]] ", " [[City]] ", " [[Country]] "."

The commas, spaces, and period are included in the calculated value. For the example using quotes, note that the spaces within the quotes will be kept, while the spaces outside the quotes will be ignored.

Adding Comments to Formulas

Comments can be added at the end of a formula and are commonly used to explain of the intent of the formula or describe the return value.

Comments are specified by the expression "//" and continue until the end of the line in the Calculated Field Formula field on the Field Management page. If comments should continue on the next line, the text must be preceded by another "//" expression. Any text following a double slash and up to the end of the line will be ignored when the formula is calculated.

Example:

(12)

Placeholders

While the field Code is used in a standard placeholder to pull in information from the submission form, specific placeholders are

required to pull in background information about the current submission or policy. This information is available in any status where the quote details have been calculated, and some transaction types may have additional options.

Information is available for the Current Transaction and the Current Term, with Previous Term information available when working with renewals.

Note: Some placeholders use single quotes ' to identify a specific version of the variable. These must be straight quotes ' or the formula does not recognize them. Some word processing programs replace straight quotes with angled quotes or "Smart Quotes". These quotes must be replaced with straight quotes, either in the word processor, or within the system.

Current Transaction Information

In any status where quote details have been calculated, that quote information is available for use in calculated fields.

Premium Details

The following placeholder returns the premium amount for a specific premium type, identified by code. [[PremiumInfo[PremiumTypeCode='code']/Amount]]

(13)

Commission Details

The following placeholders return the commission amount for a specific premium type, as well as the gross premium and the net premium after commission. The premium types are identified by premium type code.

[[PremiumCommissionList/PremiumCommissionInfo[PremiumTypeCode='code']/GrossPremium]] [[PremiumCommissionList/PremiumCommissionInfo[PremiumTypeCode='code']/CommissionAmount]] [[PremiumCommissionList/PremiumCommissionInfo[PremiumTypeCode='code']/NetPremium]]

Wherecodeis the system code of the required premium type.

Tax Details

The following placeholders return the tax information for a specific premium type, identified by premium type code. [[TaxDefinition[PremiumTypeCode='code']/TaxName]]

(14)

Current Term Information

The Current Term placeholders access the total values for all bound transactions in the current term. The references can access premium values, commissions, and taxes, for individual premium types or a total for all premium types.

Premium Details

The following placeholder returns the term premium amount for a specific premium type, identified by code. [[CurrentTerm/Premium/PremiumInfo[PremiumTypeCode='code']/Amount]]

The following placeholder returns the total bound premium for the term, for all premium types. [[CurrentTerm/Premium/TotalPremiumAmount]]

Commission Details

The following placeholder returns the term commission amount for a specific premium type, identified by code. [[CurrentTerm/Premium/PremiumInfo[PremiumTypeCode='code']/CommissionAmount]] Wherecodeis the system code of the required premium type.

(15)

[[CurrentTerm/Premium/TotalCommissionAmount]]

Tax Details

The following placeholder returns the term tax amount for a specific premium type, identified by code. [[CurrentTerm/Premium/PremiumInfo[PremiumTypeCode='code']/TotalTaxAmount]] Wherecodeis the system code of the required premium type.

The following placeholder returns the total tax amount for the term, for all premium types. [[CurrentTerm/Premium/TotalTaxAmount]]

Notes:

Only values from Bound transactions within the current term are returned. Using these references in a submission may have one value before binding (when the transaction being viewed is not included in the calculation) and a different value after bind-ing (when the transaction bebind-ing viewed is included in the calculation).

Once a transaction in a particular term is bound, the calculated fields are locked for that transaction. They are not updated if other transactions are subsequently bound within the same term.

Term Period Dates

(16)

(17)

Previous Term Information

The Previous Term placeholders access the total values for all bound transactions in the previous term. The references can access premium values, commissions, and taxes, for individual premium types or a total for all premium types.

Note: When a Renewal transaction is created, the values for the previous term are copied into the renewal transaction for use with these placeholders. If the previous term is changed in any way (such as by an endorsement), the details saved in the renewal transaction may no longer be valid. If the renewal has not yet been bound, it may be possible to delete it and create a new renewal transaction with the updated values.

If a Renewal transaction is voided and a replacement transaction is created, the system populates the placeholders with the val-ues from the policy term of the last Bound transaction of type New Business or Renewal.

Premium Details

The following placeholder returns the previous term premium amount for a specific premium type, identified by code. [[PreviousTerm/Premium/PremiumInfo[PremiumTypeCode='code']/Amount]]

The following placeholder returns the total bound premium for the previous term, for all premium types. [[PreviousTerm/Premium/TotalPremiumAmount]]

(18)

The following placeholder returns the previous term commission amount for a specific premium type, identified by code. [[PreviousTerm/Premium/PremiumInfo[PremiumTypeCode='code']/CommissionAmount]]

The following placeholder returns the total bound commission amount for the previous term, for all premium types. [[PreviousTerm/Premium/TotalCommissionAmount]]

Tax Details

The following placeholder returns the previous term tax amount for a specific premium type, identified by code. [[PreviousTerm/Premium/PremiumInfo[PremiumTypeCode='code']/TotalTaxAmount]]

The following placeholder returns the total tax amount for the previous term, for all premium types. [[PreviousTerm/Premium/TotalTaxAmount]]

Policy Number

(19)

Limits

The following placeholders return specific limits information defined for the current transaction. The information is available for each premium type, identified by code.

(20)

Deductibles

The following placeholders return specific deductibles information defined for the current transaction. The information is available for each premium type, identified by code.

(21)

Functions

The Bridge Specialty Suite provides an advanced set of tools for retrieving and manipulating data within the system. Functions provide ways to retrieve and work with dates, analyze data within a table, set conditional results within a formula, and much more.

A function is made up of the function name, which may begin with the $ symbol, followed by round brackets ( ). The $ symbol is optional for some functions, and may be included to help identify functions in complex formulas. The parameters of the function are added within the brackets separated by commas.

$Function(p0,p1,...)

Some functions require a specific number of parameters, others allow as many as required, and some do not require any parameters at all.

Note: Spaces are optional, but can be included for clarity. They will be ignored by the system.

All functions are listed in theFull Function Reference Listsection, which includes descriptions of the functions, parameters, and results of each.

(22)

Defining Multiple Fields in a Function

Some functions evaluate multiple fields to provide a result. These functions may calculate the average of all values in a single column of a grid, the sum of a series of individual fields throughout the submission form, or a mix of fields and columns.

For functions that support multiple fields, a comma or Pipe character ( | ) can be used to separate the fields in the list. Using commas is considered the best practice for legibility.

For columns in a grid, only the field names must be provided. The system automatically retrieves all records in the grid. Examples:

To determine the average value of three fields:

Avg([[field1]],[[field2]],[[field3]]) -or- Avg([[field1]]|[[field2]]|[[field3]]) To determine the sum of all records in a column, plus one field outside the grid:

(23)

Conditional Results – the IF Function

The If function is used to define the value of a calculated field based on other data, such as system information or the content of other fields in the workflow.

The condition of the function can either be a pair of values and a comparison operator, or a trigger defined in the system. The function returns one value if the condition evaluates as true, or a different value if the condition evaluates as false.

There are two versions of the If statement. The If/Then version, which is formatted as follows. IfCondition thenTrueValue elseFalseValue endif

Then there is the $If() version, which is formatted as follows. $If(TriggerCode,TrueValue,FalseValue)

The If/Then version is more powerful and flexible, so it is the recommended version. The $If() version will most commonly be encountered when reviewing older calculated fields.

The If/Then Conditional Structure

TheConditionis any conditional expression that evaluates to boolean values (True or False). This can be a simple field containing boolean values, a function that returns a boolean value, a comparison between two values, or even multiple conditions that resolve to a single boolean result. The Trigger() function can also be used to evaluate a trigger with additional conditions.

(24)

The $If() Function

TheTriggerCodeidentifies a trigger, which is created in the system and contains all necessary conditions to evaluate as true or false. For details about configuring triggers, see the Managing Triggers section of the User Guide - Product Design document.

Notes:

The Code for the trigger must be used. The code is based on the name of the trigger, but may not match exactly.

If you need a conditional structure that makes use of an existing trigger configuration, the trigger can be referenced in the If/Then version using the Trigger() function.

Defining the Results

TheTrueValueandFalseValuedata can include placeholders, formulas, or even other functions (including other If functions). When using the If/Then structure, the else can be omitted which produces no result (null) if the function evaluates as false.

When embedding additional If functions within the true or false calculations, each If function must have its own endif parameter. As an alternative, the elseif parameter can be used in place of the else parameter. This allows multiple conditions to be chained together with only one endif for each standalone If function.

Examples:

(25)

-or-IfValue1operatorValue2then [[FieldA]]*12 else [[FieldA]]endif

The function could return the user's name (concatenated from two fields with a space to divide them) or their spouse's name (also concatenated).

String:$If(TriggerCode,[[UserFirstName]] [[UserLastName]],[[SpouseFirstName]] [[SpouseLastName]]) (The String: option is included to ensure that the spaces are treated as text)

-or-IfValue1operatorValue2then [[UserFirstName]] " " [[UserLastName]] else [[SpouseFirstName]] " " [[SpouseLastName]] endif

(The spaces between the names are enclosed in quotes, or they would be ignored)

Using functions in theTrue/Falsevalues allows these If functions to return the sum of a table column, or the average of the val-ues in that column.

$If(TriggerCode,Sum([[Column1]]),Avg([[Column1]]))

-or-IfValue1operatorValue2then Sum([[Column1]]) else Avg([[Column1]]) endif

Multiple If functions can be included in a single calculated field. The results can be used with arithmetic formulas or simple con-catenation to form the final value of the calculated field.

(26)

-or-(If Value1operatorValue2then TrueValue else FalseValue endif + [[Value]]) * IfValue3operatorValue4

then TrueValue else FalseValue endif / 2

These functions take the conditional result of the first If statement and add it to the amount in the Value field, then multiply that by the conditional result of the second If statement, and divide the entire value by 2.

Multiple If functions can be chained to check one condition, then another, then another, and so on. The elseif function is used to insert a new condition when the preceding condition evaluates as false.

The following structure refers to a radio button field with three options. It systematically checks for each value, and returns a spe-cific result when it finds the selected value.

If[[Field]]="Option 1" then "Option 1 selected"

elseif [[Field]]="Option 2" then "Option 2 selected"

elseif [[Field]]="Option 3" then "Option 3 selected"

else "No option selected"

endif

The indented multiple-line structure is recommended to help organize complex conditional formulas. Also, it is best to include a final else statement in case none of the conditions evaluate to true.

(27)

Sequential Conditions - the MapValue() function

The MapValue() function allows a calculated field to perform a series of value comparisons until it finds a matching value, then returns a specific value for that result.

The function is provided a specific field to evaluate, and one or more sets of paired conditions. An optional Default value can be provided.

The function evaluates each condition in order. As soon as a condition evaluates as true, the corresponding value is returned and the operation is complete. Subsequent conditions are not evaluated.

The format is as follows:

MapValue(p0,p1, p2,p1,p2,…,p3,p4)

P0 Placeholder for the target field to be evaluated.

P1 EachP1parameter must have a matchingP2parameter. These are the paired conditions and return results. The condition can be a static value, placeholder, or another function.

The condition value must match the value of the target field exactly, or the function will move on to the next con-dition.

P2 EachP2parameter must have a matchingP1parameter. These are the paired conditions and return results. The return result can be a static value, placeholder, or another function.

P3 TheP3parameter must have a matchingP4parameter. This parameter is optional, and should contain the text

(28)

P4 TheP4parameter must have a matchingP3parameter. This parameter is optional, and returns the default value if all other conditions fail.

Tips:

Because the condition and target values must match exactly, this function may not be useful for evaluating field types where the user can enter values directly. This is best used with selection fields such as radio buttons and checkbox groups, or calculated fields that produce predictable results.

When using target fields that can contain multiple values, such as checkbox groups, multiple values are saved differently than single values. A single selection may be saved as "Value1", while multiple values are saved as "Value1|Value2". Individual con-dition and return pairs must be created for each combination of values that should produce a result.

(29)

Conditional Selection of Grid Rows - the Where() function

When used on their own, most functions or placeholders that reference data in a grid will use all rows in the grid. This may be a cal-culation function that produces the sum of values in a column, a Grid Mapping function that copies some or all of a row, or just a simple placeholder that pulls all values for reference.

The Where() function applies conditions when referencing a grid, so that only rows that meet the conditions will be included. The format is as follows:

Subject Where(Condition)

l TheSubjectis what will be modified by the Where function. This can be a placeholder, another function, or a single parameter of

another function. The Where function will apply to the subject that directly precedes it. For example:

[[Placeholder]] Where(Condition)

This will return all values from the specified column for each row that meets the conditions.

Function(Column1, Column2) Where(Condition)

With the Where function outside of the function parameters, it applies to the entire function. The function will evaluate column1 and column2 for each row that meets the conditions.

(30)

With the Where function inside the function parameters, it only applies to the preceding parameter. The function will eval-uate column1 for every row, but only evaleval-uate column2 for each row that meets the conditions.

Note: Care should be taken when applying conditions to parameters. Using Where to omit a required parameter will result in an error. However, two versions of a required parameter can be provided with conditions that use one version or the other (do not include additional commas).

l TheConditionis any conditional expression that evaluates to boolean values (True or False). This can be a simple field containing

boolean values, a function that returns a boolean value, a comparison between two values, or even multiple conditions that resolve to a single boolean result.

In general, at least one of these will be a field in the grid or a calculated value based on a field in the grid, producing separate results for each row. The other value can be a grid field, calculated value, static value, or a top-level field (field outside of a grid).

See the section onBuilding Conditional Expressionsfor information on operators, negative conditions, and combined conditions. Examples:

A column in a table has five values, 100, 200, 300, 400, and 500. The following basic formula is used. Sum([[NumberColumn]])

This sums up all values in the column and displays 1500. If the following conditional formula is used instead: Sum([[NumberColumn]]) Where([[NumberColumn]]>300)

Only the fourth and fifth rows are greater than 300, so the calculated field sums those values and displays 900.

(31)

used for display, or as a parameter for another function. [[NumberColumn]]

This returns all values in the column, "100|200|300|400|500". If the placeholder is used with a condition instead: [[NumberColumn]] Where([[NumberColumn]]<300)

Only the first and second rows are less than 300, so the calculated field returns those values, "100|200".

The Round() function uses a parameter to determine how a value is rounded. A condition can be applied to determine if the value should be rounded up or rounded down.

Round([[OriginalValue]], 1, 1 Where([[RoundUpOrDown]]="Up") 2 Where([[RoundUpOrDown]]= "Down"))

As this is a required parameter, the conditions must use one value or the other, or the function will fail. In this example, the two values could be pulled from a Radio Button control, ensuring that one or the other is selected.

If the condition were instead comparing if a value was more or less than a threshold value, one condition could verify if the value is less (<) than the threshold, but the other condition would need to check if the value is greater than or equal (>=) to the

threshold.

Tip: The Where function is useful when copying data between tables (grid mapping). See theFunctions to Enter Data Into Grids

(32)

Building Conditional Expressions

Some functions allow multiple results based on conditions, such as the If and Where() functions. The condition is any conditional expression that evaluates to boolean values (True or False). This can be a simple field containing boolean values, a function that returns a boolean value, a comparison between two values, or even multiple conditions that resolve to a single boolean result.

The most common format isValue1operatorValue2which compares one value to another, although more complex comparisons are possible. TheValue1andValue2data can include placeholders, formulas, or even other functions (including other conditional func-tions).

The operators and other options are detailed below.

Operators

Theoperatordetermines what comparison will be made between the values.

= Checks if the two values are exactly equal.

< Checks if the first value is less than the second value.

> Checks if the first value is greater than the second value.

<= Checks if the first value is less than or equal to the second value.

>= Checks if the first value is greater than or equal to the second value.

(33)

Examples:

IfSum([[GridColumn]])>[[Tolerance]] then TrueValue else FalseValue endif

Uses theSum()function to determine the total of all values in a grid column, and checks if it isgreater than a maximum value found in the[[Tolerance]]field.

If[[RenewalDate]]<=TodayXml()then TrueValue else FalseValue endif

Retrieves the value of the[[RenewalDate]]field and checks if it isless than or equal totoday's date, retrieved by the

TodayXml()function.

Negative Conditions

Starting the function with If not will check that the conditions are not met. If the conditions evaluate as false, then theTrueValue is returned, else theFalseValueis returned. While using different operators can often achieve the same results, using Not may sim-plify complex conditions.

This can also be used with the Where() function, by adding it to the beginning of the conditions, such as Where(Not Value1 oper-atorValue2).

Examples:

If5<3 then TrueValue else FalseValue endif returns theFalseValuebecause we are checking that the first value is less than the second.

(34)

Combined Conditions

Multiple conditions can be checked within a single expression. Placing multipleValue1operatorValue2sets, separated by and or or, will evaluate each set individually, then evaluate the and conditions followed by the or conditions.

Example:

If5<3 and8>4 or 9=9 and4>2then TrueValue else FalseValue endif The individual conditions are evaluated first, producing the following results.

Iffalse and true or true and true then TrueValue else FalseValue endif

The and conditions are evaluated next. An and evaluates to true if both conditions are true, producing the following results. Iffalse or true then TrueValue else FalseValue endif

The or conditions are evaluated next. An or evaluates to true if either condition is true, producing the following results Iftrue then TrueValue else FalseValueendif

The final result istrue, so the function returns theTrueValue.

In situations where an or condition must be evaluated before an and condition, brackets () can be used to divide entire sections. The contents of the innermost brackets will be completely evaluated first, then the next brackets out, and so on.

Example:

(35)

The individual conditions are evaluated first, producing the following results.

If (false and (true orfalse)) andtrue then TrueValue else FalseValue endif The (true or false) is evaluated first. Being an or, it evaluates astrue.

If (false andtrue) and true then TrueValue else FalseValue endif The (false andtrue) is evaluated next. Being an and, it evaluates asfalse.

Iffalse and true then TrueValue else FalseValue endif

The remaining and condition is evaluated, producing in afalseresult, and the function returns theFalseValue.

Working with Boolean Values

Triggers and certain functions validate one or more conditions and return either "True" or "False", known as boolean values. These can be used in a variety of ways.

l When evaluating conditions in a trigger, If statement, or Where() function, the system retrieves the data to be checked and

com-pares it to the condition value to determine if the statement is true or false.

If the data to be checked is either a boolean function or a field with a saved boolean value, the condition value can be left out. The system will accept the data as the result.

For example, the two following If statements will work exactly the same:

(36)

As will the two following Where() calculations:

Sum(Value) Where(BooleanFunction = "True") Sum(Value) Where(BooleanFunction)

l The Checkbox field type stores a boolean value, and can be used without condition values as described above.

l By default, boolean functions return "True" or "False", which will be shown if the results are displayed in the workflow. However,

"1" and "Yes" are also recognized as "True", while "0" and "No" are also recognized as "False". These alternate values are mainly supported for compatibility with older calculations, but may be used if necessary. Boolean values are not case-sensitive.

l A null value evaluates to "False" in boolean expressions. If a field used in a boolean expression evaluates to null, and that field is

then used in comparison to another specified value through an If statement or Where() function, the following rules are respec-ted depending on the value of the comparison field.

Value of Comparison Field Boolean Result Notes

'' True Two single quotation marks.

Null / null True

False / false True

No / no True

0 True

'0' True

(37)

'No' / 'no' False 'False' / 'false' False

1 False

(38)

Full Function Reference List

The following is a complete list of all functions currently available in the system. For each function, the following information is provided:

l The full name of the function, plus placeholders (in green) for the required parameters.

l A brief description of the function.

l A list of the required parameters (if any), the required format, and any notes about the parameters.

l The value that is returned by the function, and the format of the response.

Tip: When using a function that refers to a date field in the submission form, if the field is blank it is considered to be

0001/01/01. If this could create unwanted results from the calculation, either set the field to Required or use the If function to return a safe value if the field is blank.

The system stores all dates in the full system format "2014-10-28T18:16:12.3313239-04:00". When pulling dates from date picker fields or functions that return full dates, this will be handled automatically. However, when providing literal date values within a calculated field, the dates must be provided in this format.

DaysBetween(p0,p1)

Counts the number of days that have elapsed between two dates.

P0 (date): First date field

P1 (date): Second date field

(39)

Examples:

Comparing date 4/22/2014 and 4/24/2014 returns 2. Comparing date 4/26/2014 and 4/24/2014 returns -2. MonthsBetween(p0,p1)

Counts the number of months that have elapsed between two dates.

Returns (numeric): Number of calendar months between p0 and p1. If the first date is earlier than the second date, the value will be positive. If the first date is later than the second date, the value will be negative.

Examples:

Comparing date 2/24/2014 and 4/24/2014 returns 2. Comparing date 6/24/2014 and 4/24/2014 returns -2. YearsBetween(p0,p1)

Counts the number of years that have elapsed between two dates.

Returns (numeric): Number of years between p0 and p1. Difference is calendar years. If the first date is earlier than the second date, the value will be positive. If the first date is later than the second date, the value will be negative.

Examples:

(40)

Checks the first provided date to determine if it is greater than the second provided date. A tolerance can be set to account for minor differences.

P0 (date): First date field.

P1 (date): Second date field.

P2 (integer): Tolerance in milliseconds. The system date/time format is accurate to a ten-millionth of a second. Even dates that seem to be calculated at the same time will have a small difference. If the P0 date is only greater than the P1 date by less than the provided tolerance, it will not be considered a difference and the function will return false.

Returns (text): Returns "True" if the P0 date is greater than the P1 date by more than the P2 tolerance, if any. Returns "False" if the P0 date is less than or equal to the P1 date, or if it is greater but within the P2 tolerance.

Examples:

If P0 is 2014-10-28T18:16:12.001-04:00, P1 is 2014-10-28T18:16:12.002-04:00, and no tolerance is specified, returns "False" since P0 is less than P1.

If P0 is 2014-10-28T18:16:12.005-04:00, P1 is 2014-10-28T18:16:12.002-04:00, and no tolerance is specified, returns "True" since P0 is greater than P1.

If P0 is 2014-10-28T18:16:12.005-04:00, P1 is 2014-10-28T18:16:12.002-04:00, and the P2 tolerance is set to 10, returns "False" since P0 is greater than P1, but only by 3 milliseconds when the tolerance is 10 milliseconds.

l SeeIdentifying When Fields Have Changed After an Integrationfor a detailed description of change detection structures.

FirstOfTheMonth(p0)

Returns the date of the first day of the month for the provided date.

P0 (date): Enter the Code for the date field, enclosed in double square brackets.

Returns (date): The date of the first day of the month.

Example: FirstOfTheMonth([[2018-09-05]]) returns 2018-09-01. LastOfTheMonth(p0)

Returns the date of the last day of the month for the provided date.

(41)

Returns (date): The date of the last day of the month.

Example: LastOfTheMonth([[2018-09-05]]) returns 2018-09-30. DaysInPeriod(p0,p1,p2,p3)

Similar to the DateOverlap() function, this function compares two date ranges to determine if they overlap, counting the num-ber of days that are common between the two ranges.

P0 (date): Start date of the first date range

P1 (date): End date of the first date range

P2 (date): Start date of the second date range

P3 (date): End date of the second date range

Returns (numeric): Number of days that are included in both ranges. Note that the start and end dates are included in each range. Time of day is not taken into account. If there is no overlap, the function returns 0.

Examples:

If the first date range is from January 1stto June 30thand the second range is from June 15thto August 31st, the function returns 17, counting the overlapping days at the end of June.

If the first date range is from January 1stto January 31stand the second range is from January 10thto January 20th, the func-tion returns 11, since the full second range is included within the first range.

DateOverlap(p0,p1,p2,p3,p4,p5)

Similar to the DaysInPeriod() function, this function compares two date ranges to determine if they overlap, returning one value if they do, and returning a different value if they do not. If any of the four date fields are missing or invalid, theP5value (no over-lap) is returned.

P0 (date): Start date of the first date range

P1 (date): End date of the first date range

P2 (date): Start date of the second date range

P3 (date): End date of the second date range

(42)

P5 (matches type of field): The value to return if there is no overlap between the date ranges

Returns (any): Either the value entered asP4orP5. CurrentDateTime()

Obtains the current date and time from the server. No parameters.

Returns (date): The current Date and time in the full system format (2015-10-28T18:16:12.3313239-04:00). TodayXml()

Obtains the current date from the server. No parameters.

Returns (date): The current Date, formatted for use in other functions. TodayLong()

Returns (text): The current Date, in Long Date format. Example: Monday, June 15, 2011

TodayShort()

Returns (text): The current Date, in Short Date format. The date will be formatted according to the browser language settings at the time the field was last calculated.

Example: 15/6/2011 or 6/15/2011 AddHours(p0,p1)

(43)

P0 (date): Date field. The date must be in the system format, such as from a date picker field, the TodayXml() function, or any system dates.

P1 (integer): Number of hours to add (positive values) or subtract (negative values). Decimal values are not supported.

Returns (date): New date with adjusted time. The date itself will change if the hours cross into the next or previous days. AddDays(p0,p1)

Takes a provided date and adds a specified number of days.

P0 (date): Date field

P1 (numeric): Number of days to add

Returns (date): Date which is the addition of p1 days to date p0. AddMonths(p0,p1)

Takes a provided date and adds a specified number of months.

P1 (numeric): Number of months to add

Returns (date): Date which is the addition of p1 months to date p0. AddYears(p0,p1)

Takes a provided date and adds a specified number of years.

P1 (numeric): Number of years to add

Returns (date): Date which is the addition of p1 years to date p0. GetYear(p0)

Takes a provided date and returns just the year.

(44)

Example: If p0 = 15/10/2011, returns 2011. GetMonth(p0)

Takes a provided date and returns just the month.

Returns (numeric): Returns the month of p0, from 1 to 12 Example: If p0 = 15/10/2011, returns 10.

GetDayOfYear(p0)

Takes a provided date and returns the number of the day, counted from January 1st.

Returns (numeric): Returns the numeric day of the year from p0. Example: If p0 = 15/02/2010, returns 46.

GetDayOfMonth(p0)

Takes a provided date and returns the number of the day, counted from the first day of the month.

Returns (numeric): Returns the numeric day of the month from p0. Example: If p0 = 15/02/2010, returns 15.

GetMonthsFromCurrent(p0)

Takes a provided date and compares it to the current date, returning the number of months difference.

Returns (numeric): Number of calendar months from p0 to the current date. Dates earlier than the current date will return a pos-itive value, dates later than the current date will return a negative value.

GetDaysFromCurrent(p0)

(45)

Returns (numeric): Number of calendar days from p0 to the current date. Dates earlier than the current date will return a positive value, dates later than the current date will return a negative value.

GetYearsFromCurrent(p0)

Takes a provided date and compares it to the current date, returning the number of years difference.

Returns (numeric): Number of calendar years from p0 to the current date. Dates earlier than the current date will return a pos-itive value, dates later than the current date will return a negative value.

DateLong(p0)

Converts a provided date into the long date format.

Returns (text): Date p0 in long date format.

Example: If p0 = 15/06/2011, returns Monday, June 15, 2011 DateTimeLong(p0)

Converts a provided date and time into the long date and time format.

Returns (text): Date p0 in long date and time format.

Example: If p0 = 2014-12-19T14:45:00.0000000-04:00, returns Friday, December 19, 2014 2:45:00 PM. The output may display differently due to regional settings.

DateShort(p0)

Converts a provided date into the short date format.

(46)

Returns (text): Date p0 in short date format.

Example: If p0 = Monday, June 15, 2011, returns 15/6/2011 DateTimeShort(p0)

Converts a provided date and time into the short date and time format.

Returns (text): Date p0 in short date and time format.

Example: If p0 = 2014-12-19T14:45:00.0000000-04:00, returns 12/19/2014 2:45 PM. The output may display differently due to regional settings.

CustomDateFormat(p0,"{0:p1}")

Converts a provided date into a custom date format defined by codes.

P1 (text): String containing formatting codes.

Returns (text): Returns date p0 in format provided in p1.

l SeeCustom Date Format Functionfor a detailed description, a list of codes, and examples.

IsAbnValid(p0)

Validates a text field to determine if the content is a valid Australian Business Number (ABN).

P0 (text): Field to be examined

Returns (numeric): Returns "True" if the field contains a valid ABN, or returns "False" if the value is not valid for any reason (too short, contains letters/special characters, failed encoding check, etc.)

$GetUser()

(47)

No parameters.

Returns (string): The full first and last name of the user logged in at the time the calculated field is evaluated. $UserContainsRole(p0)

Checks the current user’s account to determine if it has a specific security role.

P0 (text): Name of security role

Returns (numeric): Returns "True" if current user account has role p0, returns "False" if it does not.

Note: This function should only be used within policy workflows. For claims workflows, please use the User-ContainsSecurityRole() function below instead.

l SeeVerifying User Security Rolesfor a detailed description of the function.

UserContainsSecurityRole(p0)

Checks the current user’s account to determine if it has a specific security role.

P0 (text): Code of security role

Returns (numeric): Returns "True" if current user account has role p0, returns "False" if it does not.

Note: This function should only be used within claims workflows. For policy workflows, please use the $UserContainsRole() function above instead.

l SeeVerifying User Security Rolesfor a detailed description of the function.

$IsNewBusiness(p0)

Checks if a provided submission, identified by transaction id, is new business.

P0 (numeric): Transaction ID number of the submission

Returns (numeric): Returns "True" if given transaction ID is new business, returns "False" if it is not. Compare(p0,p1,p2,p3)

(48)

P0 (text): The first source value for comparison.

P1 (text): The second source value for comparison.

P2 (text): The value to return if the comparison values are an exact match.

P3 (text): The value to return if the comparison values do not match exactly.

Returns (text): The value for eitherP2orP3, depending on whether the source values match or not. DetectChanges(p1,p1,...)

This function is used to determine if any changes have been made to one or more fields since the last time the function was eval-uated. This can be used to manage integrations that should only occur when critical data has changed, or to control complex func-tions that only need to be run when necessary.

The first time the function is evaluated, the value of each defined field is added to an internal table. This first instance is con-sidered a change, even if the fields are null or still contain default values.

Each time the function is evaluated after that, each field is compared to the stored value in the internal table. If the value has changed in any way, it is flagged as a change and the new value is stored in the table. If the value has not changed, the table is not updated for that field.

If multiple fields are being evaluated by the function, it returns True if any field has changed.

The function also stores the date that the change was detected, which can be retrieved with the ChangedOn() function, described below.

P1 (text):Enter the Codes for all fields to be evaluated. Multiple fields should be separated by commas, and each code should be in quotes.

Returns (boolean): Returns True if any of the defined fields have changed since the last time the function was evaluated, or returns False if none of the defined fields have been changed.

Example:

DetectChanges("FieldCode1","FieldCode2")

(49)

FieldCode2 is then modified, and then the function is evaluated again. The function returns True as one of the fields has been modified.

Neither field is modified, and the function is evaluated again. The function returns False as no changes have been made since the last time the function was evaluated.

ChangedOn(p1,p1,...)

The DetectChanges() function validates selected fields and records if the fields were changed, including the date and time that the change was detected. The ChangedOn() function is used to retrieve these date values.

Note that the dates are not when the actual change occurred, but rather when the DetectChanges() function identified that the field had changed.

The change dates are populated and updated by the DetectChanges() function, so the dates will not be available if DetectChanges() has not run yet, or they may be old dates if ChangedOn() is evaluated before DetectChanges().

P1 (text):Enter the Codes for all fields to check for dates. Multiple fields should be separated by commas, and each code should be in quotes.

Returns (date): Returns the most recent change date and time from the defined fields. Returns nothing if no change dates were found. The returned date is in the full system format, such as "2018-04-10T08:56:32-04:00".

Example:

DetectChanges("FieldCode1","FieldCode2") ChangedOn("FieldCode1","FieldCode2")

The first time the fields are evaluated, both fields are detected as changed and the ChangedOn() function returns the date and time that the changes were detected.

FieldCode2 is then modified, and then the functions are evaluated again. The change is detected and recorded, and the ChangedOn() function returns the date the change was detected forFieldCode2, as it is newer than the last date for

FieldCode1.

(50)

HashAndModifiedOn(p0,p0,p0,...,p1,p2)

Note: It is recommended to use the DetectChanges() and ModifedOn() functions (listed above) for any new configurations. The first time this function runs, it combines the content of all P0 fields, calculates a hash value (a unique value derived from the content), stores the hash value in the P1 field, and stores the date and time of the calculation in the P2 field.

Each time the function runs after the first time, it calculates the hash value for all fields then compares it to the previous hash value stored in P1. If the hash value has changed, meaning that at least one of the fields was changed since the last time the func-tion ran, the funcfunc-tion stores the new hash value in the P1 field and updates the date and time stored in the P2 field.

The date stored in the P2 field can be compared to another date to determine if any of the fields changed within a certain time period. The IsDateGreaterThan() function is useful for making the comparison.

Note: The date stored in the P2 field indicates the last time the function identified the changes. It does not reflect when the changes were made.

P0 (text): All fields to be included in the hash calculation should be provided, separated by commas.

P1 (Text Area): The Code of the field to contain the hash value. This will be an alphanumeric value with no meaning outside of this function, so the field should most likely be hidden. This condition is literal and must contain the Code of the field without any square brackets, no placeholders or functions can be used here.

P2 (text): The Code of the field to contain the last date and time that changes were detected. This condition is literal and must con-tain the Code of the field without any square brackets, no placeholders or functions can be used here. This should be a text field to ensure the full date and time are stored.

Returns (text): Returns the same hash value stored in P1.

l SeeIdentifying When Fields Have Changed After an Integrationfor a detailed description of change detection structures.

$CrossPolicyExactMatch(p0,p1,p3,p3,...) $CrossPolicyFuzzyMatch(p0,p1,p2,p3,p3,...)

(51)

P0 (text): This identifies the field containing the source value that the function will search for. The field Code should be provided, enclosed in square brackets.

P1 (text): This identifies the resource containing the stored data. The Code of the Cross-Policy Data Configuration should be provided, without any brackets.

P2 (integer): This is the tolerance, ranging from 0 to 100, and is only used for the $CrossPolicyFuzzyMatch() function. As the function compares the source value to the stored data, it calculates a percentage match score from 0 (no similarity at all) to 100 (exact match). The percentage must be equal to or greater than the tolerance value for the function to consider it a positive match.

P3 (text): These are optional filters to control what data will be searched within the Cross-Policy Data Configuration. The source value will only be compared against data that fits within all of the selected filters.

Each filter should be formatted as Filter=Value, and only one filter of each type can be used in each instance of the function, except where noted.

Filter Values

Product All, Current, Other Searches through data related to All products, the Current product, or all products Other than the current product. Policy All, Current, Other Searches through data related to All policies, the Current

policy, or all policies Other than the current policy. If this filter is not specified, it will be applied with the default value of Other.

Assured All, Current, Other Searches through data related to All clients, the Current cli-ent, or all clients Other than the current client.

(52)

PolicyTransaction All, Current, Other Searches through data related to All transactions, the Cur-rent transaction, or all transactions Other than the curCur-rent transaction. If this filter is not specified, it will be applied with the default value of Other.

PolicyTransactionStatus Quoted, Referred, Bound, UnderwritingRequired, Incomplete

Searches through data related to transactions in the selec-ted status. This filter can be applied multiple times with dif-ferent statuses.

Returns (text):

$CrossPolicyExactMatch() returns "True" if an exact match is found within the stored data. Returns "False" if no match is found.

$CrossPolicyFuzzyMatch() returns "True" if data is found that has a percentage match score that equals or exceeds the tolerance. Returns "False" if no data matches closely enough.

l SeeSearching Across Policiesfor a detailed description of these functions, including examples.

Note: The Cross Policy Match functions use the Q-gram Index search algorithm by default. To change this to the Soundex search algorithm, please contact your Insurity representative.

$CrossPolicyExactMatchList(p0,p1,p3, p3,..., return=p4|p4|..., p5) $CrossPolicyFuzzyMatchList(p0,p1,p2,p3,p3,..., return=p4|p4|…, p5)

Used with a Cross-Policy Data Configuration, these functions take a value from the current transaction and compare it to stored values from other transactions. The functions return a custom list of values if they find an exact match ($CrossPoli-cyExactMatchList()) within the stored data or data that is similar within a certain tolerance ($CrossPolicyFuzzyMatchList()). These functions can be used to provide data to other functions, such as NewGrid or SaveToGrid.

(53)

P1 (text):This identifies the resource containing the stored data. The Code of the Cross-Policy Data Configuration should be provided, without any brackets.

P2 (integer):This is the tolerance, ranging from 0 to 100, and is only used for the $CrossPolicyFuzzyMatchList() function. As the function compares the search value to the stored data, it calculates a percentage match score from 0 (no similarity at all) to 100 (exact match). The percentage must be equal to or greater than the tolerance value for the function to consider it a positive match.

P3 (text):These are optional filters to control what data will be searched within the Cross-Policy Data Configuration. The search value will only be compared against data that fits within all of the selected filters.

Each filter should be formatted as Filter=Value, and only one filter of each type can be used in each instance of the function, except where noted.

Filter Values

Product All, Current, Other Searches through data related to All products, the Current product, or all products Other than the current product. Policy All, Current, Other Searches through data related to All policies, the Current

policy, or all policies Other than the current policy. If this filter is not specified, it will be applied with the default value of Other.

Assured All, Current, Other Searches through data related to All clients, the Current cli-ent, or all clients Other than the current client.

Distributor All, Current, Other Searches through data related to All distributors, the Cur-rent distributor, or all distributors Other than the curCur-rent distributor.

(54)

transaction. If this filter is not specified, it will be applied with the default value of Other.

PolicyTransactionStatus Quoted, Referred, Bound, UnderwritingRequired, Incomplete

Searches through data related to transactions in the selec-ted status. This filter can be applied multiple times with dif-ferent statuses.

P4 (text):These parameters are used to define the list of fields and values to be returned for each transaction that matches the search value.

The list must be preceded by the return= text, followed by each field separated by pipe | characters.

To return the values from fields within the transactions, enter the Code for each field, without any brackets. Note that all fields to be returned must be included in the Cross-Policy Data Configuration as Associated Fields.

Two keywords are also available to return information about the transaction itself. These keywords should be entered like the field codes, without any brackets.

l TransactionID returns the ID of the transaction.

l For fuzzy match searches, Similarity returns the match score.

Note: A maximum of 50 fields and values can be returned.

P5 (integer):This parameter is used to restrict how far back the system will search. Enter a number of days, and the system will only search transactions with a Last Modified Date within that period.

For example, enter 7 to search transactions modified within the last 7 days.

Returns (text):

$CrossPolicyExactMatchList() returns allP4values for each transaction containing an exact match for the search value. Does not return anything if no match is found.

(55)

l SeeSearching Across Policiesfor a detailed description of these functions, including examples.

Note: The Cross Policy Match functions use the Q-gram Index search algorithm by default. To change this to the Soundex search algorithm, please contact your Insurity representative.

ValueExists(p0,p1)

Used with Field Indexing, this function takes a value from the current claim and compares it to stored values from other claims.

P0 (text): This identifies the field containing the source value that the function will search for. The field Code should be provided, enclosed in square brackets.

P1 (text): This identifies the index containing the stored data. This can be the Code for a single indexed field, or an Alias for mul-tiple indexed fields. This value must be provided without any brackets.

Returns (text): Returns "true" if a match is found within the stored data. Returns "false" if no match is found. Examples:

ValueExists([[FieldCode]],Code)

This function will search through the indexed field "Code" for the text found in the[[FieldCode]]field. ValueExists([[FieldCode]],AliasName)

This function will search through all indexed fields with the "AliasName" alias for the text found in the[[FieldCode]]field. IsNull(p0)

Determines if a specific field is empty.

P0 (any): The field to be evaluated.

Returns (boolean): Returns True if the field value is null or an empty string. Returns False if the field contains any data of any type.

IsNotNull(p0)

Determines if a specific field contains any data.

(56)

Returns (boolean): Returns True if the field contains any data of any type. Returns False if the field value is null or an empty string.

IsGridEmpty(p0)

Takes the Code of a grid to determine whether that grid contains data.

P0 (text): Enter the Code for the grid to be evaluated.

Returns (boolean): Returns True if the grid is empty, or False if the grid contains data. IsNumeric(p0)

Determines if a specific value is a number.

P0 (any): The value to be evaluated. This can be a field placeholder, function, or formula.

Returns (boolean): Returns True if the value is a number, including 0. Returns False if the value is null, an empty string, or if it con-tains any non-numeric characters.

Periods and commas are recognized as decimal separators, while commas are also recognized as thousands separators. NextPolicySequenceNumber()

Retrieves the next sequence number, as it appears in the Next Sequence Number field in the Master Cover - Policy Num-bering page.

No parameters.

Returns (numeric): Returns the next sequence number. GetAndIncrementSequenceNumber(p0)

Retrieves the next sequence number from a sequence number configuration and then increments the sequence number by 1.

P0 (text): The Code of the sequence number configuration.

Returns (numeric): Returns the next sequence number.

(57)

If the function is called from a transaction whose master cover is in live mode, the number from the configuration’s Live - Next Sequence Number field is returned.

Note: The function will retrieve and increment the number every time it is evaluated. Conditional structures, such as an If state-ment or Field Evaluation Rule, can be used to control when the function is evaluated.

$GetTermStatus(p0)

Retrieves the current status of the provided submission or policy, identified by transaction id.

P0 (numeric): Transaction ID number of the submission or policy

Returns (text): Returns the current status of the submission or policy. $GetTransactionType(p0)

Retrieves the current type of the provided transaction, identified by transaction id.

Returns (text): Returns the current type of the transaction. $GetTransactionStatus(p0)

Retrieves the current status of the provided transaction, identified by transaction id.

Returns (text): Returns the current status of the transaction. $GetTermNumber(p0)

Returns the sequential term number of the provided transaction.

P0 (numeric): Transaction ID number of the submission. The [[SubPolSystemID]] placeholder can be used to automatically insert the Transaction ID of the current transaction.

Returns (numeric): Returns the number of the current term.

(58)

Returns the next adjustment number in line for the term.

[[SubPolSystemID]]: This is a placeholder that automatically inserts the transaction ID for the current transaction. This parameter should not be changed.

Returns (numeric): Returns the number that will be assigned to the next bound adjustment in the current term.

Example: In a newly created term with no adjustments, this function returns 1. If 3 adjustments have been bound in the cur-rent term, this function returns 4.

$NextEndorsementNumber([[SubPolSystemID]])

Returns the next endorsement number in line for the term.

[[SubPolSystemID]]: This is a placeholder that automatically inserts the transaction ID for the current transaction. This parameter should not be changed.

Returns (numeric): Returns the number that will be assigned to the next bound endorsement in the current term.

Example: In a newly created term with no endorsements, this function returns 1. If 3 endorsements have been bound in the current term, this function returns 4.

$TotalGrossPremiumAmount()

Returns the total gross premium for the current quote. No parameters.

Returns (numeric): Returns the combined total of all premium types included in the current quote. $TotalCommissionAmount()

Returns the total calculated commission for the current quote. No parameters.

Returns (numeric): Returns the combined total commission from all premium types included in the current quote.

Bridge Specialty Suite

Table of Contents

Introduction

Building Formulas

Operators

Simple Arithmetic Formulas

Placeholders Within Formulas

Defining String Data

Concatenation (Combining Data)

Adding Comments to Formulas

Placeholders

Current Transaction Information

Premium Details

Commission Details

Tax Details

Current Term Information

Premium Details

Commission Details

Tax Details

Term Period Dates

Previous Term Information

Premium Details

Tax Details

Policy Number

Limits

Deductibles

Functions

Defining Multiple Fields in a Function

Conditional Results – the IF Function

The If/Then Conditional Structure

The $If() Function

Defining the Results

Sequential Conditions - the MapValue() function

Conditional Selection of Grid Rows - the Where() function

Building Conditional Expressions

Operators

Negative Conditions

Combined Conditions

Working with Boolean Values

Full Function Reference List