anchor.diff:  The deployment and definition services prepare process data in the {PROCESS_ENGINE}. To execute processes based on this data, use the process service. The process service supports interaction with the {PROCESS_ENGINE} execution environment, including the following actions:
   
   * Starting a new process instance
  +* Running a process as a single transaction
   * Working with an existing process instance, for example, signalling events, getting information details, and setting values of variables
   * Working with work items
   
  
positive.code: 
  [IMPORTANT]
  ====
  The process service is optimized for runtime operations. Use it when you need to alter the process instance, for example, signal events or change variables. For read operations, for example, showing available process instances, use the runtime data service.
  ====
  
  The following code sample shows deploying and running a process:
  
negative.code: ProcessInstance pi = processService.getProcessInstance(processInstanceId);
  ----
  
  The `startProcess` method expects `deploymentId` as the first argument. Using this argument, you can start processes in a certain deployment when your application might have multiple deployments.
  
  For example, you might deploy different versions of the same process from different KJAR files. You can then start the required version using the correct `deploymentId`.
  
  The following definition shows the complete `ProcessService` interface:
  
  