IBM Sustainability Software - Ideas Portal
Hide about this portal
This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
continuing from my previous comment..
For the record, I encourage developers to log to mbo.getMboLogger() when their script runs in the context of an MBO -- as is the case for all Object and Attribute launch points, and as is usually the case for Action and Condition launch points. But sometimes logging under maximo.script.SCRIPTNAME makes the most sense. And under maximo.script.SCRIPTNAME is where the service.log_<level>() methods log.
Maybe a better solution is to be able to specify on the script, and override on the launch point, the key for which logger should be passed into the script in an implicit "log" or "logger" variable. Maybe I'll make a new enhancement request for that.
"Developers can create their own logger and log their own DEBUG messages to that logger."
Yes, they can. But should they? If we jettison the idea of logging to a child of the OOTB maximo.script logger, then everyone and their dog is going to come up with a different place to log, making a mess for support personnel and maintenance programmers.
However, perhaps we need an alternative to TRACE, to save the trouble of introducing that level to all of Maximo when we only care to distinguish that far for automation scripts. Perhaps instead of supporting the TRACE logger each script's default maximo.script.SCRIPTNAME logger needs to have a child "trace" logger. Or perhaps there should be a maximo.script.trace root logger that could have SCRIPTNAME child loggers.
I think there is a misunderstanding about the loggers.
Developers can create their own logger and log their own DEBUG messages to that logger.
The autoscript logger should be used to understand what the automation script engine is doing. The autoscript logger can record key details about when a script is run without affecting the number of messages that the script generates.
TRACE isn't a log level that is currently available in the Maximo system
Thank you for your submission. We will consider this in a future release.