DOCSLIB.ORG

Flowable 5.23.0 User Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Flowable 5.23.0 User Guide Flowable 5.23.0 User Guide Table of Contents 1. Introduction 1.1. License 1.2. Download 1.3. Sources 1.4. Required software 1.4.1. JDK 7+ 1.4.2. IDE 1.5. Reporting problems 1.6. Experimental features 1.7. Internal implementation classes 2. Getting Started 2.1. What is Flowable? 2.2. Flowable and Activiti 2.3. Building a command-line application 2.3.1. Creating a process engine 2.3.2. Deploying a process definition 2.3.3. Starting a process instance 2.3.4. Sidetrack: transactionality 2.3.5. Querying and completing tasks 2.3.6. Writing a JavaDelegate 2.3.7. Working with historical data 2.3.8. Conclusion 2.4. Getting started with the Flowable REST API 2.4.1. Setting up the REST application 2.4.2. Deploying a process definition 2.4.3. Start a process instance 2.4.4. Task list and completing a task 3. Configuration 3.1. Creating a ProcessEngine 3.2. ProcessEngineConfiguration bean 3.3. Database configuration 3.4. JNDI Datasource Configuration 3.4.1. Configuration 3.4.2. JNDI properties 3.5. Supported databases 3.6. Creating the database tables 3.7. Database table names explained 3.8. Database upgrade 3.9. Job Executor (since version 6.0.0) 3.10. Job executor activation 3.11. Mail server configuration 3.12. History configuration 3.13. Exposing configuration beans in expressions and scripts 3.14. Deployment cache configuration 3.15. Logging 3.16. Mapped Diagnostic Contexts 3.17. Event handlers 3.17.1. Event listener implementation 3.17.2. Configuration and setup 3.17.3. Adding listeners at runtime 3.17.4. Adding listeners to process definitions 3.17.5. Dispatching events through API 3.17.6. Supported event types 3.17.7. Additional remarks 4. The Flowable API 4.1. The Process Engine API and services 4.2. Exception strategy 4.3. Query API 4.4. Variables 4.5. Transient variables 4.6. Expressions 4.7. Unit testing 4.8. Debugging unit tests 4.9. The process engine in a web application 5. Spring integration 5.1. ProcessEngineFactoryBean 5.2. Transactions 5.3. Expressions 5.4. Automatic resource deployment 5.5. Unit testing 5.6. JPA with Hibernate 4.2.x 5.7. Spring Boot 5.7.1. Compatibility 5.7.2. Getting started 5.7.3. Changing the database and connection pool 5.7.4. REST support 5.7.5. JPA support 5.7.6. Further Reading 6. Deployment 6.1. Business archives 6.1.1. Deploying programmatically 6.2. External resources 6.2.1. Java classes 6.2.2. Using Spring beans from a process 6.2.3. Creating a single app 6.3. Versioning of process definitions 6.4. Providing a process diagram 6.5. Generating a process diagram 6.6. Category 7. BPMN 2.0 Introduction 7.1. What is BPMN? 7.2. Defining a process 7.3. Getting started: 10 minute tutorial 7.3.1. Prerequisites 7.3.2. Goal 7.3.3. Use case 7.3.4. Process diagram 7.3.5. XML representation 7.3.6. Starting a process instance 7.3.7. Task lists 7.3.8. Claiming the task 7.3.9. Completing the task 7.3.10. Ending the process 7.3.11. Code overview 7.3.12. Future enhancements 8. BPMN 2.0 Constructs 8.1. Custom extensions 8.2. Events 8.2.1. Event Definitions 8.2.2. Timer Event Definitions 8.2.3. Error Event Definitions 8.2.4. Signal Event Definitions 8.2.5. Message Event Definitions 8.2.6. Start Events 8.2.7. None Start Event 8.2.8. Timer Start Event 8.2.9. Message Start Event 8.2.10. Signal Start Event 8.2.11. Error Start Event 8.2.12. End Events 8.2.13. None End Event 8.2.14. Error End Event 8.2.15. Terminate End Event 8.2.16. Cancel End Event 8.2.17. Boundary Events 8.2.18. Timer Boundary Event 8.2.19. Error Boundary Event 8.2.20. Signal Boundary Event 8.2.21. Message Boundary Event 8.2.22. Cancel Boundary Event 8.2.23. Compensation Boundary Event 8.2.24. Intermediate Catching Events 8.2.25. Timer Intermediate Catching Event 8.2.26. Signal Intermediate Catching Event 8.2.27. Message Intermediate Catching Event 8.2.28. Intermediate Throwing Event 8.2.29. Intermediate Throwing None Event 8.2.30. Signal Intermediate Throwing Event 8.2.31. Compensation Intermediate Throwing Event 8.3. Sequence Flow 8.3.1. Description 8.3.2. Graphical notation 8.3.3. XML representation 8.3.4. Conditional sequence flow 8.3.5. Default sequence flow 8.4. Gateways 8.4.1. Exclusive Gateway 8.4.2. Parallel Gateway 8.4.3. Inclusive Gateway 8.4.4. Event-based Gateway 8.5. Tasks 8.5.1. User Task 8.5.2. Script Task 8.5.3. Java Service Task 8.5.4. Web Service Task 8.5.5. Business Rule Task 8.5.6. Email Task 8.5.7. Mule Task 8.5.8. Camel Task 8.5.9. Manual Task 8.5.10. Java Receive Task 8.5.11. Shell Task 8.5.12. Execution listener 8.5.13. Task listener 8.5.14. Multi-instance (for each) 8.5.15. Compensation Handlers 8.6. Sub-Processes and Call Activities 8.6.1. Sub-Process 8.6.2. Event Sub-Process 8.6.3. Transaction subprocess 8.6.4. Call activity (subprocess) 8.7. Transactions and Concurrency 8.7.1. Asynchronous Continuations 8.7.2. Fail Retry 8.7.3. Exclusive Jobs 8.8. Process Initiation Authorization 8.9. Data objects 9. Forms 9.1. Form properties 9.2. External form rendering 10. JPA 10.1. Requirements 10.2. Configuration 10.3. Usage 10.3.1. Simple Example 10.3.2. Query JPA process variables 10.3.3. Advanced example using Spring beans and JPA 11. History 11.1. Querying history 11.1.1. HistoricProcessInstanceQuery 11.1.2. HistoricVariableInstanceQuery 11.1.3. HistoricActivityInstanceQuery 11.1.4. HistoricDetailQuery 11.1.5. HistoricTaskInstanceQuery 11.2. History configuration 11.3. History for audit purposes 12. Eclipse Designer 12.1. Installation 12.2. Flowable Designer editor features 12.3. Flowable Designer BPMN features 12.4. Flowable Designer deployment features 12.5. Extending Flowable Designer 12.5.1. Customizing the palette 12.5.2. Validating diagrams and exporting to custom output formats 13. REST API 13.1. General Flowable REST principles 13.1.1. Installation and Authentication 13.1.2. Configuration 13.1.3. Usage in Tomcat 13.1.4. Methods and return-codes 13.1.5. Error response body 13.1.6. Request parameters 13.2. Deployment 13.2.1. List of Deployments 13.2.2. Get a deployment 13.2.3. Create a new deployment 13.2.4. Delete a deployment 13.2.5. List resources in a deployment 13.2.6. Get a deployment resource 13.2.7. Get a deployment resource content 13.3. Process Definitions 13.3.1. List of process definitions 13.3.2. Get a process definition 13.3.3. Update category for a process definition 13.3.4. Get a process definition resource content 13.3.5. Get a process definition BPMN model 13.3.6. Suspend a process definition 13.3.7. Activate a process definition 13.3.8. Get all candidate starters for a process-definition 13.3.9. Add a candidate starter to a process definition 13.3.10. Delete a candidate starter from a process definition 13.3.11. Get a candidate starter from a process definition 13.4. Models 13.4.1. Get a list of models 13.4.2. Get a model 13.4.3. Update a model 13.4.4. Create a model 13.4.5. Delete a model 13.4.6. Get the editor source for a model 13.4.7. Set the editor source for a model 13.4.8. Get the extra editor source for a model 13.4.9. Set the extra editor source for a model 13.5. Process Instances 13.5.1. Get a process instance 13.5.2. Delete a process instance 13.5.3. Activate or suspend a process instance 13.5.4. Start a process instance 13.5.5. List of process instances 13.5.6. Query process instances 13.5.7. Get diagram for a process instance 13.5.8. Get involved people for process instance 13.5.9. Add an involved user to a process instance 13.5.10. Remove an involved user to from process instance 13.5.11. List of variables for a process instance 13.5.12. Get a variable for a process instance 13.5.13. Create (or update) variables on a process instance 13.5.14. Update a single variable on a process instance 13.5.15. Create a new binary variable on a process-instance 13.5.16. Update an existing binary variable on a process-instance 13.6. Executions 13.6.1. Get an execution 13.6.2. Execute an action on an execution 13.6.3. Get active activities in an execution 13.6.4. List of executions 13.6.5. Query executions 13.6.6. List of variables for an execution 13.6.7. Get a variable for an execution 13.6.8. Create (or update) variables on an execution 13.6.9. Update a variable on an execution 13.6.10. Create a new binary variable on an execution 13.6.11. Update an existing binary variable on a process-instance 13.7.
Load more

Recommended publications
  • A Language to Coordinate Collaborative Reuse
    The Journal of Systems and Software 131 (2017) 505–527 Contents lists available at ScienceDirect The Journal of Systems and Software journal homepage: www.elsevier.com/locate/jss CollabRDL: A language to coordinate collaborative reuse ∗ Edson M. Lucas a,b, , Toacy C. Oliveira a,d, Kleinner Farias c, Paulo S.C. Alencar d a PESC/COPPE, Federal University of Rio de Janeiro, Brazil b IPRJ/UERJ, Polytechnic Institute, State University of Rio de Janeiro, Brazil c PIPCA, University of Vale do Rio dos Sinos (Unisinos), Brazil d David Cheriton School of Computer Science, University of Waterloo, Canada a r t i c l e i n f o a b s t r a c t Article history: Coordinating software reuse activities is a complex problem when considering collaborative software de- Received 19 June 2015 velopment. This is mainly motivated due to the difficulty in specifying how the artifacts and the knowl- Revised 17 January 2017 edge produced in previous projects can be applied in future ones. In addition, modern software systems Accepted 31 January 2017 are developed in group working in separate geographical locations. Therefore, techniques to enrich collab- Available online 2 February 2017 oration on software development are important to improve quality and reduce costs. Unfortunately, the Keywords: current literature fails to address this problem by overlooking existing reuse techniques. There are many Software reuse reuse approaches proposed in academia and industry, including Framework Instantiation, Software Prod- Collaboration uct Line, Transformation Chains, and Staged Configuration. But, the current approaches do not support Framework the representation and implementation of collaborative instantiations that involve individual and group Language roles, the simultaneous performance of multiple activities, restrictions related to concurrency and syn- Reuse process chronization of activities, and allocation of activities to reuse actors as a coordination mechanism.
    [Show full text]
  • Digital Archive: Arrange, Assign & Sign!
    Digital Archive: Arrange, Assign & Sign! Patrícia Raquel Vieira Sousa Mestrado Integrado em Engenharia de Redes e Sistemas Informáticos Departamento de Ciência de Computadores 2016 Orientador Prof. Dr. Luís Filipe Coelho Antunes, Professor Auxiliar, FCUP Coorientador Eng. Pedro Vasconcelos Castro Lopes Faria, Consultor, HealthySystems Todas as correções determinadas pelo júri, e só essas, foram efetuadas. O Presidente do Júri, Porto, ______/______/_________ Patr´ıcia Raquel Vieira Sousa Digital archive: Arrange, Assign & Sign! Departamento de Ciˆencia de Computadores Faculdade de Ciˆencias da Universidade do Porto Junho de 2016 Patr´ıcia Raquel Vieira Sousa Digital archive: Arrange, Assign & Sign! Disserta¸c˜ao submetida `aFaculdade de Ciˆencias da Universidade do Porto como parte dos requisitos para a obten¸c˜ao do grau de Mestre em Engenharia de Redes em Sistemas Inform´aticos Orientador: Prof. Dr. Lu´ıs Filipe Coelho Antunes Co-orientador: Eng. Pedro Vasconcelos Castro Lopes Faria Departamento de Ciˆencia de Computadores Faculdade de Ciˆencias da Universidade do Porto Junho de 2016 To my parents and my love for all the support and patience... 3 Acknowledgments I want to thank my advisor Professor Lu´ıs Antunes for the support in all this time of work, for all suggestions that improved my thesis and for this opportunity. I also want to thank my co-advisor Pedro Faria for all dedication, support, patience and guidance that made all this work possible. Thanks for innovative ideas and the security knowledge transmitted during this thesis. I also want to thank Professor Manuel Eduardo Correia for the interest that has always shown for this thesis work and for all the support and ideas.
    [Show full text]
  • Alfresco Developer Series: Advanced Workflows
    ecmarchitect.com Alfresco Developer Series Advanced Workflows 2nd Edition February, 2012 Jeff Potts This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. ecmarchitect.com Alfresco Developer Series Advanced Workflows 2nd Edition February, 2012 Jeff Potts About the Second Edition This tutorial was originally written in November of 2007. Since then, Alfresco has added the Share web client and the Activiti workflow engine, so, at first glance you could say that a lot has changed. On the other hand, if you've already worked through the Custom Content Types and Custom Actions tutorials, you'll already be comfortable with configuring the form service for Alfresco Share. And, although Activiti is an entirely new workflow engine, it was built by the same guys that built jBPM, after all, so it is similar enough in concept that people already familiar with building Alfresco workflows using jBPM should have a pretty easy transition moving to Activiti. The original version of this tutorial spent a little too long on details up front, which I tried to fix when this tutorial was used as the basis of the workflow chapter in the Alfresco Developer Guide. So, for this edition of the tutorial, I cut down on theory and moved into some Hello World examples as quickly as I could. I also did a little bit of rearranging to provide two distinct parts to the tutorial so that the first part covers everything you need to know, from concepts to deploying and running processes, with the focus being on the steps and tools using simple processes.
    [Show full text]
  • Activiti Timer Boundary Event Example
    Activiti Timer Boundary Event Example CharacteristicRoilier Dietrich and variolates allied Chris her flax sobs: so anarthrouslywhich Constantine that Noach is nettled inwrap enough? very definably. Saturated and uneven Freddy still acidulated his Ciliata victoriously. Your profile picture is used as the logo for your personal space. Thanks for contributing an answer to Stack Overflow! Text: Enter descriptive text. So far, Alexandrya would look as expected. This language enables analysts to model their business. If you press two active signal boundary events catching the same signal event, of boundary events are triggered, even if anyone are district of warehouse process instances. The boundary definition. Can Digital Transformation happen without Process Automation? Execute any arbitrary expression! The example is an start events but were found. Alfresco Share with service i understand. Time event example activiti events, active while in boundary event listeners were all activities based on given listener and rest web service task and uses. Within the subprocess, a separate token is born which runs through the subprocess from the start to the end event, but the token of the parent process waits until the subprocess completes. So it looks like name due core is properly set, but why per the workflow immediately goes to remove next task instead have waiting press the discount date? But eventually continues after which is set of eclipse workspace to true. However, due to the broadcast semantics of the signal, it would also be propagated to all other process instances which have subscribed to the signal event. Compensation handlers are not contained in normal flow and are only executed when a compensation event is thrown.
    [Show full text]
  • Introduction to Flowable
    Introduction to Flowable Filip Hrisafov (@filiphr) Jose Antonio Alvarez (@jaam_eu) 1 Short Introduction Filip Hrisafov Jose Antonio Alvarez • Core Software • Head Solutions Architect at Flowable Architect at Flowable • Flowable core dev • Flowable core contributor • MapStruct project lead • 11 years experience in process management 29.01.2020 2 © 2020 Flowable AG. All rights reserved. Agenda & Goals • Explaining all that Flowable can do in 60 mins is … impossible • Short History • Open Standards (BPMN, CMMN, DMN) • A glimpse of what you can do • And hope to inspire you to look deeper! 29.01.2020 3 © 2020 Flowable AG. All rights reserved. Flowable Open Source Project Native BPMN, CMMN and DMN engines Speed, scalability and innovation process instances • High performance, high scale • Fastest engines available per second • Years of real world use • Lightweight FlowableFlowableA C 5.23 6.3 Community is key Long heritage of Open Source BPM • Credibility through engagement • Origins since 2010 in Activiti and jBPM & contributions • Established 2016 by Alfresco co-founder • Usage all over the world and Activiti team 2016 Flowable and in all kind 2010 Activiti jBPM of industries 29.01.2020 4 © 2020 Flowable AG. All rights reserved. Flowable Family Tree Implemented BPM on Red Hat R&D focus shifted to new microservice Drools architecture orchestration engine (Zeebe) jBPM 5 Camunda 7 Flowable 6 2010 2013 jBPM 3 Activiti Flowable 2009 2013 2016 Bonitasoft Effektif Activiti 5/6/7 Dropped jBPM and built own Lightweight BPMN, now rolled into Continues without architects but no core engine updates engine, but no longer a focus Signavio (not open source) 29.01.2020 5 Case and Business Process Management The heart of Digitalization Case management Manage complex business activities that require a mix of human and electronic actions, such as an incoming application, a submitted claim, a complaint, or incident management Business process management Coordinate or orchestrate the behaviour of people, systems, information, and things to produce business outcomes.
    [Show full text]
  • BPMN Conformance in Open Source Engines
    BPMN Conformance in Open Source Engines Matthias Geiger, Simon Harrer, Jorg¨ Lenhard, Mathias Casar, Andreas Vorndran and Guido Wirtz Distributed Systems Group University of Bamberg Bamberg, Germany fmatthias.geiger, simon.harrer, joerg.lenhard, [email protected] Abstract—Service-oriented systems are increasingly imple- when it comes to the construction of service orchestrations. mented in a process-based fashion. Multiple languages for More and more vendors are currently implementing the building process-based systems are available today, but the specification, resulting in a variety of freely available or Business Process Model and Notation (BPMN) is becoming 1 ubiquitous. With BPMN 2.0 released in 2011, execution seman- commercial modeling tools and engines . BPMN engines tics were introduced, supporting the definition of executable are able to consume and execute processes provided in the processes. Nowadays, more and more process engines directly correct format. Since BPMN standardizes the format and support the execution of BPMN processes. However, the BPMN semantics of processes, their execution behavior should not specification is lengthy and complex. As there are no official differ on different engines. However, this only works if all tests and no certification authority, it is very likely that engines a) implement only a subset of the language features and b) engines fully implement BPMN in the same manner with implement language features differently. In other words, we respect to semantics, which is an unrealistic assumption. If suspect that engines do not conform to the standard, despite the engines do not fully conform to the standard, i.e., if they fact that they claim support for it.
    [Show full text]
  • Open-Source Workflow Evaluation an Evaluation of the Activiti BPM Platform
    Mid Sweden University The Department of Information Technology and Media (ITM) Author: Mikael Nilsson E-mail address: [email protected] Study programme: M. Sc. In engineering – computer engineering, 240 ECTS Examiner: Tingting Zhang, [email protected] Tutors: Anders Trollås, Cybercom Group, [email protected] Fredrik Håkansson, Mid Sweden University, [email protected] Scope: 29901 words inclusive of appendices Date: 2012-06-29 M.Sc. Thesis within Computer Engineering AV, 30 ECTS Open-source Workflow Evaluation An evaluation of the Activiti BPM Platform Mikael Nilsson Open-source Workflow Evaluation - An evaluation of the Activiti BPM Platform Abstract Mikael Nilsson 2012-06-29 Abstract The aim of this thesis is to evaluate the newly released open-source business process management platform Activiti. The platform is evalu- ated in the first instance by implementing the control-flow patterns which will be used at a later stage as a comparison with other platforms that have already been evaluated. Activiti comes with a web application called Activiti Explorer which is a graphical user interface between the process engine and the user. As all the desired features commissioned by the Cybercom Group were not available in the Activiti Explorer its source-code was extended. These extended features included support for several companies per installation and the ability to customize the layout of the components in user task forms. The report is concluded with a comparison between Activiti, jBPM, OpenWFE and Enhydra shark with regards to the control-flow patterns. Keywords: Open-source, Workflow, BPM, BPMN 2.0, Activiti, Work- flow patterns, Control-flow patterns ii Open-source Workflow Evaluation - An evaluation of the Activiti BPM Platform Acknowledgements Mikael Nilsson 2012-06-29 Acknowledgements Thanks to..
    [Show full text]
  • Opportunities for Business Process Semantization in Open-Source Process Execution Environments
    Proceedings of the Federated Conference on DOI: 10.15439/2015F250 Computer Science and Information Systems pp. 1307–1314 ACSIS, Vol. 5 Opportunities for Business Process Semantization in Open-source Process Execution Environments Krzysztof Kluza and Krzysztof Kaczor and Grzegorz J. Nalepa and Mateusz Sla´ zy˙ nski´ AGH University of Science and Technology al. A. Mickiewicza 30, 30-059 Krakow, Poland E-mail: {kluza,kk,gjn,mslaz}@agh.edu.pl Abstract—Business Process models help to visualize the pro- The paper is structured as follows. In Section II, we present cesses of an organization. There are open-source process execu- selected open-source process execution environments and their tion engines that provide the environments for enacting process general architecture. Section III gives an overview of business models. However, they lack semantization capabilities. In this paper, an overview of Business Process semantization techniques process semantization approaches, especially focusing on the is provided. Moreover, we discuss the common architecture of solution developed in the SUPER project and the SAP AG the selected open-source process execution environments (Activiti, company. Section IV analyzes the possibilities of process jBPM and Camunda) and provide the insights how they can be semantization in the open-source process execution environ- improved using semantization methods. We also present the use ments. The paper is concluded in Section V. of the introduced techniques in the Prosecco (Processes Semantics Collaboration for Companies) research project. II. OPEN-SOURCE PROCESS EXECUTION ENVIRONMENTS Index Terms —Business Process Model and Notation (BPMN), 3 4 Business Process Semantization, Business Process Management All three environments, Activiti [4], jBPM [5], and Ca- munda5 [6], are light-weight BPM suites with extensible I.
    [Show full text]
  • Evaluation of Business Process Management Systems
    Evaluation of business process management systems Daina Ardzevičiūtė doc. dr. Tomas Skersys Ernestas Kvedaras Department of Information Systems Department of Information Systems Kaunas, Lithuania Kaunas University of Technology Kaunas University of Technology e-mail:[email protected] Kaunas, Lithuania Kaunas, Lithuania e-mail: [email protected] e-mail: [email protected] Abstract—Nowadays, more and more industrial organizations are modeling their business processes and implementing business II. THE FRAMEWORK FOR EVALUATING BUSINESS PROCESS process management systems. Therefore, it is very important to MANAGEMENT SYSTEMS choose a suitable business process management system. The main Criteria identified during literary analysis were divided into purpose of this paper is to propose and verify the framework for six groups: evaluating business process management systems. This method covers the most important aspects of a business process • Business process modeling criteria – evaluate systems management systems from the design to the monitoring of the ability to model clear and complete processes and to business process. The main advantage of the proposed approach import and export them; is that it is independent from any specific domain and execution engine. The evaluation framework was tested by applying it to • Systems development criteria – evaluate business four different business process management systems: “Bonita process execution capabilities and user interface BPM”, “Camunda”, “jBPM“, “Activiti”. design; Keywords—Business
    [Show full text]
  • Activiti in Action
    Executable business processes in BPMN 2.0 IN ACTION Tijs Rademakers FOREWORDS BY Tom Baeyens AND Joram Barrez SAMPLE CHAPTER MANNING Activiti in Action by Tijs Rademakers Chapter 1 Copyright 2012 Manning Publications brief contents PART 1INTRODUCING BPMN 2.0 AND ACTIVITI..............................1 1 ■ Introducing the Activiti framework 3 2 ■ BPMN 2.0: what’s in it for developers? 19 3 ■ Introducing the Activiti tool stack 32 4 ■ Working with the Activiti process engine 49 PART 2IMPLEMENTING BPMN 2.0 PROCESSES WITH ACTIVITI..........85 5 ■ Implementing a BPMN 2.0 process 87 6 ■ Applying advanced BPMN 2.0 and extensions 112 7 ■ Dealing with error handling 146 8 ■ Deploying and configuring the Activiti Engine 169 9 ■ Exploring additional Activiti modules 193 PART 3ENHANCING BPMN 2.0 PROCESSES ................................223 10 ■ Implementing advanced workflow 225 11 ■ Integrating services with a BPMN 2.0 process 260 12 ■ Ruling the business rule engine 286 v vi BRIEF CONTENTS 13 ■ Document management using Alfresco 311 14 ■ Business monitoring and Activiti 340 PART 4MANAGING BPMN 2.0 PROCESSES ..................................367 15 ■ Managing the Activiti Engine 369 Part 1 Introducing BPMN 2.0 and Activiti This first part of the book provides an introduction to the Activiti framework and the background about the BPMN 2.0 standard. In chapter 1, we’ll cover how to set up an Activiti environment, starting with the download of the Activiti framework. In chapter 2, you’ll be introduced to the main elements of the BPMN 2.0 standard in order to create process definitions. Chapter 3 offers an overview of the Activiti framework’s main components, including the Activiti Designer and Explorer.
    [Show full text]
  • Business-Driven Software Engineering Lecture 6 – Process Implementation
    IBM Research – Zurich Process Management Technologies Business-Driven Software Engineering Lecture 6 – Process Implementation Jochen Küster [email protected] IBM Research – Zurich Process Management Technologies Agenda ° Motivation ° Different Abstraction Levels of Process Models ° The Concept of a Process Engine ° Overview of the Activiti Process Framework ° Process Implementation with the Activiti Process Engine ° Summary and References 2 Dr. Jochen Küster | BDSE2013 IBM Research – Zurich Process Management Technologies Motivation 3 Dr. Jochen Küster | BDSE2013 IBM Research – Zurich Process Management Technologies Motivation ° So far: – How to express process models with BPMN? – How to use a process model for documentation? ° But: – How to implement a process and make it executable? – How to execute the process model? 44 Dr. Jochen Küster | BDSE2013 IBM Research – Zurich Process Management Technologies Different Abstraction Levels of Process Models 5 Dr. Jochen Küster | BDSE2013 IBM Research – Zurich Process Management Technologies Different Levels of Abstraction of Process Models ° Different persons in a company want different view on processes ° Leads to different levels of process models ° Example: – Business View for Business Analysts – IT View for IT architects ° Levels of abstraction depend on the company and the domain of process modeling as well as the goals 6 Dr. Jochen Küster | BDSE2013 IBM Research – Zurich Process Management Technologies Process Models at Different Abstraction Levels IT Architect/ Business Analyst Business- Developer Technical level Process Process Model Model ° Process models are used both by business and IT people in companies ° Business-level Process Model – detailed understanding of the main behavior from business view – requirements specification for process implementation ° Technical Process Model – used for automated process execution ° Existence of process models at different abstraction levels is very common in companies today 7 Dr.
    [Show full text]
  • A Generic BPMS User Portal for Business Processes Execution Interoperability
    A generic BPMS user portal for business processes execution interoperability Andrea Delgado, Daniel Calegari Instituto de Computacion,´ Facultad de Ingenier´ıa Universidad de la Republica´ Montevideo, Uruguay, 11300 fadelgado, dcalegarg@fing.edu.uy Abstract—A Business Process Management System (BPMS) REST/SOAP API that allows the portal and other applications integrates several software modules to support the business to invoke specific operations from the process engine. process (BP) lifecycle. A process modeler, process engine, a web There is a wide variety of BPMS, both open source and portal for interaction with users, and a REST/SOAP API which exposes operations from the engine are key ones. In previous proprietary, with different support levels for the BPs lifecycle. works we have evaluated several BPMS identifying similarities In previous works we have evaluated several BPMS [7], [8] in terms of the concepts they manage in their user portals and identifying similarities in terms of the concepts they manage the APIs they expose, and how the user portals became highly in their user portals and the APIs they expose. In such works coupled to the underlying process engine through the provided we have evidenced that user portals are usually tightly coupled API. We proposed a generic user portal that makes invocations to a generic API decoupling the portal from the specific process with the native process engine API. The independence between engine it invokes, which can be exchanged through the generic the front-end and the process engine provides means to migrate API invocation to different process engines. In this paper we from one process engine to another without affecting the user present an extension of this work by adding concepts to the experience, as well as offers a unified interaction layer for generic API and data model, a comparative analysis between external applications, similarly to the way applications already BPMS, as well as the implementation of adapters for three different engines to show its capabilities.
    [Show full text]