Viewing Business Rule Logs

This topic describes how to access the logs generated when a business rule runs and explains the information contained in the logs.

Use business rule logs to gather more insight into the status and results when your business rules run. Each time a rule runs, triggered by either an event or a scheduled rule, that information is captured and stored. The information can help you confirm that a rule has run, what its status is, and it can also help you to identify, troubleshoot, and resolve any errors or discrepancies. Typically, the logs would be used to assist development and testing efforts, however, log information can also be useful for communicating issues with Oracle support teams.

Accessing Business Rule Logs

To access the business rule logs:

1. In the Navigator, select Common Setup > Business Rules Framework.

2. Click View Logs on the Business Rules Framework landing page.

3. On the Logs page, use the search controls to filter the logs and isolate the log(s) you need to review.

   You can select to view logs for the last 7, 14, or 30 days. Or, you can select Date Range from the drop-down list to specify a custom range.

4. Click anywhere in the row for a particular log to open the Log Detail page for that business rule run.

Working with Log Details

The Log Detail page displays this information regarding a business rule.

Page Element	Description
Reference Name	Indicated the object the rule is running against, such as permit, an incident, a user profile, and so on.
Reference ID	The system identification for the object the rule is running against. For example, in the case of a user profile it may display the user name, while in the case of a permit, it displays the transaction ID, which can be clicked to navigate directly to the transaction associated with the rule.
Resource Code	The system name for the business object of the event that triggered the rule. For example, CE_INCIDENT.
Resource	The name of the business object of the event that triggered the rule. For example, Code Enforcement Incident.
Event Code	The system name of the event that triggered the rule. For example, CE_INCIDENT_STATUS_UPDATED.
Event	The name of the event that triggered the rule. For example, Incident Status Updated.
Log ID	The unique identifier of a particular log entry.
Execution ID	The unique identifier of the internal system instance associated with the Business Rules Framework request.
Created Date	The date and time at which the Business Rules Framework request was created.
Created By	The user ID of the individual user, system component, or application that created the Business Rules Framework request. For example, it could be the Oracle Integration Cloud user,and individual user, or Oracle Permitting and Licensing application (FUSION_APPS_PSC_APPID).
Log Message	The detailed message associated with this log entry, providing the process sequence, if the criteria is valid, if any action was completed, if anything was missing, what the ultimate status is, and so on. Note: The message display is limited to 1,000 characters. In the case of a longer log message, some critical information may not be visible.
Status	The status of log message, such as Success, Error, or No Rules. In the case of No Rules, it can indicate the rule found nothing to be completed or the rules associated with an event are not enabled.