Code Issue:
La descripcióe pmtables en Audit Log es muy generica.
Solution:
Se coloca el caracter de separacion "," para comprender mejor los mensajes.
- It don't have the functionality.
- A functionality was added in pmtables and reportTables index.
- A field was added in table fields FLD_TABLE_INDEX.
The search option in PMTables has a validation where the APP_UID field is ignored in the search because this was causing some search troubles when you wanna search a number that was include into the APP_UID (eg. 'APP_UID':405044408538cb9472ade260172, 'text to search':4408 )
Now, we add a checkbox field near the search text field to customize this behavior. With this checkbox 'Search also in the APP_UID field' you can decide if the search will include or not the APP_UID field.
The search option in PMTables has a validation where the APP_UID field is ignored in the search because this was causing some search troubles when you wanna search a number that was include into the APP_UID (eg. 'APP_UID':405044408538cb9472ade260172, 'text to search':4408 )
Now, we add a checkbox field near the search text field to customize this behavior. With this checkbox 'Search also in the APP_UID field' you can decide if the search will include or not the APP_UID field.
Cuando se crea un nuevo campo en una pmtable del tipo DATETIME, a la hora de editar la misma PMtable Este campo se muestra como TIMESTAMP. Esto ocurre por que la version de propel que usa PM, no genera clases con el campo DATETIME, esto al crear la PMTable, sino en cambio utiliza el tipo de dato TIMESTAMP.
Por lo tanto se agrego una validacion para que a la hora de recuperar los campos a editarse, se muestre el valor correcto, en este caso DATETIME.
Cuando se crea un nuevo campo en una pmtable del tipo DATETIME, a la hora de editar la misma PMtable Este campo se muestra como TIMESTAMP. Esto ocurre por que la version de propel que usa PM, no genera clases con el campo DATETIME, esto al crear la PMTable, sino en cambio utiliza el tipo de dato TIMESTAMP.
Por lo tanto se agrego una validacion para que a la hora de recuperar los campos a editarse, se muestre el valor correcto, en este caso DATETIME.
Se aniadio la nueva funcionalidad de busqueda en el display de los datos de los PMTables y Report Tables, en ADMIN > Settings > PM Tables > Data, el cual realiza las busquedas por todas las columnas del PM Table o Report Table.
Se corrigio el ordenamiento ASC y DESC.
Se aniadio la nueva funcionalidad de busqueda en el display de los datos de los PMTables y Report Tables, en ADMIN > Settings > PM Tables > Data, el cual realiza las busquedas por todas las columnas del PM Table o Report Table.
Se corrigio el ordenamiento ASC y DESC.
Se aniadio la nueva funcionalidad de busqueda en el display de los datos de los PMTables y Report Tables, en ADMIN > Settings > PM Tables > Data, el cual realiza las busquedas por todas las columnas del PM Table o Report Table.
Se corrigio el ordenamiento ASC y DESC.
- Al repoblar la tabla no se estaba considerando la validacion agregada cuando se actualiza el registro
- Se agrego la validacion faltante al momento de popular toda la tabla
- 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.
- 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.
- 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).
- 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.
>>>Probably because ProcessMaker is trying to add a record to the RP Table with an empty date field set to "" instead of NULL.
- that was exactly the problem, but it is fixed now
(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
