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 Delivered
Created by Guest
Created on Sep 16, 2022

add implicit "log" variable to autoscripts, initialized from script or launch point record

Automation Scripts should be passed an implicit "log" variable.

A Developer or Administrator should be able to specify on the script record, and override on the launch point record, the key for which logger would be passed into the script.

The domain of loggers to pass to the script could include a "default" option. If default is chosen, the key for the logger passed into the script should be "smart":

  • If the script is an integration script, the key should default to "maximo.integration.SCRIPTNAME". This is because integration scripts are named after how they are used by the system and, hence, already break down further by the integration component and by the direction of data flow.

  • If the script is launched from an Object, Attribute or Condition launch point, the key should default to the result of mbo.getMboLogger(). This is because when support personnel turn logging for maximo.service.WORKORDER.WORKORDER to DEBUG, they should see the log output from scripts that get launched against those MBOs. It makes no sense to make support personnel hunt through scripts to see which logger they need to turn on to troubleshoot a problem with WORKORDERs.

  • For an Action launch point, the key should default based on the execution context. For example, if the Action was launched from an app, then maximo.application.APPNAME.SIGOPTION sounds to me like a good default candidate. Or if the Action was launched from an Escalation, it should be something like maximo.crontask.ESCALATION.ESCNAME.ESCPOINT.ACTION. Or if the Action was launched from workflow, it should be some thing like maximo.workflow.WOPROCESS.WOREV.NODE.ACTION.

By encouraging developers to log to a key consistent with the execution context of their script, support personnel and maintenance developers will be able to troubleshoot and resolve problems faster. This is because logging keys in use will not be just "maximo.script" and will not be as subject to the passing whims of an inexperienced developer.

This should also save developers some time and lines of redundant code to get access to a logger.

Idea priority Medium
Needed By Not sure -- Just thought it was cool
  • Guest
    Reply
    |
    Jan 12, 2023

    Excellent idea