Input value updated as a result of a rule

[Tomasz Kot]

Would it possible to extend "input" element, so that it can be changed not only by manual entry, but also as an effect of another rule?
Fore example when a rule triggers, it also changes the 'input' current value from "0" to "1" so that we have a variable that stores that information (that something already happened) for other rule purposes.

Or alternatively, it could be not 'input' but additional element called "parameter" or "variable" (with a given individual name).

[NakedMarkets]

Hello,
Thanks for your interesting suggestion.
Indeed, we thought about adding "meta" parameter/variable/flag to give more possibilities to users.
A direct use-case would be your need for the M1 bar pausing the backtest above the H1 previous high, on your other post.
We have to analyze the different ways to implement it, in order to be easy to use and not too complex for users since this could add a significant layer of complexity.
But yes, it could be a new rule called "variable" or "flag", which could contain numeric value or boolean value.
We would need to add some ordering in rules execution as well, to let the users decide if the Setup Rule or the "variable" setting rule has to be executed before the other. And we would need to find a way to easily define a "variable" for the user (it's important for us to keep the interface easy to use).

[Tomasz Kot]

Thank you for your reply.
Yes, it would be perfect if it worked as you described.
Do you think it is possible to include it soon or it rather wont be possible?

[NakedMarkets]

We are polishing right now the last update (mainly tradingview interface update) and will analyze after how this new feature could be implemented without adding too much complexity but this look not that hard.
We will let you know when it could be implemented

[dboanca62]

Can't wait to see how this ends...looks like less confusion than my request...and could work for me also...