Jun 30, 2009 12:02 pm
45 posts
Senior Boarder
|
|
|
Karma: 3
|
|
Is there any way I can reuse an existing (sub)process? I searched the forum and it seems this is doable, but can any one give an simple example?
|
|
|
|
|
|
|
The administrator has disabled public write access. |
Jul 1, 2009 2:22 pm
27 posts
Junior Boarder
|
|
|
Karma: 1
|
|
Step 1) Create your subprocess as a separate process. Make sure you've made a definitive decision about the input/output message types and error messages. Step 2) Locate the file build/MyReusableProcess-MyProcessPool.wsdl and copy/paste that into the required folder. Step 3) Rename if desired, but don't name is MyReusableProcess.wsdl as that name is already in use. So, better make it reusable_ProcessName.wsdl. Step 4) Drag n' drop this wsdl into your calling process like you would with any other (external) wsdl.
That's all there is to it :)
|
|
|
|
|
|
|
The administrator has disabled public write access. |
Jul 2, 2009 1:23 am
2755 posts
Admin
|
|
|
Karma: 58
|
|
All those steps can be skipped when using process templates, available in 6.0 as part of the Enterprise Edition.
Chris, you should mention that your way of doing things will break if the WSDL changes, and that you should not reuse an internal WSDL in the project where it is defined, or you'll run into conflicts.
Thanks,
Antoine
|
|
|
|
|
|
|
|
|
|
The administrator has disabled public write access. |
Jul 2, 2009 6:13 am
45 posts
Senior Boarder
|
|
|
Karma: 3
|
|
hi chris,
thanks for your reply. I tried your method without success. Another important fact is that the subprocess I wanna create actually involves many people tasks, and has a very long time span. So even if I successfully deployed it as you suggested, the call to WSDL will still timeout. Do you have any advice for this?
|
|
|
|
|
|
|
The administrator has disabled public write access. |
Jul 2, 2009 6:15 am
45 posts
Senior Boarder
|
|
|
Karma: 3
|
|
hi antonie,
does the EE support people activities in those "templates", as I mentioned in the reply to chris?
|
|
|
|
|
|
|
The administrator has disabled public write access. |
Jul 2, 2009 7:51 am
2755 posts
Admin
|
|
|
Karma: 58
|
|
Hi Liu,
we would have you model your process using asynchronous operations, so that no timeout would occur. The EE of course supports that. Chris solution can be modeled as well in an asynchronous manner. Just make sure you aren't using the same task for a request and a response, and it will be interpreted as an asynchronous interaction (that's what happens when defining a create and complete workflow operation for example).
Thanks,
Antoine
|
|
|
|
|
|
|
|
|
|
The administrator has disabled public write access. |
|