I spent hours first time today to examine Automation, but found it is quite difficult to understand.
This was first time to feel tons of difficulties to understand Appsheet features so far I learned amng others.
RETURN value step. In the programming, it means one particular function to return the value. If there is any subsequent steps, they will not executed, as return is sign of the end of process.
If we ended up steps with return step, then we need to move to another step, thats why I feel Appsheet is graying out the following step so that we are not allowed to add any more steps as it wont be processed. This was what I thought.
then as you rightly said, it is troublesome and painful we start to build up the separete process.
But today I faced the problem and difficulties to understand how to pass the previous process return value… On the premier document, return value is used for validation, to see yes and no.
If we think this new Automation as kinda of programming, my assumption was “returned value” could be a sort of variable, either local or global, so those value could be reachable through the new . dot notation.
I tested several time in different scenario how to get the returned value (variable) which was generated by the previous / parent process and push to child process, but I could not find it.
Either way, I found new Automation is quite difficult to understand and handle.
The current action/workflow set ups could be more easy and intuitive, at least to me.