We recently deployed a change to remove the Bed Number from a subset of alerts in Engage by removing any reference to a bed_number in the Subject, Message, and Additional Content section of our XMPP Rule settings. It was observed during testing that an additional setting "Place" was referencing an attribute called #{bed.uid}, which displayed a text value that was a combination of the Facility, Unit, Room, and Bed that the alert was triggered for. We attempted to manipulate the data being displayed in this section to remove the bed number from the end of the string by forcing it to instead display #{bed.room.facility.name} #{bed.room.unit.name} #{bed.room.room_number}, but when that was tested the Place setting was null on the end devices. We also attempted to update the Place setting to utilize the #{room.uid} attribute, which also resulted in that setting being null on end devices. Finally, we attempted to manually update the bed.uid attribute for the bed we were testing in the database to strip the "1" from the end of the string, then restarted XMPP to push that change to the xmpp_cache database. Test results for that final workaround were also unsuccessful.

As the "Place" setting is customizable in the Engage Rule configuration, we would like to submit an enhancement request to allow that setting to accept a value other than #{bed.uid}. For our use case, we wanted to remove the bed number from the end of the string, but other use cases can be presented as well to add/remove text from that setting as needed on a per customer basis.

Case 496792