So I guess I can place "flow" data into the Content of each User Task indicating the next possible steps. That way, I can dynamically render pages for users depending on the current task, and the next possible outcome?
Do you think this is the best approach?
For example, when a user loads their task, say a REVIEW task, I want to dynamically determine what are the next possible outcomes (APPROVE -> Go to Test, REJECT -> Go back to development) and display those buttons on the screen for the user.
Is the Content field, the best place to store this information?
Thanks in advance.
Charlie