Free-Form Rule Writing

What makes inLOGIC so powerful is that it allows you to write compensation rules no matter how complex they are. The Free-Form Rule Writing is too important to ignore when you are selecting a software, because this feature determines whether you will have the full control over implementation of your business requirements.

Using a Plan and Measurement Wizard, you can write Qualification, Credit and Plan rules.

Since it gives you the complete freedom to build your own rules, it is very important to write them seamlessly aligned with your Sales Compensation Plans and Policies.

Well-written rules, given the source data is not corrupted, should give you the accurate and precise results for a given period. In order to write a good rule, you need to know a little bit of the convention how to write an acceptable rule within inLOGIC. Although you are not required to learn the whole complexity of the programming language, learning the following common and basic usages, you will be able to maximize the performance of inLOGIC at a higher level.

Art vs. Math

Rule writing is the Art of combining Attributes with appropriate Operators, Symbols, and/or other attributes available. Depending on how you configure your application, variables available vary. Your will find those in the Measurement or Plan Wizard. Using these elements and making up possible combinations can truly be considered as the Art rather than Math.

Operators

Type	Name	Function
||	Double pipe	OR (A or B)
&&	Double ampersand	AND (A and B)
==	Double equal sign	EQUAL TO (A==1,000)
!=	Exclamation point + Equal	NOT EQUAL TO (A!=B)
in	In	If value exists listed in the specified parameter, it returns the value.
not in	Not in	If value exists out of the specific parameter, it returns the value.
< >	Angle brackets	Less than or Greater than
><=	Angle bracket + Equal	Less than or equal to
>=	Angle bracket + Equal	Greater than or equal to
Function	Table	Table
+	Plus	Addition
–	Minus	Subtraction
*	Asterisk	Multiply
/	Slash	Division
%	Percent	Remainder (or modulus)

This will give you 100 percent satisfied results and also is safe order cialis uk to use. Eat a balanced diet, drink lot of liquids, cut down intake of caffeine, quit smoking, get sufficient rest, and exercise on a regular basis, are more likely levitra 40 mg check to suffer from erectile dysfunction. Mental issues likewise improve the probability that individuals will settle lowest priced tadalafil on poor behavioural decisions which can add to physical issues, for example, coronary illness, ulcers, and colitis. Potential treatments levitra 20mg price should also be compared before a selection is made.

Symbols

Type	Name	Function
( )	Parentheses	( ) can be used when determining the order of operations e.g. (3+5)*10=80 vs. 3+(5*10)=53
[ ]	Square brackets	[ ] can be used when expressing indexes of a collection of data e.g. [startDate >= ‘2014-01-01’]
‘	Single quotation	Single quotations are used when expressing DATE values e.g. [startDate >=’2014-01-01′]
“	Double quotation	Double quotations are used when expressing text values e.g. firstName==”Brian”
,	Comma	Commas are used when separating elements in sequence e.g.attribute1==(“A,B,C”)

“if…then…else” Conditional Statement

• if: if opens up the if-then-else statement, and it commands the system to evaluate a certain criteria followed by if.
• then: When the if clauses evaluate to true, the statement followed by then will be executed.
• else: When the if clauses evaluate to false, the statement followed by else will be executed.
• else if: When there are more than one conditions to test, from the secondary commands, you can nest the if statements using else if

Previous Payment