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.
Hi @Guest , can you please answer the queries so that IBM can take RFE to the next state?
thanks,
Bharat K
Hi @Guest thanks for detailing out the RFE.
Question.
1. Do you look for uploaded file to map with one form context at a time or multiple forms context in a on-boarding flow? How about if some forms are made to run in the loop?
Once file is uploaded, data will be mapped to the form elements to get subsequently mapped to the apis or xslt transformation. Please correct the understanding.
It is assumed that custom data as mentioned in example of catalog, customer etc, to be stored in external systems through calling the external apis and not in sfg and B2BI.
regards,
Bharat K
@Guest