anchor.diff:  
   Flowable provides several web applications to demonstrate and leverage the functionality provided by the Flowable project:
   
  -* Flowable IDM: the identity management application that provides single-sign-on authentication functionality for all the Flowable UI applicatons and for users with the idm admin privilege it also provides functionality to manage users, groups and privileges.
  -* Flowable Modeler: the modeler application that allows for modeling processes, forms, decision tables and application definitions.
  -* Flowable Task: the runtime task application that provides functionality to start process instances, edit task forms, complete tasks and query on tasks and process instances.
  -* Flowable Admin: an admin application that allows for querying the BPMN, DMN, form and content engines and provides several options to change process instances, tasks and jobs etc. The admin application connects to the engines through the REST API that is deployed together with the Flowable Task app and the Flowable REST app.
  -
  -The Flowable IDM is required to be present for all other apps to be able to authenticate. The WAR files for each app can be deployed to the same servlet container (like Apache Tomcat), but can also be deployed on different servlet containers. Because the same cookie is used for authentication for each app, the apps need to run on the same domain.
  +* Flowable IDM: an IDentity Management application that provides single sign-on authentication functionality for all the Flowable UI applicatons, and, for users with the IDM administrative privilege, it also provides functionality to manage users, groups and privileges.
  +* Flowable Modeler: an application that allows users with modeler privileges to model processes, forms, decision tables and application definitions.
  +* Flowable Task: a runtime task application that provides functionality to start process instances, edit task forms, complete tasks and query on tasks and process instances.
  +* Flowable Admin: an administrative application that allows users with admin privilege to query the BPMN, DMN, form and content engines and provides several options to change process instances, tasks, jobs and so on. The admin application connects to the engines through the REST API that is deployed together with the Flowable Task app and the Flowable REST app.
  +
  +The Flowable IDM is required for all other apps to enable authenticatation. The WAR files for each app can be deployed to the same servlet container (such as Apache Tomcat), but can also be deployed on different servlet containers. Because the same cookie is used for authentication with each app, the apps need to run on the same domain.
   
   
   [[uiAppInstallation]]
   
   === Installation
   
  -Like mentioned before, all four UI apps can be deployed together on the same Tomcat server and to get started this is probably the easiest approach. You can also choose to only install the Modeler app for example, but make sure the Flowable IDM app is always running/deployed as well. For this installation guide we'll describe the installation of all four apps to a Tomcat server.
  +As mentioned before, all four UI apps can be deployed together on the same Tomcat server, and to get started this is probably the easiest approach. You can choose to only install the Modeler app, for example, but make sure the Flowable IDM app is always running/deployed as well. For this installation guide we'll describe the installation of all four apps to a Tomcat server.
   
   1. Download a recent stable version of link:$$http://tomcat.apache.org$$[Apache Tomcat].
   2. Download the latest stable link:$$http://www.flowable.org/downloads.html$$[Flowable 6 version].
  
positive.code: 
  image::images/flowable_admin_processdefinitiondetails_screen.png[align="center"]
  
  In the process definition details view, the first page of process instances is shown, together with optional decision table definitions and form definitions that are used in the process definition. For the vacation request process definition, there's one connected decision table and one connected form definition. Clicking on the decision table table definition navigates the Flowable Admin application to the DMN Engine. You can always navigate back to the Process Engine by clicking on the _Parent Deployment ID_ link.
  
  In addition to the deployments and definitions, you can also query on process instances, tasks, jobs and event subscriptions in the Process Engine. The views all work in a similar way to what's already described.
  
negative.code: rest.process.app.password=test
  ----
  
  These values can be used when the Flowable Task app (with all the Flowable engines included) is managed by the Flowable Admin application.
  
  [[flowableIDMApp]]
  
  === Flowable IDM application
  
  The Flowable IDM application is used by all other three Flowable web applications for authentication and authorization and is therefore required to be available when you want to run the Modeler, Task or Admin application. The Flowable IDM application is a simple identity management application and is targeted at providing single sign-on capabilities to the Flowable web applications, including providing a central place to define users, groups and privileges.
  
  The IDM application boots the IDM engine at startup and will create the identity tables as defined in the IDM engine in the datasource defined in the properties configuration.
  
  