Who is this article for?

  Users who encounter business rule errors.

  IT Administrator permissions are required to investigate further.

This article describes the function of business rules, and next steps for investigating issues.

1. Overview

Internal Audit makes use of business rules, which define how the application behaves.

For example:

• If a field should be mandatory
• Whether fields can be edited after a record status changes from Open to Completed
• Whether a record status can be changed, e.g. from Accepted back to Open

Configuration changes and System Settings activate and deactivate business rules.

2. Investigating issues

In certain situations, business rules can be inactive in error.

If the system is behaving 'strangely', for example:

• If there are problems changing sign-off state
• If document file names or record names are blank
• It is possible to change status of Action Updates that have been Accepted

. . . it might be that there has been a problem applying a business rule.  This is normally temporary, and is corrected once an application pool has recycled.

To check for evidence of problems with business rules:

1. Review the main service log file, at Service\PentanaTngService.log.
    You might find one or more of these messages:
   • Could not fetch business rules because query of type Behavior could not be executed
   • Exception of type: TngException[Fatal] - Message: Msg 701, Level 17, State 123, Line 1: There is insufficient system memory in resource pool 'internal'to run thisquery.
   • Exception of type: IndexOutOfRangeException - Message: Cannot find table 0
     
2. Run the attached script against the database
   It reports the numbers of active business rules:

If the errors shown above appear in the log file, or if the number of active business rules <1000, then further investigation might be required.  Please contact our Support team for further assistance.