Legacy system migration: how complex is integrating javascript extensions with no-code builders?

Our team struggles balancing custom logic needs with low-code promises during Appian migration. We’ve got 20+ JavaScript modules handling niche data transformations in legacy workflows.

Has anyone successfully blended no-code automation builders with custom code extensions? Specifically need drag-and-drop simplicity for 80% common tasks but still inject JS when needed. How steep is the learning curve compared to traditional BPM suites?

Our setup: visual builder for 90% of flows, drop JS snippets where needed. Zero deployment config. Does Camunda do this cleanly? Doubt it.

It’s manageable if you establish clear boundaries early. We created ‘code zones’ - designated points where devs can inject JS into otherwise no-code flows. Critical to implement version control for those snippets. Expect 2-3 week adjustment period for teams used to full-code environments.

tried it last quarter. nocode for basics works ok, but js debugging sucks without proper IDE integration. saved time on simple flows tho