- 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.
- Se agrego la nueva columna solicitada APP_STATUS, para report tables ya creados no se mostraráes necesario crearlos de nuevo para que aparezcan
- Sobre el bug de las filas vacias, es el mismo problema que para el bug 10230, la BD del cliente tiene un problema de integridad, cuando uno borra el caso usando el Sistema (listado de casos en draft) borra todos los registros relacionados en todas las tablas asociadas, pero al hacer un borrado manual se olvidaron de elimar los datos de alguna de las tablas (posiblemente APP_CACHE_VIEW), por favor soliciten la BD del cliente y revisen la integridad de los datos.
- In the creation/editing of PMTables/ReportTables, not validated the
use of reserved words
- It has validated the use of keywords in the creation/editing of
PMTables/ReportTables
- It has been validated using reserved words to importing a process with
ReportTables (old version)
* Available from version 2.0.44
- 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
- The primary key joined with "-".
- We have the following recommendations:
- The primary key must be in separate columns.
- Now you can use "-" within the primary key, but does not support the use of ",".
- When importing the CSV header must be deleted.
- Could not create report tables with fields that have reserve words.
- Validation reserved words in the fields definitión in the report tables creation.
- There is a major problem when using the new editor for PM Tables with Database Connections, if you choose a database connection (anything you have created as a Database Connection in process designer).
- Fix-bug and Addition of session variable in the different connections PMTables(Victor).
- 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
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
- verification & validation for column name defined twice or more added
- fixed IE compaitbility for variable named length (use it cause problems in IE)
- fixed slashed added on json value posted on a ajax request, soldev adding stripslashed on server side
