anchor.diff:  
   During the server boot up, you'll notice some Flowable logging messages passing by. At the end, a message like '_INFO [main] org.apache.catalina.startup.Catalina.start Server startup in xyz ms_' indicates that the server is ready to receive requests. Note that by default an in-memory H2 database instance is used, which means that data won't survive a server restart.
   
  -In the following sections, we'll use cURL to demonstrate the various REST calls. All REST calls are by default protected with _basic authentication_. The user 'kermit' with password 'kermit' is used in all calls.
  +In the following sections, we'll use cURL to demonstrate the various REST calls. All REST calls are by default protected with _basic authentication_. The user 'rest-admin' with password 'test' is used in all calls.
   
   After bootup, verify the application is running correctly by executing
   
   ----
  -curl --user kermit:kermit http://localhost:8080/flowable-rest/service/management/engine
  +curl --user rest-admin:test http://localhost:8080/flowable-rest/service/management/engine
   ----
   
   If you get back a proper json response, the REST API is up and running.
  
positive.code: Such a task can now be completed using:
  
  ----
  curl --user kermit:kermit -H "Content-Type: application/json" -X POST -d '{ "action" : "complete", "variables" : [ { "name" : "approved", "value" : true} ]  }' http://localhost:8080/flowable-rest/service/runtime/tasks/25
  ----
  
  However, you most likely will get an error like:
  
negative.code: When the process instance is started, the first task is assigned to the 'managers' group. To get all tasks for this group, a task query can be done through the REST API:
  
  ----
  curl --user rest-admin:test -H "Content-Type: application/json" -X POST -d '{ "candidateGroup" : "managers" }' http://localhost:8080/flowable-rest/service/query/tasks
  ----
  
  which returns a list of all tasks for the 'managers' group
  