Improvement Idea – Variable Scope and Naming in Microflows

Hello everyone,

I would like to propose an improvement regarding variable scoping in microflows.

Current Situation:

• In a single microflow, it is not possible to have more than one variable with the same name (e.g., $IteratorShift), regardless of the declared scope. The system simply uses the first declared variable, which can lead to confusion and potential errors when working with nested or conditional logic.
• Additionally, when naming conflicts occur, the platform automatically appends suffixes like _1_1_1_1_1 to variable names. This makes the flow harder to read and maintain, especially in complex scenarios.

Suggested Improvement:

• Allow variables with the same name to exist in different scopes (for example, inside separate if blocks or loops), similar to block scoping in programming languages like JavaScript.
• Improve the naming mechanism to avoid excessive suffixes and instead provide a clearer, context-aware naming strategy or allow developers to reuse names safely within isolated scopes.

Benefits:

• Increased readability and maintainability of microflows.
• Reduced risk of errors caused by unintended variable reuse.
• Cleaner naming conventions for better developer experience.