- Actions by email: No manda la manda la notificacion
- Problema resuelto, al configurar el Email de tipo "Mail PHP" y utilizando una activacion Actions by Email,
la notificacion se envia.
* Available from version ProcessMaker-2.5.2-testing.1
- Actions by email: No manda la manda la notificacion
- Problema resuelto, al configurar el Email de tipo "Mail PHP" y utilizando una activacion Actions by Email,
la notificacion se envia.
* Available from version ProcessMaker-2.5.2-testing.1
- Actions by email: No manda la manda la notificacion
- Problema resuelto, al configurar el Email de tipo "Mail PHP" y utilizando una activacion Actions by Email, la
la notificacion se envia.
* Available from version ProcessMaker-2.5.2-testing.1
- Actions by email: No manda la manda la notificacion
- Problema resuelto, al configurar el Email de tipo "Mail PHP" y utilizando una activacion Actions by Email, la
la notificacion se envia.
* Available from version ProcessMaker-2.5.2-testing.1
- El metodo caseList, utiliza las tablas principales de ProcessMaker
- Problema resuelto, se ha reescrito el query para que use la tabla APP_CACHE_VIEW,
si SOLR esta habilitado/activo se utilizara este servicio para la obtencion
de los datos
* Available from version ProcessMaker-2.5.1-testing.4
- El metodo caseList, utiliza las tablas principales de ProcessMaker
- Problema resuelto, se ha reescrito el query para que use la tabla APP_CACHE_VIEW,
si SOLR esta habilitado/activo se utilizara este servicio para la obtencion
de los datos
* Available from version ProcessMaker-2.5.1-testing.4
- El estado no era actualizado correctamente ya que al ejecutar el trigger se tenia datos antiguos con el cual se reescribia el estado del caso.
- Al ejecutar un trigger se realiza el unset de las variables APP_STATUS, APP_PROC_STATUS, APP_PROC_CODE, APP_PIN para que no sean modificadas.
- El metodo caseList, utiliza las tablas principales de ProcessMaker
- Problema resuelto, se ha reescrito el query para que use la tabla APP_CACHE_VIEW
* Available from version ProcessMaker-2.5.2-testing.1
- El estado no era actualizado correctamente ya que al ejecutar el trigger se tenia datos antiguos con el cual se reescribia el estado del caso.
- al ejecutar un trigger se realiza el unset de las variables APP_STATUS, APP_PROC_STATUS, APP_PROC_CODE, APP_PIN para que no sean modificadas.
- No execute triggers according the configuration in case scheduler
- Solved problem, add code to execute triggers in method newCase() in wsBase class
* Available from version ProcessMaker-2.5.1-testing.3
Error: There were no parameter to set which starting task to select.
Sol: Adding a optional paramater to the newCaseImpersonate function.
plus code style changes.
- PMFSendMessage function can't be set for send mail with format text plain
- Fixed, PMFSendMessage now use the extension of the template for get the
format of the mail, example:
> path_to_template/MyTemplate.html
the extension is html, then use text/html content type for the mail
> path_to_template/MyTemplate.txt
the extension is txt, then use text/plain content type for the mail
> If the extension is different to html/htm, then used text/plain in all cases
* Available from version ProcessMaker-2.0.46
- Problem with the variable $_SESSION
- The variable $_SESSION should not lose the default values ..set
- Added functions to save and restore the values ..of the variable $_SESSION
- Revised class.pmFunctions.php functions and class.wsBase.php
- The QA team should test this functions (most of these functions running
triggers, try running triggers):
PMFAddInputDocument
PMFGenerateOutputDocument
PMFDerivateCase, WSDerivateCase, wsBase::derivateCase
PMFNewCase, WSNewCase, wsBase::newCase
PMFRedirectToStep
PMFDeleteCase, WSDeleteCase, wsBase::deleteCase
PMFCancelCase, WSCancelCase, wsBase::cancelCase
PMFPauseCase, WSPauseCase, wsBase::pauseCase
PMFUnpauseCase, WSUnpauseCase, wsBase::unpauseCase
wsBase::executeTrigger
wsBase::reassignCase
* Available from version 2.0.46
- Every time I send E-mails with PMFSendMessage() function, it doesn't
keep a track in DEL_INDEX field from APP_MESSAGE table
- Added parameter $delIndex to the function
* Available from version 2.0.46
- New feature
- Web Services for add case note
- Added functions "PMFAddCaseNote, WSAddCaseNote" in "class.pmFunctions.php"
- Added function "addCaseNote" in "class.wsBase.php"
- Added functionality for applications using Web Services
* Available from version 2.0.46
- New feature
- Web Services for getting information of user
- Added functions "PMFInformationUser, WSInformationUser" in "class.pmFunctions.php"
- Added function "informationUser" in "class.wsBase.php"
- Added functionality for applications using Web Services
* Available from version 2.0.46
- The getVariables() web service is not very useful, if you don't know which case variables have been defined.
- Changed name from getAllVariables to getVariablesNames.
- The getVariables() web service is not very useful, if you don't know which case variables have been defined.
- Added a new function for web services getAllVariables.
- New feature
- Web Services for pause and unpause case
- Added functions "PMFPauseCase, PMFUnpauseCase, WSPauseCase, WSUnpauseCase" in "class.pmFunctions.php"
- Added function "pauseCase, unpauseCase" in "class.wsBase.php"
- Added functionality for applications using Web Services
- Cancel case it's solved in bug 7385
- Function "pauseCase" from "class.pmFunctions.php" has changed its name to "PMFPauseCase"
* Available from version 2.0.44
- New feature
- Web Services for delete and cancel case
- Added functions "PMFDeleteCase, PMFCancelCase, WSDeleteCase, WSCancelCase" in "class.pmFunctions.php"
- Added function "deleteCase, cancelCase" in "class.wsBase.php"
- Added functionality for applications using Web Services
* Available from version 2.0.44
We've detected 2 problems:
1.- The new algorithm to detect if the password is encrypted don't support passwords with a ":" character
2.- When recover the email configuration the system don't decrypt correctly the password of a previous version (without encryption, backwards compatibility)
- New feature
- Web Services for updating user accounts
- Added functions "PMFCreateUser, PMFUpdateUser, WSCreateUser, WSUpdateUser" in "class.pmFunctions.php"
- Added function "updateUser" in "class.wsBase.php"
- Added functionality for applications using Web Services
- PMFDerivateCase not set variables of the case to derivate
- In the "derivateCase" method of the class "class.wsBase.php", no set
variables of the case to derivate
- Problem solved, now set appropriate variables to derivate
- 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
- 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
