Generic Condition Maintenance
You use this program to add conditional statements for specific details to be displayed in the calling program.
For example:
-
You can configure an organization list with customers belonging to branch N, W and NW, as well as all their contacts with an email extension of .com.
-
You can configure a user-defined conditions against an eSignature condition.
The list of fields that can be selected in the conditional dialog include, but are note limited to:
-
Customer, Supplier and Account master fields
-
Customer, Supplier and Account custom form fields
-
Contact master fields
-
Contact custom form fields
This saves the condition configuration details you have entered and returns you to the previous screen.
This lets you add a new condition row to the list of conditions (above the currently highlighted condition row). However, you can't insert a condition row above the first condition row.
This lets you remove the currently highlighted condition row from the condition.
This lets you delete all condition rows from the condition.
This has the same effect as deleting the entire conditional statement for the transaction.
Condition Configuration
Column | Description |
---|---|
And/Or |
For the beginning of the first condition, this defaults to If and cannot not be changed.
|
Open bracket |
Use brackets to group multiple conditions, as brackets determine how multiple conditions must be evaluated. |
Field or Variable |
Select a table field, user-defined variable or system/key variable to use in the condition. |
Condition |
Enter a valid condition that must be used to compare the fields. The following options are available:
Numeric fields are compared algebraically, alphanumeric fields are compared alphabetically and date fields are compared chronologically. |
Field, Variable, String or Constant |
Select a table field, user-defined variable, or system variable; or a string, number, time, date or constant to use in the condition. The following special fields are available:
eSignature considerations
Only variables whose values are available prior to the transaction being completed are displayed. This is because if you had a condition such as if %OrderValue > 10000 then deny transaction, the order value can only be established once the order is complete. Therefore, the transaction can't be denied before the order is complete so the condition can't be applied. Similarly for add or post type transactions, you can't use a field from the item being added (e.g. when adding a customer you cannot specify that a field against the customer has a value, as the customer has not yet been added). You can however use one or more of the supplied user variables. |
Close bracket |
Use brackets to group multiple conditions, as brackets determine how multiple conditions must be evaluated. |
Notes and warnings
Custom forms
-
Conditions can also include custom forms.
Including all organizations in a condition
-
If you want to include all organizations where a contact field (or contact custom form field) is used in the condition, the condition must be repeated for account, supplier, customer.
Copyright © 2024 SYSPRO PTY Ltd.