Bug 1033541 - Task-Form not removed after task completion
Summary: Task-Form not removed after task completion
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: CR1
: 6.0.0
Assignee: Mauricio Salatino
QA Contact: Tomas Livora
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-22 10:50 UTC by Patrick Steiner
Modified: 2014-08-06 20:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 13528, User Guide-6-Beta-1 Build Date: 28-10-2013 14:07:45 Topic ID: 22390-549020 [Latest]
Last Closed: 2014-08-06 20:07:18 UTC
Type: Bug


Attachments (Terms of Use)

Description Patrick Steiner 2013-11-22 10:50:59 UTC
Title: Task-Form not removed after task completion

Describe the issue:
When working on a human task with a task-form, the task form is not removed after completing the task. This results in all task data remaining on the screen for the user, until he manually closes the task-form or starts a new task.


Suggestions for improvement:
Close the task-form when a user completed a task.


Additional information:

Comment 2 Mauricio Salatino 2013-11-22 11:11:07 UTC
Hi, the task is not removed because sometime the users wants to for example: add a comment to the completed task. Closing the window suddenly will be awkward from the usability perspective. In the future when we add  more options for the task lifecycle, like for example rollback a task completion this feature will be needed. It's also needed when you want to inspect where the process instance is after your task completion. IMO we should keep it open for now.

Comment 3 Mauricio Salatino 2014-01-03 13:41:47 UTC
This is BZ is related with this more concrete bug: https://bugzilla.redhat.com/show_bug.cgi?id=1042520
That is already fixed in master.. I will be waiting for all the acks to migrate the fix to 6.0.x

Comment 5 Tomas Livora 2014-01-24 11:14:30 UTC
Verified on BPMS 6.0.0 CR1


Note You need to log in before you can comment on or make changes to this bug.