- 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.
- In the APPLICATION.APP_STATUS field in the database, the status never changes from "TO_DO" to "COMPLETED" when finishing the case
- The problem was caused by the solution to bug 8169, see http://bugs.processmaker.com/view.php?id=8169
- Solved problem, now APPLICATION.APP_STATUS field, changes to "COMPLETED" when finishing the case
- this is a important improvement, now we can have two configurations levels
1. Global Configuration Level (workflow/engine/config/env.ini)
2. Workspace Configuration Level (.../shared/sites/some_workflow/env.ini)
- improvement to read env's ini files once and store on session,
- if any file has been changed (verify by checksum files) that session value is updated
(removind debug print_r)
- this is a important improvement, now we can have two configurations levels
1. Global Configuration Level (workflow/engine/config/env.ini)
2. Workspace Configuration Level (.../shared/sites/some_workflow/env.ini)
- improvement to read env's ini files once and store on session,
- if any file has been changed (verify by checksum files) that session value is updated
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.
- The activation of a tab in ADMIN does not work with URL (setup/main?s=PMENTERPRISE or setup/main_init?s=PMENTERPRISE)
- Solved the problem, now looks for the variable "s" in the menu to set the active tab
- By using the function PMFGenerateOutputDocument was not versioned documents.
- According to the analysis was appropriate to change the $ for SUID for $ outputID as only used for the query to find if the document existed.
- Text instruction in Trigger Wizard for PMFSendMessage() function is wrong, asks for semicolon instead of coma to separate emails
- Replaced the word "semicolon" with the word "comma"
- The APP_CACHE_VIEW table does not contain the changes made in the CONTENT table when you rename processes/tasks
- The name change in processes/tasks is now reflected in the APP_CACHE_VIEW table
- Note.- The APP_CACHE_VIEW table contains values ..for only one language
- En algun momento se cambio la funcion "getAllGroup" de la clase "processMap" y ahora retorna otra estructura.
- Se adapto el code del formulario de creacion de permisos para que funcione con la nueva estructura de la respuesta de la funcion
- 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.
- Previous and Next step link not found when HTML is enable
- Uncommented lines in the method "get_htmlcode" where this "__DYNAFORM_OPTIONS" this for add the links, when it generate the html file in the HTML tab
- In existing dynaforms with the enabletemplate=1 does not affect the change will only affect the new dynaforms as you have enabletemplate=1 generate the html file with the corresponding links
- Se identificaron todas las etiquetas que se deberian modificar dependiendo si esta en PM TAbles o Report Tables.
- Se procedio al cambio de etiquetas para evitar la confusion de los casos de PM Tables y Report Tables.
- Problem in "Resending emails"
- Not being properly authenticating with the mail server
- Solved the problem with authentication with the mail server
- The problem with the file "processmaker/workflow/engine/bin/plugins/ldapadvancedbck.php" could not replicate, because this file does not belong to any plugin of the enterprise-plugin, it is noted that the cron.php runs all the files that are on "processmaker/workflow/engine/bin/plugins" and uses the class "...ClassCron" for each file, executing the corresponding method
- Nuevo requerimiento, agregar la opcion "Export" en el listado de procesos
- Se agrego la opcion "Export" (exportar un proceso) en la barra de herramientas y menu contextual
- 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
- Cuando se realiza una instalacion de cero de esta version, en el navegador IE9 no se visualiza la opcion Heartbeat, lo cual hace que exista un mal funcionamiento del mismo.
- Adjustment extJS javascript coding for iExplorer problem.
- Cuando se configura el forgot password, no se aplica al hacer login en dicha ventana, es decir no se visualiza el link para enviar el otro password
- Adjustment in the forgot password in send mail, encryption of password, and correction in the visualization of the forgot password link on the classic skin.
