Debugging Tasks and Escalations using the Event Journal
Event Journal Overview
The Event Journal section of the Configure tab provides an overview of all record transactions, application publications, and callouts for a server.
The list is initially sorted by the most recent events, but several options are available to search and filter the list down further.
All administrators who have access to the Public site for a server can do the following:
- Search by: App name, Operation Name, Record ID, and User
- Filter by event types: Record Transaction, Publish, and Callout
- Filter by status: Success, Warning, Revert, Reject, and Error
- Filter by source: Web Access, Token Access, Flowfinity Client, etc.
- Filter by date: Last 10 min, Last Hour, Yesterday, and Custom Date
Example
A system admin at ABC Property Management has downloaded the Flowfinity Remote Work Bundle, intending to amend these app templates for use in the production server.
However, after customizing the app templates, the admin has been alerted to a submission error by an end user.
The following process shows the Event Journal can be used to help in debugging task and escalation errors.
Errors associated with tasks and escalations appear during the submission of a record. These pop-up windows provide a snapshot of the reason for the error to the end-user, but not to system admins.
The Event Journal allows system admins a detailed way to review the submission process which can be used to debug errors with submissions which may include tasks and escalations.
By navigating to the Event Journal, system admins can see all submissions and errors in real-time.
Each entry can be expanded to provide a more detailed breakdown of the error. This allows system admins to identify the origin of an error quickly and amend the configuration.
In this instance, the 'Add task' operation was unable to complete due to an 'invalid object name.'
The origin of this error is the amended name of the Target app (i.e. Project Lists, not Project List). Since the app name was recently modified, the Task Action must also be updated as the previous app name no longer exists in the system.
After identifying and reconfiguring the task using the Event Journal, the system admin can test or simply observe future submissions in the Event Journal to ensure that the new configuration is correct.
The Event Journal, in conjunction with the Deployment tab, provide system admins an overview of the operation of tasks and escalations in Flowfinity and can be used to debug errors in both the production and development servers.