What problem does this feature request solve?
Users building custom interfaces for workflows requiring multiple file uploads currently only receive an array of URLs for these files, not the extracted text. This forces a workaround involving sub-workflows and additional blocks, which increases workflow complexity and runtime cost. Additionally, the ‘On Cancel’ action is not natively supported in custom interfaces, requiring another workaround with Logic blocks, again adding complexity and cost. While the native interface supports these features directly, it is visually outdated, creating a dilemma for users who desire both modern UIs and efficient functionality.
What is the use case for this feature?
A user needs to build a modern, custom interface for a workflow that involves uploading multiple documents (e.g., candidate resumes, project drafts, invoices). They expect the text from these multiple files to be automatically extracted and available for further processing, similar to how single files or native interfaces function. Concurrently, they need a straightforward ‘cancel’ option within their custom UI that seamlessly routes the workflow as defined, without adding extra, costly steps or blocks.
Please describe the functionality of this feature request
- Native Multi-File Text Extraction in Custom Interface: Extend the custom interface’s file upload capability to automatically extract text from multiple uploaded files, providing an array of extracted texts directly, rather than just URLs. This functionality should be consistent with how single files are handled and mirror the efficiency of the native interface.
- Native ‘On Cancel’ Action Support: Integrate direct support for the ‘On Cancel’ action within custom interfaces. This would allow users to configure a specific workflow path to be executed when a user cancels input, eliminating the need for manual workarounds involving Logic blocks.
Is there anything else we should know?
The current uploadFile function appears to behave differently for single versus multiple files, causing confusion regarding automatic text extraction. Implementing these features natively in the custom interface would significantly improve user experience by providing a more streamlined, cost-effective, and intuitive way to handle complex file uploads and user interaction flows, allowing developers to leverage modern UIs without functional compromises.