flowable-designer's People
Forkers
dbmalkovsky zhangwei5095 zhiqinghuang deadtrickster nagyistge x-isme lsmall dhzy0425 cephdon amethystdiana koke24 codeaudit happyshi0402 weizai118 leon-trainee eric-lemesre newlysoft sunfirescm zjdyzww easense paullmc patwanjau sarahchanqd hejun5448 egova-safety rogan0 bpmetc20 laashub-sda skummitha szjerrywang ofeliiab arenaswan dystudio sa-jackmax 8847141 directxbegin saiflowable baocang pei-han changsongyang moayyaed elambda zhaopufeng mounb blank-1 nowsun lisphi liuwuzhi pengpanfeng liuxiongwei123 hanxiaowen keren123 github-dengyu a925907195 david0718 help-lixin fairhopeweb tianxiaren dhineshaz 358302936flowable-designer's Issues
Eclipse designer removes important attributes
When saving a file, the Eclipse designer removes the following attributes from serviceTask nodes:
flowable:async="true" flowable:exclusive="false" flowable:class="MyClass"
The most important one being class
. Then, when I run my project, it blows up with something like:
org.flowable.engine.common.api.FlowableException: Errors while parsing:
[Validation set: 'flowable-executable-process' | Problem: 'flowable-servicetask-missing-implementation'] : One of the attributes 'class', 'delegateExpression', 'type', 'operation', or 'expression' is mandatory on serviceTask. - [Extra info : processDefinitionId = myProcessDefinition | processDefinitionName = MyProcessDefinition | | id = test | | activityName = Test | ] ( line: 7, column: 5)
Original issue: flowable/flowable-engine#738
Form key not working, probably due to erroneous 'activiti' namespace
A form key set in the properties of a start event or user task in the Eclipse modeler does not trigger the form to be presented. Inversely, a form key set in the Modeler App does work, but does not show in the properties view when the model is viewed in the Eclipse modeler.
Looking at the XML, the likely cause is that the Eclipse modeler (incorrectly) places the formKey attribute in the activity
namespace, defined as xmlns:activiti="http://activiti.org/bpmn"
:
<startEvent id="startevent1" name="Start" activiti:formKey="startForm"></startEvent>
whereas the Modeler App puts it in the flowable
namespace which is defined as xmlns:flowable="http://flowable.org/bpmn"
:
<startEvent id="startevent1" name="Start" flowable:formKey="startForm"></startEvent>
Perspective icon hover-over still shows Activiti
not supported myeclipse2019
I have the errors when i installed flowable-desinger plugs:
Cannot complete the install because of a conflicting dependency.
Software being installed: Flowable Eclipse BPMN 2.0 Designer 5.22.0 (org.flowable.designer.feature.feature.group 5.22.0)
Software currently installed: MyEclipse CI 16.0.0.c0000006t201904031303 (package.2915-Enr-0574.windows.x86_64 16.0.0.c0000006t201904031303)
Only one of the following can be installed at once:
Graphiti (Incubation) 0.15.0.201806050830 (org.eclipse.graphiti 0.15.0.201806050830)
Graphiti (Incubation) 0.13.1.v20160830-1309 (org.eclipse.graphiti 0.13.1.v20160830-1309)
Cannot satisfy dependency:
From: Graphiti (Incubation) 0.13.1.v20160830-1309 (org.eclipse.graphiti.feature.feature.group 0.13.1.v20160830-1309)
To: org.eclipse.equinox.p2.iu; org.eclipse.graphiti [0.13.1.v20160830-1309,0.13.1.v20160830-1309]
Cannot satisfy dependency:
From: Flowable Eclipse BPMN 2.0 Designer 5.22.0 (org.flowable.designer.feature.feature.group 5.22.0)
To: org.eclipse.equinox.p2.iu; org.eclipse.graphiti.feature.feature.group [0.13.1.v20160830-1309,0.13.1.v20160830-1309]
Cannot satisfy dependency:
From: MyEclipse CI 16.0.0.c0000006t201904031303 (package.2915-Enr-0574.windows.x86_64 16.0.0.c0000006t201904031303)
To: org.eclipse.equinox.p2.iu; org.eclipse.graphiti [0.15.0.201806050830,0.15.0.201806050830]
When I Checked my softwares, I found that the plugs import an old compent named org.eclipse.graphiti ,I try to hardcode the plugs version,but it did not work . How Can I Fixed this Error?
Runtime deploy feature
In the old activiti Kickstart was a buggy CMIS deploy feature to deploy your model + workflow to let's say Alfresco. This was a buggy feature which I never got to work.
Now I go wayy back to JBPM which had a flawless working deploy feature (custom servlet I know) which worked almost all the time and made workflow development fun.
So my request is to create a new deployment feature in the activiti designer which can remotely deploy the workflow via "whatever". A custom servlet or something similar is also an option, this is for development purposes en never intended for production systems. So adding an 'extra' jar to the activity system is doable.
Thanks!
Lane to support horizontal layout
Lane to support horizontal layout
Whether to consider using angular 4
Whether to consider using angular 4
Designer eliminates exception mapping declarations
We use Flowable Exception Mapping declarations und add them manually per XML-Editor to the bpmn, e.g.
<activiti:mapException errorCode="myErrorCode1">org.activiti.SomeException</activiti:mapException>
When opening the BPMN with the Flowable Designer and by changing/saving something, the exception mapping declarations are gone.
Is there any way to get around this? Will there be Exception Mapping Support in the Designer
question: flowable designer vs eclipse bpmn2
Hello,
quick question: what is recommended way to create BPMN2 files?
https://www.eclipse.org/bpmn2-modeler/ - works for Oxygen 4.7, last updated December 15, 2017.
Flowable designer works only for Mars 4.5 and Neon 4.6, and was last updated Nov 1, 2016 (and i doubt it support Flowable 6.x features).
signalintermediatethrowevent Properties Signal ref selection not work!
java.lang.NullPointerException
at org.activiti.designer.property.ActivitiPropertyFilter.getContainer(ActivitiPropertyFilter.java:42)
at org.activiti.designer.property.ActivitiPropertyFilter.getContainer(ActivitiPropertyFilter.java:42)
at org.activiti.designer.property.ActivitiPropertyFilter.getBusinessObject(ActivitiPropertyFilter.java:30)
at org.activiti.designer.property.PropertyGeneralFilter.accept(PropertyGeneralFilter.java:23)
at org.eclipse.graphiti.ui.platform.AbstractPropertySectionFilter.select(AbstractPropertySectionFilter.java:35)
at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyRegistryClassSectionFilter.appliesToSelection(TabbedPropertyRegistryClassSectionFilter.java:82)
at org.eclipse.ui.views.properties.tabbed.AbstractSectionDescriptor.appliesTo(AbstractSectionDescriptor.java:57)
at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyRegistry.adaptDescriptorFor(TabbedPropertyRegistry.java:328)
at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyRegistry.filterTabDescriptors(TabbedPropertyRegistry.java:305)
at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyRegistry.getTabDescriptors(TabbedPropertyRegistry.java:291)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.setInput(TabbedPropertySheetPage.java:730)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.selectionChanged(TabbedPropertySheetPage.java:556)
at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:335)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:237)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.handlePostSelectionChanged(SelectionService.java:122)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$1(SelectionService.java:112)
at org.eclipse.ui.internal.e4.compatibility.SelectionService$3.selectionChanged(SelectionService.java:80)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:167)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:164)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:161)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:273)
at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:270)
at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:114)
at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341)
at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356)
at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:36)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$3.selectionChanged(CompatibilityPart.java:132)
at org.eclipse.gef.ui.parts.AbstractEditPartViewer.fireSelectionChanged(AbstractEditPartViewer.java:247)
at org.eclipse.gef.ui.parts.AbstractEditPartViewer$1.run(AbstractEditPartViewer.java:131)
at org.eclipse.gef.SelectionManager.fireSelectionChanged(SelectionManager.java:156)
at org.eclipse.gef.SelectionManager.deselect(SelectionManager.java:126)
at org.eclipse.gef.ui.parts.AbstractEditPartViewer.deselect(AbstractEditPartViewer.java:202)
at org.eclipse.gef.editparts.AbstractEditPart.removeNotify(AbstractEditPart.java:942)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.removeNotify(AbstractGraphicalEditPart.java:823)
at org.eclipse.gef.editparts.AbstractEditPart.removeChild(AbstractEditPart.java:880)
at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:793)
at org.eclipse.graphiti.ui.internal.parts.ShapeEditPart.refreshChildren(ShapeEditPart.java:682)
at org.eclipse.gef.editparts.AbstractEditPart.refresh(AbstractEditPart.java:726)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:644)
at org.eclipse.graphiti.ui.internal.parts.ShapeEditPart.refresh(ShapeEditPart.java:596)
at org.eclipse.graphiti.ui.internal.parts.DiagramEditPart.refresh(DiagramEditPart.java:189)
at org.eclipse.graphiti.ui.editor.DefaultRefreshBehavior.internalRefreshEditPart(DefaultRefreshBehavior.java:264)
at org.eclipse.graphiti.ui.editor.DefaultRefreshBehavior.refresh(DefaultRefreshBehavior.java:177)
at org.eclipse.graphiti.ui.editor.DiagramBehavior.refresh(DiagramBehavior.java:806)
at org.eclipse.graphiti.ui.internal.editor.DiagramRefreshJob.runInUIThread(DiagramRefreshJob.java:107)
at org.eclipse.graphiti.ui.internal.editor.DiagramChangeListener.resourceSetChanged(DiagramChangeListener.java:152)
at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl$1.run(TransactionalEditingDomainImpl.java:781)
at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.runExclusive(TransactionalEditingDomainImpl.java:328)
at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.postcommit(TransactionalEditingDomainImpl.java:771)
at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.deactivate(TransactionalEditingDomainImpl.java:543)
at org.eclipse.emf.transaction.impl.TransactionImpl.close(TransactionImpl.java:712)
at org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:474)
at org.eclipse.emf.workspace.AbstractEMFOperation.execute(AbstractEMFOperation.java:155)
at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:516)
at org.eclipse.emf.workspace.impl.WorkspaceCommandStackImpl.doExecute(WorkspaceCommandStackImpl.java:208)
at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
at org.eclipse.graphiti.ui.internal.editor.GFWorkspaceCommandStackImpl.execute(GFWorkspaceCommandStackImpl.java:97)
at org.eclipse.graphiti.ui.internal.editor.GFCommandStack.execute(GFCommandStack.java:138)
at org.eclipse.graphiti.ui.internal.action.AbstractPreDefinedAction.executeOnCommandStack(AbstractPreDefinedAction.java:75)
at org.eclipse.graphiti.ui.internal.action.AbstractPreDefinedAction.genericRun(AbstractPreDefinedAction.java:94)
at org.eclipse.graphiti.ui.internal.action.DeleteAction.run(DeleteAction.java:96)
at org.eclipse.gef.KeyHandler.performStroke(KeyHandler.java:83)
at org.eclipse.gef.KeyHandler.keyPressed(KeyHandler.java:55)
at org.eclipse.gef.KeyHandler.keyPressed(KeyHandler.java:59)
at org.eclipse.gef.ui.parts.GraphicalViewerKeyHandler.keyPressed(GraphicalViewerKeyHandler.java:355)
at org.eclipse.gef.tools.SelectionTool.handleKeyDown(SelectionTool.java:331)
at org.eclipse.gef.tools.PanningSelectionTool.handleKeyDown(PanningSelectionTool.java:161)
at org.eclipse.gef.tools.AbstractTool.keyDown(AbstractTool.java:1016)
at org.eclipse.gef.tools.SelectionTool.keyDown(SelectionTool.java:491)
at org.eclipse.gef.EditDomain.keyDown(EditDomain.java:169)
at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchKeyPressed(DomainEventDispatcher.java:252)
at org.eclipse.draw2d.LightweightSystem$EventHandler.keyPressed(LightweightSystem.java:497)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1137)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1122)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1164)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1160)
at org.eclipse.swt.widgets.Widget.wmKeyDown(Widget.java:1883)
at org.eclipse.swt.widgets.Control.WM_KEYDOWN(Control.java:5049)
at org.eclipse.swt.widgets.Canvas.WM_KEYDOWN(Canvas.java:428)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4708)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:339)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5050)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3767)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
connection 'Name' wraps to next line (label width is reset to 100)
We have a rule engine in our application and rule names are pretty long, like
ENABLE_THIS_FUNCTIONALITY_AND_BLAH_BLAH.
We use references to these rules names in our bpmn flows over the 'connections' but at some point of activiti designer upgrade, these labels started to wrap. Label width (50-500) seems like has no use, it is always reset to '100'.
I was hoping this is fixed in flowable 5.22 designer, but still not working (Installed on Eclipse Neon).
Any hope, this could be fixed?
update site link to install eclipse flowable-designer its broken.
please fix it
Unable to add fields or click ok on the listener popup
ServiceTask extensionElements are removed at Process Definition edit
Describe the bug
When a process definition file having an extensionElements element within a serviceTask element is edited, extensionElements are removed from the XML.
For example, when you edit a Process Definition with a serviceTask having a failedJobRetryTimeCycle setting like bellow:
<serviceTask id="test" name="Test" flowable:async="true" flowable:expression="${someBean}"> <extensionElements><flowable:failedJobRetryTimeCycle>R60/PT1M</flowable:failedJobRetryTimeCycle></extensionElements> </serviceTask>
The corresponding xml file will just contain the following:
<serviceTask id="test" name="Test" flowable:async="true" flowable:expression="${someBean}"></serviceTask>
Expected behavior
extensionElements should not be dropped from process definition as this is an official Flowable feature. See documentation here: https://flowable.org/docs/userguide/index.html#failRetry
DATA_GRID is missing?
Hi,
I'm essentially copypasting
@Property(type = PropertyType.DATA_GRID, displayName = "Grocery List")
@DataGridProperty(itemClass = GroceryListItem.class)
private List<GroceryListItem> groceryList;
from the docs and editor complains about DATA_GRID is missing. I wasn't able to find it in the source too.
How to use it?
Thank you!
Diagram Window is not displayed on initial load - Oxygen 4.7.2
I installed the plugin on Oxygen and found that it mostly works but has one annoying bug that I found:
- The BPMN diagram does not appear when you first open it or when you switch between diagrams .
** Subsequent resizing of the diagram window will refresh the diagram
Eclipse Version: Oxygen 4.7.2
Flowable Plugin Version: 5.22
OS: Windows 7 Enterprise, SP 1, 64Bit
spring-boot-admin 2.x support
Hello,
author of spring-boot-admin is not going to rewrite activiti integration for 2.x (codecentric/spring-boot-admin#465 (comment)) :
Currently only 5% of the core-ui downloads uses the uiactivitu as well - so I'm not planning on reimplementing this for 2.0
So, are there any plans to support Flowable to spring-boot-admin?
Consider using angular2 front-end framework
hello , tijsrademakers,The front-end framework will choose angular2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.