phatboyg / automatonymous Goto Github PK

Hi,

I was wondering if automatonymous can support multple different actors.
For example, if i had a StateMachine that represented authorizing a timesheet.
You'd have 2 different people, the line manager and the worker.

Worker can: Submit, Update
Line Manager can: Authorize, Reject

So I'd like to be able to ask the StateMachine, what are the possible actions for the Worker?
So perhaps:

State = Saved
Worker Can: Submit
Line Manager can: []

State = Submitted
Worker Can: []
Line Manager can: Authorize, Reject

Does that make sense?

In addition to Enter and Leave, consider an After event that is trigger after the state has become active...

Record an audit trail of state transitions, including a timestamp of when the transition occurred and which event caused the transition.

Keep the details of the event? Might be a lot of data, so consider two levels of auditing I guess.

Provide dynamic properties on the engine to match states that return true if the instance is in that state.

machine.Approved(instance) - kinda strange I guess.

instance.Approved - again, with a dynamic target places on the instance, which seems sorta icky if the machine is not known.

Just a thought.

Support dynamic, allowing events to be raised using the event name as a method invocation.

Something like:

machine.Approve(instance) - Event = Approve
instance.Approve() - could be done if instance implemented a dynamic target (optional, seems to confuse responsibilities)

supportTicketWorkflow.Close(ticket);

Just idea...