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.

Upload UI component - make file details available for mapping

In a Dialog sceen, when a partner uploads a file using the Upload UI component, the only values available for mapping to an API or XSLT are the file contents in plain-text or Base64 encoded format.

We should be able to map the file details to our API calls and XSLT inputs:

Name provided by partner

Original filename as uploaded by partner

Size of file

ContentType (e.g. text/plain, application/pdf, etc)

These are values already available in the vchDocument API when looking at "ACTIVITY" files, for sponsor-uploaded files.

  • Guest
  • Jun 18 2020
  • Planned for future release
What is your industry? Non-Industry Specific
How will this idea be used?

1) Map these values back to the UI to provide confirmation to the user that they uploaded the correct file.

2) Pass these values to API calls so that they can be tracked and audited.

e.g. for an activity where a user is uploading files to be tested, we would be able to track the filenames that a user has uploaded. That way the partner would know which files they have already tested and which files still need to be uploaded.

  • Guest commented
    12 May, 2021 06:27am

    Greg,


    The vchDocument API only provides information on SPONSOR-uploaded files when called using a sponsor user account or Internally generated token. It appears the only way to retrieve PARTNER-uploaded file information is to call it using the account of the partner that uploaded it.


    Additionally, the vchDocuments API does not provide the name provided by the user in the Upload dialog. Example output:


    "documentKey": "964e744d-1155-4dab-b7d8-452e26951768",

    "contentLength": 7,

    "documentName": "test.hex",

    "contentType": "application/octet-stream",


    The real issue is that none of these fields are available for mapping as part of the activity. Not even documentKey is available so - even if the vchDocument API returned all of the information for all uploaded files - we would not have a documentKey to pass to it.


    Thanks,

    John

  • Admin
    Greg Russell commented
    10 May, 2021 03:15pm

    John,

    In the details of this Idea, it is mentioned

    "These are values already available in the vchDocument API when looking at "ACTIVITY" files, for sponsor-uploaded files."


    By using the vchDocument API, are you able to solve your use case of passing these additional values to the back-end API? So, if we are to implement an enhancement to the API to expose additional parameters directly , would this really mean that one less API could be called for the implementer? Or would there be a reason in your use case where we would need an additional API to call these additional parameters?

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.