Bug 1128383 - FTL forms can't parse Expressions
Summary: FTL forms can't parse Expressions
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Form Modeler
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Andy Taylor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-09 21:14 UTC by Anton Giertli
Modified: 2018-03-31 22:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
[0] full stack trace (8.82 KB, text/plain)
2014-08-09 21:15 UTC, Anton Giertli
no flags Details

Description Anton Giertli 2014-08-09 21:14:07 UTC
Description of problem:
If you use some expression in the human task, for example, you specify actor as #{actor} and not via "actor" then the FTL form used for this human task will be causing issues.

Version-Release number of selected component (if applicable):
bpm 6.0.2

How reproducible:
always

Steps to Reproduce:
1. Create process definition , start->human task->end
2. create process variable dynamicActor:string
3. configure Human Task actor with value #{dynamicActor}
4. generate all forms
5. delete all forms created by Form Modeler, only leave FTL forms.
6. execute the process, fill in the process variable, start working on a task (by pressing Work button), following exception will be displayed in the log

23:12:10,070 ERROR [freemarker.runtime] (http-localhost/127.0.0.1:8080-6) Template processing error: "Expression EXPRESSIONVALUE is undefined on line 216, column 45 in sample human task.": freemarker.core.InvalidReferenceException: Expression EXPRESSIONVALUE is undefined on line 216, column 45 in sample human task.

Actual results:
FTL form can't work with expressions

Expected results:
FTL form can work with expressions

Additional info:

Comment 1 Anton Giertli 2014-08-09 21:15:27 UTC
Created attachment 925408 [details]
[0] full stack trace


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