Documente Academic
Documente Profesional
Documente Cultură
Presenter
Partha Ghosh - Supporting OTM since November, 2000. - GC3 Version 2.6
It is difficult to get to the log after receiving an error in the UI Some actions did not provide a direct link to the logs. Therefore, the user had to navigate to the log page, and search for their information
Types of Logs
Ad Hoc logging selective business processes like integration, or bulk planning System logging events throughout the system
4.
5.
Mark the Append and type a Max Size in bytes for the file
Check to Turn On the Log
6.
Using the Left and Right blue arrow buttons move the log IDs you want to enable
7.
Click Finished
Notes: Use the Top Level Process to constrain what log content you see. If you do not know your Top Level Process ID use the Search For to find it. You can use the Gid of the object your were working with to search for. Use the Save to file feature and always set Max to Save to 5000. It will guarantee you get as much log as possible.
Log Results
Tech Tips
Default Logging recommendations: Agent Exception Glog Planning Workflow
Integration Records events related to the integration of data, via XML schemas, between the database and external systems
Explanation Viewer
Displays a hierarchical tree view of all issues associated with an explanation Tree view can expand/collapse issues Ability to view summary information or drill down further into the stack trace Diagnostics are available for advanced users, similar to the current Exception Viewer All messages on the Explanation Viewer are translated into your preferred language
Explanation Settings
Mode ACTION records explanations when various business actions are run. Business actions include most actions that appear on the Actions menu for a business object. It also includes functions such as add, edit, and delete. AGENT records explanations for agents that are triggered as a result of events. PROCESS records explanation for background workflow processes such as tendering and event notification. ALL records explanations for all of the above. Severity INFO description of process: no follow-up activity required WARNING precondition to an error: follow-up required based on condition ERROR failure to complete processing: requires re-input of customer information INCOMPLETE failure to complete a system process that halts order creation, shipment planning, rating, tendering, or other process Diagnostic Turn On
View Diagnostics
When using Explanation view you are given the button to View Diagnostics
Diagnostics Contents
Another Level of Details with the ability to expand and collapse details
Thank You!
Partha.Ghosh@MavenWire.com
www.MavenWire.com