When I'm trying to create a low code app which triggers an Automation script where app data is linked to Automation script input parameters, I noticed that the value get wrapped as ["raw value"] which I assume is a JSON array.
Is there a way to pass in the raw value directly without having to parse it from inside the automation script?
As an example app:
- Dropdown component linked to ELEMENTS
- Button with onclick = Launch script X where a script parameter is linked to feed Dropdown > Elements > Element ID
The script receives ["12345/678"] as input where I would have preferred to receive 12345/678
Hi Wouter,
We have chosen this approach because feeds typically originate from a table, grid, or timeline that supports multiple selections. To ensure a reliable method for handling multiple values, we've decided to utilize JSON, as it eliminates any issues with separators.
While we acknowledge that the dropdown context does not allow for multiple selections, modifying your script would be necessary based on the feed source. Therefore, we believe that the current solution is the most consistent and practical choice.
Thanks for confirming and clarifying. I’ll manage.
The main annoyance here (at least for the current case where there’s only one dropdown value being passed along) is that some extra handling is required on the automation script code side to get to the actual input data, especially if one wants to re-use the same script for both manual invocation as well as automatic invocation through low-code apps. That, as well as not being able to use scripts that existed before out of the box.