Infotip |
---|
This integration was added in v1.4, check out the full release notes for this version here: |
...
EMS Platform Services API version 44.1.19000.180 or higher. To check your version navigate to your Platform Services status URL e.g. http(s)://<servername>/EmsPlatform/status
An EMS Platform Services Integration Account, see the below Integration Account Configuration section for the account requirements
Access to the EMS Desktop Client and EMS SQL database
...
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
An integration account is required to enable authentication and two-way communication between ResourceXpress and EMS Platform Services. To create the integration account:
A client secret will now be generated and shown at the top of the page. Copy the newly created Client ID and Client Secret for later use.
|
...
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Once the Platform Services Integration Account has been created you can configure the integration details in ResourceXpress.
|
...
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Each resource profile in ResourceXpress is linked to a resource profile in EMS. Before configuring ResourceXpress you should have the EMS profiles already created. For each profile in EMS, you will need the individual ID number assigned during creation, to retrieve this ID number
|
...
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
When a booking is initiated using ResourceXpress via a Room Screen, Qubi, Kiosk or Map the booking is created based on specific parameters defined in EMS. To enable RX to use the correct options various SQL IDs need to be retrieved and defined in the application.
SQL IDs for the following options in EMS will be required to complete the configuration:
Example Running the below query in SQL Server Management Studio against the EMS database
yields the following results To enable ResourceXpress to create bookings using the Conference setup type the ID 1 would be defined in the application.
SQL IDs for the remaining 3 options can be obtained the same way by querying the relevant table in the EMS database |
...
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
ResourceXpress can utilise existing EMS user (group) accounts for device-level authentication via the Platform Services API. To enable this feature navigate to Administration Settings - System Settings - User Authentication in the ResourceXpress admin console and select one of the below two options for the Authentication Protocol
There are two values in the EMS group record used for User Authentication at the devices. By default, the field used for Access (PIN) Code is Personnel Number and the field used for RFID is Badge Number. Network ID and Other ID can be used instead if required, please contact helpdesk@qedas.com if you need to substitute the default values.
|
...
Expand | ||
---|---|---|
| ||
Check In
Prior to the booking starting the Check in button will flash and the LEDs will be amber, the amount of time the Check In button is visible can be configured under the Interactive Tab - Check In. For bookings with setup and teardown, the Check In option is synchronized with EMS. It is recommended the Check In settings are the same as those in EMS. The Check In button is displayed as per the settings even if it that time is setup time. The meeting will automatically start if not checked in with the option to Check In still available. If not checked in the meeting could automatically cancel if Auto Cancellation option is enabled in RX Admin Console. Once the booking has completed the Clear (tear) down time begins allowing time to vacate the room and return it to its usual condition. |
...
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|