Re: [shark] How to 'Activate' a Shark process sometime in the future.

["Sasa Bojanic" <sasaboy@xxxxxxxxxxxxx>]

And what about activity1? In whose worklist will it appear?

But maybe you're right - if you make activity1 to be a tool activity with 
automatic start and manual finish mode, and make a tool
agent that never finishes (you can use an empty code for the tool agents), 
and define a deadline on activity 1 - maybe it'll work as
required, although I'm not sure without testing it.

Sasa.

----- Original Message -----
From: "David Delbecq" <delbd@xxxxxx>
To: <shark@xxxxxxxxxxxxx>
Sent: Monday, October 24, 2005 10:19 AM
Subject: Re: [shark] How to 'Activate' a Shark process sometime in the future.


Am surprised of your answer.
I was pretty sure it could be done using a deadline?
Move from activity1 to activity2 on a deadline basis
and have activity2 assigned to user.


Sasa Bojanic a écrit :

>Hi Geeta,
>
>this is something that is not directly supported by XPDL and also by shark.
>
>What you could do is to make your client (worklist) application smarter,
>and to read some ext. attribs. or process variables and to display the
>worklist according to some specific values (I think you've suggested this
>solution?).
>
>Also, I think you know that the time of creation of the process might not
>be the same as the time of its start (you have two API methods, one to
>create WfProcessMgr.create_process() or SharkConnection.createProcess()
>and another one to start the process WfProcess.start()), so maybe your
>client application can manipulate with this.
>
>The third option, and probably the most efficient (and most dangerous) one
>is to make some shark kernel extensions.
>
>
>Hope this helps,
>Sasa.
>
>
>
>>We have a requirement in our web app as follows: an admin may
>>create/instantiate a process, say today, but it should "become active",
>>ie. show up in the appropriate person's worklist only say 5 days later.
>>
>>I can of course make this possible programmatically using process vars
>>and  checking the current time etc. and I can also add an activity in
>>the  system's swim lane (before the very first activity) whose toolagent
>>will  be something very much like WaitProc.java in jctaprocs.. but I was
>> wondering if these are my only options or something cleaner/simpler
>>exists? ..Actually my boss seems to think this would be a very basic
>>requirement and therefore would be supported "natively" in Shark.. which
>> is why i am asking..:)
>>
>>Thank you for your time!
>>Geeta
>>
>>
>
>
>
>
>
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the shark@xxxxxxxxxxxxx mailing 
>list.
>To unsubscribe: mailto:shark-unsubscribe@xxxxxxxxxxxxx
>For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>





--------------------------------------------------------------------------------


>
> --
> You receive this message as a subscriber of the shark@xxxxxxxxxxxxx mailing 
> list.
> To unsubscribe: mailto:shark-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>