- Al crear un PmTable con un nombre extenso y guardar el mismo, despliega un mensaje de error, de nombre de tabla incorrecto.
- Validate table name of the new PM Tables
- not taken into account the types of mask and separators in fields currency and percentage
- was add validation.
- In fields currency and percentage was changed FLOAT -> DOUBLE.
When adding a field, the 'Field Name' must be an string without spaces in the middle, because this makes the name of some funtions were generated wrong, like getColosa Email() when it must be like getColosaEmail() or getColosa_Email(). So, this field in the creating PM Table form, was validated to transform any string into a string without spaces.
When adding a field, the 'Field Name' must be an string without spaces in the middle, because this makes the name of some funtions were generated wrong, like getColosa Email() when it must be like getColosaEmail() or getColosa_Email(). So, this field in the creating PM Table form, was validated to transform any string into a string without spaces.
- Problem in IE8 with "Compatibility mode" (bug 10199)
- Problem in "Report Tables" to select checkbox in the list
- Solved problem "Compatibility mode" (bug 10199)
- Solved problem to select checkbox
- The QA team should test with:
* Browsers IE7, IE8, IE9, Firefox and Chrome
* Skins uxmodern and classic
* Available from version ProcessMaker-2.0.46
- When importing a ReportTable in a process, not shown in the list of
ReportTables
- Problem solved, the PRO_UID variable is created with the UID of the
process, when the user is in the ProcessMap
* Available from version 2.0.44
- Report Tables in IE does not display correctly, transparent boxes appear
- Problem solved, now display reportTables in popup window when the browser is IE
- Se identificaron todas las etiquetas que se deberian modificar dependiendo si esta en PM TAbles o Report Tables.
- Se procedio al cambio de etiquetas para evitar la confusion de los casos de PM Tables y Report Tables.
- El bug se corrigio en el core no en el plugin, las etiquetas q se muestran en
el menu contextual estan embedded en el codigo del core y simplemente se usan
cuando el plugin esta activo, no mostraba la etiqueta correcta porque el ID del label
no estaba correcto
- Se cambiaron los ID erroneos:
ID_CONVERT_TO NATIVE_REPORT_TABLE -> ID_CONVERT_NATIVE_REP_TABLE
ID_CONVERT_TO_SIMPLE_REPORT -> ID_CONVERT_SIMPLE_REPORT
- there was no validations for native & custom date files while data preview for report tables
- validations added and posibles empty strings now are mapped to NULL on db.
- the reporter is right, DATETIME field type is missing
- DATETIME field type was added, it is not a directly supported type by our ORM (propel), but we're handling that with its equivalent TIMESTAMP, but don't worry it is transparent by final users.
(Fixes for import feature)
According the solution raised on the meeting
- the default selection for db connetions is workflow instead REPORT
- the prefix PMT for all pmtables was added
- fix a sintax error
(Fixes for import feature)
According the solution raised on the meeting
- the default selection for db connetions is workflow instead REPORT
- the prefix PMT for all pmtables was added
According the solution raised on the meeting
- the default selection for db connetions is workflow instead REPORT
- the prefix PMT for all pmtables was added
