- 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)
- After upgrading from version 2.0.38 to 2.0.40, there is no way to change the user's authentication source, from internal to LDAP or to LDAP to internal.
- Uncommented Buttom of the Authentication tab and activation in summary.
- KnowledgeTree and webEntry don't work when you try to upload
some files
- Added the missing code in this section when the KnowledgeTree plugin
is enabled
- The ldap list was generated with an excessive size and the checkboxes
were not selected in the entire page.
- The Ldap list was optimized to generate it with the smallest size possible
- It was created a new template to improve the selection of the checkbox.
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.
- 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
- 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
- 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.
