- 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.
- there were some 3 new validations for 3 variables to process importing, but not always they're set
so, before validation we're askin if exists
- the same por a variable dynaform when importing process the process already exists and a update was requested
- that was happening for imported process.
on the workspace where it has been imported the process category didn't exists
- It is fixed now, the process category is being imported with the process,..
so, when the process is being imported if the process category doesn't exist, it is created.
>>>Probably because ProcessMaker is trying to add a record to the RP Table with an empty date field set to "" instead of NULL.
- that was exactly the problem, but it is fixed now
(Fixes for import feature)
According the solution raised on the meeting
- the default selection for db connetions is workflow instead REPORT
- the prefix PMT for all pmtables was added
