| Summary: | Missing a method to get a process variable via JBPM Remote API | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Ivo Bek <ibek> |
| Component: | Business Central | Assignee: | Marco Rietveld <mrietvel> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ivo Bek <ibek> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0.0 | CC: | kverlaen, mbaluch, smcgowan |
| Target Milestone: | ER5 | ||
| Target Release: | 6.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-06 20:11:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ivo Bek
2013-11-04 14:43:30 UTC
Hi Marco, would you mind explaining why this issue was marked with devel_ack-? I asked Kris some time ago what is the recommended approach to get information about the process (variables, visited nodes, etc.) when using REST or JMS but I haven't got an answer yet. I know you can use the VariableInstanceLog and similar classes to get this information but I do not think that users using REST or JMS will have the information about the database which is required. Thank you. Regards Marek Hi Marek, I've added devel_ack- because I see this as a request for a new feature and not as a bug. Users are unfortunately constrained to the pure REST api or pure JMS api if they want to access history/variable information. However, I'm leaving the last word to Kris: I've just e-mailed him asking him to comment on this issue, one way or the other. I do agree with the need for this feature -- I will definitely add it with (jBPM) 6.1. However, IMHO, the problem is not severe enough to be included in jBPM/BPMS 6.x. Fixed. 6.0.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/7a0d593a94c4f893001faf39c95fcbe0ee117f43 master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/d66c701ab00c4e1922b51024766a032535be2fcd I had a little bit of extra time to implement this and, once I thought about it, it was easier than expected -- and adding it helped me test a couple of other fixes as well. So I changed the devel_ack (-> +) and pushed the commits. Again, the main reason for the devel_ack- was the priority of the issue, given that this issue does not affect whether or not the API works, just which features are availability (as opposed to other issues). Verified in BPMS 6.0.0.ER5 |