The Engage XMPP Adapter 3.4 SR1 is a maintenance release and has no new features.

The Engage XMPP Adapter 3.4 provides the following new features:

• User Inactivity timeout for Engage Mobile Users based on role. (PFM-8929)

  The facility can now decide when a user must re-authenticate after a specified time of inactivity. The specified time is in minutes and can be from 1 to 10,080 minutes. Because this number is set in the Security Policy, different roles can have different timeout lengths. The application is considered inactive when it is in the background and/or when the device is asleep. Messages will continue to be delivered while the user is timed out and will be available once the user re-authenticates into the application. This feature requires Engage Mobile 5.3.

• Patient Information access is now determined by role. (PFM-8828)

  The facility can now decided, based on role, which employees have access to Patient Information. This is also set in the Security Policy. There are two choices, either Full or Restricted. It is important to know that if a facility sets a role to restricted access, users will not be able to do the following:

  • Cannot search for patients in the roster.
  • Cannot create conversations that have a patient linked.
  • Cannot see patient information, (Names, MRN's, etc.) in conversations that have a patient linked. This includes alarms.
  • Do not have access to the More Info screen in any type of conversation, regardless of whether a patient is linked or not.
  • Cannot launch AirStrip in Clinical Alarms.

  If the facility choses Full access then the user will be able to see anything that contains Patient Information. This feature requires Engage Mobile 5.3.

• New Ringtones

  • We are pleased to announce the addition of 6 new ringtones for messages.

  • These ringtones will play for a minimum of 5 seconds, but can be configured to play longer.

    This feature requires Engage Mobile 5.3.

The following issues are fixed in Engage XMPP Adapter 3.4 SR1:

• XMPP failed to update the APNS certificate when it expired. (PFM-10052)

  When the APNS certificate expires, a new one should be automatically installed by the adapter. This did not happen and caused connections to fail which in turn, did not allow APNS messages to be delivered.

The following issues are fixed in Engage XMPP Adapter 3.4:

• XMPP did not check the Time To Live for an alert based conversation before allowing a user to join the conversation (PFM-9095)

  Alarms were not expiring properly which allowed users to join conversations with stale alerts. This issue has been corrected and those are expiring as expected.

The following issues are fixed in Engage XMPP Adapter 3.2 (3.2.9):

• 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.