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 Submitted
Categories Integration
Created by Guest
Created on Dec 2, 2024

Enable a way to set non-persistent attributes in outbound processing classes only when they're requested

In a lot of the outbound definition classes, additional MboSets are established to set a non-persistent field. These should ideally be done via attribute field classes on the non-persistent attribute(s) instead of depending on the outbound definition class. But if we at least enabled a more efficient method in the outbound definition classes, then we can minimize the impact.

For example, the asset outbound processing class (psdi.iface.app.asset.MoutAssetProcess) sets hierarchypath in the checkBusinessRules using mbo.getString("CLASSSTRUCTURE.HIERARCHYPATH"). This requires for every asset record we are establishing a new set to get the hierarchy path even if we don't need that data. For example, in the REST API if we are only retrieving the assetnum & description field. And even in the scenario that we want hierarchy path, this prevents us from being able to utilize the REST API caching mechanism. This can negatively impact performance, especially during bulk downloads like Maximo Mobile.

In addition to Asset, the Item (MoutItemProcess), Job Plan (MoutJPProcess), Locations (MoutOperLocProcess), and likely others set the hierarchy path.

There are other examples as well. For example, multiple inventory outbound definition classes (MoutInvBalancesProcess, MoutInvProcess, MoutRSVProcess, MoutInvVendorProcess, etc.) set the ITEMTYPE field.

If setting these attributes could be moved out of the checkBusinessRules and put into a method that only sets these fields when they are being requested, we can minimize the performance impact when they're not needed.

Idea priority High
Needed By Yesterday (Let's go already!)