flowable-engine | highly efficient workflow | BPM library

by flowable Java Version: flowable-6.7.2 License: Apache-2.0

Download this library from

kandi X-RAY | flowable-engine Summary

flowable-engine is a Java library typically used in Automation, BPM, Nodejs, MongoDB, Spring Boot, Framework applications. flowable-engine has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can download it from GitHub, Maven.

A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.

Support

Quality

Security

License

Reuse

kandi-support Support

flowable-engine has a medium active ecosystem.
It has 5101 star(s) with 2029 fork(s). There are 255 watchers for this library.
There were 3 major release(s) in the last 12 months.
There are 224 open issues and 800 have been closed. On average issues are closed in 54 days. There are 32 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of flowable-engine is flowable-6.7.2

flowable-engine Support

Best in #BPM

Average in #BPM

flowable-engine Support

Best in #BPM

Average in #BPM

quality kandi Quality

flowable-engine has no bugs reported.

flowable-engine Quality

Best in #BPM

Average in #BPM

flowable-engine Quality

Best in #BPM

Average in #BPM

security Security

flowable-engine has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

flowable-engine Security

Best in #BPM

Average in #BPM

flowable-engine Security

Best in #BPM

Average in #BPM

license License

flowable-engine is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.

flowable-engine License

Best in #BPM

Average in #BPM

flowable-engine License

Best in #BPM

Average in #BPM

build Reuse

flowable-engine releases are available to install and integrate.
Deployable package is available in Maven.
Build file is available. You can build the component from source.

flowable-engine Reuse

Best in #BPM

Average in #BPM

flowable-engine Reuse

Best in #BPM

Average in #BPM

Top functions reviewed by kandi - BETA

kandi has reviewed flowable-engine and discovered the below as its top functions. This is intended to give you an instant insight into flowable-engine implemented functionality, and help decide if they suit your requirements.

Returns the time after the given date .
Generates the model for the given model object .
Prepare change activity state builders .
Gets the tasks from a query request .
Create a timer job entity for a timer event
Inject a sub - process with the given id .
Process the rules .
Reads edge information from the edge map .
Migrate model node model .
Extract content items from a query request .

flowable-engine Key Features

A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.

flowable-engine Examples and Code Snippets

No Code Snippets are available at this moment for flowable-engine.

See all Code Snippets related to BPM

Community Discussions

Trending Discussions on flowable-engine

How to read form fields by formKey from Activiti/Flowable API
Scala cannot resolve constructor

Trending Discussions on flowable-engine

QUESTION

How to read form fields by formKey from Activiti/Flowable API

Asked 2019-Jan-11 at 07:19

Using Flowable 6.4.0 (also applies to Activiti 6.0.0) I am rendering task form in my application by reading task form properties:

for (FormProperty formProperty : formService.getTaskFormData(taskId).getFormProperties()) {
//... render form field
}

I would like to replace this with Forms that can be designed in form designer and are set on task as formKey (also formReference, seems formReference is web app feature to select form to set formKey and deploy form to app). Problem is I do not see any API method to read form properties based on form key.

Reading answers in this question using formKey is correct way since task form properties are "deprecated", but is there API support for reading form fields for given formKey? Something like formService.getFormData(formKey, taskId).getFormProperties();?

Documentation (Flowable, Activiti) talks only about reading deployed form resource file my-custom-form.xml, does that mean I have to parse form file myself? I also checked Flowable Form Documentation and Sources but I do not see how to read form fields.

ANSWER

Answered 2019-Jan-11 at 07:19

If you want to use forms designed with the Flowable Form Designer, then there are additional API methods to fetch a start form and task form in Flowable. The getTaskFormModel(String taskId) method in TaskService gives you for example the form definition associated with the Task with that id:

https://github.com/flowable/flowable-engine/blob/master/modules/flowable-engine/src/main/java/org/flowable/engine/TaskService.java#L323

If you look in the implementation of this method you can see that it uses the formKey attribute of the userTask element to lookup the form definition based on key.

To get a start form of a process definition you can use the following code to lookup the formKey attribute of the startEvent element and get the form definition by key from the FormEngine:

https://github.com/flowable/flowable-engine/blob/master/modules/flowable-rest/src/main/java/org/flowable/rest/service/api/repository/ProcessDefinitionResource.java#L145

When you retrieved the FormInfo class from the getTaskFromModel method you can use the getFormModel method to retrieve the FormModel interface to get an instance of the Form model. Because the FormModel is made pluggable to make it easier to define your own Form model structure, you need to cast the FormModel interface to SimpleFormModel. From there you can use the getFormFields method to get to the form fields of the form definition.

Source https://stackoverflow.com/questions/54093038

QUESTION

Scala cannot resolve constructor

Asked 2017-Jan-23 at 16:58

I'm leveraging the interoperability between Scala and Java and have the below code that uses Scala, to instantiate a class in the same project that was written in Java. The CommandExecutor parameter is inherited from a parent class.

class IdmIdentityServiceImpl extends ServiceImpl with IdmIdentityService {
    override def createNativeUserQuery: NativeUserQuery = {
        new NativeUserQueryImpl(commandExecutor)
      }
}

I get an error, in instantiating NativeUserQueryImpl that says cannot resolve constructor

NativeUserQueryImpl was written in Java, but I've been reading about the interoperability between Java and Scala and feel like it should work.

This is the NativeUserQueryImpl class, which takes in that CommandExecutor type in one of it's constructors. The class comes from the flowable-engine library.

public class NativeUserQueryImpl extends AbstractNativeQuery<NativeUserQuery, User> implements NativeUserQuery {

  private static final long serialVersionUID = 1L;

  public NativeUserQueryImpl(CommandContext commandContext) {
    super(commandContext);
  }

  public NativeUserQueryImpl(CommandExecutor commandExecutor) {
    super(commandExecutor);
  }

  // results ////////////////////////////////////////////////////////////////

  public List<User> executeList(CommandContext commandContext, Map<String, Object> parameterMap, int firstResult, int maxResults) {
    return commandContext.getUserEntityManager().findUsersByNativeQuery(parameterMap, firstResult, maxResults);
  }

  public long executeCount(CommandContext commandContext, Map<String, Object> parameterMap) {
    return commandContext.getUserEntityManager().findUserCountByNativeQuery(parameterMap);
  }

}

EDIT:

Full error

Error:(31, 5) overloaded method constructor NativeUserQueryImpl with alternatives:
  (x$1: org.flowable.idm.engine.impl.interceptor.CommandExecutor)org.flowable.idm.engine.impl.NativeUserQueryImpl <and>
  (x$1: org.flowable.idm.engine.impl.interceptor.CommandContext)org.flowable.idm.engine.impl.NativeUserQueryImpl
 cannot be applied to (org.flowable.engine.impl.interceptor.CommandExecutor)
    new NativeUserQueryImpl(commandExecutor)

ANSWER

Answered 2017-Jan-23 at 16:58

From the full error posted in the original question, it appears that the CommandExecutor that is inherited from the parent class ServiceImpl has two different versions in the library

org.flowable.idm.engine.impl.interceptor.CommandExecutor and org.flowable.engine.impl.interceptor.CommandExecutor where the subtle difference is that one is from an idm package and one is not.

Changing ServiceImpl from the second package to the first, updates the CommandExecutor parameter that's being passed in, and fixes the issue.

Source https://stackoverflow.com/questions/41810996

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install flowable-engine

You can download it from GitHub, Maven.
You can use flowable-engine like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the flowable-engine component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .