anchor.diff:  
   === Performing an action ===
   
  -To implement the necessary actions to execute the developer has just to override the doItImpl method.
  +To implement the necessary actions to execute you just have to override the doItImpl method.
   
   [source]
   @Override
  
positive.code: 
  === Configuration of PmCommandCfg annotation ===
  
  With the PmCommandCfg you have the possibility to change the default behaviour of the PmCommand object. This means that you can configure the behaviour before or after executing the command as well as ...
  
  ==== BeforeDo ====
  
  
negative.code:     }
  }
  
  === Success message ===
  
  After executing your action, it is possible to present the user a success message. This could happen via two different ways:
  
  * By implementing a success message via PmMessageApi in the doItImpl method of your PmCmmand object.
  
  [source]
  ------------------------------------------------------------------------
  @Override
  protected void doItImpl() throws Exception {
      ...
      PmMessageApi.addMessage(this, Severity.INFO, "message.key", value1, value2);
  }
  ------------------------------------------------------------------------
  
  Then you also have to add a message for your message key into the related resource file.
  [source]
  message.key={0} successfully done in {1}.
  
  * By defining a string resource having the postfix _successInfo.
  [source]
  cmdDoSomething=Do Something
  cmdDoSomething_successInfo=Something was successfully done.
  
  Example:
    cmdDoSomething=Do Something
    cmdDoSomething_successInfo=Something was successfully done.
  
  
  === Testing commands ===
  
  It quite easy to test the implemented functionality of a PmCommand object. To do so you have to create a test conversation for the view that contains your command, first (1).
  Then you can test the implementation of the PMCommand by calling the doIt method (2). To check, if the execution of doIt was successful or not you can validate the CommandState 
  of the PmCommand cmd, now. In our first test the execution should be successful, so the CommandState should be EXECUTED (3).
  
  When calling the doIt method, it first validates the command like it is descriped in "Validation of a PM area" [HIER LINK SETZEN!]. So it is sometimes required to initialize all 
  the attributes of the parent of your command to prevent a validation error, first (4). But if you want to check that the validation also works fine, you only have to call the doIt method 
  