When using the Script widget within a Flow to classify and route calls based on data, such as mapping inbound ANIs to caller types, the target list must live directly within the JS block. Any updates to that target list creates a new published version of the script.
We can upload a .js script to the asset library, but we’ve found that there’s no way to reference that asset via the flow.
Maybe someone can enlighten me as to what purpose uploading the script to the asset library is, beyond an easy backup.
Without native asset support, the only way to workaround this and decouple the script’s data from the flow logic is to host it externally and get it at runtime using the HTTP Request widget to call that external source.
I’m curious if this is on the roadmap , or if there’s any additional feedback from the team.