This portal is to open public enhancement requests for IBM Sterling products and services. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Fix manageNodeTransferSchedule API to create Node Relationship that does not exist
Currently, the manageNodeTransferSchedule API creates a relationship in one direction from Node A to Node B. However if a Node Transfer Schedule is created in the reverse direction (from Node B to Node A), the reverse Org relationship is not created. This seems like a bug and not a design feature.
What is your industry?
How will this idea be used?
Node Transfer Schedules are updated regularly. While the manageOrgRelatnship api can be used to create relationships that do not exist, it would be much easier for the manageNodeTransferSchedule to take care of this, as it does today for the forward relationship. That way, the implementation does not need to worry about Org Relationships. The Schedule and Org Relationship are automatically kept in sync.
Do not place IBM confidential, company confidential, or personal information into any field.