Show/Hide Toolbars

Jim2® Business Engine Help File

toolshistory

 

There are number of ways to access the history of objects:

on the ribbon, go to Tools > History

right click on Tools in the Nav Tree and select History

click the History icon in the Quick Access Toolbar.

historyinnavtree

 

History in the Nav Tree acts exactly the same way as lists, allowing switching between objects within the Nav Tree.

 

There is an extensive list of objects for viewing within History, not all of which are showing in this image.

 

historyoptions

 

Besides history on objects, History can show information such as users disconnected (time outs), when backups were performed, Jim2 errors, when users log on and when they were recently logged in, when updates have been installed, etc. There are a large number of objects that will show history, so it is worthwhile looking at what is available.

 

History for Logins only shows last login, however you can click on Jim2 in the top left hand corner and select Logged Users. This will show everyone that is logged into Jim2.

 

Right click options on most events will produce a pop-up menu to view the event's related object (job, quote, etc.), or to export/print the log.

 

viewhistory

 

Normal list/grid grouping, sorting and filtering applies.

 

This allows searching by user, date ranges, last 1000, etc. Additionally, History logs events like trackable reports, and allows easy access to Jim2 objects via right click.

 

Be sure to update Security Groups as required via Tools > Security> Tools > Allow viewing History.

 

allowviewhistory

 

If Allow viewing History is not ticked, only Server logs will be displayed.

 

In History, the default Most Recent selection criteria displays the last 1000 logged events. Edit the selection criteria as required and click Run.

 

mostrecent

 

Comments made by users can also be seen (within objects that have a Comment grid):

 

objecthistory1

 

At the bottom right is the Server Logs tab.

 

serverlogs

 

This will show information and errors on the Jes instance that is running.