- The colors in the trackerLogin processMap are different to the processMap of a normal user
- The colors in the trackerLogin processMap are equal to the processMap of a normal user
- The PMFNewCaseImpersonate(), WSNewCaseImpersonate() and newCaseImpersonate() web service, do not return the UID and number of the new case like PMFNewCase(), WSNewCase() and newCase()
- It improved the code of the PMFNewCaseImpersonate method, for to returns the UID of case, as PMFNewCase
- It improved the code of the WSNewCaseImpersonate method, for to returns the UID of case, as WSNewCase
- Corrections made in the methods "Simple Trigger Web Services", including the files involved
- Al revisar la forma de exportacion se vio que para poder guardar un archivo el maximo del path mas el nombre del archivo no deberia de sobrepasar los 256 caracteres.
- Se realizo la validacion para truncar el nombre del archivo cuando se llegue al limite, para ambos archivos .pm y .xpdl.
- La variable SYS_CASE_PRIORITY se estaba hardcoded en prioridad 3 - Normal.
- Se pusieron validaciones para que se pudiera utilizar la prioridad de acuerdo con la variable.
- La variable SYS_CASE_PRIORITY ahora se setea manualmente ya no se crea de manera automatica.
- The Trigger Wizard doesn't include the fourth parameter $sUserLogged for the PMFDerivateCase() function
- Added in the trigger wizard the fourth parameter $sUserLogged for the PMFDerivateCase() function
- Al adicionar una tarea en un proceso en un determinado idioma no toma en cuenta la numeracion correspondiente
- En el idioma ingles e adicionan dos tareas en un proceso, luego se cambia al idioma españal adicionar una tarea esta se agrega con la etiqueta "Tarea 2", lo correcto era "Tarea 3"
- Se cambio el algoritmo de generacion de la etiqueta para una tarea, el algoritmo toma en cuenta la numeracion de las tareas no importando el idioma, tambien el algoritmo toma en cuenta el formato de la etiqueta de una tarea (G::LoadTranslation('ID_TASK') . ' ' . $iTaskNumber), se debe tener en cuenta que el idioma por defecto es el ingles (en) el cual tiene mayor prioridad que los otros idiomas. Tomar en cuenta los siguientes casos:
* Se crea un nuevo proceso
Idioma ingles se adicionan dos tareas -> "Task 1", "Task 2" (2 tareas)
se cambia a españy se adiciona una tarea, se tienen -> "Task 1", "Task 2", "Tarea 3"
* Se crea un nuevo proceso
Idioma ingles se tienen las siguientes tareas -> "Task 4", "Task 5", "Task 6" (3 tareas)
se cambia a españy se adiciona una tarea, se tienen -> "Task 4", "Task 5", "Task 6", "Tarea 7"
* Se crea un nuevo proceso
Idioma ingles se tienen las siguientes tareas -> "Task One", "Task Two", "Task 4" (3 tareas)
se cambia a españy se adiciona una tarea, se tienen -> "Task One", "Task Two", "Task 4", "Tarea 5"
* Se crea un nuevo proceso
Idioma ingles se tienen las siguientes tareas -> "Task One", "Task 2", "Task Two", "Task Three" (4 tareas)
se cambia a españy se adiciona una tarea, se tienen -> "Task One", "Task 2", "Task Two", "Task Three", "Tarea 5"
- Al eliminar el plugin enterprise en un workspace, no se elimina del registro de plugins en los demas workspaces, quedando registros de los plugins en el "plugin.singleton" en cada workspace
- Al eliminar un plugin en un workspace se eliminan tambien los registros en los demas workspaces, se ha implementado la accion "uninstall" para los plugins, ahora al eliminar un plugin se llama a su metodo "uninstall" si esta definido
- La version de los dashlets siempre estaba mostrando 1.0, el cual es el valor por defecto
- Ahora cada clase (dashlet) puede tener una version diferente que se ira modificando dependiendo de los cambios futuros q existan
- Cuando un usuario/grupo/departamento era borrado y tenia dashlets asignados da un error al generar el listado y no muestra ningun resultado
- Se agregro una validacion para que no de el error y el registro "muerto" es eliminado
- Faltaba agregar una validacion en el formulario de edicion en caso de que la clase del dashlet haya sido desactivada o borrada
- Ahora se redirecciona de nuevo al listado y se muestra un mensaje de error que indica que el objeto no existe y que posiblemente
el plugin relacionado haya sido desactivado
- for some php versions date.timezone is not configurated by default, that why th problem
- on cli.php date.timezone is being configurated now, if env.ini exists, its configuration in read
- When install the plug-in enterprise-1.4 and upgrade to version enterprise-2.0 generate one "Fatal error"
- Added methods in the core of processmaker
- Added code in the plug-in enterprise-2.0 to uninstall the previous version automatically
- It was found that had several labels that are hardcoded.
- Changed hardcoded labels reusing some existing labels and some things were created some labels.
- labels created: ID_INIT_DATE(Init Date), ID_OVERWRITE(Overwrite),ID_BROWSE(Browse),ID_UPLOADING_TRANSLATION_FILE(Uploading the translation file...),
ID_EVALUATION_RESULT ([Success] Evaluation result)
- Labels reused: ID_TITLE, ID_DESCRIPTION, ID_DUE_DATE, ID_FINISH_DATE, ID_SEND, ID_UPLOADED_DOCUMENTS, ID_GENERATED_DOCUMENTS, ID_FILE, ID_FIRST_NAME,
ID_LAST_NAME,ID_ACTIVE,ID_INACTIVE, ID_MSJ_REPORSTO
- image for Starting a case ...
it is labeled translation.ID_TITLE_START_CASE which works only if you change the language to es-ES
-
- When the plugin is enabled Knowledgetree displays an error when you download the file
- Was added the necessary code to download the file when the plugin Knowledgetree is enabled
- Also added code in the plugin Knowledgetree, for this change to work properly
- Showed a modification in the function getAllGroup which changes the whole structure due to commit 917a1ac704.
- Changed foreach structure to explore the new listing.
- a complete refactoring on skingEngine bootstrapper, now this is a class
- the mvc templatting engine was updated to work perfectly with templates that is using extjs engine
- a new "unmodern" was added to contains the new pmos modern main interface
- When the title is too long the window is offset by the scroll bar to see a wrong way and also the title.
- Molding was conducted in the processmap title and also the link generated in the process_export to trim the name according to the box you have.
- These fields are ommited when the list is generated
- An optional parameter was added, which if it is on "1" includes multiple selection fieds: such as listbox, checkgroup and grid
- File field can't be included becuase it's necessary to define first how files will be copied if we decide to include it later
- there was no validations for native & custom date files while data preview for report tables
- validations added and posibles empty strings now are mapped to NULL on db.
- the problem originally was that never is derivation handling correctly to conditional forks and normal forks
- code was improed and handled for both forks at derivation types
- New requirement in the creation of plugins, creating dashlets
- The new option was added in the wizard for creating dashlets
- Fixed the files needed for this new option
- Migrate Case "Information" lists to ExtJS (from master branch)
- migrated the following items: Case history, Messages History, Dynaforms, Uploaded Documents, Generated Documents
- Added field title for to opcion "new" and "edit" dashlet
- Added field title in list of dashlets
- Added title value in DASHLET_INSTANCE.DAS_INS_ADDITIONAL_PROPERTIES field, this in "inser.sql" file
- The main problem was on the onclick user functions were being setting up on paged tables headers, (with gulliver vars like @QSTEP_UID, etc) that were not replacing properly beuase are headers and not normal rows!!, that was wrong and causing the famous problem of "Conditional Compilation Error" on IE
- Finally this problem is solved leaving the onclick events for those hheaders only with doSort() at propeltable function.
- The reassignCase() web service doesn't allow assigned users to be designated to work on cases, but it does allow non-assigned users to be designated.
- Fix-Bug in the reassignCase function to be adjusted according to suggestion.
- We'd need to increase the max-length of the Condition of the Evaluation routing rule because there are some special rules that need more length.
- Adjust the maxlength the ROU_CONDITION field in Evaluation, Selection, Parallel By Evaluation Routing Rule.
- When you disable the plugin is removed the records from the table DASHLET_INSTANCE
- Solved the problem by avoiding the removal of the records in the table DASHLET_INSTANCE
- To the list are taken into account records the DASHLET_INSTANCE that have a bearing on DASHLET
- The problem arises when you run the method "routeCase" through web services, in the execution of the triggers can not access variables like @ @ APPLICATION.
- The problem is solved by keeping the variables @ @ APPLICATION and others in the execution of method "derivateCase"
- Cuando se crea un trigger en un idioma y se hace correr el proceso con ese trigger en otro idioma, este no se mostraba en el debug
- Este problema se soluciono cambiando la entrada vacia del content que tiene el titulo del trigger, e insertandolo nuevamente con el idioma que se solicito.
- Se esta usando una asignacion por refenencia cuando se almacena la informacion de los plugins, esto provoca q los
elementos posteriores al primero tengan la misma informacion, posiblemente se deba por compatibilidad con PHP 4.x
- Se cambio la asignacion por referencia por una asignacion normal ya que los objetos en PHP 5 siempre se asignan por referencia
- The problem arises when the task notifications in a given language, the language change does not send the notification. That when you run the case.
- By sending the notification had problems with "SMTP Password" in the Email settings.
- You have created the necessary records in CONTENT to the task, this depending on the language.
- By sending the notice was corrected the problem with the "SMTP Password".
