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 Submitted
Categories Workflows
Created by Guest
Created on Aug 5, 2026

Enable Dynamic Mapping of Uploaded File Data to Forms, API Requests, and Transformation Inputs

Currently, file upload functionality allows users to upload files (CSV, Excel, XML, JSON, etc.) but does not provide a mechanism to map the uploaded file contents directly to downstream components such as:

  • UI Forms
  • API Request Payloads
  • XSLT Inputs
  • and more

As a result, users must manually extract, transform, and populate data before it can be consumed by applications or integrations. This creates additional implementation effort, increases the risk of errors, and limits the usefulness of file uploads in automation scenarios.

Proposed Enhancement

Introduce a configurable File-to-Target Mapping Framework that allows users to define how data from uploaded files should be mapped directly into target destinations.

Supported targets should include:

1. Form Field Mapping

Map file columns or data elements directly to UI form fields.

2. API Request Mapping

Allow uploaded file data to populate API request payloads.

3. XML/XSLT Input Mapping

Allow uploaded file data to be transformed into XML structures that can be used by XSLT processors.

and more

Mapping Designer

Provide a visual mapping interface that allows users to:

  • View uploaded file structure
  • Select source columns/elements
  • Select destination fields
  • Define transformations
  • Save reusable mappings

Expected Benefits

Improved Automation

Reduces manual data entry and eliminates repetitive mapping activities.

Faster Integrations

Allows business users and developers to connect uploaded files directly to downstream systems without custom coding.

Reduced Errors

Automated mapping minimizes transcription and transformation mistakes.

Better User Experience

Users can upload a file and immediately populate forms, trigger APIs, or initiate workflows.

Reusability

Saved mapping templates reduce implementation effort across multiple projects and use cases.

Example Business Scenarios

Customer Onboarding

Upload a customer CSV and automatically populate onboarding forms and create customer records through APIs.

Bulk Employee Creation

Upload employee data and automatically invoke HR system APIs for provisioning.

Product Catalog Import

Upload product spreadsheets and map data directly into catalog management APIs.

Legacy Data Transformation

Convert uploaded CSV or Excel data into XML structures and feed them into XSLT-based integration processes.

Vendor Data Processing

Upload vendor files and automatically initiate procurement workflows.

Success Criteria

  • Users can map uploaded file fields to forms, APIs, and transformation inputs without custom development.
  • Mapping configurations can be saved and reused.
  • Validation occurs before execution.
  • Support for structured file formats (CSV, Excel, XML, JSON).
  • Significant reduction in implementation effort for file-driven integration scenarios.

Business Value: This enhancement would transform file upload functionality from a simple file ingestion capability into a powerful integration and automation feature, enabling low-code/no-code data onboarding and accelerating enterprise integration scenarios.