Skip to Main Content
IBM Sterling


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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Created by Guest
Created on Jun 18, 2020

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.

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
    May 12, 2021

    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
    May 10, 2021

    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?