Hi Chathura, I think one other case is it is deployed already, and we just get a URL.
Also, I think we need to think how above can be useful in real life scenario, basically we need to come up with a full story on how above can be used. --Srinath On Wed, Dec 3, 2014 at 4:56 PM, Chathura Ekanayake <[email protected]> wrote: > > Executable process model is a BPEL or BPMN model, which can be executed in > a process runtime. We can support executable models in process center as > follows: > > Executable model contains: > - Process archive (e.g. BPEL archive) > - [optional] Deployment URL (e.g. URL of a BPS server) > - [optional] Webapp URL - This URL points to a web application which can > be used to create a new process instance and work on human tasks defined in > the process (i.e. this is the operational UI for the process). > > If a webapp URL is provided, process center provides a "Start" button > which simply directs to that URL. For example, employees can search process > models from the store side and start them if they are executable. If it is > not provided, the human task web app shipped with BPS can be used to start > and work on human tasks. > > If a deployment URL is provided, a "Deploy" button is shown, which deploys > a process archive in the corresponding BPS server. > > Thoughts... > > Regards, > Chathura > > > -- ============================ Blog: http://srinathsview.blogspot.com twitter:@srinath_perera Site: http://people.apache.org/~hemapani/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
