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.

mailbox messageid and PrimaryDocument at AWS S3 custom protocol

During  AWS S3 custom protocol, at delivery side (consumer) AWSS3 client service is not getting primary document.
          to provide  primary document to AWS S3 service, we need to define logic like below
          <assign to="PrimaryDocument" from="/ProcessData/PrimaryDocument/@SCIObjectID"></assign>,
          which is an additional step which we are giving to our B2Bi processing engine.
          where as this not the behavior for other custom protocols implementation.
          During the AWS S3 custom protocol implementation for  MessageID we are defining extra logic to put the messages into
          staging mailbox by using Mailbox Add Service to get the messageID becuase of these extra steps our flow execution will take some more additional time.

  • Guest
  • Jan 14 2020
  • Future consideration
How will this idea be used?

During  AWS S3 custom protocol, at delivery side (consumer) AWSS3 client service is not getting primary document.
          to provide  primary document to AWS S3 service, we need to define logic like below
          <assign to="PrimaryDocument" from="/ProcessData/PrimaryDocument/@SCIObjectID"></assign>,
          which is an additional step which we are giving to our B2Bi processing engine.
          where as this not the behavior for other custom protocols implementation.
          During the AWS S3 custom protocol implementation for  MessageID we are defining extra logic to put the messages into
          staging mailbox by using Mailbox Add Service to get the messageID becuase of these extra steps our flow execution will take some more additional time.

What is your industry? Non-Industry Specific
What is the idea priority? Medium
  • Attach files