[jBPM5]Nodes and Process instance are not mapping after persistence
by Leo.Li
Hello All,
I'm a new to JBPM5, I think it should be a very good platform
for integration of business rules and workflow.
It might be one of our planning in 2012.
As we investigate and PoC in last two months, we found some unstable
problem in this platform. (http://community.jboss.org/thread/175443)
We had a template solution to fix this problem, made the Ksession
as singleton object. But we cannot load the snapshot or new assets easily.
We have following questions:
1. how to fix this kind of old data?
2. Can the JBPM5 store the data as the JBPM4 (RDBMS)?
3. Can we have some way to watch the data in
*PROCESSINSTANCEBYTEARRAY*
<http://localhost:8082/query.do?jsessionid=eba938cf1dbf38d4a410125bbe377788#>
?
4. If we have more than one history snapshot in the same processid(like
"leadprocess"), can the JBPM5 load the correct history version for my
instance?
In other word, we had created the instance1 on snapshot1, instance2 on
snapsot2. After the third version as the latest package. And than when I'm
handling the instance1, will they still using the snapshot1 workflow? Or we
need to coding in our side to achieve this?
Thanks a lots
Leo.Li
12 years, 11 months
Implementing recall functionality in JBPM
by Anupindi RaviShankar
Hi All,
The below diagram represents our workflow as per business requirements.
STATE A -----> STATE B ---------> STATE C
Control will flow from STATE A to STATE B. User at STATE B Can reject the
approval request or approve the request. If he approves the flow is smooth
ie. control should go to STATE C for approval.
Now if user at STATE B rejects then business demands the following 1)
Provide a recall option to user at STATE B so that we can change his
decision( means we have to keep the worklfow in waiting state here) 2) At
the same time control should go to STATE C where user will be shown only
the Reject button and if he rejects first then entire workflow will stop.
But if he has not taken any action then user at STATE B can recall his
reject decision and approve it. once he do it then control should go to
USER at state C as usual.
Now our doubt is this. 1) can we have the same workflow state at node B and
node C simultaneously. if we have to achieve what should be our approach.?
Thanks
Ravi
12 years, 11 months
API to access historic data
by Miklos Vajna
Hi,
During my thesis[1] part of the time was spent to extend jbpm and
bpm-console to implement REST API to query historic data. All these
infos are already logged in SQL, but there were no REST API to access
this data. To be exact, by "historic data", I mean:
1. Info about completed process instances.
2. Info about completed node instances.
3. Info about completed task instances.
To achieve this, I hacked jbpm and bpm-console. Given that the
bpm-console changes depend on jbpm, I would like to upstream the jbpm
patches first.
The original work is available in my jbpm/5.1.x-thesis and
bpm-console/thesis branches [2][3], but today I spent some time to
rebase the jbpm patches against master, where I guess such new features
are accepted. ;-)
The result landed at [4], but right now the build fails, as jbpm-gwt in
master depends on jbpm-bam-5.2.0, while jbpm-bam in master provides
jbpm-bam-5.3.0. (So even if I modify jbpm-bam, it gets delivered as
5.3.0 and when i build jbpm-gwt, it downloads the 5.2.0 snapshot.)
Any idea what is the solution for such a problem?
Thanks,
Miklos
[1] https://github.com/downloads/vmiklos/msc-thesis/thesis.pdf
[2] https://github.com/vmiklos/jbpm/tree/5.1.x-thesis
[3] https://github.com/vmiklos/bpm-console/tree/thesis
[4] https://github.com/vmiklos/jbpm/tree/for-upstream
12 years, 11 months
