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
- Migrate Case "Information" lists to ExtJS (from master branch)
- migrated the following items: Case history, Messages History, Dynaforms, Uploaded Documents, Generated Documents
- Cuando se crea un trigger en un idioma y se hace correr el proceso con ese trigger en otro idioma, este no se mostraba en el debug
- Este problema se soluciono cambiando la entrada vacia del content que tiene el titulo del trigger, e insertandolo nuevamente con el idioma que se solicito.
- The problem arises when the task notifications in a given language, the language change does not send the notification. That when you run the case.
- By sending the notification had problems with "SMTP Password" in the Email settings.
- You have created the necessary records in CONTENT to the task, this depending on the language.
- By sending the notice was corrected the problem with the "SMTP Password".
- The first problem, when the tab diagram showing the map did not hide when you selected the option NONE, and when they entered a white screen is displayed, the error speak second to show the dynaforms not present a session variable the which was shown as a notice.
- To display dinaforms valid only in the XmlForm class, and q if you increase the session showed the Dynaform across the page, to edit the first problem is how to obtain permits in class case by changing the role permission caseTrackerPermissions addition to improving function, also modified the way to generate depending on the function menu caseTrackerPermissions also modified the authentication to lead the tab corresponding to the relevant validations.
- en realidad no duplica el password, sino que muestra el mismo pero encriptado
- para evitar este tipo de confusiones decidimos dejar vacio el password asi como está en el editor de usuarios, este solo se solicitara si no tiene guardada una contraseña en el servidor o si la direccion del servidor ha cambiado.
- it was happening with forks with conditional in one at all threads
- the solution was complete an unhandled condition on the original code
- other problem was found when a thread has not completely started, producing a warning, was solved.
- at the same time the code was improved modulating a section of the code in a function that is called twice
This Feature allow a user to post a note at any stage of a Case and from cases lists
Conflicts:
workflow/engine/data/mssql/schema.sql
workflow/engine/methods/cases/casesListExtJs.php
workflow/engine/skinEngine/base/css/pmos-xtheme-gray.css
workflow/engine/templates/cases/casesList.js
workflow/engine/templates/cases/open.js
* A radio group option was added into smtp configuration interface to select a secure connetion type
* The phpMailer thirdparty library was updated to support ssl and tls secure connections
