- You are able to select various user re re-assign task
- Problema resuelto, cuando se aplica "Reassign" de una tarea, de la lista que aparece para reasignar la tarea se podra
seleccionar solo a un usuario de la lista.
- 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.
- En el listado de trigger wizards no estaba ordenado, ahora se despliega ordenadamente
- Se corrigio el .feature correspondiente para que aplique el cambio
- Otros fixes tambien se realizaron
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.
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.
