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
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.
- On query aren't filtering by disticts pro_uid's
- adding distinct by pro_uid works fine
NOTE.- Why someone reason somebody comment a initial distinc on query, but it wasn't working fine.
- In the file where it addresses the url does not take intoaccount a shipping option.
- They change the addressing mode to load the menus above, plus you take two conditions, in order to load all the menus at the top that when you have a parent, not having a parent will have to address but without the menus higher for compatibility with the Outlook plugin.
- 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.
- Por alguna razon en la version de browser que usan algunas de las distribuciones de Outlook, al abrir una pagina q hace un stream como la que descarga el documento, el broser va ala pagina antes derecibir respuesta, espor eso q muestra en blanco, y el comportamiento normal en los otros browsers es q se mantieene mostrando la ultima pagina hasta q recibe respuesta del servidor.
- Ahora se abre el documento en una nueva ventana, se probo en IE, Firefox y Chrome
- Problem running case with field file with property value "Input" in the Dynaform, generates the following error: "This row doesn't exist!"
- Added the missing code in this section when the KnowledgeTree plugin is enabled.
- The changes made by process supervisors to fields in DynaForms are not recorded in the Change Log
- Changes made by process supervisors to fields in DynaForms, may be viewed by a user if this is defined in "process permissions". with this the user will see the "Change Log" of a case.
- Additionally the following error was corrected:
> Fatal error: Call to undefined method Ajax::dynaformViewFromHistory() in processmaker/workflow/engine/methods/cases/ajaxListener.php on line 42
> The error was corrected by adding code to complete the "Change Log" in the option "View"
- Cuando el contenido de un iframe (como los listados) es abierto en una ventana nueva y se accede
a los casos da un error JS porque se trata de acceder a un metodo del parent, que en este caso no existe
- Se agrego una validacion para prevenir este error
- Al revisar el panel se advirtio que en el archivo cases_ToReviseOutputDocView.php se ejecutava un js creando el panel.
- Se verifico que al borrar el js no afecte a otros procesos que puedan estar llamando a este file.
- In the case step was not performed for external verification step, the case if a plugin existed or not.
- Added a verification whether or not there is a plugin for an external step, plus add a label in os environment.
- It was verified that no distinction was being the type of file that was downloaded.
- Added code to identify the Tido powerful file so just download and display the correct download link.
- Migrate Case "Information" lists to ExtJS (from master branch)
- migrated the following items: Case history, Messages History, Dynaforms, Uploaded Documents, Generated Documents
- Una vez habilitado el debugger, al loguear con un usuario no aparece el área "Depurador de ProcessMaker", área donde se muestran las variables y los triggers(Browser: Chrome).
- They attached the script cases_step.js when a process runs.
