2.7.27 Release Notes

Bug fixes

admission_reject () : Was setting the rejection date to 1970-01-01 instead of the current date
case_insert_associate() : Do not allow to set a person as an associate of himself
case_set() : The properties ‘editable_by_case’ and ‘editable_by_user’ were not stored
formula_exec () : When the QUESTION ID provided did not exist, the function crashed
library_program_version_list ( session, program ) : Actions to PUBLISH/DELETE/CREATE DRAFT were only added when the active session TEAM was the owner of the PROGRAM. Now the active user must have role "PROGRAM EDITOR" as member of the TEAM owner of the PROGRAM
session_password_set() : The old password was ignored. The new password was set even if the old password was wrong

New functions

admission_reject ()
event_insert ()
itemAnswerRender() REPORT function : New helper macro for generating REPORTS
session_close ()

Improvements

admission_set () : Allow to indicate a TEAM CODE (and not only a TEAM reference) when assigning the ADMISSION to a referral
https://linkcare.atlassian.net/wiki/spaces/DES/pages/17989895 : Returns the audit log date in the current user’s timezone
audit_list() : Returns the audit log in the current user’s timezone
event_role_list () : When the EVENT is assigned to an ADMISSION, show only the ROLES that have been assigned to the members of the SUBSCRIPTION (not all existing ROLES)
event_team_list ( session, event, role) : When the EVENT is assigned to an ADMISSION, shw only the TEAMS that are members of the SUBSCRIPTION with the selected ROLES (not all TEAM members of the SUBSCRIPTION)
https://linkcare.atlassian.net/wiki/spaces/WS/pages/1310731 : When the EVENT is assigned to an ADMISSION, show only the users that are members of the SUBSCRIPTION with the selected ROLE and TEAM (not all users of the selected TEAM)
https://linkcare.atlassian.net/wiki/spaces/WS/pages/525893650 :
- Includes information about the minimum requirements of a password
- Allows to indicate a TEAM to customize the instance logos with the images of the TEAM
https://linkcare.atlassian.net/wiki/spaces/WS/pages/524509 : Will never lock an account when login is incorrect if the platform is configured to not lock accounts.
https://linkcare.atlassian.net/wiki/spaces/WS/pages/3899438 : Added new parameter to indicate the ROLES that must be assigned to the membership of the USER in the TEAM
https://linkcare.atlassian.net/wiki/spaces/WS/pages/96024402 : TASKs not assigned to a PROFESSIONAL will appear in the list of TASKs of a user with ROLE "Role Manager" only when the TASK is open (previously closed TASKs were also included)

$GLOBALS['GROUP_NOTIFICATION_MESSAGES']: Allows to send a single message to a user when there are more than one notifications pending to be delivered
$GLOBALS['MAX_LOGIN_ATTEMPTS']: Now accepts a value of “0” to indicate that the accounts should never be locked after any number of failed logins
$GLOBALS['DB_TYPE']: Allows to indicate the underlying DB manager. Currently only “Oracle” is supported.

Reviewed support for REST API

The following functions have been revised to ensure that the reponse generates a correct JSON structure when invoking the API via REST protocol

2.7.27 Release Notes

Bug fixes

New functions

Improvements

FORM FORMULAS

OBJECT CODES

System configuration

Reviewed support for REST API

Related content