- Un usuario NO Administrador pero con permisos de PM_USERS puede
auto-configurarse como Administrador
- Adjustment in the validation of user from administrator roles can not
change if not an administrator.
BUG 10921 "When changing the password, the old password..." SOLVED
- When changing the password, the old password should be
required (and verified)
- Problem solved, added a new field to validate the user, when changing
the password (user's profile)
* Available from version ProcessMaker-2.0.47 (2.5.1)
- When changing the password, the old password should be
required (and verified)
- Problem solved, added a new field to validate the user, when changing
the password (user's profile)
* Available from version ProcessMaker-2.0.46
- Despues de revisar los registros se determino que en 2 instancias diferentes se ha creado al mismo ususuario con diferencia de segundos y al no haber validacion al momento de crear permite crear 2 usuarios con el mismo username
- Se agrego una validacion adcional antes de crear a usuario
- New feature
- Request that an "Edit" button be added to the page to view the
profile of a particular user
- Added edit button in Summary view
* Available from version 2.0.46
- In the class "derivation" doesn't exist the validation for the "Replaced By" field
- Added the business logic to set the replaced by user when a case is derivated
- Reverted the changes made in "Users.php"
- Solved wrong display of information "Country, State or Region, Location"
in "View_Edit_Profile" this in IE, all this in "usersAjax.php"
- When modifying a user's data "ADMIN>Users" or "View/Edit Profile"
shows the incorrect data in the dropdowns
- Problem solved, display incorrect information in Dropdowns is because
the response time of AJAX requests, this was solved by improving the
order of AJAX requests
- Changed the label "Saving process" (ID_SAVING_PROCESS) for
"Saving ..." (ID_SAVING)
- Solved wrong display of information "Country, State or Region, Location"
in "View_Edit_Profile" this in IE
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)
- After upgrading from version 2.0.38 to 2.0.40, there is no way to change the user's authentication source, from internal to LDAP or to LDAP to internal.
- Uncommented Buttom of the Authentication tab and activation in summary.
- In the user list to sort by any field is not ordered only the current page and so all the listing grid.
- RemoteSort attribute was added to activate the update by ajax and all you can sort the list in addition to increasing the query in ajax options which have listed.
- en la pestaña de grupos, si admitia asignar "Simplified" en "User Experience" a grupos que tienen algun usuario administrador
- se añadio un case que filtre esos usuarios.
Passwords were stored in clear text just in some circunstances.. specially when the user it self change its password. Now every time PM stores a password it is stored encrypted.
