- 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)
The following changes were made:
- fix update Solr index process
- implement casesenuLoader using Solr server to display counters
- fix cron missing reference to system class
- add function and classes documentation
- It was verified that the table was not updated application status.
-Was modified and functions pauseCase unpauseCase tate to change the application in the table.
Now the Solr configuration variables are read from the env.ini file that
is stored in the shared//sites/SYS_SYS/ folder.
The system class is used to get the environment variables using the
solrenv function.
Solr support in PMOS2 includes:
Functionality:
- Implementation of Home views (Inbox, Draft, Participated, Unassigned). The views return fast results.
- Include read, unread, all, and process filter in inbox View.
- Include process filter in draft view.
- Include started by me, completed by me, all, process, and status filter in participated view.
- Include process filter in unassigned view.
- Improved search functionality (search in user defined variables): Use the following syntax to search in process (user defined) variables. {variable_name}:{search_word} ex1:"causal:20*" where causal is the variable defined by the user.
+ Use of wildcards in search: Use * as wildcard at the begin or end of word
+ Multiple conditions in search: Separate multiple conditions by space ex2:"Materiales causal:20*" means that we are searching for the word Materiales and the causal that begin with 20.
+ Search in dates (interval ): Format=> {variable_date}:[yyyy-mm-dd TO yyyy-mm-dd]
Local date not UTC date required
ex: FechaRegistro:[2011-04-15 TO 2011-04-30] //registros con fecha entre el 2011-04-15 y el 2011-04-30.
+ we can use the wildcard *:
ex: FechaRegistro:[* TO 2011-04-30] //registros con fecha menor o igual a 2011-04-30.
FechaRegistro:[2011-04-15 TO *] //registros con fecha mayor o igual a 2011-04-15.
+ Search of exact phrases. format: {variable}:"frase a buscar"
ex: Cliente:"Jesus Marin"
- Application update function.
+ The function is called every time a change is detected in the application's data including the related delegations.
- Use of cache to improve performance
Not included:
- Order of task, sent by, and due date columns.
Pending:
- Advanced search view using faceted lists.
- Se crearon varias funciones para este caso.
- La funcion getCaseNotes en la class.case.php con los parametros applicationID, type que es la forma que quiere que se devuelvan los datos, puede ser array, objetc, string por defecto esta en array, y userID que nos daria solo las notas de ese usuario, por defecto nos devuelve de todos los usuarios.
- Se modifico la funcion getNotesList para poder traer las notas por un determinado usuario y por defecto recupera las notas de todos los usuarios.
- en class.pmFunctions.php se creo la funcion PMFGetCaseNotes con los parametros applicationID, type que es la forma que quiere que se devuelvan los datos, puede ser array, objetc, string por defecto esta en array, y userID que nos daria solo las notas de ese usuario, por defecto nos devuelve de todos los usuarios.
- En class.wsBase.php la funcion getCaseNotes con los parametros applicationID, userID que nos daria solo las notas de ese usuario, por defecto nos devuelve de todos los usuarios, esta funcion nos devuelve un array con los fieds en minuscula.
- En soap2.php getCaseNotes donde se tienen los siguiente parametros: sessionId, se necesita iniciar una session para poder utilizarlo, applicationID, userID que nos daria solo las notas de ese usuario, por defecto nos devuelve de todos los usuarios.
- Se adiciono la funcion para utilizarlo en SoapServer.
- En wsResponse se creo un nuevo template para la respuesta del webservice wsGetCaseNotesResponse con los campos status_code, message, notes, timestamp.
- En pmos2.wsdl se agregaron los datos necesarios para la salida correcta del webservice.
- La variable SYS_CASE_PRIORITY se estaba hardcoded en prioridad 3 - Normal.
- Se pusieron validaciones para que se pudiera utilizar la prioridad de acuerdo con la variable.
- La variable SYS_CASE_PRIORITY ahora se setea manualmente ya no se crea de manera automatica.
- the problem originally was that never is derivation handling correctly to conditional forks and normal forks
- code was improed and handled for both forks at derivation types
