- Function "executeQuery" in triggers is not working properly with external
database, when run through Web Services with the functions "executeTrigger" or "routeCase"
- Problem solved, settled the session variables required by the method Propel::getConnection
Error
-----
Error in reassign and review of supervisor. This is caused because Solr
don't support those views.
Solution
---------
The filter to use Solr or DB was corrected to use DB in the case of Supervisor views.
Also a new exception was created to inform that APP_DATA could not be unserialized,
and the logic is not going to stop when an error of unserialization is run in the reindex process.
- Creating user via web services, no option to set expiry date
- Create user via web services, can now be set parameters:
expiry date and status (in the functions: createUser, WSCreateUser and PMFCreateUser)
- These changes in functions must be documented in the wiki.processmaker.com
- PMFNewCaseImpersonate function not working when start task of process to
instance is assigned to group and not to user
- Delete validation "user assigned to task"
- PMFNewCaseImpersonate function not working when start task of process to
instance is assigned to group and not to user
- Solved problem with PMFNewCaseImpersonate function, in class
wsBase (newCaseImpersonate) now working with groups
- 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)
Error
-----
can't search string without fieldname only fields are searched
Solution
--------
correct identification of field name to allow the search using plain string
in processname, status fields.
Error
-----
Error in date interval search, the second date in the interval was not used.
Solution
--------
The second date was changed to the correct variable to use it in the interval.
Error
-----
Error unserializing APP_DATA with null value
Solution
--------
Verify if the APP_DATA contains serialized NULL before trying to unserialize
The APP_DATA with NULL serialized = "N;" is generated with the function PMFNewCaseImpersonate
- 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).
- We verified that in searches reappears previous value.
- Was modified the class.propelTable for not to show the parameter in the following search, besides a validation for triggers was written.
