It would be great if the activity log was customizable for the activities to be logged. Broken down into Modules, and for each module have criteria that can be logged. This would make it better for the company that wants to only log certain information instead of everything.
Then when you want to view the log the same logic can hold true. Have a blank starting page and select which activities you want to view the logs for. This would make the Activity Log file open quickly and only pull back records that you want to see.
Activity Log Setup Example:
Bill Of Materials:
Options:
1) Log new Bill creations - (Userid, Time, Bill#, Etc..)
2) Log Bill deletions - (Userid, Time, Bill#, Etc..)
3) Log Bill component additions/ deletions - (Userid, Time, old component, new component, etc...)
4) Log Bill quantity changes - (Userid, Time, old quantity, new quantity, etc...)
You could then show what the previous value was and what the new value is for certain logged events.
by: Andrew M. | over a year ago | General Enhancements
Comments
Also, add teh ability to limit the number of records stored in the files and/or purge data (with a Security setting)
I agree with the original post and also agree that we need tools to manage the log file. Ours takes about 10 minutes to display.
We would like the a purge function that would display (based on date range) the record types to purge (such as VI jobs). We also like the blank starting page that Andrew M. mentions.
Away to clean up the file without just reinit. Also options to not track data written to this file, like VI records, valid login etc
I have suggested in the past that the activity log needs to be segmented such that things like errors, user logins, period end closing, access to data file display and maintenance, vi jobs and their results can be easily broken down. This log gets huge very quickly, takes forever to load and reports a great deal of information not generally required. Unfortunately the log is not well delineated by Type which would be very useful. Even some errors are reported as System Activity. I’d like to see more types at least so that I can quickly get what I need. The other thing which would be really useful is to know the launch program when an error occurs. Yes the error happened in PL_COMMONUTILITY.M4P or SY_ReportEngine.pvc or CI_CreditCard_val.pvc but I would really like to know not simply the module but also the function being processed when the error occurred.
There needs to be a utility to purge the activity log
For the report, I'd like to be able to search for text in the description, error, program, or line (Maybe I want to see who last changed the A/R System Parameters, or who changed tax codes, or how many error 47's have occured and where).
I'd also like to see more information about where the error came from (Allen H's comment).
It would also be nice if the activity log could be separated into a main and detail file for records like installs, VI jobs, and conversions. The main log could say "installed product update x", with a drill down to a detail file of what that product update included. Similarly, when VI jobs are run, the main log can say "job x import started" with the details of records skipped, imported, failed in the detail file. For errors, it would be helpful to know more information about an error, especially when it occurs in a common program (if an error occurs on a CI program, from what data entry/update was the CI program called?).
PLEASE, PLEASE, PLEASE stop posting VI job records to the Activity Log. Some of us have customers that import hundreds of thousands of records over time and it is severely compromising the value of the SY_Activity Log. Keep multiple Job Logs in VI instead. Thank You!
After upgrading to Version 4.5 I was told that Error 86 no longer shows on the Activity Log. If this is true it should be added back.
I'm glad the purge utility was added however I think there really needs to be a separate log for VI records. It would be okay if the System Activity Log tracked when a job was run and the name of the job - even the summary of records imported - but NOT EVERY SINGLE RECORD!!!!
I agree 100% with Cullen that we need a separate VI Activity log. Having detailed VI entries for every VI job makes the Activity Log useless for other purposes. Very frustrating!
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)