- User appear more than once in the Process Supervisor window
- Problema resuelto, cuando se elimina a un usuario por ADMIN>USERS>Users, este usuario puede se eliminado sin restricciones
aunque el usuario este asignado como supervisor de un proceso lo cual no es correcto.
Se hace una validacion que verifica si el usuario esta asignado como supervisor le saldra un mensaje de confirmacion
que indica si deseea eliminar el usuario de todas maneras. Si la respuesta es Si, se eliminara de la lista de usuarios
y de la lista de usuarios asignados como supervisores.
- User appear more than once in the Process Supervisor window
- Problema resuelto, cuando se elimina a un usuario por ADMIN>USERS>Users, este usuario puede se eliminado sin restricciones
aunque el usuario este asignado como supervisor de un proceso lo cual no es correcto.
Se hace una validacion que verifica si el usuario esta asignado como supervisor le saldra un mensaje de confirmacion
que indica si deseea eliminar el usuario de todas maneras. Si la respuesta es Si, se eliminara de la lista de usuarios
y de la lista de usuarios asignados como supervisores.
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.
- Even if a user has an INACTIVE status, using the PMFCreateUser function, he/she is able to login to ProcessMaker.
- Problema resuelto, al crear un usuario con la funcion PMFCreateUser con tipo de estado "INACTIVE", el usuario se creara
como inactivo y se registrara en las bases de datos correspondientes y no podrácceder a ProccessMaker.
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.
- 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.
