guide for using Ash.Flow and multi step user flow with retries.
Hi Jack. Thanks for the good work you have put so far.
I was looking at Ash.Flow and the
Here is the Use case in detail:
A student submits his solution (let's call it
At any time, staff can cancel the submission assigned to the teacher. Staff can then re-assign it to any other teacher.
If any teacher does not evaluate the submission for 3 days, staff is notified.
Teacher can refuse to evaluate the assigned submission.
This
1. Is Ash.Flow a good use case for this?
In short, i need
I was looking at Ash.Flow and the
step DSL feels what i Might need. Here is the Use case in detail:
A student submits his solution (let's call it
submission) on a portal. The administrator / staff then assigns that to a teacher. The teacher evaluates the submission and submits back to the portal. Staff approves of the evaluation submitted by teacher. Student can then see the evaluated submission. At any time, staff can cancel the submission assigned to the teacher. Staff can then re-assign it to any other teacher.
If any teacher does not evaluate the submission for 3 days, staff is notified.
Teacher can refuse to evaluate the assigned submission.
This
Flow can span several days.1. Is Ash.Flow a good use case for this?
In short, i need
steps that are more like a gen state machine. I could sketch a rough diagram if that helps.
