Use Lookups with Rulebases

Repository lookups (for example, a drop-down list to show records from another repository) can be very expensive if the lookup is performed against a large repository.

Such queries do not use cached data because it assumes that the data in the target repository could change any time. Such lookups have been found to be the primary cause of many slow user interface service requests. The same applies to any SQL based lookups.

TIBCO recommends that you initially design modular rulebases and separate the rules by usage based on conditions. Important conditions to consider are:

  • CHANGED: this condition indicates whether the record data has changed. If the record data has not changed, you can skip some validations.
  • RECORD_ACTION: this context var indicates the action being taken. that is ADD or EDIT (check with rulebase guide).
  • RELATIONSHIP_CONTEXT: this condition indicates the direction of traversal.