ProcessMaker 2.0.30 Release: Report Tables Replaced With PM Tables

By jamie | July 5, 2011 | Uncategorized

ProcessMaker release 2.0.30 includes several bug fixes, and a major change: Report Tables have been completely replaced with PM Tables. This means that Report Tables are being marked as deprecated, but still usable for backward compatibility. Starting with this version, when defining a new Report Table, you can decide which DB Connection will be used to create this table, and define a field type to map for each variable.

Below is a summary of bug fixes, improvements, new features, and known issues.

Fixed bugs

For this release, nearly 80 bugs have been fixed and tested by our QA team in 10 cycles. The most important are (to see the detail of this please refer to the Change Log):

1. Issues with date fields were fixed.
2. Microsoft Internet Explorer issues with grid calculations were solved.
3. Functions such as onAddRow and onDeleteRow were fixed.
4. Layout issues with double scrollbars were addressed.
5. Javascript issues involving special characters were corrected.
6. When exporting and importing process definitions, the subject of custom notifications is now included.
7. Dynaform issues involving Suggest Field were fixed.

Improvements

1. Credentials from Database Connections are now stored as encrypted strings.
2. DBArray improvements: labels from fields using DBArray as connection are now properly stored.

New Features

1. Report Tables changed its engine to PM Tables inheriting the main features. Upon creating PM Tables, the corresponding DB layer classes and all required triggers to fill this table are being created.
2. SharePoint Triggers: this release includes 12 triggers for SharePoint documents area, thus allowing users to create Sites and Folders, as well as upload and download documents (and versions).

Known Issues

1. Language files other from English and Spanish should be updated.
2. Chrome, Firefox 4 and MSIE 9 may exhibit some unexpected issues. We are in the process of testing these versions.
3. Due date calculation is failing in some cases, specially in Windows environments.
4. Processes created in languages other than English can’t start a case. There is a workaround, though: just open the process definition in English once.
5. An asynchronous subprocess may create two cases instead of one under some circumstances.