Connect PropertyPlex to Infor HMS using the Liaison Databridge interface — event-driven room sync for cloud-hosted HMS.
https://hmsweb.hms.inforcloudsuite.com)HOTELNAME_PRD)You need to create a new Databridge partner that PropertyPlex will use to receive events from HMS.
PROPERTYPLEXPropertyPlex IntegrationSTONE) — double-click the field to select from the listbasicPROPERTYPLEXNow you need to tell HMS which events to send to PropertyPlex. You'll add three subscriptions for room status changes, room moves, and PMS events (check-in/check-out).
ROOMSTATUSRoomStatushttps://prprtyplex.com/api/webhooks/infor (or your PropertyPlex server URL)DefaultMessageHandler/R01/R01/LiaisonStandardROOMMOVERoomMovehttps://prprtyplex.com/api/webhooks/inforDefaultMessageHandler/R01/R01/LiaisonStandardPMSEVENTLiaison_Eventhttps://prprtyplex.com/api/webhooks/inforDefaultMessageHandler/R01/R01/LiaisonEventRESERVATIONEVENTLiaison_Eventhttps://prprtyplex.com/api/webhooks/inforDefaultMessageHandler/R01/R01/LiaisonStandardWORKORDERLiaison_Eventhttps://prprtyplex.com/api/webhooks/inforDefaultMessageHandler/R01/R01/LiaisonStandardDefaultMessageHandler/R01/R01/LiaisonStandard, HMS will fail to deliver events with a ClassNotFoundException error. You can verify delivery in HMS Web under the event log — check for "Event Distribution" entries for the PROPERTYPLEX partner.
https://hmsweb.hms.inforcloudsuite.com)HOTELNAME_PRD — visible in the HMS login URL)PROPERTYPLEX (the partner you created in Step 1)STONE)Since cloud-hosted HMS uses event-driven sync (not polling), rooms are created automatically when HMS sends status events. To populate all your rooms for the first time:
All statuses are inbound only (HMS → PropertyPlex). Status changes cannot be pushed back to Infor HMS.
| HMS Code | Shows in PropertyPlex As | Confirmed | |
|---|---|---|---|
| CLEAN / CL | → | Ready | ✓ Tested |
| DIRTY / DI | → | Dirty | ✓ Tested |
| INSPCT | → | Inspection | ✓ Tested |
| TRNDWN | → | Turndown | ✓ Tested |
| PICKUP | → | Pickup | ✓ Tested |
| OCCP / occupiedFlag | → | Occupied | ✓ Tested |
| OOS / OO | → | Out of Order | ✓ Tested |
Housekeeping status changes in HMS automatically update PropertyPlex in real time via ROOMSTATUS events.
When a guest is moved to a different room in HMS, the old room is set to Turning and the new room to Occupied.
Guest check-ins set rooms to Occupied with guest name. Check-outs set rooms to Turning and clear guest info.
Rooms are automatically created in PropertyPlex the first time HMS sends an event, with room type, bed type, and building info.
Work orders created in HMS are automatically imported into PropertyPlex with title, room assignment, priority, and due dates.
Room inventory changes (out of order, out of inventory) are synced via PMSEVENT with room counts per type and property-wide totals.
Since this connector is inbound-only, room status changes must originate from HMS to appear in PropertyPlex. There are two ways housekeepers can update room status:
Many hotels have a PBX integration where housekeepers dial a code from the room phone (e.g., *6) to mark the room clean. This triggers a status change in HMS, which pushes a webhook to PropertyPlex. The flow is:
Housekeeper dials code → PBX notifies HMS → HMS pushes webhook → PropertyPlex updates
The housekeeper only does it once — PropertyPlex picks it up automatically.
A supervisor or head of housekeeping updates the room status directly in Infor HMS Web. The change pushes to PropertyPlex automatically via webhook.
Based on Infor HMS status codes, the expected housekeeping flow is:
DIRTY → INSPCT → CLEAN
This assumes INSPCT means "awaiting inspection." This will be verified with live testing when the property reopens. If the flow is different, the status mapping can be adjusted without code changes.
webhook_room_status entryThe Special Handling field is missing or incorrect on the subscription. Set it to DefaultMessageHandler/R01/R01/LiaisonStandard for all three subscriptions (ROOMSTATUS, ROOMMOVE, PMSEVENT). This tells HMS which message builder class to use for formatting the event.
HMS expects a SOAP-formatted acknowledgment response. If your PropertyPlex server returns a non-SOAP response, HMS won't mark the delivery as complete and will keep retrying. Make sure your PropertyPlex server is up to date.
Check that the Default Property is set on the PROPERTYPLEX partner record (Record View tab). Without a property assignment, HMS won't route events to the partner's subscriptions.
Check the PropertyPlex connector sync log for details. The event XML format may not be recognized. Make sure the connector is active and the PropertyPlex property is correctly linked to the connector.
This is normal for cloud-hosted HMS. Cloud HMS does not expose query APIs (SOAP, Databridge) to external systems. The connector runs in webhook-only mode where HMS pushes events to PropertyPlex rather than PropertyPlex pulling data from HMS.
Rooms are only created when HMS sends an event for them. To populate all rooms, you need to trigger a status change for each room in HMS (e.g., mark dirty then clean). HMS delivers events at approximately one per minute.
Infor HMS uses the Liaison Databridge messaging system. When a room status changes, HMS creates a Databridge Event, then distributes it to all subscribed partners. HMS posts SOAP 1.2 XML with WS-Security authentication headers to the subscription address.
The XML payload uses the http://schema.softbrands.com/Liaison/event/1 namespace with a Liaison_RoomStatus root element containing room details (ID, type, status, bed configuration, building, attributes).
PropertyPlex's webhook endpoint at /api/webhooks/infor receives these SOAP messages, parses the room data, and creates or updates rooms in the database. It responds with a SOAP acknowledgment so HMS marks the delivery as complete.
ROOMSTATUS — Fired when a room's housekeeping status changes (CLEAN, DIRTY, INSPCT, TRNDWN, PICKUP, OOS). Includes full room details, bed configuration, and building. Document Type: RoomStatus.
ROOMMOVE — Fired when a guest is moved from one room to another. Includes source and destination room numbers. Document Type: RoomMove.
PMSEVENT — Fired for inventory changes (rooms out of order/inventory counts). Includes room type, date ranges, and availability counts. Document Type: Liaison_Event.
RESERVATIONEVENT — Fired when reservations are created, modified, or cancelled. Includes guest information and dates. Document Type: Liaison_Event.
WORKORDER — Fired when a maintenance work order is created or updated in HMS. Includes title, room, reason code, department, dates, and priority. Auto-creates work orders in PropertyPlex. Document Type: Liaison_Event. Uses ProcessMaintenanceOrder BOD format.