IBM Sterling Ideas

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

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.

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 14 2020
  • Uncommitted Candidate
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