These release notes were last updated on 4/14/2019. For a more recent copy, please reach out to your Voalte representative.
Voalte One 3.7 offers exciting new features that further the electronic health record (EHR) integration experience. You can link patient listings to third-party applications so you can quickly get more patient information, view EHR roles within Voalte One, and create group messages with patient-centric titles. Voalte One 3.7 also introduces single sign-on (SSO) support for a smoother experience when starting your shift.
Most features require upgrading to Voalte Platform Server 3.7. Voalte One is available starting December 4, 2018. Please reach out to your Voalte representative for more information.
The minimum operating system for Voalte One 3.7 varies by device. Please refer to the Android Voalte One validations support article (/en/knowledge/article/portal/360025945051-Android-Voalte-One-validations) for specifics regarding each device.
Voalte One 3.7 introduces many other new features and fixes several known bugs, which are listed below.
Requires 3.7 Voalte Platform Server
Users with patient-viewing privileges can tap or click the patient information within a room and be redirected to a third-party patient-centric system, such as an electronic health record (EHR). For example, a user could tap a patient's name in Voalte One to be redirected to the patient's record in Epic Rover.
You can link up to five unique sources per patient listing in Voalte Platform. Links can be set up to use patient identifiers to connect Voalte Platform with native applications or websites. Websites will display in the in-app web browser on the mobile client if the client has been configured accordingly in Voalte Admin.
Requires 3.7 Voalte Platform Server
When a user with patient-viewing privileges creates a group message addressed to members of a care team, the subject of the group message is formatted to display the patient’s name, room and date.
If one of the recipients included in the group message is not a part of the care team or does not have patient-viewing privileges, the group message subject will not include the patient's name.
Requires 3.7 Voalte Platform Server
With 3.7, users can enable a new display and interaction method for Voalte Platform alerts. Instead of an Active Events screen, an incoming alert is displayed at the top of the screen, similar to an incoming text. In Voalte One, the user can perform an action, such as Accept or Escalate, entirely from this notification without launching a Voalte Platform application. This feature allows users to quickly acknowledge an alert with minimal distraction from what they are doing.
Note: If the alert has unique responses not preloaded by Voalte, users must launch the application to respond to the alert.
Requires 3.7 Voalte Platform Server
Android Voalte One users can now set the volume of notifications they hear while on a call. Users can also choose to set in-call notifications to vibrate along with the notification sound. This feature is set under Menu→Settings→Notifications & Sounds.
Requires 3.7 Voalte Platform Server
You can now choose to allow users to use dictation, also known as talk-to-text, to create a text message. When a user taps the dictation icon on the keypad for the first time, a HIPAA-compliance warning appears.
Requires 3.7 Voalte Platform Server
Hospitals that have integrated Voalte Platform with their EHR can choose to display EHR roles for Voalte Platform users in the care team when a patient is viewed in a Voalte Platform app. The EHR role listed will be in addition to the Voalte Platform roles the user selected during login. The EHR role is visible only from the patient screen and is not searchable.
Requires 3.7 Voalte Platform Server
The redirect message played when a call is placed to a Voalte Platform user who does not answer has been shortened. The message now says, "Please hold while I transfer you to the next available staff member."
Requires 3.7 Voalte Platform Server
Voalte Platform can override the Do Not Disturb (DND) settings on Android devices. This is configured within Voalte Admin and is a global setting for all Voalte One users.
Requires 3.7 Voalte Platform Server
When a user changes the font size for text messages, the setting will now be retained from session to session.
Requires 3.7 Voalte Platform Server
Voalte Platform now has the ability to push out a key value through the mobile device management (MDM) software that will populate the correct server settings for Voalte One. This feature gives you more control over which devices point to which server. This feature is optional; if it is not implemented, the existing auto-configuration method will still be used.
Requires 3.7 Voalte Platform Server
Voalte Platform supports single sign-on (SSO), which allows users to sign in to one application that also can log them into Voalte Platform. Multiple authentication services can be added to each user’s account. You can choose to require users to log in with SSO only.
Note: Voalte Platform will need to validate against each identity provider.
| Key | Release Note Summary |
|---|---|
| ADR-6475 | The application may crash if receiving a call while change your presence. |
| ADR-6460 | [Voalte Me or Voalte One (TC51)] Initiating a search while on the Favorites screen may crash the application. |
| ADR-6459 | The web viewer will be displayed over Active Events screen if receiving an alarm after PIN timer expires. |
| ADR-6452 | When using the OS back button to go back from the Add Units screen to the Buildings and Select Units screens, the number selected might not be accurate and the Units will appear to not be selected, but they actually are selected. |
| ADR-6449 | Patient and room information is not displayed under Shift info the first time a user accesses the other user's profile (and user being viewed is assigned to Patient, not to room) |
| ADR-6448 | The units and rooms counter during shift selection does not update properly in certain scenarios. |
| ADR-6443 | Application crashes upon first launch. |
| ADR-6400 | "This app version not supported ...." message will rarely display briefly upon log out of a user with a hospital based role. |
| ADR-6286 | The code indicating reconnection ("R") is not shown while in call rescue. |
| ADR-6276 | Device may display message regarding the app not being supported with the server when it is supported (race condition). |
| ADR-6214 | The application crashes when the user taps the Start Over button in Shift Overview (while having only one unit based exclusive role and no home unit). |
| ADR-6126 | App may crash after an IRIS failover. |
| ADR-6096 | When creating a group message a user assigned to a room will not be deselected via deselect all or by using the room's radio button if the room was not previously accessed. |
| ADR-6081 | The read receipt is sent for all unresponded alarms when the Active Events screen is dismissed by an interapp action from an MCR Alarm. |
| ADR-6075 | App may crash when user is forced logged off from Admin. |
| ADR-6072 | Two matching audit records for patient viewing are created if a user a room without a patient, hits the PIN timer, and then enters the PIN and views the patient in the room. |
| ADR-6066 | If a modal screen occurs while the 'Waiting for presence update...' pop-up is displayed, the app may crash. |
| ADR-6045 | Using the Contacts interapp URI before logging in will crash the app logging in and going through self assignment. |
| ADR-6041 | The Favorites list may not update properly immediately after removing users from the list. |
| ADR-6040 | Scrolling quickly through a list of over 300 recipients with pictures will crash the application. |
| ADR-6016 | Incorrect role results are returned when user searches for a role only he or she holds. |
| ADR-5996 | The overall assignments are not properly re-calculated after logging in following a change to the value of the overall assignment limit (user must have one hospital and one unit based role). |
| ADR-5981 | User with hospital based role is stuck on the Shift Overview page if canceling a bump of another user after tapping Start Over with shift assignments. |
| ADR-5961 | The call record for a blind transfer is not displayed in Call History but may be displayed after removing the call record for the original call. |
| ADR-5915 | Application may crash when returning to a unit with more than 500 users after looking at a user profile from search. |
| ADR-5885 | The application may crash when rapidly tapping on a user's name int the directory or call details multiple times. |
| ADR-5837 | The application will crash if My Profile is accessed from a Group Message profile or by tapping on his or her own name in the directory. |
| ADR-5822 | [MC40] Call rescue may play while the other user can hear the call if the user answered the call right before it redirects. |
| ADR-5820 | User may be unable to complete shift assignment is the app was left idle while editing shift. |
| ADR-5786 | Units that were previously selected in current shift assignment are not deselected when tapping "Deselect All" (in Buildings screen). |
| ADR-5780 | The application may crash and display calls records with no display name if app is left idle and then the user taps Load More. |
| ADR-5706 | Notifications are not muted if a conversation is muted, messages are cleared, but the conversation is still open. |
| ADR-5343 | Tapping on "Tap to use Voalte while on a Call" banner will display the call history or alarm history screen instead of the screen the user was on before the call. |
| ADR-5153 | While in Patients search mode, rapidly tapping the "Load More..." button several times will multiply the results just as many times. |
| ADR-5064 | The thick divider line from Home view is displayed in search results. |
| ADR-5010 | Application may crash in certain scenarios. |
| ADR-4835 | Users are marked for group message with a delay when user photos are loading. |
| ADR-4732 | An endless loading spinner is displayed when accessing My Rooms after the user accessed a patient from Search. |
| ADR-4596 | Home view does not update dynamically when getting bumped from assignments. |
| ADR-4482 | Quick Response is not displayed when opening the conversation for the first time. |
| ADR-3500 | App crashes while having low connectivity and scrolling rapidly through a large group message recipients list of users with images. |
| ADR-665 | Contact name is not displayed in the call history. |
| Key | Release Note Summary | Known Workarounds |
|---|---|---|
| ADR-6989 | [Banner alert notifications] User is not able to respond to an alert from the notification if it's received while the notification drawer is expanded. | Open the app to respond or close and reopen the notification drawer. |
| ADR-6893 | Reminder tone does not break through do not disturb. | None. Reminder tones do breakthrough for Missed calls on Voalte One. |
| ADR-6877 | "Something went wrong. Please try again" error is prompted when the User tries to mute a conversation with no text message sent or received yet. | Mute the conversation after one message has been sent, or received. |
| ADR-6838 | Chat text sometimes becomes extremely small and unreadable. | Force quit and relaunch application or go to Chat size settings and move the slider to the right. |
| ADR-6821 | Device plays a tone one more time than the value set for "reconnect_failure_tone_repeats" parameter. | None. |
| ADR-6812 | At every call history request, if having missed calls, the missed call notification that appears in the notification drawer is re-created (even if it was previously dismissed by the user). | None. |
| ADR-6791 | Using Recent Apps while in Forgot PIN / Set PIN / Change PIN screens places the application in the background, after successfully setting/changing the PIN. | Manually resume the application via Recent Apps or via app's icon. |
| ADR-6770 | Application crashes when accessing a notification while user is in Favorites and search is active. | Relaunch application. |
| ADR-6765 | Custom Lock Screen is not displayed and user might be asked to input PIN twice if locking device's screen while app is force closed (or app re-launches itself while device is locked). | Manually unlock the device's lock screen and input PIN twice if it's required. |
| ADR-6762 | If a patient is discharged when viewing by rooms, the patient name may still be showing with an empty care team. | Force close and relaunch the application or navigate away and back to the page. |
| ADR-6760 | The "Show" password button does not change to "Hide" when the password is being displayed. | None. The button still functions correctly. Tap "Show" again to hide the password. |
| ADR-6747 | When encountering a failure during logout (error 10502), app is taken to login screen then backgrounded. | If the screen flashes and the app automatically backgrounds, that indicates that you didn't get logged out successfully. Re-authenticate with your username and password, then try to logout again. |
| ADR-6746 | [SSO] The User will not be able to set a PIN (if first logging in) or change the PIN if a wrong account is selected after the PIN fields were filled. | Force quit and relaunch the app. |
| ADR-6743 | The PIN screen is requested the second time a notification is accessed while in Edit Shift. | Complete the Edit Shift before accessing notifications. |
| ADR-6733 | The application crashes when receiving a call (within 3 seconds) right after changing the PIN and the "Security PIN set successfully" is displayed. | Back out of the "Security PIN set successfully" screen right after completing it. |
| ADR-6708 | App crashes when tapping the Text button from another user's Profile, after sending them a new ad-hoc message | This does not occur if more than one message is sent to the user before accessing their profile, or if the profile is accessed from the directory instead of the conversation view. |
| ADR-6705 | App does not return an error message when receiving an Alarm with a Voice Interapp URI containing an incorrect username. | None. |
| ADR-6701 | Unable to add/remove users to/from Favorites, after previously trying to favorite a deactivated user | Force close and relaunch the application. |
| ADR-6700 | User might still see the In-Call screen (call not properly end) if the other party ended the call while in Call Rescue. | Manually end the call on User A's side. |
| ADR-6690 | [Banner alert style] Break out of multi select mode pop-up is displayed when receiving an alarm containing a voice inter-app URI with the force parameter. | None. |
| ADR-6689 | [Banner Alert Style] User is not prompted to break out of multi select mode when receiving an alert containing a voice inter-app URI link without the force parameter. | None. |
| ADR-6683 | Hold button stops working after a server restart that occurs during the call. | End the held call, and manually call back the previously held contact. |
| ADR-6682 | User is displayed as not callable, when swiping left on a role entry of a user logged into Voalte Messenger with Role Extension and Role DID | Continue with calling the user as normal; uncallable status is incorrectly displayed in this scenario. |
| ADR-6681 | The cursor is placed before the search string when performing a Search by tapping a Search Interapp URI | Manually place the cursor at the end of the search string. |
| ADR-6674 | "Refreshed SSO session with different account" pop-up is received the first time a wrong account is used when changing the PIN | The intended error message is that the incorrect SSO account was chosen while changing the PIN. Make sure to select the correct SSO account when changing the PIN code. |
| ADR-6673 | User is taken inside the app instead of Transfer Menu, after inputting the valid PIN during a call received, while on PIN screen. | Manually transfer the call once taken inside the application, after PIN unlock. |
| ADR-6662 | User may get stuck in shift overview if a "server busy" event occurs before reaching landing spot | Force-quit the app, and perform the login process again. |
| ADR-6658 | Overall limit banner displays 0, instead of the current number of assignments when limit is reached in Role Selection | Tap Continue to proceed to the next step, then go back to Role Selection. |
| ADR-6650 | The Department name is not displayed on the Floating Alert, if the calling/texting user does not have a Home Unit set. | Ensure all users set a home unit prior to placing a call/sending a text message. |
| ADR-6648 | The camera is not dismissed after the photo is selected, if the User had to respond to the camera permission dialog first | Cancel the camera via the X option. |
| ADR-6638 | After receiving a new message and selecting the notification while in Group Message mode, tapping 'Continue' on the Break Out of Multi Select Mode pop-up will not redirect the user to the appropriate conversation. | Manually navigate to the appropriate conversation. |
| ADR-6626 | The Transfer menu is not initially opened when tapping Transfer, after the person getting Attended Transfer ended the call. | Tap Transfer more than once to open the Transfer menu, in this scenario. |
| ADR-6624 | [Banner alert style] The alarm history does not scroll to the most recent alarm when tapping on an alarm notification after scrolling down on the alarm history tab. | Scroll to the top to see the most recent alarm. |
| ADR-6623 | Denying the Location Permission does not trigger a new location permission pop-up when the user enters the Call Metrics view. | Accept the Location Permission when the app is first installed. |
| ADR-6622 | The application plays the failure tone more than the value set in the reconnect_failure_tone_repeats parameter | Set the number of reconnect failure tones in Voalte Admin to be one less than the desired amount. |
| ADR-6611 | Favorite units appear as ghost records, and Server Operation Failure message is shown, after a unit is deleted via Voalte Admin | Force close and restart the app to clear the ghost entries. |
| ADR-6600 | Application crashes when tapping the Forgot PIN button, after successfully changing the PIN. | This issue only occurs when tapping Forgot PIN for the first time after successfully changing the PIN. Tapping Forgot PIN again after restarting the application will work as expect. |
| ADR-6599 | User remains stuck on the Login Screen, if the device loses connectivity between initiating Single Sign-On and reaching the Shift Assignment screen | Force close the application and re-launch it. |
| ADR-6597 | Group message compose pop-up triggered in locations with more than 500 users is not dismissed by various Inter-app actions which take the user to other views (and app may crash). | Dismiss pop-up. |
| ADR-6582 | The user will see "Server Operation Failure" when favoriting a user if he or she has previously tried to favorite a deactivated user. | User is still correctly favorited. Force close and relaunch the application to stop the pop up from displaying for future users that are favorited. |
| ADR-6579 | Call Records that were deleted while in Call History Modal View will appear again when Modal View is cancelled. | Force close and relaunch the application. |
| ADR-6575 | User is placed in Login Screen after Force Closing the app while in Shift Assignment. | Force close and relaunch application, or wait for the application to automatically relaunch. |
| ADR-6567 | Breaking out of Multi Select Mode pop-up overlaps the Group Messaging pop-up when tapping on the View Button on the Floating Alert triggered by a missed call/text. | Tap Cancel on the Floating Alert, then foreground the app via the home screen icon (the Group Messaging pop-up will be dismissed and only the breaking out of Multi Select Mode pop-up will be displayed). |
| ADR-6562 | A loading spinner is displayed indefinitely when accessing a building that does not have any units. | Ensure that every building has at least one unit. |
| ADR-6503 | Action sheet (from Patients inter-app or from Group Message bulk select) is still displayed after tapping on an inter-app link that redirects the user to a different screen. | Dismiss the action sheet by tapping Cancel or by swiping it down. |
| ADR-6501 | The list of third party actions is displayed twice when tapping rapidly on the patient information. | None. |
| ADR-6500 | The application crashes when receiving a call then a message, while having text and missed call floating alert, from the same user when the application is in background. | Avoid tapping the Cancel button on the floating alert. |
| ADR-6359 | Empty Call Records might be displayed when tapping multiple times on the Load More button from Call History. | Force close and relaunch the application. |
| ADR-6354 | The call record is displayed twice when calling a Voalte Me user a second time after a force close. | Force close and relaunch application. |
| ADR-6344 | Numbers (not equal to 7 or 10 digits in length) will not format properly in an alarm if the first three numbers are separated by a hyphen or space. | None. |
| ADR-6249 | [Banner alert style] Alarm ringtone keeps playing after the alarm notification was swiped up (hidden) or down (expanded). | None. |
| ADR-6143 | [Rare observance] The application may crash after a server restart. | Relaunch application. |
| ADR-6113 | The overall limit warning is still displayed (Units and Rooms are still counted) even though user deselected the unit-based roles and selected a hospital-based role. | Deselect the units and rooms prior to changing the role selected. |
| Key | Release Note Summary | Known Workarounds |
|---|---|---|
| ADR-7010 | ||
| ADR-6906 | The app crashes when unlocking the screen and receiving multiple messages after previously placing the app in background while having unread messages from the same user. | Read messages before placing the app in the background. |
| ADR-6886 | The call ends prematurely when completing an attended transfer while the other party has lost connectivity. | |
| ADR-6883 | Missed Call tone is played instead of Reminder tone when receiving Missed Call Reminders. | None. |
| ADR-6773 | [TC51] Flashing indicators for reminders are not working. | None. |
| ADR-6763 | The incorrect loading message is displayed if launching the app without internet connectivity, tapping the back button, and then opening the application again. | None. The app should connect normally once a connection is established. |
| ADR-6726 | The 30 recipient limit pop-up is displayed twice when bulk selecting more than 30 online & offline users | Please make sure to select fewer than 30 recipients. |
| ADR-6457 | Tapping the red dot to trigger the 'Clear' button (in Conversation History) does not work for all conversations. | Swipe across the entry or go into the conversation to clear it. |
| ADR-6450 | The location selection is displayed again if the user selects the option 'Don't bump. Continue as' and has at least two unit based roles. | Tap Continue to proceed with shift selection. |
| ADR-6175 | User cannot re-log into the application and a misleading error message is displayed when user is disconnected due to "Unexpected Error". | Force close and re-launch application. |
| ADR-6142 | A user may have to enter a PIN twice if logged in during an IRIS restart. | None. |
| ADR-6112 | User may rarely see "Already logged in" pop up after regaining VDS connectivity. | Dismiss pop up. |
| ADR-6087 | If a user taps Continue during shift selection when VDS connectivity is lost, the application may crash. | Relaunch application. |
| ADR-6085 | The user might remain stuck in shift overview if tapping the Done button after losing VDS connectivity. | Force close and re-launch the application. |
| ADR-6046 | [TC51] Application crashes when a user is logged out of Voalte while the application is in the background. | Relaunch application (application will also relaunch itself). |
| ADR-6042 | Unknown error is displayed when a user attempts to mute a conversation after that feature has been turned off. | This can only happen if the Mute Conversation feature has been turned off, and only on clients that have not yet received the updated setting through autoconfig. Once users force quit or log off and back on they will get the updated setting. |
| ADR-6036 | Default role appears incorrectly selected after the app is background when no role is selected. | Re-select the desired role. |
| ADR-6026 | Application crashes when logging in on another device while a floating alert is present. | Relaunch application or wait for application to launch itself. |
| ADR-6005 | Outgoing call might remain in ringing state (both parties can hear each other). | None. This is a rare observance. |
| ADR-5970 | The Delete button from Favorites does not work properly when perform a long press. | Tap the Delete button. |
| ADR-5966 | Active events is not displayed after ending a call made from a MCR alarm response. | Tap on Alarm history to view other active alarms. |
| ADR-5954 | User is stuck in shift selection if multiple users bump the user out of exclusive role prior to completing shift assignment. | Force close and re-launch application. |
| ADR-5939 | If 10 recipients are selected in Group Message mode and a model screen appears and then is dismissed, a pop up will appear multiple times saying "You have reached the max allowed number of 10 recipients". | None. |
| ADR-5933 | Tapping on a Search Interapp URI while having an open search displaying results from a single category will crash the application. | Re-launch application. |
| ADR-5920 | Conversation will auto-scroll down to the latest message in certain scenarios (after an earlier photo, dismissing active events, or looking at the user's profile). | Scroll back to desired position in the conversation. |
| ADR-5919 | Scroll position is not reset when searching for users in the To field of a new message. | Manually scroll to the correct place. |
| ADR-5911 | If a patient is transferred while actively searching for that patient, the patient may appear in the original location. | Force close and relaunch the application. |
| ADR-5910 | If a patient is accessed from search and then discharged while the result is still is shown and then selected, the application may crash or show corrupt data. | Force close and relaunch the application. |
| ADR-5888 | The application crashes when swiping to text yourself in a Team view. | Relaunch application. The user should not be able to swipe to text himself or herself. |
| ADR-5886 | Reminders will vibrate when on a call. | None. Reminders should be paused while on a call. |
| ADR-5858 | The application will crash if a user repeatedly taps Load More in Call History and then accidentally taps a call record that was where Load More previously was. | Relaunch application. |
| ADR-5821 | The application may crash if a user locked his or her device while looking at a room view and a patient is discharged while the device is locked. | None. Re-open the application. |
| ADR-5811 | Users deleted from Favorites are selected as group message recipients when perform a Select All without exiting the Favorites screen after the deletion. | Exit the Favorites screen and then access it again after deleting the user. |
| ADR-5758 | [Marshmallow] Device buttons like Home and Back are active in alarm and call screens | None. |
| ADR-5485 | In a multiple call scenario, the user cannot take the call off of hold until the participant who lost the connectivity regains it. | None. |
| ADR-5361 | Reminders and flashing indicators do not trigger when the user receives an event while in native lock screen. | None, Most users do not see native lock screen. |
| ADR-5328 | The flashing indicators are not triggered for events received when the application is placed in background with the phone screen unlocked. | None. |
| ADR-5264 | Group messaging mode is still active after successfully sending a group message if the user navigates away from the group conversation chat box using any notification, alarm, interapp or call transfer. | None. |
| ADR-5060 | If a username is changed while the user is logged in, the user will get kicked out of the application. | Log the user out before changing the username. |
| ADR-5055 | Reminders tone interrupts alarm tone if reminder plays while alarm tone is playing. | None. |
| ADR-5000 | Rooms and Patient assignments are not updated dynamically on User or Role profiles. | Close and reopen the profile. |
| ADR-4898 | "There are no users in this location" or "List is too long" screens are displayed immediately after search results if the list is not scrollable. | None. |
| ADR-4893 | Not all users are displayed when switching views or entering a location when attempting to transfer a call. | Scroll the view to show all users. |
| ADR-4885 | Tapping on the rightmost edge of the text priority button will send the message and not mark it as priority. | Tap on the middle of the text priority button. |
| ADR-4799 | Blind transfer displays incorrect caller ID if an attended transfer was completed prior to blind transfer for PSTN/PBX to Voalte calls. | None. |
| ADR-4701 | A unit or team is marked/unmarked as a favorite when swiping and tapping on the other side of the unit or team. | No workarounds available. |
| ADR-4679 | User may be able to favorite a department when accessed from search in certain scenarios. | None. The department does not actually add to their Favorites list. |
| ADR-4668 | When the Bluetooth accessory is connected and the device is set on silent, the ringtone for received calls and texts will not play on the Bluetooth accessory. | None. |
| ADR-4543 | "View by" selection is retained on the device after the user logged out. | Switch to whatever "View by" selection you want after logging in. |
| ADR-4513 | Active events screen is displayed again when opening the app via recent apps after dismissing or responding to the alarm. | Open the application via the app icon. |
| ADR-4501 | List may automatically scroll when switching the view option (names, roles, or rooms). | Manually scroll to the top or desired location. |
| ADR-4479 | Reminders and flashing indicators may be cancelled when reaching the PIN screen. | None. |
| ADR-4453 | Search may be canceled when tapping on a user while in the Favorite screen. | None. |
| ADR-4306 | The user might be displayed in the wrong unit when they log back in after logging out from a unit that is not their home unit. | Force close and restart. |
| ADR-4140 | The Load More button is displayed in role collapsed cell search results even if there are no more results to be loaded. | None. This only happens when you have selected more Teams in Self Assignment than the system is configured to return in directory searches. |
| ADR-4103 | Active events, lock screen and incoming call screen are displayed with a delay in the first seconds after placing the app in background. | None. |
| ADR-3971 | Might receive an Application Not Responding (ANR) when sending a Group Message to ~1300 users. | None. |
| ADR-3871 | During shift selection, manual deselection of all teams does not trigger default "No Teams" | None. |
| ADR-3813 | 'Receive timed out on local sequence number' is received multiple times after the app recovers from Wi-Fi drop. | None. The app reconnects and recovers without user action. |
| ADR-3532 | App crashes if sip 409 is received during call setup. | None. |
| ADR-3509 | Display name of users in a large Group Profile are not initially presented (until fully loaded) - May remain stuck in this state if you open an 'empty' profile after a force close. | This only happens when scrolling through large Group Profiles (~200+ members) very quickly. Scrolling at a moderate pace and allowing names to load will prevent this issue. |
| ADR-3497 | User having a hospital-based role is displayed, in the Admin assigned Home Unit, after he or she logs out. | None. This only happens about 50% of the time, and they are only shown in the Offline section. |
| ADR-3479 | If a message is received while in Chat History the drawer notification is not automatically dismissed and persists even after clearing all messages. | Move away from Chat History then access it again to clear the notifications. |
| ADR-3435 | User is displayed as not callable when swiping on him/her while viewing by roles or name inside a team. | The call still goes through; this is cosmetic only. |
| ADR-3283 | User may get stuck if the VDS connectivity is lost right when the uploading picture pop-up is displayed. | The application recovers after about 1 minute and reconnects. Force close and restart to recover if necessary to recover more quickly. |
| ADR-2778 | The incoming call screen remains displayed if an alarm is received and the Active Events screen is dismissed after the call ends. | Sliding to Answer or Decline will close the Incoming Call screen. |
| ADR-2557 | Exceeding 100 Active Alarms might cause the server to not send the first alarms that were received after a force close and restart. | This only happens if you force close the application after having 100 active alarms. Each new alarm received after that will replace the oldest alarm. |