Javascript in visual workflow builders - overkill or essential for RFP specs?

Evaluating how to balance no-code simplicity with enterprise needs in our Camunda RFP. Sales demos all promise ‘easy’ visual builders but we need proof of real customization.

Latenode’s JS hooks caught my eye - anyone using these for complex transformations? Specifically need to mandate array operations like the context’s survey analysis merging. How do you validate that low-code isn’t just pretty UI covering limited functionality?

We pushed their JS to extremes - custom NPM packages for data blending across 5+ sources. Visual builder handles 80%, we drop to code for complex merges. Audit team loves the versioned history. https://latenode.com

Make vendors demonstrate: 1) Build simple workflow visually 2) Inject custom code for exception handling 3) Show execution logs with both elements. Latenode’s unified debugging convinced our architects.

code hooks non-negotiable. our etl jobs need js array magic

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.