3.1 - 3.8 - Using Conditions

Overview

ProcessMaker uses conditions in a number of different situations to determine whether execution happens or not. Conditions evaluate to either true or false, based upon the Boolean logic found in PHP. Conditions can be defined for steps (Dynaforms, Input Documents, Output Documents, and triggers), Evaluation and parallel gateways, and events.

Additionally, conditions can be created to show or hide elements in a Dynaform using JavaScript's Boolean logic.

Understanding Conditions

Conditions in ProcessMaker are based upon Boolean logic, which is the idea that any expression can be evaluated to either a value of True or False. If the expression is True, then execution will occur. If it is False, no execution will occur. In ProcessMaker, a condition can take many forms. These are all valid types of conditions:

Condition	Description
3124.5	A floating point number that evaluates to true
"hello world"	A string that evaluates to true
false	The boolean value of false
@@ContactType	A case variable
@%Total == 400	Equality comparison with an integer
"check" === @@PaymentType	Equality comparison between strings
@@USR_USERNAME != "admin"	Non-equality comparison between strings
@#InvoiceAmount > 100.00	Greater than comparison with a floating point number
max(@#Invoice, @#TotalBill) < 1000	Less than comparison with the return value of a function
(@#Price - @#Discount) * @%Quantity <= 3000	Less than comparison with a mathematical operation using () to prioritize elements
(@#Amount >= 5000.00 and @@priority == "high")	Two comparisons joined by AND
((@@contact=="sales" or @@contact=="lead") and !(@@priority=="high"))	Logical OR, AND, NOT using () to prioritize elements

Variables in Conditions

Conditions can contain system or case variables, which are preceded by an @ sign, and then another symbol that indicates how the variable is parsed:

Variable Type	Description
@@variable_name	The variable will be parsed as astring. If originally another type, it will be converted to a string. So -1, 0 and 12.45 become "-1", "0" and "12.45", respectively.
@%variable_name	The variable will be parsed as an integer (a whole number). If originally another type, it will be converted to an integer. A real number will be converted to a whole number, so 12.45 becomes 12. A string that contains numbers will be converted to a whole number, so "655" and "34.19" become 655 and 34, respectively.
@#variable_name	The variable will be parsed as float type (a real number with decimals).
@=variable_name	The variable will not be changed and is parsed as its original type.

 

Case variables are variables that hold information about a case and are created either when a field in a Dynaform is submitted or when defined in a trigger. Variable names must start with either a letter or underscore and are case sensitive, so @@_myvar, @@myvar, @@MyVar, @@MYVAR, and @@myvar2 are five different variables. Make sure to spell case variables exactly like their field names in Dynaforms or how they were defined in a trigger.

Conditions can NOT contain local or global PHP variables that were defined in triggers, but they can use PHP's superglobal variables, such as $_SERVER['SERVER_ADDR'] and $_ENV['PATH'].

If a condition only contains a variable (and nothing else), then the value of the variable will be examined and evaluated to true or false. In PHP, a value is only considered false when it is one of the following values:

Value	Description
FALSE	The boolean value of false
0	An integer zero
0.0	A float zero
""	An empty string
"0"	A string with a value of zero
array()	An array with zero elements
new StdClass()	An object with zero member variables
NULL	A special value meaning "no value"

All other values in PHP are considered true. For example, all of these values are considered true:

Value	Description
TRUE	The boolean value of true
97	A positive integer
-4	A negative integer
100.99	A positive float
-4.23	A negative float
"a nice string"	A non-empty string
array("jack", "jill", "hill")	A non-empty array

Comparison Operators in Conditions

If a condition contains a comparison operator, such as equals, greater than or less than, then the values to the right and left of the operator will be compared and evaluated to true or false. The following comparison operators are available in PHP:

Operator	Description	Example
==	Equals	@@CurrencyType == "dollars"
===	Equals to same variable type	@%Total === 100
<>	Not equal	@@CurrencyType <> "euros"
!=	Not equal	@%Total != 0
!==	Not equal to same variable type	@=RunTest !== false
<	Less than	@%Total < 1000
<=	Less than or equal to	@#SubTotal <= @#Total
>	Greater than	@#Balance > 0
>=	Greater than or equal to	pow(@#Total, 3) >= @#Limit

Type Conversion

It is generally a good idea to use the correct type of variable when doing comparisons, so if comparing to a string, use @@variable_name. If comparing to an integer, use @%variable_name. If comparing to a floating point number, use @#variable_name. If comparing to a boolean value, an array or an object, use @=variable_name. Nonetheless, if the types don't match, PHP will try to convert both values to the same type before doing the comparison. Due to type conversion, the following conditions are all considered true:

True Condition	Description
"42" == 42	The string "42" is converted into the integer 42, then compared.
" 42 " == 42	The string " 42 " is converted into the integer 42 (spaces are ignored), then compared.
"42 frogs" == 42	The string "42 frogs" is converted into the integer 42, then compared. Only strings starting with numbers can be converted into integers or floats.
42 == 42.0	The integer 42 is converted into the float 42.0, then compared.
0 == false	The integer 0 is converted into the boolean FALSE, then compared.
42 == true	The integer 42 is converted into the boolean TRUE, then compared.
"" == false	The empty string "" is converted into the boolean FALSE, then compared
"hello" == true	The string "hello" is converted into the boolean TRUE, then compared.

 

To prevent the comparison from converting value types, use the === and !== operators, which will only evaluate to true when comparing the same types of values, so "42"==42 is true, but "42"===42 is false.

While automatic type conversion can be useful, remember that conversion will not round numbers, nor will it truncate strings. Here are a number of solutions to common problems in conditions:

False Condition	Problem	Solution	Examples
42 == 42.1	The integer 42 is converted to the float 42.0, which doesn't equal 42.1, so the condition evaluates to false.	Use the (int) type cast or the @% variable parsing to convert a float into an integer.	42 == (int) 42.1 42 == @%Total
42 == (int) 41.999	When the float 41.999 is converted to an integer, all decimal numbers are simply dropped and there is no rounding up, so the comparison is 42 == 41.	Use PHP's round() function to round to the nearest integer. Also use the ceil() and floor() functions to round a number up or down.	42 == round(41.999) 42 == round(@#Total)
5 / 2 == 2.5	This is false, because the integer 5 is divided by the integer 2. Since both are integers, the result is the integer 2 (the remainder is dropped). Then, the integer 2 is converted to the float 2.0 to compare with 2.5.	Use the type cast (float) or reference the variable as @# to convert one of the numbers to a float before dividing. This will cause a floating point division, so the remainder won't be lost.	5 / (float) 2 == 2.5 5 / @#var == 2.5
42.12 == 42.123	For two floats to be equal, their decimal numbers must also be equal.	Specify the number of decimal points to round to before comparing.	42.12 == round(42.123, 2) 42.12 == round(@#Total, 2)
"hel" == "hello"	The condition is false, because strings have to have the same number of characters to be equal.	Use PHP's substr() function to cut the string to a set number of characters before comparing. To compare a variable number of characters use the strlen() function. To look for a string inside another string, use the strstr() function.	"hel" == substr("hello", 0, 3) "hel" == substr(@@s, 0, 3) @@s1 == substr(@@s2, 0, strlen(@@s1)) strstr(@@s, "hel")
"hello" == " hello "	The condition is false, because PHP doesn't eliminate spaces when comparing strings.	Use PHP's trim() function to eliminate any whitespace (including tabs and returns) from the beginning or end of a string. Also use ltrim() or rtrim() to only eliminate from the beginning or end of a string.	"hello" == trim(" hello ") "hello" == trim(@@Greet)
"HeLlO" == "hello"	The condition is false, because the comparison of strings is case sensitive.	Use strtoupper() or strtolower() to convert the strings to the same case, or use strcasecmp() or strncasecmp() to do case insensitive comparisons.	strtolower("HeLlo") == "hello" strtoupper(@@s1) == strtoupper(@@s2) !strcasecmp(@@s1, @@s2)

Math in Conditions

Conditions can use PHP's mathematical operators, such as - (negation), + (addition), - (subtraction), * (multiplication), / (division), % (modulus, i.e., division remainder). When using mathematical operators, keep in mind the rules of operator precedence and remember to use parentheses to evaluate certain elements before other elements in the expression.

To do more advanced mathematical operations, use PHP's math functions, such as pow(), max(), min(), sin(), cos(), log(), abs(), etc.

Logical Operators in Conditions

Conditions can also use logical operators to join together multiple expressions and construct complex conditions.

 

Operator	Example	Description
and	(@@a and @@b)	True if both @@a and @@b are true.
&&	(@@a && @@b)	True if both @@a and @@b are true. && is like the and operator, but it has a higher operator precedence.
or	(@@a or @@b)	True if either @@a or @@b is true.
||	(@@a || @@b)	True if either @@a or @@b is true. || is like the or operator, but has a higher operator precedence.
xor	(@@a xor @@b)	True if either @@a or @@b is true, but not both.
!	!@@a	Reverses the outcome, so true becomes false and false becomes true.

Like true and false, the spelling of the and, or, xor operators is case insensitive, so and can also be spelled as And, AnD, AND, etc.

Warning: If using the logical operators AND, OR, XOR, &&, || in a condition, it is recommended to enclose the statement inside parentheses () to ensure that the entire statement is evaluated and not just the first part of the statement. It is also recommended to use && and || instead of AND, OR, XOR. In recent versions of ProcessMaker, the following condition:

@@myvar != "X" AND @@myvar != "Y"

is evaluated as:

@@myvar != "X"

To ensure that the entire statement is evaluated, enclose it in parentheses:

(@@myvar != "X" AND @@myvar != "Y")

Strings in Conditions

Most data entered into Dynaform fields is stored as strings, so it is useful to know how to handle strings in ProcessMaker.

All strings must be enclosed in either single quotes '...' or double quotes "...".

Single quotes treat the enclosed string as plain text, meaning that none of the characters in the string will be interpreted as an escape character. In double quotes, escape sequences are interpreted along with any variables, and will be replaced by their values. For instance, in double quotes \t is interpreted as a horizontal tab.

• Variables in Strings: Unlike normal PHP variables, which can be inserted inside double quoted strings, such as "I say $greeting to you" or "Give {$arrayNames['manager']} the letter", ProcessMaker case variables cannot be inserted inside double quoted strings, so "I say @@Greeting to you" will NOT work.

• Concatenate strings: PHP uses the dot operator "." to concatenate strings. For example: "Hello" . " " . "World!" evaluates to "Hello World!".
  People coming from other languages commonly try to write "Hello" + " " + "World!", but PHP only uses the + operator for adding integers and floats, so it will try to convert each string into an integer or float and then add them together.
  If the string starts with a number (such as '42 is the answer' or " 3.5 duckies"), then it will be successfully converted to an integer or float. Otherwise, the string will become zero, so "Hello" + " " + "World!" becomes 0 + 0 + 0

• Concatenate strings and ProcessMaker variables: ProcessMaker system and case variables can be concatenated. Remember to reference them as @@variable_name, so they will be parsed as strings:

  • "Hello " . @@USR_USERNAME
  • @@FirstName . ' ' . @@LastName

• Comparing Strings: For the condition to be correctly evaluated when comparing strings, the triple-equals operator === must be used. The use of == is not recommended because of unpredictable results.

  @@USER_LOGGED === "00000000000000000000000000000001"

  

Operator Precedence in Conditions

A condition is evaluated according to the rules of operator precedence, so certain operators will be executed before other operators.

For example, how does ProcessMaker know whether 2 + 3 * 4 equals 20 or 14? If addition has precedence over multiplication, then first 2 + 3 = 5, then 5 * 4 = 20. If multiplication has precedence, then first 3 * 4 = 12, then 2 + 12 = 14. Since ProcessMaker uses the PHP rules of operator precedence, multiplication has higher precedence than addition, so the result is 14.

In the following table, the operators are ordered according to their precedence, with the highest precedence at the top. So parentheses "()" have the highest precedence and commas "," have the lowest.

Operators	Description
( )	Groups elements to give them highest precedence.
[ ]	Accessess an element in an array or a character in a string
++ --	Increment or decrement operator
- (type)	Negation, Type casting such as (int), (float), (string), (boolean), etc.
!	Logical NOT (inverse of true or false)
* / %	Multiplication, division, modulus
+ - .	Addition, subtraction, string concatenation
< <= > >= <>	Greater than, less than, not equal to
== != === !==	Equal, not equal, equal same type, not equal same type
&&	Logical AND
||	Logical OR
? :	Ternary operator for constructing if-then-else statements
= ^= <<= >>= =>	Assignment operators
and	Logical AND
xor	Logical XOR
or	Logical OR
,	Commas separate parameters in function calls and elements in arrays

 

If operators have the same precedence, then they are parsed from left to right. For example, in the expression 5 - 6 / 2 . " for you!", division has the highest precedence so 6 / 2 will happen first. Subtraction and string concatenation (which is the "." operator) have the same precedence, therefore the leftmost operator, which is subtraction, will happen first followed by concatenation. Here is the order of operation:

• 6 / 2 = 3
• 5 - 3 = 2
• Integer 2 converted into the string "2", then: "2" . " for you!" = "2 for you!"

To change the order of operations, place parenthesis around elements to give them the highest precedence. For example, the expression @#Price - @#Discount * @%Quantity can not be used to calculate the total price, because the discount needs to be subtracted before multiplying by the quantity. Therefore parentheses can be used to first subtract, then multiply: (@#Price - @#Discount) * @%Quantity

Parentheses can be nested as many times as necessary. For example: ((@#Price - @#Discount) * @%Quantity) * @#TaxRate

Parentheses can be useful when combined with "!" (logical NOT) to take the inverse of a comparison. For example, in the expression !(@%Amount > 1000), if the amount is greater than 1000, then true would be inverted to false by the ! operator.

When in doubt about the precedence, it is a good idea to use parentheses, because it makes the precedence explicit and the code is easier to understand.

Conditions with Dynaform Fields

When a Dynaform is submitted, a case variable is created for each of the fields contained in the Dynaform. These case variables can be used later in the process and added to the conditions.

Textboxes and Suggest Boxes

Textbox and suggest box values are stored as strings so they can be referenced in conditions as @@field_name. For example, a datetime control named "datetime_1" might have a condition to only displays the current date if the user fails to fill out a textbox named "textVar" and a suggest box named "suggestVar".

To recreate this example, first create the Dynaform shown in the image below before placing the condition.

This Dynaform contains the following controls:

Control Type	ID	Label	Variable Name
Textbox	textVar	text_1	textVar
Suggest Box	suggestVar	suggest_1	suggestVar
Datetime	datetimeVar	datetime_1	datetimeVar
Dropdown	dropdownVar	dropdown_1	dropdownVar

Then, create a trigger by going to the Process Objects toolbox. Locate the Triggers option, hover the pointer of the mouser over the plus (+) sign and click on the Create button.

In the Create Custom Trigger window, place the following code inside the Code box.

Click on the Save button to store the trigger.

Add the Dynaform and the trigger as steps in one of the tasks by right clicking on the task and selecting Steps.

Drag and drop the trigger where it needs to go, then click on the Condition button as seen in the image below.

The Condition Trigger window will be displayed where the condition code can be added.

When the case runs, the trigger will be executed successfully, as seen in the image below. If the "text_1" (variable: @@textVar) and "suggest_1" (variable: @@suggestVar) fields are empty then the current time will be shown in the "datetime_1" field.

Textareas

Reference textareas as @@field_name in conditions. Textareas can have multiple lines of input; therefore, conditions can use the strlen() function to count the number of characters, and/or the count() and explode() functions to find the number of hard returns in the string. The conditions can either be:

or

As an example, use the first condition as seen in the image below:

The condition dictates that if the text introduced in the "textarea_1" control (variable: @@textareaVar1) has a length of more than 10 characters, then the trigger created in the Textboxes and Suggest boxes example will be fired. Remember that this trigger shows the current date in the "datetime_1" control.

If the textarea_1 control has less than 10 characters, then the "datetime_1" control will not show anything. Observe the images below:

Datetime

Datetime variables are stored as strings in the format "YYYY-MM-DD HH:MM:SS", such as "1999-01-01 01:01:01" or "2010-12-31 23:59:59". If the datetime field doesn't include the hours, minutes and/or seconds in the format property, then these portions will be set to zeros. The @@datetime_label variable will hold the value of the datetime in the configured format for the field.

For example, if the format is set to "MM/DD/YYYY" for a datetime field associted with the "startDate" variable, then @@startDate might hold a value such as "2017-12-28 00:00:00" and @@startDate_label would be set to "12/28/2017". Likewise, if the format is "DD-MM-YYYY HH:mm", then @@startDate might have a value such as "1998-05-25 09:35:00" and @@startDate_label would be 25-05-1998 09:35".

Because dates are stored as strings, they should be accessed as @@field_name. For simple comparisons, dates in standard "YYYY-MM-DD" format can be compared as strings.

However, advanced comparisons require that dates be converted to PHP timestamps with PHP's strtotime() function. For example, set this condition to only display the Dynaform if the current date doesn't exceed the due date of the case plus 10 days.

To make calculations between dates, it is advisable to use the DateTime::add function.

Checkboxes

By default, checkbox fields are stored as arrays with values of:

Array ( 1 )	If checked
Array ( 0 )	If unchecked

Therefore, a condition that verifies that a control named "checkboxVar1" was checked will look like:

For example, add the condition shown above to the trigger created in the Textboxes and Suggest boxes example, so the trigger will only be fired if the checkbox is checked.

So when running a case, if the checkbox control has been clicked, as seen in the image below:

The condition will fire the trigger that sets the current date in the datetime control.

Dropdowns and Radiogroups

These controls store the value (not the label) of the selected option. Generally, dropdown boxes and radiogroups are accessed as @@field_name, but if the values of the options are integers, they can be accessed as either @@field_name or @%field_name. Due to automatic type conversion, @%var == 2 or @@var == 2 mean the same thing and both would work. Examples:

To check for the label (not the value) of the selected option in a dropdown box, then check the option Save label of selected value in variable when defining the dropdown box. Then reference it as @@field_name_label. Example:

For example, add the following condition to a trigger where one of the options in the dropdown is the condition for the trigger to be executed.

Choose the option added to the trigger.

And the trigger, which will show the current date, will be executed.

Checkgroups

Checkgroups store the values of the selected options as an array and the labels of the selected options are stored as an array in a JSON string in another case variable with the same name as the checkgroup with "_label" appended to the end. Unlike dropdown boxes, which require one selected option, checkgroups allow zero, one, or multiple options to be selected.

For example, a checkgroup whose variable is named "ContactOptions" has the following 4 options:

If the "Phone" and "Other" options are selected, then the @@ContactOptions variable will have the following value: array(2, 4)

And, the labels of the selected options will be stored in the @@ContactOptions_label variable, which is a JSON string holding an array of the selected labels:

'["Phone","Other"]'

To deal with situations where more than two options might be selected, it is recommended to search for a value in the array using the in_array() function.

To search whether the option "Phone" was selected in the "ContactOptions" checkgroup, first it is necessary to know its value. The option "Phone" has the value "2", therefore, the condition will be:

To search whether the option "Phone" was NOT selected, then use ! (Logical NOT):

To search for multiple values, then the first parameter of in_array() should be an array of the values to be found:

If the user wants to search if the option "Fax" was selected using the labels of the selected options, use the json_decode() function.

Use count() to count the number of selected options. For example, to check whether more than one option was selected:

Files

File fields store the filename of the uploaded file as a string. For example, the following condition can be used to check whether a file was uploaded with the empty() function or whether the file extension is not a "doc" type:

If the condition seen in the image below is added to a trigger using the empty() function.

If the file control is empty, then the trigger will be fired and the current date will be shown in the datetime control, as shown in the image below.

Grids

A grid is stored in a case variable as an array of associative arrays, so it has to be referenced as @=field_name, where the field name of the grid object in a master form is used. The counting of objects in the array starts from the number 1 (not 0 like a normal array). Each row is stored as an associative array where the grid field names are the keys and the entered data are the values.

Check how many rows are in a grid by using the count() function. For example, to check whether the "Products" grid has more than 3 rows:

It is not a good idea to reference a particular grid row in a condition, because an error will be generated if the row doesn't exist. Instead, wrap the condition inside a ternary operator, which first checks whether the row exists.

For example, to check whether the Price field in the first row in the Products grid is greater than 100, first check if the row exists with the count() function. If it exists, then check the value of the first Price field; otherwise return false.

If unsure whether the grid form was submitted, it is a good idea to first check whether the grid case variable exists with isset(). For example, to check whether the Imported Yes/No checkbox in the first row of the Products grid is marked "Yes" (which has a value of 1):

The condition first checks whether the grid exists, then it checks whether there is at least one row in the grid and finally checks whether the "Yes" option was selected in the Yes/No box (Yes is 1, No is 0).

To check whether any of the Price fields in any of the rows is greater than 100, it is recommended to fire a trigger before the condition that passes through all the rows in the grid and assigns the return value to a case variable that could be checked in the condition. For example, use the following trigger:

Then use the following condition:

Setting Conditions

Conditions can be set for a number of different elements in ProcessMaker.

Conditions for Triggers

Setting a condition for a trigger is similar to setting conditions for other types of steps. First, assign the trigger to fire at a particular point in a task. Then right click on the task in the process map and select the Steps option from the dropdown menu.

When the Steps for the task window is opened, add a trigger as a step. Then click on the Condition button.

When the Condition Trigger window is opened, there is a section where a condition for the execution of the trigger can be added. This condition will work as an IF for the trigger's execution. Notice that case and system variables can be added by clicking on the @@ button.

After clicking on the @@button, the Process Variables window will be displayed, where case variables and system variables can be found and added to the condition.

After a condition has been added to the trigger, the Condition button will have an asterisk next to it, letting the user know that the trigger has a condition that needs to be met before it fires.

Conditions in Routing Rules

Routing rules can use conditions to decide which paths to follow in a process.

A condition can be set for each path. If the condition evaluates to True, then the next task on that path will be executed. If False then the next task (and any subsequent tasks on the same path) will not be executed. If the condition on a routing rule is left blank, then the condition will evaluate to True and the next task on the path will be executed.

Add a condition to a gateway by right clicking on it and then selecting the Properties option.

A new window will open where the conditions of the gateway's routing rules can be set.

Set the conditions for the routing rule under the Condition section. Make sure that at least one of the conditions will evaluate to true, otherwise an error will be thrown and the process will stop at that point. Also remember that the routing rules of a gateway can be prioritized, read this documentation for more information.

Conditions for ProcessMaker Mobile

To restrict the execution of triggers or steps according to the environment where the case is being run, it is possible to set the following conditions.
To restrict a trigger or step to work only with ProcessMaker Mobile, assign the following condition:

To restrict a trigger or step to work only with ProcessMaker Desktop Version, then assign the following condition:

Errors in Conditions

It can be difficult to debug problems in conditions, so it is recommended to run cases with the Debugger activated. As a case progresses, examine the values of the case and system variables used in the conditions and verify that the conditions are testing for the right values.

If there is a syntax error in a condition, an error message will appear to indicate the problem while running cases.

If ProcessMaker encounters a case variable that doesn't exist or hasn't yet been defined in the process when evaluating a condition, then it gives no indication of the problem. Instead, it inserts a value of "" (an empty string) in place of the variable and evaluates the expression. This kind of problem can be very hard to debug, because the case continues to run without giving any indication of a problem.

If all of the conditions of an exclusive or inclusive gateway evaluate to false and there is no available default flow, then the process stops and the following error message appears:

Fix the conditions so at least one of them will always evaluate to true.

Common Condition Problems

These are some common problems when designing conditions:

• Misspelled variable names. Remember that variable names are case sensitive and must be spelled exactly as defined (either in the field names in Dynaforms or as case variables in triggers).

• Using a case variable in a condition before it has been created in the process. Do not use a case variable in a condition if it is created later in a Dynaform field or in a trigger.

• Using a case variable from a Dynaform field whose data may not have been submitted in a condition. By default, clicking on the Next Step link in a Dynaform will not save the data, so no case variables will be created for each DynaForm field. To fix this problem, set the Next Step Link property for Dynaforms to the "Save & Continue" option, so the data will automatically be saved when the user clicks on the Next Step link. If it is necessary to give the user the choice to save the Dynaform data or not, then fire a trigger AFTER the Dynaform that will create case variables for each of the fields that are used in subsequent conditions. The trigger code would be:

• When comparing strings, remember to use the same case and the same spacing. "HeLlO" does not equal "hello", and " hello " does not equal "hello". If comparing text entered by the user, it is a good idea to eliminate surrounding spaces with the trim() command and convert all input to either upper or lowercase with strtoupper() or strtolower(). For example:

 trim(strtoupper(@@Department)) == "FINANCE"

If searching within text entered by the user, consider using preg_match(). For example:

• In PHP, = is used for assignment, whereas == or === is used for equality. The condition @%ExpenseType = 3 will always evaluate to true, because the integer 3 is being ASSIGNED to the variable rather than testing for equality. Instead, use the condition @%ExpenseType == 3 to check if @%ExpenseType is equal to the integer 3.