September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (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 Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-364?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-364. --------------------------- Resolution: Out of Date > 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://issues.jboss.org/browse/GPD-364 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 4.0.0.GA > Reporter: Alexandre Navarro > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > 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 was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

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

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-33?page=com.atlassian.jira.plugin.sys... ] Koen Aers resolved GPD-33. -------------------------- Resolution: Out of Date > remember the previous form generation data fields > ------------------------------------------------- > > Key: GPD-33 > URL: https://issues.jboss.org/browse/GPD-33 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > 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 was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-40) A slash character in Node name causes crash. Graphical Process Designer allows the slash to be entered anyway.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-40?page=com.atlassian.jira.plugin.sys... ] Koen Aers resolved GPD-40. -------------------------- Resolution: Out of Date > A slash character in Node name causes crash. Graphical Process Designer allows the slash to be entered anyway. > -------------------------------------------------------------------------------------------------------------- > > Key: GPD-40 > URL: https://issues.jboss.org/browse/GPD-40 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > The Graphical Process Designer allows the user to enter a Task Node name that includes a slash, such as "Accounting/Finance". The slash causes a crash later on when the process is run, and it isn't obvious what the source of the problem is. Suggestion: somehow prevent the user from entering a name that includes a slash. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-355) offer conversion support for files from jBPM 3 to jBPM 4

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-355?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-355. --------------------------- Resolution: Out of Date > offer conversion support for files from jBPM 3 to jBPM 4 > -------------------------------------------------------- > > Key: GPD-355 > URL: https://issues.jboss.org/browse/GPD-355 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Optional > Fix For: jBPM jPDL Designer 4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-286) support deployment of process archives to runtime

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-286?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-286. --------------------------- Resolution: Out of Date > support deployment of process archives to runtime > ------------------------------------------------- > > Key: GPD-286 > URL: https://issues.jboss.org/browse/GPD-286 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > should be based on ant targets. > for each process file, an action "Create Deploy Target" will be exposed > Create Deploy Target will create a target in an ant build file. The generated target should look like the one below. > I think we can assume a "build.xml" in the root as the build file. If not present, the build file should be created. If the file already exists, the target for deployment of the new process definition should be added to the existing build file. Maybe an macrodef can be used. > It is assumed that the processes and process classes that are to be deployed as a business archive are part of one src directory. > The jPDL process designer plugin should leverage the ant view to allow users to activate the build. If a user decides to create a deploy target for a process definition, then the ant view should be made visible and the build file should be added to the list of build files if not already present. Ideally the build file would be expanded so that the process deploy target is immediately visible. > <?xml version="1.0" encoding="UTF-8"?> > <project name="zzz" default="deploy.zzz"> > <property name="database" value="hsqldb" /> > <property name="jbpm.home" value="c:/Software/jbpm-4.1-SNAPSHOT" /> > <target name="deploy.zzz"> >  > <path id="compile.classpath"> > <fileset dir="${jbpm.home}"> > <include name="jbpm.jar" /> > </fileset> > <fileset dir="${jbpm.home}/lib" /> > </path> > <mkdir dir="target/classes" /> > <javac srcdir="src" > destdir="target/classes" > classpathref="compile.classpath" /> > <copy todir="target/classes"> > <fileset dir="src"> > <exclude name="**/*.java" /> > </fileset> > </copy> >  > <jar destfile="target/zzz.bar"> > <fileset dir="target/classes" /> > </jar> >  > <mkdir dir="target/deploycfg" /> > <copy file="${jbpm.home}/install/src/cfg/hibernate/jdbc/${database}.hibernate.cfg.xml" > tofile="target/deploycfg/jbpm.hibernate.cfg.xml" > overwrite="true"> > <filterset filtersfile="${jbpm.home}/install/jdbc/${database}.properties" /> > </copy> > <copy file="${jbpm.home}/install/src/cfg/jbpm/standalone.testsuite.jbpm.cfg.xml" > tofile="target/deploycfg/jbpm.cfg.xml" > overwrite="true" /> >  > <path id="deploy.classpath"> > <pathelement location="target/classes" /> > <pathelement location="target/deploycfg" /> > <path refid="compile.classpath" /> > </path> > <taskdef name="jbpm-deploy" > classname="org.jbpm.pvm.internal.ant.JbpmDeployTask" > classpathref="deploy.classpath" /> >  > <jbpm-deploy file="target/zzz.bar" /> > </target> > </project> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

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

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-360?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-360. --------------------------- Resolution: Out of Date > Refine wire object configuration > -------------------------------- > > Key: GPD-360 > URL: https://issues.jboss.org/browse/GPD-360 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

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

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-359?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-359. --------------------------- Resolution: Out of Date > Events attached to activities > ------------------------------ > > Key: GPD-359 > URL: https://issues.jboss.org/browse/GPD-359 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > This means adding the capability of the gpd to place BPMN events on the border of activities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-339) pageflow designer

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-339?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-339. --------------------------- Resolution: Out of Date > pageflow designer > ----------------- > > Key: GPD-339 > URL: https://issues.jboss.org/browse/GPD-339 > Project: jBPM GPD > Issue Type: Feature Request > Components: seam > Reporter: Tom Baeyens > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > new version of the pageflow designer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-306) Self Referencing Connections

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-306?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-306. --------------------------- Resolution: Out of Date > Self Referencing Connections > ---------------------------- > > Key: GPD-306 > URL: https://issues.jboss.org/browse/GPD-306 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Minor > Fix For: jBPM jPDL Designer 4.x > > > There should be a convenient way to create connections that reference the same node as source and target -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-309) CDATA sections in custom elements of actions with config-type="bean" cause a NPE in the jBPM GPD.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-309?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-309. --------------------------- Resolution: Out of Date > CDATA sections in custom elements of actions with config-type="bean" cause a NPE in the jBPM GPD. > ------------------------------------------------------------------------------------------------- > > Key: GPD-309 > URL: https://issues.jboss.org/browse/GPD-309 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.6 > Environment: Eclipse 3.4.1 > Reporter: Roman Heinz > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.2 > > > CDATA sections in custom elements of actions with config-type="bean" cause a NPE in the jBPM GPD. > <?xml version="1.0" encoding="UTF-8"?> > <process-definition > xmlns="urn:jbpm.org:jpdl-3.2" > name="simple"> > <start-state name="start"> > <transition name="to_state" to="first"> > </transition> > </start-state> > <state name="first"> > <event type="node-enter"> > <action class="foo.Bar" name="fooAction" config-type="bean"> > <rowdocid><![CDATA[ Test ]]></rowdocid> > </action> > </event> > <transition name="to_end" to="end"> > </transition> > </state> > <end-state name="end"></end-state> > </process-definition> > Result: > java.lang.NullPointerException > at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source) > at org.jbpm.gd.common.xml.GenericElementXmlAdapter.doModelAdd(Unknown Source) > at org.jbpm.gd.common.xml.XmlAdapter.initialize(Unknown Source) > at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source) > at org.jbpm.gd.jpdl.xml.ActionDomAdapter.doModelAdd(Unknown Source) > at org.jbpm.gd.common.xml.XmlAdapter.initialize(Unknown Source) > at org.jbpm.gd.jpdl.xml.ActionDomAdapter.initialize(Unknown Source) > at org.jbpm.gd.jpdl.xml.EventDomAdapter.doModelAdd(Unknown Source) > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016