You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A layout using the Calendar Widget configured to trigger for No Event and Current Event are not functioning as intended. The layout is configured to manage a meeting room occupancy. Note that, the Trigger a web hook option from Displays execute successfully when sent manually from the CMS,
Steps to Reproduce:
Create a layout and add the Calendar Widget.
Select the Static Template, i.e., Daily Calendar
Set the No Event and Current Event triggers (e.g., RED and GREEN) to show a message
Schedule the layout event and observe the layout on player.
Expected Behaviour:
The text should change to RED when there is a current event (indicating the room is in use).
The text should change to GREEN when there are no events (indicating the room is vacant).
Actual Behaviour:
The triggers do not activate the changes on the player.
Manual execution of the trigger codes from the CMS does result in the correct change in message
Additional Notes:
On the Tizen player, the message is visible when the layout initially starts; however, the layout does not restart when its duration is finished.
An internal layout with ID 2395 can be used to test the issue.
The text was updated successfully, but these errors were encountered:
* Widget: calendar not sending trigger events
fixes to xibosignage/xibo#3509
* Widget: calendar number of items to be handled by onDataLoad.
fixes to xibosignage/xibo#3515
CMS Tested: 4.1.0
Player Tested: XfA, XfT
A layout using the Calendar Widget configured to trigger for
No Event
andCurrent Event
are not functioning as intended. The layout is configured to manage a meeting room occupancy. Note that, theTrigger a web hook
option from Displays execute successfully when sent manually from the CMS,Steps to Reproduce:
Expected Behaviour:
Actual Behaviour:
Additional Notes:
The text was updated successfully, but these errors were encountered: