IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Make FGArrivedFile REST API useable.

A great use for the Sterling REST API would be to query the FGArrivedFile, FGRoute, and FGDelivery endpoints in order to build a modern delivery dashboard for business users.
This is currently impossible with the current implementation due to a couple of poor implementation choices.

1. the ModifyTs cannot be queried on, thus making it impossible to query for recently changed entries.

2. Having to query all 3, FGArrivedFile, FGRoute, and FGDelivery and merging the data between the arrivedFileKey and RouteKey is a usability nightmare. All of the data is relevant and must be combined into 1 endpoint.

3. Once the above is completed then the REST API will finally be somewhat usable; however, not modern. A modern implementation would allow consumers to subscribe to changes via websocket so that consumers could get instant updates to transmissions without having to constantly poll the rest api.

1&2 is a must. 3 is a nice to have.

  • Guest
  • Jan 13 2021
  • Future consideration
What is your industry? Financial Markets
How will this idea be used?

This will allow us to continue to build out our managed file transfer program and deliver to the business visibility and self service features. IBM continues to reaffirm that users of Sterling should build solutions for the business outside of Sterling instead of inside. This is due to the fact that we still do not have granular permissions and the user interface continues to lack usability for non-tech business users.

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.