I found this documentation for new drag and drop functionality explained in the "HowTo.PDF":
Aware IM supports drag and drop functionality between grids (standard query results), custom query views (custom query results) and trees. In addition drag and drop is supported within the calendar and scheduler. You do not have to configure anything for calendar and scheduler as drag and drop within these components is provided by default.
If you want to drag data between query grids, custom views or trees you need to define processes that would handle the “drop” action. When the user performs a “drop” she always does it on some node in the grid, custom view or tree. This node always represents some instance of a business object. We will call it the “drop instance”. The node being dragged also represents some instance of a business object (it can be the same business object as the “drop” object or it can be a different one). We will call this instance the “drag instance”
The process implementing the drop must have the object(s) representing drag and drop instances as its input. Both drag and drop instances will be in the Context of the process. If the user drags records within the same grid (or custom view) drag and drop instances will be represented by the same object. The “drop” instance will always be the first in the Context and can be referred to with the “This” prefix. The drag instance will be the second in the Context and can be referred to with the “That” prefix. The rest is up to the process – it can do whatever it wants with the drag and drop instances. For example, if a Task is dragged from a grid of active tasks to the grid of completed tasks, the process could change the status of the dropped task to COMPLETED:
ThisTask.Status = ‘COMPLETED’
Note that if the user holds down the CTRL button when performing drag and drop it can be interpreted as the “copy” operation – the dragged instance can be copied rather than moved. In this case you can define a separate process that would perform a copy. If you do not define such a process, move and copy operations will work in the same way.
Once you have defined processes to handle drag and drop you can start configuring drag and drop for those components that need to support it. The Drag and Drop options are available for Trees (reference attributes represented as Trees) and queries represented as a standard or custom form (the latter is supported only for custom templates, not for custom presentations).
The Drag and Drop options allow you to specify whether the user is allowed to drag records of the grid (custom view or tree) and whether they are allowed to drop records dragged from other (or the same component). In the latter case you need to define object types allowed to be dropped on the grid (custom view or tree) and the processes that would handle the drop of these object types.
