Skip to Main Content
IBM Sustainability Software - Ideas 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Created by Guest
Created on Dec 5, 2023

Enhancing Maximo Exception Scripts for Improved Debugging Capabilities

Currently, automation scripts associated with message errorGroup and errorKey in Maximo are executed when an MXException is instantiated, provided the script is named MXERR.{errorgroup}.{errokey}. While this mechanism is valuable for automating actions during issue identification, its effectiveness is limited by the lack of access to MXException object as implicit variable within the script.

By incorporating MXException object as implicit variable, it can be used to access & print stack trace for comprehensive debugging.

Idea priority Low
Needed By Not sure -- Just thought it was cool
  • Admin
    Kim Woodbury
    Reply
    |
    Feb 5, 2024

    No response at this point. Will close with provided information being acceptable.

  • Admin
    Kim Woodbury
    Reply
    |
    Dec 11, 2023

    Thank you for your request. There is a way to print the stack trace using the below sample. Please let us know if this does not meet your needs.


    ---------------------------------------------------------------------------------------------- # throw stack trace # Make sure the integration logger is set to debug. from psdi.iface.mic import MicUtil from java.lang import Exception if mbo.getString("wonum") == 'the wonum he noted' e = Exception('hello') MicUtil.INTEGRATIONLOGGER.error(e.getMessage(),e)