November 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-33) remember the previous form generation data fields

by Koen Aers (JIRA)

remember the previous form generation data fields ------------------------------------------------- Key: GPD-33 URL: http://jira.jboss.com/jira/browse/GPD-33 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 In the form generation, we currently start from the data entered in the task controller (if any) Whenever a form is generated, I would like the form generation data to be stored in the gpd.xml. Then, whenever the user does a second generation, the taskform generation form is prefilled with the previous data instead of starting from the controller data again. The motivation for this is that mostly people will not have controllers. Then if they have 5 data items to display and collect, it takes a lot of clicking. Users don't want to redo this effort for every little change they want to make to the form (additions and removals of fields). I think users should be able to live with the fact that controller data items are not kept automatically in sync with the task form data items. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (GPD-20) refactor naming strategy

by Koen Aers (JIRA)

refactor naming strategy ------------------------ Key: GPD-20 URL: http://jira.jboss.com/jira/browse/GPD-20 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 1) generate default node names when nodes are created: {node1, node2, ...}. use this naming strategy for each node type. 2) do not generate a node name for the start-state. users should be able to give the start-state a name, though. 3) use the following naming strategy for end states: {end, end2, end3, end4, ...} 4) do not generate names for transitions. the problem reporting should generate warnings if a node-type requires named nodes. the correlation between the graphical information and the processdefinition.xml will be done based on the position (index), rather then on the name. 5) disallow slashes in names in a process definition (nodes, transitions, process definition, actions, ...) Because slashes will be used as a separator in hierarchical names. We should also investigate if it would be useful to specify a strict set of chars that can be used like e.g. 0-9,a-z,A-Z,space,dot -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
11
0 / 0

[JBoss JIRA] Created: (GPD-31) Make sure all tasks in a process definition have a unique name

by Koen Aers (JIRA)

Make sure all tasks in a process definition have a unique name -------------------------------------------------------------- Key: GPD-31 URL: http://jira.jboss.com/jira/browse/GPD-31 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 When retrieving all tasks from a process definition like so: processDefinition.getTaskMgmtDefinition().getTasks() it returns a MAP of tasks, keyed by task name. This is a problem if two tasks anywhere in the same process definition have the same name. By default, the GPD creates all tasks as "task1" when it is the first task on a task node. If none of these were renamed, you would only get a single task when trying to get all of them for the process definition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (GPD-15) add a readme in the create-project wizard

by Koen Aers (JIRA)

add a readme in the create-project wizard ----------------------------------------- Key: GPD-15 URL: http://jira.jboss.com/jira/browse/GPD-15 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: Koen Aers Assigned To: Koen Aers all features that help beginner get started are vital imho. therefor, i think the forum user points out a good opportunity for us: we could create a readme.txt in the root of the generated project. that readme is opened when the wizard creates the project and it explains the contents of the project and what do to next. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (GPD-17) jpdl designer user guide and documentation

by Koen Aers (JIRA)

jpdl designer user guide and documentation ------------------------------------------ Key: GPD-17 URL: http://jira.jboss.com/jira/browse/GPD-17 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers A new user guide using screenshots of the new product should be written. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
5
0 / 0

[JBoss JIRA] Updated: (GPD-374) It is not possible to define variable mapping in jBPM process editor Created: 08/Jan/08 04:26 AM Updated: 10/Mar/09 05:41 AM

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-374?page=com.atlassian.jira.plugin... ] Koen Aers updated GPD-374: -------------------------- Component/s: jpdl Fix Version/s: jBPM jPDL Designer 3.2 > It is not possible to define variable mapping in jBPM process editor Created: 08/Jan/08 04:26 AM Updated: 10/Mar/09 05:41 AM > ------------------------------------------------------------------------------------------------------------------------------- > > Key: GPD-374 > URL: https://jira.jboss.org/jira/browse/GPD-374 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Environment: Environment: FC7/Eclipse Europa/jPDL Designer 3.1.0.SP1 > Reporter: Trevor Kirby > Assignee: Tom Baeyens > Fix For: jBPM jPDL Designer 3.2 > > > It is not possible to edit XML content of bpmToEsbVars and esbToBpmVars elements. > This now requires to edit process definition twice - once in graphical designer and second time in text editor to define mapping. This is very inconveniet for user as he frequently lose process arrangement as it is rearranged after this modification. > 1) I do not know if the jPDL designer supports editation of nested XML element > 2) If he supports it then we should find out if this is problem of only one platform or general deficiency -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-359) Events attached to activities

by Koen Aers (JIRA)

Events attached to activities ------------------------------ Key: GPD-359 URL: https://jira.jboss.org/jira/browse/GPD-359 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: Koen Aers Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (GPD-364) Differentiate a human task from a programmatic task (java, sql ... or state) in the editor as you do between a decision and a task

by Alexandre Navarro (JIRA)

Differentiate a human task from a programmatic task (java, sql ... or state) in the editor as you do between a decision and a task ----------------------------------------------------------------------------------------------------------------------------------- Key: GPD-364 URL: https://jira.jboss.org/jira/browse/GPD-364 Project: JBoss jBPM GPD Issue Type: Feature Request Affects Versions: jBPM jPDL Designer 4.0.0.GA Reporter: Alexandre Navarro Assignee: Koen Aers Differentiate a human task from a programmatic task (java, sql ... or state) in the editor as you do between a decision and a task -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1757) Tests that rely on timing may fail in slow test environments

by Howard Gao (JIRA)

Tests that rely on timing may fail in slow test environments ------------------------------------------------------------ Key: JBMESSAGING-1757 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1757 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.4.6.GA, 1.4.5.GA, 1.4.0.SP3.CP09 Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA Some tests, especially some clustered tests, are easy to fail due to slow test machines and networks. Need a way to alleviate the situation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (GPD-360) Refine wire object configuration

by Koen Aers (JIRA)

Refine wire object configuration -------------------------------- Key: GPD-360 URL: https://jira.jboss.org/jira/browse/GPD-360 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: Koen Aers Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2009