- La tabla LOGIN_LOG almacena el ip errado
- Problema resuelto, se registra el ip utilizando el metodo getIpAddress().
Disponible para la versió.5.3 de ProcessMaker.
- No se puede realizar la import, export, delete, data, edit de un Report Table.
- Problema Resuelto, el problema que se tenia era por la version de php que era php 5.4. Esta version de php
exige mejor control cuando se utiliza los metodos de una clase, no se puede utilizar los metodos directamente sin antes
de ser creados.
Se puede realizar las acciones de: edit, delete, data, import y export en un Report Table. y NO muestra error.
Disponible para la versió.5.3 de ProcessMaker.
- Los saltos de linea no estaban siendo parseados correctamente debido a un cambio previo en la version 2.5.2
- Se repuso y adapto parte del codigo que hacia el cambio de los saltos de linea
- Se han implementado los siguientes Endpoints:
GET /api/1.0/{workspace}/project/{prj_uid}/dynaforms
GET /api/1.0/{workspace}/project/{prj_uid}/dynaform/{dyn_uid}
POST /api/1.0/{workspace}/project/{prj_uid}/dynaform
PUT /api/1.0/{workspace}/project/{prj_uid}/dynaform/{dyn_uid}
DELETE /api/1.0/{workspace}/project/{prj_uid}/dynaform/{dyn_uid}
- Al enviar lo correos se aprecian campos vacios que se agregan al correo.
- Esto no era causa del plugin sino que al hacer una mejora para los outputdocuments se valida los campos añadiendo la etiqueta <br> que es lo que ocasionaba los espacios en el correo. se retiraron nl2br de la funcion replaceDataGridField en la class.g y se agrego la validacion en OutputDocument.php.
- The function sent in the variable $_REQUEST['action'] was always executed
- A new method was implemented to validate if is a user custom function or a system function (G::isUserFunction)
- Al tratar de eliminar un directorio, se elimina el contenido,
pero no asi el directorio
- Problema resuelto, se ha cambiado el orden de la eliminacion
del directorio
- Al realizar la migracion a la nueva estructura de directorios, no se
puede descargar los archivos, desde HOME>Documents
- Problema resuelto, al crear la nueva estructura de directorios se ha dado
los permisos necesarios para dicho directorio
* Available from version ProcessMaker-2.5.1-testing.4
- Please consider include "special" pages layout to the SKIN.
- Problema resuelto, se han customizado las interfaces "error404" y "updating", ahora estan disponibles en los
skins "neoclassic" y "classic". Se ha validado esta interfaz en los skins, de no existir los templates en un
determinado skin, automaticamente utilizara el template del skin "classic".
* Available from version ProcessMaker-2.5.2-testing.1
- Please consider include "special" pages layout to the SKIN.
- Problema resuelto, se han customizado las interfaces "error404" y "updating", ahora estan disponibles en los
skins "neoclassic" y "classic". Se ha validado esta interfaz en los skins, de no existir los templates en un
determinado skin, automaticamente utilizara el template del skin "classic".
* Available from version ProcessMaker-2.5.1-testing.3
- Please consider include "special" pages layout to the SKIN.
- Problema resuelto, se han customizado las interfaces "error404" y "updating", ahora estan disponibles en los
skins "neoclassic" y "classic". Se ha validado esta interfaz en los skins, de no existir los templates en un
determinado skin, automaticamente utilizara el template del skin "classic".
* Available from version ProcessMaker-2.5.1-testing.3
- Please consider include "special" pages layout to the SKIN.
- Problema resuelto, se han customizado las interfaces "error404" y "updating", ahora estan disponibles en los
skins "neoclassic" y "classic". Se ha validado esta interfaz en los skins, de no existir los templates en un
determinado skin, automaticamente utilizara el template del skin "classic".
* Available from version ProcessMaker-2.5.1-testing.3
- Safe upgrade for JavaScript files of the plugins's translations
- Improved programming logic for this issue
- Problem solved, has been added the code necessary for the plugins's translations
* Available from version ProcessMaker-2.5.2-testing.1
Description: ./files directory cannot be up 32000 directories max at ext3 configuration.
Solution : split the uid case directory at 3 level to create a tree structure. Apply this new structure to all PM. Set a upgrade procedure at time to use processmaker upgrade <workspace> commnand as su.
- New feature
- Safe upgrade for JavaScript files
- Added new feature,
- This new feature is activated when you run one of the following commands:
$ ./processmaker upgrade
$ ./processmaker build-js
$ ./processmaker browser-cache-files-upgrade
- The new feature creates an attribute in the file "processmaker/workflow/engine/config/env.ini"
Example:
browser_cache_files_uid = "xxxxxxxxxxyyyyyyyyyyzzzzzzzzzzaa"
- After running the command, the browser should automatically cache the new files
* Available from version ProcessMaker-2.5
- Simplified Interface not reflecting minutese
- Solved problem, the list of cases in the simplified interface, the minutes show correctly
* Available from version ProcessMaker-2.0.47 (2.5.1)
- New feature
- Safe upgrade for JavaScript files
- Added new feature,
- This new feature is activated when you run one of the following commands:
$ ./processmaker upgrade
$ ./processmaker build-js
$ ./processmaker browser-cache-files-upgrade
- The new feature creates an attribute in the file "processmaker/workflow/engine/config/env.ini"
Example:
browser_cache_files_uid = "xxxxxxxxxxyyyyyyyyyyzzzzzzzzzzaa"
- After running the command, the browser should automatically cache the new files
* Available from version ProcessMaker-2.5
- New feature
- Safe upgrade for JavaScript files
- Added new feature,
- This new feature is activated when you run one of the following commands:
$ ./processmaker upgrade
$ ./processmaker build-js
$ ./processmaker browser-cache-files-upgrade
- The new feature creates an attribute in the file "processmaker/workflow/engine/config/env.ini"
Example:
browser_cache_files_uid = "xxxxxxxxxxyyyyyyyyyyzzzzzzzzzzaa"
- After running the command, the browser should automatically cache the new files
* Available from version ProcessMaker-2.5
- New feature
- Safe upgrade for JavaScript files
- Added new feature,
- This new feature is activated when you run one of the following commands:
$ ./processmaker upgrade
$ ./processmaker build-js
$ ./processmaker browser-cache-files-upgrade
- The new feature creates an attribute in the file "processmaker/workflow/engine/config/env.ini"
Example:
browser_cache_files_uid = "xxxxxxxxxxyyyyyyyyyyzzzzzzzzzzaa"
- After running the command, the browser should automatically cache the new files
* Available from version ProcessMaker-2.5
- URL no valid no redirects to the 404 page
- Solved problem in validation of template
- Solved problem, add validation for URL no valid
* Available from version ProcessMaker-2.0.46
- Problem with fonts in OutputDocuments with report generator TCPDF
- The problem specifically is with the font tag, this tag is obsolete
- Solved problem, added validation when use font tag
* 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
- With Aymara translation can not use Date Picker dialog and can't open Output Documents for editing
- Adjustment in the condition of the calendar when the language doesn't exist.
