Re: Keep sequence for launched concurent requests

Hans Forbrich wrote:

> Create a workflow with the following activities:
>
> Start -> Execute Concurrent Process (=report 1) -> Execute (or Submit)
> Concurrent Process (=report 2) -> End
>
> Then use the WF Admi screens to launch process = workflow.
>
> You have all the tools available with Apps to do this!
>
> /Hans
>

Thought about this a bit more .... Execute Concurrent Process will wait & appear to hang the user's screen, which is no good if Report 1 takes a long time.

Revised suggestion:

Step 1: Start
Step 2: Submit Concurrent Process for report 1
Step 3: Wait for Concurrent Process
Step 4: Submit Concurrent Process for report 2
Step 5: (optional) notify that it's all done
Step 6: End

With Workflow Builder, it should not take a long time to do this if the reports are set up a concurrent processes.

>
> Guy Van Rinsveld wrote:
>
> > Hi,
> > How to keep the sequence ordered launching 2 differents concurrent
> > requests (containing both reports) ?
> > The registration of those concurrent requests have been done by adding
> > incompatibilities between each other and with themselves.
> > It's a script in a form which is launching both reports one after the
> > other.
> > Hoping that the order of resulting concurrent request ids would be used
> > for the execution timing sequence.
> > But it's not always the case.
> > 11.5.8 is the level used.
Received on Sun Jun 08 2003 - 19:48:05 CDT