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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
There seems to be business logic around Material Requisition status that is being executed in bean classes and not within the Maximo Business Object associated with MRs.
If a new MR is created in the Maximo UI and there is an active workflow on the MR object, the MR will be placed into a status of WAPPR and the workflow will be started.
If a new MR is created via integration and there is an active workflow on the MR object, the MR will be placed into APPR status (assuming the status is not supplied in the payload of the message) and the workflow will be ignored.
To re-create the logic of the Maximo UI using the Maximo JSON API, one must make separate HTTP calls to:
Create the MR in DRAFT status
Query the WFPROCESS object to see if there is an active workflow for the MR object
Change the status of the MR to WAPPR if there is an active workflow (APPR if not)
Start workflow on the MR if there is an active workflow (not needed if not)
It would be best if the logic for status on creation of a new MR were moved out of bean classes and into the MBO for the MR object. This way developers do not need to re-create business logic outside of what should be handled internally in Maximo.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you for your submission this change will be taken into consideration in a future release when we replace the Desktop Requisition app with the new rol e based application.
Was a Support Case raised for this?