| Summary: | Process Instances screen - aborting a task does not refresh/update the Process Instances view | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Tihomir Surdilovic <tsurdilo> |
| Component: | Business Central | Assignee: | Mauricio Salatino <msalatin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Livora <tlivora> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.0 | CC: | jpaulraj, kverlaen, paradhya, rrajasek, rzhang, zkrejcov |
| Target Milestone: | CR1 | ||
| 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:10:14 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
Tihomir Surdilovic
2013-12-12 23:29:39 UTC
Please see bug 1006827 - Improve partial refresh in console perspectives. The idea, as far as I remember, was to only automatically refresh a part of the whole perspective. The use-case being: User has a list of instances and is going through them. He wants to check the whole list. Aborts some, signals others or whatever, but still wants to check this exact list of instances after he is done. This is hard to do if he has to search through active, completed and aborted instance. Partial refresh makes it easier as he can keep the old list until he specifically requests a refresh. The UX team agreed with that, the issue is fixed and verified. This BZ requests we do the exact opposite. Please reconsider this issue. I think the issue is different here. When I take action in the details screen, if the state has changed it should be reflected on the instance list also. That is a logically expected behaviour. I am OK if this is not addressed for 6.0.0..but needs to be looked into 6.01. fixed in 6.0.x: http://github.com/droolsjbpm/jbpm-console-ng/commit/db6f1dcf1 Verified on BPMS 6.0.0 CR1 |