- En la version de PM 2.0 testing 16 cuando se habilita la opcion de forgot password y este despliega un mensaje de fatal error.
- Correción en el mensaje de respuesta de error.
- Migrate Case "Information" lists to ExtJS (from master branch)
- migrated the following items: Case history, Messages History, Dynaforms, Uploaded Documents, Generated Documents
- Despues de presionar el boton "Save" en las propiedades de las tareas simplemente se estaba cerrando el panel
- Ahora despues de cerrar el panel se muestra un mensaje de confirmacióe que los cambios fuerin guardados con exito
- Una vez habilitado el debugger, al loguear con un usuario no aparece el área "Depurador de ProcessMaker", área donde se muestran las variables y los triggers(Browser: Chrome).
- They attached the script cases_step.js when a process runs.
- The problem is very old and change that screen interface with ExtJS.
- But reviewing the functionality of "move" and "copy" we see that were not completed, was it advanced with "move" in order to move a file to another address, simply drag the file to your new location.
- The first problem, when the tab diagram showing the map did not hide when you selected the option NONE, and when they entered a white screen is displayed, the error speak second to show the dynaforms not present a session variable the which was shown as a notice.
- To display dinaforms valid only in the XmlForm class, and q if you increase the session showed the Dynaform across the page, to edit the first problem is how to obtain permits in class case by changing the role permission caseTrackerPermissions addition to improving function, also modified the way to generate depending on the function menu caseTrackerPermissions also modified the authentication to lead the tab corresponding to the relevant validations.
- The search option doesn't works when return big quantity of results, for each result a query was executed
- The search was optimized and now uses a array cache to store the PrccessMaker Users
- 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.
solved problem in "import" for plugins, fatal error in class.pluginRegistry.php. Also resolved the problem in inclusion of the variable PATH_SEP in $path
Grammar problem in "2 You have not privileges to execute this function". It needs a "do not", but it is better to not use "You".
In workflow/engine/methods/services/soap2.php,
change:
$o->guid = "2 You have not privileges to execute this function";
To:
$o->guid = "2. Insufficient privileges to execute this function'
