- 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.
In javascript section of main file that load Designer UI
for 'var credentials' now we're sending the access token and refresh token, instead access code, and client credentials.
This is just because currently a lot of access tokens were being created for each process design is open, and while it is being open is sending two request, the first one to exchange an access code by an access token,..
Now, whith this change, while a process design is open we will made just one request to some resource with access token in the header,.. exchange access code by an access token is not needed any more.
NOTE.- the access token passed to the front-end can be expired at first time,.. so we need that the exchange an access token by a refresh token handling is working well.
- 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.
- Al editar el nombre de un proceso este permite ingresar el
nombre de uno ya existente
- El problema no esta al editar el proceso (esto cuando se ingresa
a "Edit process"), sino cuando el ProcessMap hace el "auto-save",
ahi si guarda el titulo del proceso
- Se ha agregado validacion cuando se actualizen los datos mediante
el "auto-save" (esto se aplica solo para los datos del proceso)
- En el lado Frontend se esta enviando los datos del proceso
(title, description) de manera continua con el "auto-save"
para su actualizacion, pero como ya existe la validacion, ahora
sale un ERROR. Esto debera ser revisado en el lado Frontend
- 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.
