deviceWISE Cloud 26.08 Release Notes

[Object Registry] - Improved access control for the LwM2M Object Registry to prevent view-only users access.

[Open Server] - The user.update and user.mfa.disable API commands now require a multi-factor authentication token when the user has MFA enabled.

[Campaigns] - Improved access control for Campaign editing to prevent view-only users from modifying campaigns.

[Connections] - The cdp.connection.list API command now returns the number of sessions and zero-data sessions for the last 1, 7, or 30 days for each connection.

[Open Server] - The connection.session.nodata cloud trigger event will now accept a notification frequency parameter.

[Triggers] - Fixed an issue where no triggers were displayed under the Table tab for view-only users.

[LWM2M] - Fixed an issue in the LwM2M Object Browser where the View Binary Data dialog title was incorrect for instance-level reads and updated resources were not highlighted correctly.

[Developer - External SMS] - Fixed an issue where adding MSISDN entries left the dialog open and displayed an incorrect message when one of the entries already existed.

[Method Aliases] - Fixed Method Aliases to correctly apply the Random option when selected as the No Target Policy.

[Method Aliases] - Fixed an issue where selecting multiple Thing Keys for a method alias caused the last entry to overwrite the previously selected keys.

[LWM2M] - Fixed an issue in the LwM2M Object Browser where values delivered through large blockwise notifications remained stale instead of updating.

[Triggers] - Fixed an issue where the resource list for the lwm2m.oir.read trigger action included a non-existent resource entry.

[Device Profiles] - Fixed an issue on the Developer > Device Profiles edit page where the Application Servers and Application ACLs tabs displayed a loading indicator that never cleared.