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.
Cuando se importaba un proceso que fue creado en el mismo servidor, pero eliminado y del cual el usuario que lo creo fue tambien eliminado, PM aun importaba el proceso con el nombre del usuario q lo creo como Process Owner, aunq este ya no existiera, ya que al ser la eliminacion de usuarios solo un borrado logico, aun este usuario estaba registrado en la BD y podia ser asignado.
Ahora PM asigna por defecto a todos los procesos que se importan el usuario actual como Process Owner.
I added a validation in file 'workflow/engine/methods/processes/processes_Import_Ajax.php' to change PROCESS.PRO_CREATE_USER value in the database to the current user.
I added a validation in file 'workflow/engine/methods/processes/processes_Import_Ajax.php' to change PROCESS.PRO_CREATE_USER value in the database to the current user.
- Se ha detectado que el archivo encargado de la importacióstaba usando short tags de PHP
- Se ha cambiado el short tag a un tag estandar de php
- Como workaround para otras versiones se debe habilitar el uso de short tags en el php.ini
- In the creation/editing of PMTables/ReportTables, not validated the
use of reserved words
- It has validated the use of keywords in the creation/editing of
PMTables/ReportTables
- It has been validated using reserved words to importing a process with
ReportTables (old version)
* Available from version 2.0.44
