New Features in Version 3.2

   1. On the Role Diagram, the objects are connected by lines instead of arrows. 
   The help tip is updated as well.
   
   2. On System/Agent/Capability overview diagram, Data is able to connect the messages 
   which are posted when some particular operations are performed on the data. Double 
   click the data graph cell on these diagrams, a dialog pops up where users can edit/remove 
   the posted messages of the selected data. When generating code, the posted messages and 
   related methods are appended in the skeleton code of this data object.
   
   3. Add attributes for records stored in Data objects. Double click the data graph cell 
   on Agent/Capability/System overview diagram, a dialog will pop up (the same one as above) 
   where user can edit/remove/add fields for this particular data object.
   
   4. User can mark a Percept object as 'external' by editing information on its descriptor panel. 
   When generating code, PDT does not generate the skeleton code for the external Percept.
   
   5. Add an 'External path' field for Capability/Message/Percept/Data objects on their descriptor panel. 
   The user defined string in this field will be added as imported directory into the skeleton code.
   
   6. If a Message and a Plan are connected on the current diagram, their connection is shown up 
   on other design views as well where both of them appear.
   
   7. If a protocol involves only one agent, for example an actor passes percept to an agent 
   through it, the protocol connects that agent with a line.
   
   8. On Protocol Editing Dialog, when checking AUML text, if the text is correct, PDT gives back 
   a confirm response.
   
   9. Resize the Protocol editing dialogs and Main frame to be adapted for the user screen size.
   
=====================================================================================================
Fixed Bugs in Version 3.1a

   1. Can not remove the role graph cell from analysis overview diagram by clicking the delete button 
   on the descriptor panel of role object.
   
   2. Can not remove the percept graph cell from system roles diagram by clicking the delete button 
   on the descriptor panel of percept object.
   
   3. Can not add step of 'other' type into scenario.
   
   4. In the generated code, if a data object is defined as "Books DB_dat" in the agent, at the 
   capability level it is defined without "_dat" appended. Now all of them have the "_dat" tail.
   
   5. When generating code, if there are spaces in the data name, it is remained in the skeleton code 
   which is against JAVA syntax.
   
   6. If user creates a Note object and inputs text, some long words will be broken up into different lines.
   
   7. Can not generate the customized html report properly.
   
   8. When an internal DB is read or written by a plan, it is not shown up on the plan descriptor panel.
   
  9. If there is more than one capability in an agent and the user creates a Note object on one of 
  the capability diagrams, this Note object will appear on all of the other capability diagrams.
  
  10. If more than one Agent has a common capability, the name of this capability will be changed 
  in the different agent diagrams. Now all of these Agents will have the same capability instance.
  
  11. 'Internal drawing error' warning is shown on the Protocol Editing Dialog when checking the AUML 
  text, even if the AUML text is fine.
  
  12. When Removing the note object from Analysis Overview by clicking the X button on the tool bar, 
  even if user click 'No' button in the pop-up dialog, the note is deleted. And the information on the 
  pop-up dialog is incorrect.
  
  13. On Agent Overview Diagram, if two-way connections present between a plan and a data (which means 
  this plan reads the data and writes to it as well), even if barely one of the connections is deleted, 
  on the plan descriptor panel both 'Used Data' field and 'Produced Data' field are influenced. The same 
  problem occurs on Capability Overview Diagram.
  
  14. On System Overview Diagram, if a Message comes into an Agent, when deleting the connection between 
  them, the Message remains in the Agent Overview and the internal objects of the Agent will keep the 
  Message in their property list if connected with that Message. The same problem occurs for outgoing message.
  For now, after the connection is deleted, the message is removed from the Agent level.