- APP_FINISH_DATE is set to 1902-01-01 00:00:00 when create new case
using webservices
- DEL_INIT_DATE is set to NULL when routing case using webservices
- Solved the problem in the fields APPLICATION.APP_FINISH_DATE and
APP_CACHE_VIEW.APP_FINISH_DATE, when you create a new case now set to NULL
- Solved the problem in the fields APP_DELEGATION.DEL_INIT_DATE and
APP_CACHE_VIEW.DEL_INIT_DATE when the case is routed set to the date corresponding
- By changing the "Case Label", this is not updated in the APP_CACHE_VIEW table
- Solved problem to changing the "Case Label", now is updated in the APP_CACHE_VIEW table
- Improvement in file, compliance with the standard PSR2
Note:
- When you change the "Case Title" of a task, affecting every case,
if it is the current task of the case (otherwise it would not affect
the APP_CACHE_VIEW table)
- If a task is saved empty the "Case Title" the APP_TITLE take the value
#APP_NUMBER (all cases are in the task, this in APP_CACHE_VIEW table)
- By changing the "Case Label", this is not updated in the APP_CACHE_VIEW table
- Solved problem to changing the "Case Label", now is updated in the APP_CACHE_VIEW table
Note:
- When you change the "Case Title" of a task, affecting every case,
if it is the current task of the case (otherwise it would not affect
the APP_CACHE_VIEW table)
- If a task is saved empty the "Case Title" the APP_TITLE take the value
#APP_NUMBER (all cases are in the task, this in APP_CACHE_VIEW table)
- There is a major problem when using the new editor for PM Tables with Database Connections, if you choose a database connection (anything you have created as a Database Connection in process designer).
- Fix-bug and Addition of session variable in the different connections PMTables(Victor).
- When trying to create a new Report Table and selecting an external database connection for the "DB Connection" parameter, the following error message appears:
- Adjustment DB Connections for a Report Table, to diferents externals databases.
- We verified that the list of the steps not working.
- Was modified the class.appCacheView, the function getTodo for parameters
include TAS_UID y PRO_UID, too was modified the template indexSingle.html
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 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
- 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.
- Al eliminar el plugin enterprise en un workspace, no se elimina del registro de plugins en los demas workspaces, quedando registros de los plugins en el "plugin.singleton" en cada workspace
- Al eliminar un plugin en un workspace se eliminan tambien los registros en los demas workspaces, se ha implementado la accion "uninstall" para los plugins, ahora al eliminar un plugin se llama a su metodo "uninstall" si esta definido
- When the plugin is enabled Knowledgetree displays an error when you download the file
- Was added the necessary code to download the file when the plugin Knowledgetree is enabled
- Also added code in the plugin Knowledgetree, for this change to work properly
- there was no validations for native & custom date files while data preview for report tables
- validations added and posibles empty strings now are mapped to NULL on db.
- We'd need to increase the max-length of the Condition of the Evaluation routing rule because there are some special rules that need more length.
- Adjust the maxlength the ROU_CONDITION field in Evaluation, Selection, Parallel By Evaluation Routing Rule.
- 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".
- 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.
