-
1. Re: workflow changes frequently, is it suitable to use jbpm?
kukeltje Dec 1, 2008 5:25 AM (in response to aspider)fixed, except.... contradictio in terminus
- what changes?
- what code changes?
- do running instances of processes have to change to
Please be way more specific -
2. Re: workflow changes frequently, is it suitable to use jbpm?
aspider Dec 2, 2008 10:22 AM (in response to aspider)we are developing a product which will be deployed in several countries, workflow of each country is same except that 2 or 3 steps are slightly different. for example
1)in one step this country need 1 confirm while other country need 2 or more comfirm
2)if amount is larger than limit, need a different approve routine.
these scenario means different workflow, is it possible to implement this without changing code? -
3. Re: workflow changes frequently, is it suitable to use jbpm?
kukeltje Dec 2, 2008 10:52 AM (in response to aspider)you can either:
- make a process which contains all these items, lots of decisionnodes etc so it will be fully generic but can get complex
- make a subprocess for each and decide runtime (by using an EL for the subprocess name and binding=late) which of the subprocesses to call. -
4. Re: workflow changes frequently, is it suitable to use jbpm?
aspider Dec 3, 2008 4:11 AM (in response to aspider)"kukeltje" wrote:
you can either:
- make a process which contains all these items, lots of decisionnodes etc so it will be fully generic but can get complex
- make a subprocess for each and decide runtime (by using an EL for the subprocess name and binding=late) which of the subprocesses to call.
Subprocess is not a good method.
But no everything can be set in process definition, because user want to set approval level number in page. if set, it need to generate several confirm process. -
5. Re: workflow changes frequently, is it suitable to use jbpm?
kukeltje Dec 3, 2008 4:42 AM (in response to aspider)Then use processvariables or other ways of retrieving that specific field from anywhere (e.g. your own db) and use it in a decisionhandler... that was what I meant with the first option.