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 Planned for future release
Categories Integration
Created by Guest
Created on Feb 19, 2021

Support Delayed Validation in REST API setupdata

In the REST API, there is a way to perform lookups on temporary objects utilizing a request like: /maximo/oslc/os/mxwo/zombie/getlist~assetnum?lean=1&oslc.select=assetnum,description&setupdata={"location":"SHIPPING","siteid":"BEDFORD"}

The setupdata query parameter allows you to provide values for the attributes so that when the list should be filtered (such as assets in a location) the Maximo framework will apply the necessary filters.

The way this object is constructed the validate is called on each attribute immediately in the order they're defined. This causes issues when one of the attributes (such as SITEID in this case) impacts how a previous attribute (LOCATION in this case) should be validated. Similar to the MIF, we'd like this (or an alterative if this negatively impacts existing processes) to utilize delayed validation so it waits until all attributes are set prior to validating these attributes. This would ensure the application doesn't have to provide these in a pre-defined order and would make it function similar to the actual submission of the record.

Idea priority Medium