ProcessMaker 2.0.30 was just released last evening. It includes several bug fixes and a very important structural change that has to do with Report Tables.
Report Tables as we know has completed its life cycle and now it got changed to PM Tables. This means that what we know as Report Tables is being marked as deprecated and is usable only for backward compatibility (you can’t create new ones but still work with existing ones) and the new implementation has been merged with PM Tables.
Why? Well this is a natural evolution of our original Report Tables to a better, flexible and powerful way to administrate Tables inside ProcessMaker.
Now when you define a Report Table, you can choose where that table will be created (which DB Connection) and the field type for each variable to be used. In the background since PM Tables is in control, the correspondent classes for the DB layer are being created and all the triggers to fill that table are defined.
This time the list of bugs fixed is close to 80 and all of them have been tested by our QA team in 10 cycles. The most important are (to see the detail of this please refer to changelog.txt):
[*] Issues with Date Fields.
[*] Internet Explorer issues in Grid calculations.
[*] Functions such as onaddrow() and ondeleterow() fixed.
[*] Layout issues with double scroll bars.
[*] Export processes with email notification subject.
[*] Issues with Suggest Field.
[*] Database credentials are saved in a secure way in DB (encrypted).
[*] DBArray improvements: Fields that use DBArray as connection now can save the labels correctly based on the SQL and table.
[*] Report Tables changed its engine to PM Tables inheriting all its main features.
[*] SharePoint Triggers: Included 12 triggers for SharePoint documents area that allow users to work, create sites, create folders, upload and download documents (and versioning).
[*] Language files different from English and Spanish should be updated.
[*] Chrome, Firefox 4/5 and IE9 present some issues, not tested yet.
[*] Due date calculation is failing in some cases. Mainly in Windows environments.
[*] Processes that started from scratch in a language other than English, can't start a case. Workaround: open the process for editing in English once.
[*] Asynchronous subprocess creates two cases instead of just one in some cases.