The Json has some quotes that was causing troubles, because the stripslashes() function was been applicated before json_decode, so it was been applied twice.
Removing stripslashes() function, this is already added in json_decode().
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.
- Pmtables: Problema al importar la data de tipo Autoincrementable
- Problema resuelto, el problema que se tenia era por los archivos que crea propel especificamente los archivos Peer,
al momento de hacer la insercióe los campos se eliminaba la columna donde se tenia los Primary Key ocasionando que
se cree nuevamente. Se valida la importacion de los pmTables cuando son de tipo Autoincrementable logrando a que
cuando se importe un pmTable mantenga los íices que se tenia al momento de exportarlos.
- Pmtables: Problema al importar la data de tipo Autoincrementable
- Problema resuelto, el problema que se tenia era por los archivos que crea propel especificamente los archivos Peer,
al momento de hacer la insercióe los campos se eliminaba la columna donde se tenia los Primary Key ocasionando que
se cree nuevamente. Se valida la importacion de los pmTables cuando son de tipo Autoincrementable logrando a que
cuando se importe un pmTable mantenga los íices que se tenia al momento de exportarlos.
- No se puede realizar la import, export, delete, data, edit de un Report Table.
- Problema Resuelto, el problema que se tenia era por la version de php que era php 5.4. Esta version de php
exige mejor control cuando se utiliza los metodos de una clase, no se puede utilizar los metodos directamente sin antes
de ser creados.
Se puede realizar las acciones de: edit, delete, data, import y export en un Report Table. y NO muestra error.
Disponible para la versió.5.3 de ProcessMaker.
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.
Descripcion: Creamos una tabla parametrica para que de acuerdo al orden que tiene la misma poder mostrar informacion dentro de un formulario, procedimos a importar el PM table al servidor de cliente y verificamos que al importar la Data del PM table no se respeta el orden ni el valor de la columna PAR_ID (es la llave primaria/automatico)
Solucion: En la importacion de un PMTable, se obtiene la llave primaria de dicha tabla para que posteriormente se ordene en base a esa columna y se almacene en base de datos como una tabla ordenada. Resuelto para la version 2.5.1-testing.1-402-gbcc9bdb
When having a process with some currency field (Real Number), and running a case before creating the RT, when you create the RT and saw the data inside it shows the number as integer. But when you run a case after creating the RT it shows the currency in good way (Real number).
It was fixed.
- 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.
- 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
