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.
- For the task completed the index and task_uid was wrong.
- A validation was added looking those id's, in file cases_Open.php.
- A validation was added for case paused.
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.
- Problemas con los Servicios Web WSDL de PM.
- Se agrega el parametro "$params->taskId" en el archivo mencionado en el presente bug, en el metodo "NewCaseImpersonate",
que contiene la siguiente linea de codigo:
$res = $ws->newCaseImpersonate($params->processId, $params->userId, $params->variables, $params->taskId);
Disponible para la version 2.5.3 de ProcessMaker.
When an already created process is imported with the 'Create a completely new process..' option, the inputs asociated in the dynaforms are not the input created for this new process, this new (copy) process still has associated the input of the original process (same UID), this because the uid of the new input is never replaced in the new process's dynaform xml file.
So it was created a new field in the data object (the data that has all the information about the new process) where is all the old inputs uid and the new ones. Then using this object this old uids are replaced with the new inputs uids.
When an already created process is imported with the 'Create a completely new process..' option, the inputs asociated in the dynaforms are not the input created for this new process, this new (copy) process still has associated the input of the original process (same UID), this because the uid of the new input is never replaced in the new process's dynaform xml file.
So it was created a new field in the data object (the data that has all the information about the new process) where is all the old inputs uid and the new ones. Then using this object this old uids are replaced with the new inputs uids.
- single click.
- The click event was changed to a double click event in order to display the directory content, moreover, the "expander" was removed beacuse it is already in the
the tree on the left side.
When a dynaform has some fields with validations, when typing some data was duplicated.
I added a validation to detect IE version, if this is 11 a meta tag is added in the HTML (<meta http-equiv="X-UA-Compatible" content="IE=8"/>). This tag let the browser use the IE8 compatibility and prevent the duplicated characters issue.
The validation for IE 11 is a preg_match php function searching a 'Trident/' string. This is diferent in IE10, where the User-agent has MSIE on it. On IE 11 MSIE was deleted and the only way to detect that the browser is IE11 is searching 'Trident/'.
- 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.
- When creating a dynaform with the character "&", the field handlers not working.
- Problema resuelto, el problema que se teníera lo siguiente cuando se utiliza el "&" en el tílo de un dynaform,
cuando se enviaba los datos via GET, el "&" lo interpretaba como un separador de variables y esto ocasionaba la
division de los datos que se enviaba. Se valida los datos enviados via GET codificáolos y al recibir estos datos
se los decodifica.
- 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.
Problem:
Case 1: The same user 'A', creates and imports the process, using the option: "Update the current process...".
Result: The user that created the process, user A in the example, is allways the User Owner of the process.
Case 2: User 'A' creates the process, and user 'B' imports the process, using the option: "Update the current process...".
Result: The user that created the process, user A in the example, is allways the User Owner of the process.
Case 3: User 'A' creates the process, then this user 'A' is deleted, and user 'B' imports the process, using the option: "Update the current process...".
Result: The User Owner is showed empty.
Razon: When the user 'A' (the one that created the process) is deleted, the delete is only logical not physical in the db, and it is updated with the Status 'CLOSED' and the username of this user is changed to an empty string " ". So, when the process is updated the username is copy like it is in the db, and copy into the User Owner field, showing the empty string " ".
Solution:
A validation was added asking if the user exist, if this dosen't the User Owner is changed to the current user logged, and the same if the user exist but his status is CLOSED.
- When creating a dynaform with the character "&", the field handlers not working.
- Problema resuelto, el problema que se teníera lo siguiente cuando se utiliza el "&" en el tílo de un dynaform,
cuando se enviaba los datos via GET, el "&" lo interpretaba como un separador de variables y esto ocasionaba la
division de los datos que se enviaba. Se valida los datos enviados via GET codificáolos y al recibir estos datos
se los decodifica
The validation for the not required parameter "unpauseDate" was wrong. When this parameter was empty the validation was taking this like this has a date, so it was trying to check the date format, and this was giving an error.
The validation was changed to only let strings of 10 or more characters go into the next validation where the format of the date is checked.
