Bug 1244345 - [GSS](6.1.z) DateTime attribute for Timers is implemented in engine but it is not exposed in Designer
Summary: [GSS](6.1.z) DateTime attribute for Timers is implemented in engine but it is...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: CR1
: 6.1.0
Assignee: Tihomir Surdilovic
QA Contact: Kirill Gaevskii
URL:
Whiteboard:
Depends On: 1244249
Blocks: bpms6.1.3-payload
TreeView+ depends on / blocked
 
Reported: 2015-07-17 20:33 UTC by Alessandro Lazarotti
Modified: 2020-03-27 20:09 UTC (History)
4 users (show)

Fixed In Version:
Clone Of: 1244249
Environment:
Last Closed: 2020-03-27 20:09:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Alessandro Lazarotti 2015-07-17 20:33:42 UTC 
+++ This bug was initially created as a clone of Bug #1244249 +++

Description of problem:

Since BPM SUite 6.0.0 jBPM engine supports DateTime for Timers but it is not present in Designer yet.
Jira to get it in engine: https://issues.jboss.org/browse/JBPM-3233

User drawing process in Eclipse is not able to migrate to business-central Designer without parser errors due that.

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


How reproducible:
Always

--- Additional comment from JBoss Product and Program Management on 2015-07-17 11:10:07 EDT ---

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 2 Jeremy Lindop 2015-08-14 14:48:12 UTC 
Fixed

master: https://github.com/droolsjbpm/jbpm-designer/commit/067c8724842663b2bae42171b9cf38c584979421
6.3.x: https://github.com/droolsjbpm/jbpm-designer/commit/2398d18228ae0703f441af1fcbf9a72bc542a13c
6.2.x: https://github.com/droolsjbpm/jbpm-designer/commit/65d20e2b85fefb057ef4740be637bba371449798
Comment 4 Kirill Gaevskii 2015-09-01 12:37:00 UTC 
Time Date have no validation. But other values (Time Cycle and Time Duration) have the same behaviour. 
Verified, but new BZ opened: https://bugzilla.redhat.com/show_bug.cgi?id=1258869
Note You need to log in before you can comment on or make changes to this bug.