The
XMPP issues often relate to client behavior; see Engage Mobile iOS 5.2.x and Engage Mobile Android 5.2.x for additional information.
This section summarizes the new features in this release.
The
The XMPP adapter now makes an APNS connection when it starts. (PFM-7861)
Previously, the APNS connection was made when the first push message was sent, costing seconds in a lazy connection.
Messages sent via rule to an Engage Mobile client are not lost. (PFM-7855)
Outbound rules are not processed in a separate thread from the delivery thread. The XMPP adapter now waits for successful processing of the JMS message before removing it from the stack to process. The
XMPP 3.2 is required for Read Receipts enhancements in
Patients displayed in the roster present PHI to users accessing the roster on their device. XMPP now logs when patient information access occurs, providing data for compliance reviews.
A single XMPP (smartphone) login per user is allowed with
A user can login to only one device and a device can only be logged into by one user at a
time. A user is automatically logged out of their original device when they log into a
second device. An initial user is automatically logged out of a device when a second user
logs into the same device. However, multiple logins as the same user are allowed if using
This section provides information about fixes and improvements made to the
The following issues are fixed in
NONE
The following issues are fixed in
A location assigned to a bed with more than 32,767 assignments no longer will cause an XMPP error when the bed is updated. (PFM-7311)
The query to get the assignment id now starts at the Assignments dataset, and adds conditions to the query to only get (active, next) assignments that have a location that includes the updated bed.
XMPP no longer fails to link LastRead for messages sent to a group containing multiple users. (PFM-6744)
The alert stanza has been updated to keep the original id of the first alert created from the firing of a rule. The previous behavior still holds true: When a rule fires to update an alert, the alert will have a new id, since it is new content.
Badge count is no longer incorrect when an alert arrives while on Home screen and Location Services is off. (PFM-6040)
An issue has been corrected that caused an infinite loop to occur when processing messages under certain circumstances.
Inactive users no longer can log in on XMPP devices. (PFM-2242)
Now sessions are not allowed to continue for an inactive user, and users that become inactive are logged out.
This release of the