WaveMaker 3.2 has is now available for download.

http://wavemaker.com/downloads/

This is mostly a bug fix release. The Fixed Bug List is attached.

If you are currently working on WaveMaker Studio version 3.1.1 or earlier, please read the following "top 4" migration notes BEFORE installing 3.2. In particular, installing 3.2 will overwrite any custom widgets you have created. The first note below has instructions for migrating your custom widgets.

 
1. Custom Widgets Changes
Custom widgets have been moved into your project directory.  If you have existing custom widgets, follow these instructions BEFORE uninstalling 3.1.1 Failure to do so will cause removal of your custom widgets.

Before uninstalling the old version of WaveMaker, copy wm/custom to a temporary location.  After upgrading, and running the studio for the first time, a new common directory will be in your WaveMaker directory.  Copy your widget files to the common/packages/example directory. Edit the module names (to reflect the new path) in your widget files, the common/packages/lib.js, and common/pacakges/packages.js. What was previously "wm.custom.widget" has become "wm.packages.example." Please use the included example widget as a guide.

2. Default Projects Directory Changed on Linux (and Mac) The default projects directory on Linux and Mac has changed to match the default set by the Windows installer (WaveMaker/projects):
 
Linux: On Linux, if you haven't set your agHome in studio-config.xml, you'll have to move your projects (and studio.properties) from ~/WaveMaker to ~/WaveMaker/projects.  
Mac: On MacOS X, your projects should be in ~/Documents/WaveMaker/projects.

If you're running from a WAR, or  you've otherwise changed the path in studio-config.xml, point the "activeGridHome" variable at your projects directory (now, ~/WaveMaker/projects or ~/My Documents/WaveMaker/projects).  

3. Services Returning Strings
Services returning strings will now return string objects. This will cause errors when string returns are used directly.
Where you need a simple string, use the 'stringValue' of the returned object. For example:
 this.editor1.setDataValue(inResult.stringValue);
 this.getUserByName.components.input.setValue("name", inResult.stringValue);
 
4. WaveMaker can't see private classes.

If you have a java service file:

public class A{}
class B{}

B will be private, and the JSON layer will not be able to see it.
Either make B a public static inner class:

public class A{
    public static class B{}
}

Or define it in its own file.