• More Documentation needed

    By Mark Teichmann 2 decades ago

    This seems to be a good starting point for a workflow application. I tried to set up a demo workflow (without looking in the source code) but there are some things I did not get to work. It would be nice to have the OrderRequest example having runnable (there are no forms for it in the database).

    • Explain

      By Emanuele Sandri 2 decades ago

      Can you explain your idea of the OrderRequest?

      You should describe the workflow for the Order.

      • Hints for setting up a simple vacation workflow

        By Mark Teichmann 2 decades ago

        I would like to set up a simple workflow for approving vacation. But I am a bit confused what fields I have to create on the form and what actions and transitions I need. Maybe you can post a simple example which should do the following:



        A user creates a vacation request. It is mailed to Manager 1. Manager 1 can approve it or reject it. When approved it is mailed to Manager 2. Manager 2 can approve it finally or reject it.

        • Explanation

          By Emanuele Sandri 2 decades ago

          I'm writing the simple example that you suggested.

          Sorry for my previous response. I don't understanded your question. Now I try to explain better the step from the PaperSupplay Workflow to the OrderRequest Workflow.



          The activity Test.PaperSupplaying.ReqestOreder, is:

          Kind: Implementation,

          Impl. alternative: Subflow,

          Impl. Type: Asynchr

          Subflow reference: Test.OrderRequest



          So, when the engine process this activity:

          • it make a copy of the document (Form PaperSupplying)
          • in the new document set ActivityID to the id of the start activity of the Test.OrderRequest workflow
          • also set InstanceID to a new ID
          • the status to DW_Activity_WBegin
          • and compute the performer.



            When this job is complete the Test.PaperSupplaying.ReqestOreder activity end without waiting the termination of the new Test.OrderRequest workflow.



            Now in the application database we can find a new document that follow the rules of the Test.OrederRequest workflow.



            The Test.PaperSupplaying.UrgentRequestOrder is very similar but with Impl. Type: Synchr it wait for the new OrderRequest to complete.



            I think that the confusion is due to my choice to use only one form for two workflows. The PaperSupplying form contain all the fields needed for PaperSupplaying and OrderRequest workflows. The second table appear only in the OrderRequest workflow.



            I hope my explanation clarify your doubt.