Sub-Workflow variables should be shown when in a sub workflow

[douglasg14b]

When in a sub workflow, like a for loop, the variable available in that context should be indicated. This helps significantly with discovery & UX.

[glime-ai]

In Elsa Workflows, when you are within a sub-workflow, such as a ForEach loop, the variables that are available in that context are typically the ones that have been passed into the sub-workflow as input variables or the ones that have been created within the sub-workflow itself.

To improve discovery and user experience, it is important that the workflow designer or the development environment provides features such as IntelliSense or auto-completion to help users identify which variables are available. This feature would suggest variable names as you type, based on the context of the sub-workflow.

As of my knowledge cutoff date, if IntelliSense is not showing up for input variables of subworkflows, as mentioned in one of the GitHub issues (elsa-workflows/elsa-core#4136), it could be a bug or a missing feature that needs to be addressed by the Elsa Workflows development team.

For the best user experience, the workflow designer should clearly indicate which variables are in scope and available for use at any point in the workflow. This could be through documentation, tool-tips, or a dedicated panel within the workflow designer that lists all available variables and their types.

If you are experiencing issues with variable discovery within a sub-workflow or any other part of Elsa Workflows, I recommend checking the official documentation for any updates on this feature or reaching out to the community or support channels for assistance.

This comment was generated by Glime.