Bug 1069747

Summary: Save button does not work with FreeMarkers forms
Product: [Retired] JBoss BPMS Platform 6 Reporter: Anton Giertli <agiertli>
Component: Business CentralAssignee: Mauricio Salatino <msalatin>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Livora <tlivora>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: kverlaen, ravindra.tubati, vigoyal
Target Milestone: ER1   
Target Release: 6.0.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
A process with a FreeMarker form (*.FTL) didn't save its data on clicking the save button. Instead, an error message would be generated in the log files with the message "User '[UserImpl:'***']' was unable to execution operation 'Start' on task id 4 due to a no 'current status' match". This issue has now been fixed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 19:50:30 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:
Embargoed:
Attachments:
Description Flags
exception
none
How to reproduce video.
none
..another reproducer none

Description Anton Giertli 2014-02-25 15:25:50 UTC
Created attachment 867467 [details]
exception

Description of problem:
If you use FTL forms for human task the save button does not work.

Version-Release number of selected component (if applicable):
BPM 6.0

How reproducible:


Steps to Reproduce:
1. Create process with human task and some output
2. Generate all forms
3. To be sure that the *.ftl forms will be displayed I have deleted all *.form files (maybe there is a better way, I wasn't sure)
4. Start the process, claim the task
5. FTL form is with input field is displayed. Type something into this field and hit SAVE button. Refresh the page and you can see that the input is empty.

Meanwhile, in the log, following exception can be observed:
Could not commit session: org.jbpm.services.task.exception.PermissionDeniedException: User '[UserImpl:'rtubati']' was unable to execution operation 'Start' on task id 4 due to a no 'current status' match

Full stack trace is attached.

Actual results:

SAVE button does not work with with FTL forms - value is not saved and WARN message is displayed in the log

Expected results:
SAVE button works with FTL forms - value should be stored and no warn should be present in the log


Additional info:

Comment 3 Marek Baluch 2014-03-06 09:06:32 UTC
Another (easier) way to reproduce:

1) create a new task in the task list (use your login for the task owner)
2) start the task
3) hit save

Comment 4 Mauricio Salatino 2014-03-13 11:30:48 UTC
Hi Marek, Anton,
Can you guys elaborate a little bit more about how the start task and save issues are related? The stack trace attached is due the fact that the task cannot be started for that user, and what is the error when you hit save? Or there is no errors just the fields are empty?

Comment 5 Marek Baluch 2014-03-13 12:54:37 UTC
Created attachment 873981 [details]
How to reproduce video.

Comment 6 Marek Baluch 2014-03-13 13:02:04 UTC
Mauricio, to be honest I have no idea why the 'save' but is there or what it's good for. I only know that if you click on it, you will get an exception. Please take a look at https://bugzilla.redhat.com/attachment.cgi?id=873981. That should put things into perspective.

Comment 7 Anton Giertli 2014-03-13 15:01:57 UTC
Created attachment 874020 [details]
..another reproducer

Comment 8 Anton Giertli 2014-03-13 15:05:45 UTC
Hi Mauricio,

I have made a little video which shows how I am reproducing the issue.

Permission denied exception is displayed when you click SAVE - the task actor is "guvnor" and logged user is "guvnor", so I find this exception actually unexpected :).

That WARN message is displayed when you click on DETAILS (Work Details Assignments Comments).

I don't know how these two errors are related, maybe there are two separate bugs, can't tell at the moment.

I simply receive both of these errors when I am reproducing the original SAVE button issue.

Cheers,
Anton

Comment 9 Anton Giertli 2014-03-13 15:09:16 UTC
Mauricio,

maybe both of these errors are completely not related to the original issue. However, the point is the value in the input field is not persisted upon clicking SAVE button.

Anton.

Comment 11 Mauricio Salatino 2014-04-06 08:58:24 UTC
Fix in jbpm form provider (6.0.x): http://github.com/droolsjbpm/jbpm/commit/fd7b57572

Comment 12 Tomas Livora 2014-04-22 15:53:55 UTC
Verified on BPMS 6.0.2 ER1