Can you perfect the example again?

[3xxx]

Thank you very much for the previous example.
Can you perfect the example again?

For example, when I create a new documents, do I create their events at the same time? Or create a new event and apply it to workflow when I clicks the action button?

In the list of documents presented to the user, for each document, is it right to list all possible actions and next states according to transition? When the user clicks on the action button, do I just create a new event and then apply it to workflow?

When I create a new event, it returns DocEventID, but what workflow applyevent needs is an DocEvent. Feel that I do is not correct.

[js-ojus]

1. When you create new documents, their events need not be created at the same time. Events should be created and applied in response to user actions (or system events).

2. Whether you list all possible actions in a list of documents is up to you. In my opinion, the possible actions - for a given user - on a given document, are best made available in the detailed view of that document (not in a document list view).

3. Yes, when the user clicks on an action button, we can create the corresponding event instance, and apply it to the document's workflow.

4. With a DocEventID, you can fetch the corresponding event instance using DocEvents.Get (please see

   flow/docevent.go

   Line 295 in a4bc409

   // Get retrieves a document event from the database, using the given

   onwards).

[3xxx]

Thank you for your patient answer, I will continue to try according to your suggestion.