PM-1445, No se muestra el calendario que esta usando un usuario. PM-1131, actualizacion de etiquetas en trigger wizard
PM-1445, se agrego el parametro CALENDAR_NAME en usersAjax.php y se recibio el mismo en users.js
A new parameter $config (associative array) was added in the PMFSendMessage function:
Example:
array(
"MESS_ENGINE"=>"PHPMAILER",
"MESS_SERVER"=>"smtp.gmail.com",
"MESS_PORT"=>587,
"MESS_FROM_MAIL"=>"xxx@gmail.com",
"MESS_RAUTH" =>1,
"MESS_ACCOUNT"=>"xxx@gmail.com",
"MESS_PASSWORD"=>"15678=865",
"SMTPSecure"=>"tls"
)
The parameters of the array showed in the Example are all the necesary parameters.
A new parameter $config (associative array) was added in the PMFSendMessage function:
Example 1:
array(
"EmailEngine"=>"PHPMAILER",
"Server"=>"smtp.gmail.com",
"Port"=>587,
"UserName"=>"jennylee@colosa.com",
"FromEmail"=>"jennylee@colosa.com",
"UserPassword"=>"asfasjeasas",
"SecureConnection"=>"tls"
)
The parameters of the $config array showed in the example 1 are all the parameters that the array $config accepts, this could just have the UserName and the UserPassword if all the other parameters are the same as those that are configured in System configuration.
Example 2:
array(
"UserName"=>"jennylee@colosa.com",
"UserPassword"=>"asfasjeasas"
)
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.
- Adjuntar dos archivos con el mismo nombre en un correo (PM v. 2.5.1).
- Problema resuelto:
Se agrega un nuevo metodo "PMFAddAttachmentToArray" el cual permite validar el indice de un array, si los indices
son iguales se diferenciara, si no lo son, se mantendra el mismo indice.
El metodo recibe los siguientes parametros:
> $arrayData: Array, valor de entrada, en donde contendra los nuevos datos.
> $index: Nuevo nombre de indice
> $value: Nuevo valor que contendra el indice
> $suffix: Cadena que se concatenara al indice diferente por default es: "$suffix = Copy({i})"
Ejemplo de cadena de concatenacio:
Fotografia Copy(1).jpg
Nota.- Suffix es un parametro opcional como se muestra en los ejemplos y su aplicabilidad:
PMFAddAttachmentToArray($array(), "notas.txt", "Notas de estudiantes");
PMFAddAttachmentToArray($array(), "notas.txt", "Notas de estudiantes", " Numero de copias-({i})");
PMFAddAttachmentToArray($array(), "notas.txt", "Notas de estudiantes", "");
> La nueva funcion es:
function PMFAddAttachmentToArray($arrayData, $index, $value, $suffix = " Copy({i})")
{
...
}
Este metodo puede ser utilizado al momento de crear triggers en: DESIGNER>Triggers>New
Disponible para la version 2.5.2
- Adjuntar dos archivos con el mismo nombre en un correo (PM v. 2.5.1).
- Problema resuelto:
Se agrega un nuevo metodo "arrayDocumentAddElement" el cual permite validar el indice de un array, si los indices
son iguales se diferenciara, si no lo son, se mantendra el mismo indice.
El metodo recibe los siguientes parametros:
> $arrayData: Array, valor de entrada, en donde contendra los nuevos datos.
> $index: Nuevo nombre de indice
> $value: Nuevo valor que contendra el indice
> $suffix: Cadena que se concatenara al indice diferente por default es: "$suffix = Copy({i})"
Ejemplo de cadena de concatenacio:
Fotografia Copy(1).jpg
Nota.- Suffix es un parametro opcional como se muestra en los ejemplos y su aplicabilidad:
arrayDocumentAddElement($array(), "notas.txt", "Notas de estudiantes");
arrayDocumentAddElement($array(), "notas.txt", "Notas de estudiantes", " Numero de copias-({i})");
arrayDocumentAddElement($array(), "notas.txt", "Notas de estudiantes", "");
> La nueva funcion es:
function arrayDocumentAddElement($arrayData, $index, $value, $suffix = " Copy({i})")
{
...
}
Este metodo puede ser utilizado al momento de crear triggers en: DESIGNER>Triggers>New
Disponible para la version 2.5.2
- El estado no era actualizado correctamente ya que al ejecutar el trigger se tenia datos antiguos con el cual se reescribia el estado del caso.
- al ejecutar un trigger se realiza el unset de las variables APP_STATUS, APP_PROC_STATUS, APP_PROC_CODE, APP_PIN para que no sean modificadas.
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.
- When you send an empty string in the parameter "Code" always returns 0. When you enter the correct parameters always returns 1.
- Changed documentation of the return value.
- PMFGetUserEmailAddress and PMFGetCaseNotes function. The wizard does not work properly.
- Solved problem, corrected default values of the parameters
* 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
- New feature
- PM Function for add a input document
- Added function "PMFAddInputDocument" in "class.pmFunctions.php"
- The QA team should test with:
* Dynaforms
* KnowledgeTree plugin
* Available from version 2.0.46
- Every time I send E-mails with PMFSendMessage() function, it doesn't
keep a track in DEL_INDEX field from APP_MESSAGE table
- Added parameter $delIndex to the function
* Available from version 2.0.46
- New feature
- Web Services for add case note
- Added functions "PMFAddCaseNote, WSAddCaseNote" in "class.pmFunctions.php"
- Added function "addCaseNote" in "class.wsBase.php"
- Added functionality for applications using Web Services
* Available from version 2.0.46
- New feature
- Web Services for getting information of user
- Added functions "PMFInformationUser, WSInformationUser" in "class.pmFunctions.php"
- Added function "informationUser" in "class.wsBase.php"
- Added functionality for applications using Web Services
* Available from version 2.0.46
- ExecuteQuery() is supposed to return the number of records affected by DELETE, UPDATE and INSERT commands.
- Adjustment in the number of records for different Engines.
- New feature
- Web Services for pause and unpause case
- Added functions "PMFPauseCase, PMFUnpauseCase, WSPauseCase, WSUnpauseCase" in "class.pmFunctions.php"
- Added function "pauseCase, unpauseCase" in "class.wsBase.php"
- Added functionality for applications using Web Services
- Cancel case it's solved in bug 7385
- Function "pauseCase" from "class.pmFunctions.php" has changed its name to "PMFPauseCase"
* Available from version 2.0.44
- New feature
- Web Services for delete and cancel case
- Added functions "PMFDeleteCase, PMFCancelCase, WSDeleteCase, WSCancelCase" in "class.pmFunctions.php"
- Added function "deleteCase, cancelCase" in "class.wsBase.php"
- Added functionality for applications using Web Services
* Available from version 2.0.44
- New feature
- Web Services for updating user accounts
- Added functions "PMFCreateUser, PMFUpdateUser, WSCreateUser, WSUpdateUser" in "class.pmFunctions.php"
- Added function "updateUser" in "class.wsBase.php"
- Added functionality for applications using Web Services
- Creating user via web services, no option to set expiry date
- Create user via web services, can now be set parameters:
expiry date and status (in the functions: createUser, WSCreateUser and PMFCreateUser)
- These changes in functions must be documented in the wiki.processmaker.com
