Problem:
Case 1: The same user 'A', creates and imports the process, using the option: "Update the current process...".
Result: The user that created the process, user A in the example, is allways the User Owner of the process.
Case 2: User 'A' creates the process, and user 'B' imports the process, using the option: "Update the current process...".
Result: The user that created the process, user A in the example, is allways the User Owner of the process.
Case 3: User 'A' creates the process, then this user 'A' is deleted, and user 'B' imports the process, using the option: "Update the current process...".
Result: The User Owner is showed empty.
Razon: When the user 'A' (the one that created the process) is deleted, the delete is only logical not physical in the db, and it is updated with the Status 'CLOSED' and the username of this user is changed to an empty string " ". So, when the process is updated the username is copy like it is in the db, and copy into the User Owner field, showing the empty string " ".
Solution:
A validation was added asking if the user exist, if this dosen't the User Owner is changed to the current user logged, and the same if the user exist but his status is CLOSED.
- PHPUnit for processmaker/workflow/engine/src/ProcessMaker/BusinessModel/Role.php
- PHPUnit for processmaker/workflow/engine/src/ProcessMaker/BusinessModel/Role/Permission.php
- PHPUnit for processmaker/workflow/engine/src/ProcessMaker/BusinessModel/Role/User.php
- When creating a dynaform with the character "&", the field handlers not working.
- Problema resuelto, el problema que se teníera lo siguiente cuando se utiliza el "&" en el tílo de un dynaform,
cuando se enviaba los datos via GET, el "&" lo interpretaba como un separador de variables y esto ocasionaba la
division de los datos que se enviaba. Se valida los datos enviados via GET codificáolos y al recibir estos datos
se los decodifica
The validation for the not required parameter "unpauseDate" was wrong. When this parameter was empty the validation was taking this like this has a date, so it was trying to check the date format, and this was giving an error.
The validation was changed to only let strings of 10 or more characters go into the next validation where the format of the date is checked.
- Se han implementado los siguientes Endpoints:
GET /api/1.0/{workspace}/role/{rol_uid}/permissions?filter={filter}&start={start}&limit={limit}
GET /api/1.0/{workspace}/role/{rol_uid}/available-permissions?filter={filter}&start={start}&limit={limit}
POST /api/1.0/{workspace}/role/{rol_uid}/permission
DELETE /api/1.0/{workspace}/role/{rol_uid}/permission/{per_uid}
- Se han implementado los siguientes Endpoints:
GET /api/1.0/{workspace}/role/{rol_uid}/users?filter={filter}&start={start}&limit={limit}
GET /api/1.0/{workspace}/role/{rol_uid}/available-users?filter={filter}&start={start}&limit={limit}
POST /api/1.0/{workspace}/role/{rol_uid}/user
DELETE /api/1.0/{workspace}/role/{rol_uid}/user/{usr_uid}
- Se han implementado los siguientes Endpoints:
GET /api/1.0/{workspace}/roles?filter={filter}&start={start}&limit={limit}
GET /api/1.0/{workspace}/role/{rol_uid}
POST /api/1.0/{workspace}/role
PUT /api/1.0/{workspace}/role/{rol_uid}
DELETE /api/1.0/{workspace}/role/{rol_uid}
Se modifica la clase wsBase para que se ejecuten los triggers before assigment, cuando se realiza el route-case. Replace harcoded labels by a translation ID
