- Cuando se borra un caso por PM, este caso no se borra en los PM Reportes.
- Problema resuelto, cuando se ejecuta un proceso que tenga Report Tables, al borrar el caso tambien se eliminara los
registros de los Report Tables.
* Available from version ProcessMaker-2.5.2-testing.1
- Cuando se borra un caso por PM, este caso no se borra en los PM Reportes.
- Problema resuelto, cuando se ejecuta un proceso que tenga Report Tables, al borrar el caso tambien se eliminara los
registros de los Report Tables.
* Available from version ProcessMaker-2.5.2-testing.1
- El estado no era actualizado correctamente ya que al ejecutar el trigger se tenia datos antiguos con el cual se reescribia el estado del caso.
- Al ejecutar un trigger se realiza el unset de las variables APP_STATUS, APP_PROC_STATUS, APP_PROC_CODE, APP_PIN para que no sean modificadas.
- El estado no era actualizado correctamente ya que al ejecutar el trigger se tenia datos antiguos con el cual se reescribia el estado del caso.
- Al ejecutar un trigger se realiza el unset de las variables APP_STATUS, APP_PROC_STATUS, APP_PROC_CODE, APP_PIN para que no sean modificadas.
- El estado no era actualizado correctamente ya que al ejecutar el trigger se tenia datos antiguos con el cual se reescribia el estado del caso.
- al ejecutar un trigger se realiza el unset de las variables APP_STATUS, APP_PROC_STATUS, APP_PROC_CODE, APP_PIN para que no sean modificadas.
- If user send an email notification when he pauses a case. The FROM is always "PROCESSMAKER". Is it possible to change it to something else.
- Added title the email sends notifications in a task.
- Cuando se pausa un hilo el status de todo el caso cambia a PAUSED
- Ya no se cambia el status de todo el caso, solo se cierra el hilo pausado
- Existe aun un problema con los listados, los cuale sno muestran el estado del caso correctamente, eso se arreglara con el bug 11791 y 12012
Description: ./files directory cannot be up 32000 directories max at ext3 configuration.
Solution : split the uid case directory at 3 level to create a tree structure. Apply this new structure to all PM. Set a upgrade procedure at time to use processmaker upgrade <workspace> commnand as su.
- Se requiere que los reenvíos que se hacen a través del historial de mensajes, no se pueda realizar desde el menú casos, ya que existe el problema que cualquier usuario que haya participado de un caso puede reenviar notificaciones, a cualquier usuario, y existe el peligro de divulgación de información crítica que debe ser restringida por roles.
- Added Roles to control Messages History.
- Process Supervisors can only reassign cases to Users&User Groups on menu Process Supervisor\Reassign. They can not reassign to Users&User Groups (Ad Hoc)
- Adjustment in the selection on Ad Hoc
- Process Supervisors can only reassign cases to Users&User Groups on menu Process Supervisor\Reassign. They can not reassign to Users&User Groups (Ad Hoc)
- Added group ad hoc in to list
- New feature
- PM Function for add a input document
- Added function "PMFAddInputDocument" in "class.pmFunctions.php"
- The QA team should test with:
* Dynaforms
* KnowledgeTree plugin
* Available from version 2.0.46
- Process Supervisors can only reassign cases to Users&User Groups on menu Process Supervisor\Reassign. They can not reassign to Users&User Groups (Ad Hoc)
- Added Search ad hoc
When logging into the Case Tracker, the case tracker PIN was case sensitive,so I added a line of code in 'workflow/engine/classes/class.case.php' which capitalized the PIN entered by the user and compares with the PIN extracted from the BD.
- Improvement for the query:
SELECT APPLICATION.APP_UID, APPLICATION.APP_NUMBER, APPLICATION.APP_STATUS, APPLICATION.PRO_UID, APPLICATION.APP_CREATE_DATE, APPLICATION.APP_FINISH_DATE, APPLICATION.APP_UPDATE_DATE, APPLICATION.APP_DATA, ad.DEL_INDEX, ad.DEL_PREVIOUS, ad.TAS_UID, ad.USR_UID, ad.DEL_TYPE, ad.DEL_THREAD, ad.DEL_THREAD_STATUS, ad.DEL_PRIORITY, ad.DEL_DELEGATE_DATE, ad.DEL_INIT_DATE, ad.DEL_TASK_DUE_DATE, ad.DEL_FINISH_DATE, ad.DEL_DURATION, ad.DEL_QUEUE_DURATION, ad.DEL_DELAY_DURATION, ad.DEL_STARTED, ad.DEL_FINISHED, ad.DEL_DELAYED, ad.APP_OVERDUE_PERCENTAGE, at.APP_THREAD_INDEX, at.APP_THREAD_PARENT, at.APP_THREAD_STATUS, capp.CON_VALUE AS APP_TITLE, cpro.CON_VALUE AS PRO_TITLE FROM APPLICATION JOIN APP_DELEGATION ad ON (APPLICATION.APP_UID=ad.APP_UID) LEFT JOIN CONTENT capp ON (APPLICATION.APP_UID=capp.CON_ID AND capp.CON_CATEGORY='?' AND capp.CON_LANG='?') LEFT JOIN CONTENT cpro ON (APPLICATION.PRO_UID=cpro.CON_ID AND cpro.CON_CATEGORY='?' AND cpro.CON_LANG='?') JOIN APP_THREAD at ON (ad.APP_UID=at.APP_UID AND ad.DEL_THREAD=at.APP_THREAD_INDEX) WHERE APPLICATION.APP_UID='?'
- Improvement for the query: SELECT CONTENT.CON_ID, CONTENT.CON_VALUE FROM CONTENT WHERE CONTENT.CON_ID IN ('?') AND CONTENT.CON_CATEGORY='?' AND CONTENT.CON_VALUE<>'?' AND CONTENT.CON_LANG='?'
- New feature
- Web Services for delete and cancel case
- Added functions "PMFDeleteCase, PMFCancelCase, WSDeleteCase, WSCancelCase" in "class.pmFunctions.php"
- Added function "deleteCase, cancelCase" in "class.wsBase.php"
- Added functionality for applications using Web Services
* Available from version 2.0.44
- When "Assignment rules" is set to "Self service", do not send
notifications
- Problem solved, the settings made in "Notifications" on a task, is
used to send notifications
* Available from version 2.0.44
- cron.php script can have several instances running at the same time
- Problem solved, added validation in cron.php script to avoid run
several times
- Variable time added to control execution of cron
* Available from version 2.0.44
- Al momento de recuperar los permisos de los dynaforms, se estaba filtrando 2 veces por el UID de la tarea, esto e sinnecesario porque la funcion que recupera los permisos ya valida por la tarea
- Habian otros issues menores (como el titulo del formulario en los tabs de preview)
- Se quito la dobre validacion por tarea y se corrigieron los issues menores
We've detected 2 problems:
1.- The new algorithm to detect if the password is encrypted don't support passwords with a ":" character
2.- When recover the email configuration the system don't decrypt correctly the password of a previous version (without encryption, backwards compatibility)
