When attempting to troubleshoot problems in Mas90/200 the activity log is generally a place to look to see if modules were closed, errors occured or other processes in the system performed errrors. Currently the activity log also contains all user log in attempts. An activity log on a medium to large system takes several minutes to display due to the increased tracking of the user logins. It would be helpful if those user login attempts were moved to a different audit log.
by: Barbara K. | over a year ago | General Enhancements
Comments
Perhaps it would be better to have the screen not load transactions by default and give the user better searching capabilities?
Activity log also records each record imported via visual integrator each time the job is run. Would be better to see just one entry showing the job was run rather than hundreds of lines each time.
It would be nice to have tools to manage log files such as purge by date, Type or company. Contrary to the documentation, the files are now getting huge. Our own inhouse sustem takes about 10 minutes before it will even display. We have clients that cannot get a display at all.
It would also be nice to have tools to control the display, specifically, user definable filters and control over the number of records to display.
John B: You can purge the Activity in versions 4.50 and higher
- You need to push the magnifying glass button and make a selection using the options available. Date Range, company, user, activity type.
When the selection returns the red X "purge log" button will be active.
TIP:
You must select something in the lookup window. If you just choose the default search selections the button will not become active.
For the 2019 Sage 100 release we are planning on making the following enhancements to the activity log:
* skip initial log loading if a user-definable # of records reached --or-- display a definable 7/30/60/90 days of last activity as the initial load
* consolidation of V/I entries and preserving the original job log as an attachment for detail within the entry.
* optionally provide more error information (stack, open files/objects)
* add ability to filter by module and/or search text
* log user and role changes
* add ability to provide basic audit logging of other system maintenance (company maintenance, system configuration)
* activity log purge changes
- ability to archive or delete during purge
- ability to define minimum # of days to keep
- ability to schedule purge (rotational, by # of days, # of records)