Support Log

How to Access

Tabs3 Billing Location

Quick Launch

View the Support Log

Menu

View | Log Files | Support Log

Access Rights

Access Profile | Tabs3 Billing tab | Utilities/View | View Support Log

R11818 - Access Rights

Exclusivity

Platinum

Multi-Access Function

Non-Platinum

Multi-Access Function

The Tabs3 Billing Support Log tracks occurrences of the following features:

	Advance Current Reporting Month: Each time the Advance Current Reporting Month utility was run in prior versions, an entry was made to the Support Log file indicating the date and time the utility was run, who ran the utility, and if year-to-date totals was also cleared. The Advance Current Reporting Month utility was replaced with the Set Current Reporting Month utility. The information in the Advance Current Reporting Month section is retained for historical purposes. The Support Log does not track changes made via the Set Current Reporting Month utility. See also: Date-Based vs. Period-Based Reports
	Archive File Integrity Check: Each time the Archive Integrity Check utility is run, an entry is made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility.
	Auto Synchronization of Tabs3 and PracticeMaster: Each time the automatic synchronization of data between Tabs3 Billing and PracticeMaster is performed, an entry is made to the Support Log file indicating the date and time of the synchronization and the User ID of the user who caused the synchronization.
	Back Up Data: Each time the Back Up Data Files program is run, an entry is made to the Support Log file showing the date the backup was made, the time the backup was started, the time the backup completed, the User ID of the user who performed the backup, whether or not the backup process was aborted, and which GLS Clients were backed up.
	Change Beginning Reporting Month: Each time the Change Beginning Reporting Month utility was run in prior versions, an entry was made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility. The First Month of the Reporting Year can now be changed at any time via Customization and is no longer tracked. The information in the Change Beginning Reporting Month section is retained for historical purposes.
	Change Key Type: Each time the Change Key Type utility is run, an entry is made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility. The Old Type column indicates the key type that was changed and the New Type column indicates the new key type that was selected. The Old Length column indicates the number of decimal places before the utility was run and the New Length column indicates the number of decimal places after the utility was run. The Ins/Del Zeros column indicates whether the Beginning or End option was selected when the utility was run.
	Client File Information: Each time a client record is added, changed or deleted using the Client file, an entry is made to the Support Log file indicating the date, time, User ID, Client ID and whether the client record was added, changed or deleted. Additionally, an entry is made to the Support Log file for each client deleted using the Delete Range of Clients utility.
	Client Ledger Changes: Each time a client ledger record was edited using the Edit Client Ledger utility in prior versions, an entry was made to the Support Log file indicating which record was changed, who changed it and the date and time it was changed. Also, a "Y/N" column is displayed to the right of the Ref # column indicating whether the receipt allocation information was automatically adjusted or not.
	Client Portal Access: Each time a contact’s access to a matter via the Client Portal is changed, an entry is made to the Support Log indicating the date and time the change was made, the user who made the change, the type of action performed, and the contact ID and matter ID affected.
	Data File Integrity Check: Each time the Data File Integrity Check utility is run, an entry is made to the Support Log file indicating the date and time the utility was run, the User ID of the user who ran the utility, whether the utility was run as Full or Limited, the number of errors detected by the utility, the duration of the integrity check, and the build of Tabs3 Software installed at the time the utility was run. The last five Data File Integrity Check Error Reports containing error messages are saved in the Current Working Directory as PDF files, and a link to open those reports will be shown next to the corresponding entry in the Support Log.
	Exchange Connector Error Notification: Each time the Exchange Connector receives an error, and notifications are configured, an entry is made to the Support Log indicating the date, time, User ID, type of notification sent, who the notification is sent to, and result. The result can either be Sent or Failed to Send.
	Final Statements: Each time final statements are run, an entry is made to the Support Log file indicating the date and time the statements were run and the User ID of the user who ran the statements.
	HotBackup Notification: Each time a HotBackup is performed, and notifications are configured, an entry is made to the Support Log file for each notification sent indicating the date, time, User ID, type of notification sent, who the notification is sent to, and result. The result can either be Sent or Failed to Send.
	Installed Updates: Each time an update is installed using the Check for Updates feature, an entry is made to the Support Log file indicating the date and time the first user accessed the newer version of the software after the update, and the release date and version of the update installed.
	Lock Out All Users: Each time the Lock Out All Users program is run, an entry is made to the Support Log file indicating the date and time the program was run, the User ID of the user who ran the program, the action that was taken (lock or unlock), the duration specified for the lockout, and the reason specified for the lockout.
	Log Off Users: Each time the Request Log Off program is run, an entry is made to the Support Log file indicating the date and time the program was run, the User ID of the user who ran the program, the application and user that was logged off (one line will be present in the Support Log for each system/user combination), the number of minutes the users had before being logged off, and the reason specified for the log off process.
	Payment Adjustment: Each time the Payment Adjustment utility is run, an entry is made to the Support Log file indicating the date and time the utility was run, the User ID of the user who ran the utility, the Client ID, Reference number, Adjustment Date, and the Amount that was adjusted. An asterisk to the right of an entry indicates the task was interrupted.
	Pre-Bills: Each time pre-bills are run, an entry is made to the Support Log file indicating the date and time the pre-bills were run and the User ID of the user who ran the pre-bills.
	Purge Archive: Each time the Purge Archive Data utility was run in prior versions, an entry was created to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility.
	Rebuild Client Ledger: Each time the Rebuild Client Ledger Detail utility was run in prior versions, an entry is made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility.
	Rebuild Receipt Allocation: Each time the Rebuild Receipt Allocation utility was run in prior versions, an entry was made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility.
	Receipt Allocation Changes: Each time a receipt allocation record was edited using the Edit Receipt Allocation utility in prior versions, an entry was made to the Support Log file indicating the date and time the change was made, the User ID of the user who made the change, and the Client ID and timekeeper that was changed.
	Reindex Files: Each time the Reindex Files program is run, an entry is made to the Support Log file indicating the date and time the program was run, the User ID of the user who ran the program, and the status of the Compact Selected Files and Delete records that contain errors check boxes when the program was run.
	Rename Contact: Each time the Rename Contact utility is run, an entry is made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility. The Old ID column indicates the Contact ID of the contact that was renamed and the New ID column indicates the new Contact ID. If PracticeMaster is installed, this entry will not be logged in Tabs3 Billing, Trust, or AP, and will instead be found in the PracticeMaster Support Log. If PracticeMaster is not installed, this entry can be found in the Tabs3 Support Log.
	Renumber Category: Each time the Renumber Category utility is run, an entry is made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility. The Old Category column indicates the category number of the category that was renumbered and the New Category column indicates the new category number.
	Renumber Client: Each time the Renumber Client utility is run, an entry is made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility. The Old ID column indicates the Client ID of the client that was renumbered and the New ID column indicates the new Client ID.
	Renumber Timekeeper: Each time the Renumber Timekeeper utility is run, an entry is made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility. The Old Tmkpr column indicates the timekeeper number of the timekeeper that was renumbered and the New Tmkpr column indicates the new timekeeper number. The Overwrite column indicates the status of the Overwrite check box when the utility was run.
	Renumber Transaction Code: Each time the Renumber Transaction Code utility is run, an entry is made to the Support Log file indicating the date and time the utility was run and the User ID of the user who ran the utility. The Old Tcode column indicates the transaction code number of the transaction code that was renumbered and the New Tcode column indicates the new transaction code number.
	Restore Data: Each time the Restore Data Files program is run, an entry is made to the Support Log file showing the date of the restoration, the time the restoration was started, the time the restoration completed, the User ID of the user who performed the restoration, whether or not a secondary backup file was created as part of the restoration process, and which GLS Clients were restored.
	Reverse Write Off: Each time the Reverse Write Off utility is run, an entry is made to the Support Log file indicating the date and time the utility was run, the User ID of the user who ran the utility, the Client ID and Reference # of the Write Off that appears in the Client Ledger. An asterisk to the right of an entry indicates the task was interrupted.
	Submit Log Files: Each time the Submit Log Files program is run, an entry is made to the Support Log file for each log file submitted indicating the date and time the file was submitted, the User ID of the user who submitted the log file, and the results of the submission (either Success or Failure).
	Synchronize Tabs3 and PracticeMaster: Each time the Synchronize Tabs3 and PracticeMaster utility is run, an entry is made to the Support Log file indicating the date and time of the synchronization, the User ID of the user who ran the synchronization utility. The Archive column indicates if the Convert Tabs3 archive records to PracticeMaster fee and cost records check box was selected. The Prompt column indicates whether the Perform synchronization and prompt for a resolution to all conflicts or Perform synchronization and do not prompt for conflicts option was selected. When the Perform synchronization and prompt for a resolution to all conflicts option is selected, the T3 or PM column indicates whether the Use Tabs3 to resolve conflicts or Use PM to resolve conflicts option was selected.
	Tabs3 Customization: Each time Tabs3 Customization is edited, an entry is made to the Support Log file indicating the date and time the information was edited and the User ID of the user who edited the information.
	Transfer Transactions: Each time the Transfer Transactions utility is run, an entry is made to the Support Log file indicating the date and time the utility was run, the User ID of the user who ran the utility, the Client transactions were moved from and the Client the transactions were moved to, and whether the transactions were Fee, Cost, Payment, or Accounts Receivable. An asterisk to the right of an entry indicates the task was interrupted.
	Unbill Final Statements: Each time the Unbill Final Statements utility is run, an entry is made to the Support Log file showing the date and time the statement was unbilled and the User ID of the user who unbilled the statements.
	Undo Split Billing: Each time the Undo Split Billing utility is run, an entry is made to the Support Log file showing the date and time the utility was run, the User ID of the user who undid the split billing, the Client ID of the client whose transactions were restored, and the batch number of the split billing batch. An asterisk to the right of an entry indicates the task was interrupted.
	Undo Updated Statements: Each time the Undo Updated Statements utility is run, an entry is made to the Support Log file showing the date and time of the statements that were reversed, the User ID of the user who reversed the statements, the statement number, the Client ID, and the current reporting month in which the statement was reversed. The reporting month shown always reflects the current reporting month at the time the statement was reversed, regardless of which options were selected. The word "Adjusted" is displayed next to the reporting month when the utility was run with the Current Reporting Month option selected in the Month to Adjust area (or for older versions, the Adjust Current Reporting Month Productivity check box was selected.) If the Undo Multiple Updated Statements utility is run, a single entry is made to the Support Log file; the statement date is displayed in the Statement column, the number of statements undone is displayed in the Cnt column, and the client range is displayed. (Note: "Multiple" will be displayed in the Client Range column if the statements were undone in some prior versions.) An asterisk to the right of an entry indicates the task was interrupted.
	Update Statements: Each time the Update Statements utility is run, an entry is made to the Support Log file indicating the date and time the utility was run, the User ID of the user who ran the utility, the client range specified when the utility was run, and the primary, secondary, or originating timekeeper range specified when the utility was run. An asterisk to the right of an entry indicates the task was interrupted.
	Write Off: Each time the Write Off utility is run, an entry is made to the Support Log file indicating the date and time the utility was run, the User ID of the user who ran the utility, the Client ID for whom the utility was run, the statement number and/or timekeeper that were written off, and the Write Off date that was entered. An asterisk to the right of an entry indicates the task was interrupted.

Interrupted Tasks

An asterisk to the right of a row in the Support Log indicates the task was interrupted and did not successfully complete. Tasks that do not complete correctly can introduce errors to any files that were used. An asterisk to the right of an entry for the Update Statements, Undo Updated Statements, Write Off, Reverse Write Off, or Payment Reversal tasks will require restoring from a backup that was made prior to starting the task.

Platinum Note: Tabs3 Platinum utilizes Transaction Processing, which makes restoring from a backup unnecessary in most situations. Most interrupted tasks in Platinum editions just require the user to attempt the task again. For detailed information on the proper procedures for any task that is interrupted in a Platinum system, see Knowledge Base Article R11179, "Transaction Processing: Auto-Recovery of Interrupted Database Transactions."