Currently, it's not possible to set a variable in one microflow and have it affect other microflows. There is currently no easy way to have a microflow require a yes/no input from a user from which it results in different outcomes.
Below is a crude microflow that shows what I mean.
Can be done in several ways through proper modelling and retrieving and commiting at the right time.
Using "CurrentSession" and an association to a tempObject that stores global variables is doable.
Hi Jim, you could define a non-persistent entity which provides you with the options you want. It is a surrogate but it works.