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 Future consideration
Categories Integration
Created by Guest
Created on May 3, 2022

OSLC Object Passback Token

When creating new records (in particular child records) using autokeys, if multiple children are difficult to identify after creation.

For example:

POST /maximo/oslc/os/someOS

{

"description":"a Root object",

"child":[{"description":"child 1"},{"description":"child 2"}]

}


would return something like:

{

"rootid":"123"

"description":"a Root object",

"child":[{"childautokey":1,"description":"child 1"},{"childautokey":2,"description":"child 2"}]

}


If the sequence of the children were guaranteed then it would be possible to match the request and response, but this is not always true.


I would suggest a new oslc object property _postbackid that the client could generate and maximo return in the message, for example:


POST /maximo/oslc/os/someOS

{

"description":"a Root object",

"child":[{"_postbackid":"example A","description":"child 1"},{"_postbackid":"example B","description":"child 2"}]

}


would return something like:

{

"rootid":"123"

"description":"a Root object",

"child":[{"_postbackid":"example A","childautokey":1,"description":"child 1"},{"_postbackid":"example B","childautokey":2,"description":"child 2"}]

}


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

    a further thought on this, it would be also very useful on patch/merge updates - so if the solution could work in both cases that would be very useful.