Bug 1013540 - Reassignment property editor doesn't accept variable expression
Summary: Reassignment property editor doesn't accept variable expression
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 5.x.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER5
: 6.0.0
Assignee: Tihomir Surdilovic
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-30 10:14 UTC by Toshiya Kobayashi
Modified: 2018-12-03 20:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1013537
Environment:
Last Closed: 2014-08-06 20:12:22 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Fixed - Screen (196.77 KB, image/png)
2013-12-09 18:05 UTC, Marek Baluch 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPM-4141 0 Major Resolved Reassignment property editor doesn't accept variable expression 2013-12-09 18:04:45 UTC

Description Toshiya Kobayashi 2013-09-30 10:14:57 UTC 
+++ This bug was initially created as a clone of Bug #1013537 +++

Description of problem:

Platform BZ for https://issues.jboss.org/browse/JBPM-4141


Steps to Reproduce:

See https://issues.jboss.org/browse/JBPM-4141

Actual results:

You cannot input a variable expression like #{delegatee} in 'Users'/'Groups'/'Expires At' columns and get an error message 'The value in this field is invalid'

Expected results:

You can input a variable expression like #{delegatee} in 'Users'/'Groups'/'Expires At' columns
Comment 1 Tihomir Surdilovic 2013-09-30 14:47:23 UTC 
fixed in designer master and 6.0.x branches
Comment 2 JBoss JIRA Server 2013-09-30 14:49:37 UTC 
Tihomir Surdilovic <tsurdilo> updated the status of jira JBPM-4141 to Resolved
Comment 3 Marek Baluch 2013-12-09 18:04:35 UTC 
Verified on ER5.
Comment 4 Marek Baluch 2013-12-09 18:05:06 UTC 
Created attachment 834424 [details]
Fixed - Screen
Note You need to log in before you can comment on or make changes to this bug.