Function-based Rule Properties

Traditionally, a rule property would traverse a path through the schema, starting from the base object, and ending at a column.

For example, the "Contact First Name" property for a case would use the path "case_reporter2contact:first_name".

However, there are instances where a path cannot be traversed, or where a calculation needs to be made.

For example, you may wish to fire a business rule only if all of the subcases on a case have been closed. So your two business rule conditions would be:

• "Number of Subcases" is greater than zero
• "Number of Open Subcases" is equal to zero

Or, you may wish to fire a business rule if the *Number of cases for product X within the last 7 days* is greater than 10.

Or you may wish to use a variable (rule property) as part of a canned response that retrieves data from another system using a web service call.

With these examples, there is not a schema path that can be traversed to provide these values.

You can now write your own custom code for these rule properties. Dovetail provides an example code project that demonstrates custom function-based rule properties. This project is freely available at https://dovetailsoftware.github.io/property-extensions/

Once your code has been written, and the assembly copied into the target application directory, then the property can be defined using the Business Rule Property UI:

• Assign it a property name, as normal.
• Check the "Is Function" checkbox
• For the Path, rather than a schema path, type in the Class Name of your custom property function, such as "NumberOfSubcases"

Did this topic help you? Email us your feedback.
Last updated: 12/12/2016 11:48:13 AM
© by Dovetail Software, Inc.