Miscellaneous Operators and Functions

Miscellaneous operators and functions include:

Abort Operator

The Abort operator serves to abort job processing (plan execution) based on data values and logic during the calculation of an ADOR value. The job itself is marked as aborted and a message reports that the job was aborted due to the Abort operation.

Example:

Say we wish to abort the current job if we find out that specific data is missing. For example, if the last name of a customer is missing we will abort the job. In this case, the expression for the last name ADOR will appear as follows:

If(|->[Last Name] = NULL or |->[Last Name] = "")

   Abort

else

   |->[ Last Name]

ReportMessage Function

The ReportMessage function inserts a message into the message list during production.

Syntax:

ReportMessage(message)

This function is different from all other functions because it does not have a value that can be used to populate the ADORs; therefore, it must be followed by an expression that has a value. You can use several calls to this function one after the other, but the last expression in the call list must be an expression that evaluates to some value (that is, not a ReportMessage function):

ReportMessage(msg1)

ReportMessage(msg2)

…

ReportMessage(msgn)

Expression

Example:

Say, for example, we want to report a message in case a record is skipped as a result of the Skip operator.

In this example, we wish to create a campaign for customers that have credit of more than 10000. An ADOR defined for the customer’s credit may appear as shown in the Skip Operator section.

If(|->[Credit] < 10000)

{

ReportMessage("Record number " & GetEnv("CurRecordNumber") & " was skipped")

Skip

}

else

   |->[Credit]

Skip Operator

The Skip operator skips the current record during job processing (plan execution), without affecting the success of the job. The Skip operator enables uProduce to continue the job without creating customer communications for specific recipients based on their data values and the logic defined for calculated ADOR values. By default, no special messages are displayed when a record is skipped. To specify that a message should be reported, you can use the ReportMessage Function.

Example:

Say we want to create a campaign directed at customers that have credit of more than 10000, and skip those that have less than 10000. In this case, the ADOR for the customer’s credit may appear as follows:

If(|->[Credit] < 10000)

   Skip

else

   |->[Credit]

Call Function

The Call function is used for integrating a plan with QLingo extension modules.

Syntax:

Call dllName.functionName(parameters)