Smarter Logging was added to SalesEZ application. The addition of a file, _LogDirectives.txt, in the appropriate ProgramData\Siriusware\Pool\EZ folder with proper configuration allows a filtered logging capability. It is possible to set SalesEZ's verbosity to zero and still get a verbosity 5 log based on an expression, for certain salespoints or certain operators or even certain function calls. Additionally, a new streamlined log type can be enabled to capture statistics for length of time spent on calls, waiting for SQL Server and logging. Instructions for using this is provided in a separate document 4058Logging_options_in_SalesEZ and 4101Logging_options_in_Middleware.

When killing an instance of an EZ from the service monitor doing so no longer kills the SQL connection for the other live instances.

All log filenames for middleware components now start with the middleware component name and is always found in the ProgramData Pool\EZ folder.

 

SalesEZ_Log.txt, SalesEZ_LongCallsAndErrors.txt, SalesEZ_MemoryDump.txt, SalesEZ_Transact_Dump.txt and SalesEZ_Performance_20110309_Log.txt - LongCallsAndErrors log files now contain entries for all logged errors. Formerly log entries with an 'E' value would only appear in the LongCallsAndErrors log if the developer made a separate (addition) call to a different log routine. This is now automatic, so you see more information in this log.

The ability for Sales to get a verbosity 5 log from SalesEZ application was added using the tag set <ReturnLog>Yes</ReturnLog>. If this is present in the call, SalesEZ appends the verbosity 5 log for that call to the regular return value inside the <SalesEZLog></SalesEZLog> tags. This is for a future enhancement to allow Sales to capture SalesEZ logs from the salespoint.