anchor.diff:  
   You can also open the Data I/O Editor to edit the Data Inputs and/or Outputs by editing the appropriate property for the activity: [parameter]``Assignments``, [parameter]``DataOutputAssociations``, or [parameter]``DataInputAssociations``.
   
  -[NOTE]
  -====
  -The Data I/O Editor tool is available in Red Hat JBoss BPM Suite 6.2 or better.
  -====
   
   === Data I/O Editor Example
  -
   
   In the following example, the Data I/O Editor has been used to create some Data Inputs and Data Outputs for the user activity ``Check Invoice``.
   The example makes use of two process variables that have been defined in the process:
  
positive.code: === Recording local history
  
  
  Local history keeps track of any changes, you apply to your process model so as to allow you to restore any previous status of the process model.
  By default, this feature is turned off.
  
  To turn on local history recording, click the *Local History* image:5225.png[] button and select *Enable Local History* entry.
  From this menu, you can also display the local history records and apply the respective status to the process as well as disable the feature or clear the current local history log.
  
negative.code: 
  Action scripts are pieces of code that define the [property]``Script`` property of a Script Task or an Element's interceptor action.
  They have access to globals, the process variables, and the predefined variable [var]``kcontext``.
  Accordingly, [var]``kcontext`` is an instance of `ProcessContext` class and the interface content can be found at the following location: http://docs.jboss.org/jbpm/v7.0/javadocs/org/kie/api/runtime/process/ProcessContext.html[Interface ProcessContext].
  
  Currently, dialects Java and MVEL are supported for action script definitions.
  Note that MVEL accepts any valid Java code and additionally provides support for nested access of parameters, for example, the MVEL equivalent of Java call `person.getName()` is ``person.name``.
  