-
1. Re: Get node info for finished process instances
kukeltje Feb 23, 2010 4:04 PM (in response to swiderski.maciej)Am I missing something?
Yes
Why there is no way to specify processInstanceId instead of these two?
Well, as you see, there is neither functionality for showing it in the console nor support for retrieving the info in the (query)api. Besides that, there are Jira issue for extending both.. use the words "jbpm history open" in the jira...
So the conclusing might be (not 1000% sure, but 999%) that it is just not implemented yet.
Cheers,
Ronald
-
2. Re: Get node info for finished process instances
swiderski.maciej Feb 24, 2010 2:43 AM (in response to kukeltje)Thanks Ronald, learning path is longer than expected I always forget about browsing Jira, remainder is always good.
I ran a search as you suggested and I think thare is one that could be quite the same:
https://jira.jboss.org/jira/browse/JBPM-2533
I will put some comments and vote for that issue. In the meantime, attaching what I achieved so far without modifying jbpm core source code (only BPM console and its integration components).
Any comments are more than welcome.
-
jbpm-concole-history-diagram.JPG 153.2 KB
-
jbpm-concole-history-view.JPG 155.4 KB
-
-
3. Re: Get node info for finished process instances
kukeltje Feb 24, 2010 2:34 PM (in response to swiderski.maciej)Well, most of the coding/bugs/... on the console is done in the BPMC project (change JBPM in the jirs url to see it's issues). So details about howto do things etc in the console are best discussed in its forum.
jBPM mainly has 'high level' issues on the console...
Cheers,
Ronald
oh... the learning path still continues for me to
-
4. Re: Get node info for finished process instances
swiderski.maciej Feb 28, 2010 1:30 PM (in response to kukeltje)True, presentation of that is definitely an issue for BPM console forum but what about extending API for it? I saw similar post on development forum about it (placed a comment on it as well). Tried to look for something of this sort in jira but did not find it.
Perhaps we could file an issue in jira to extend the API?!