Here is my workaround, it’s actually very smooth from the user’s perspective.
My Alarm Journal Component’s startDate and endDate properties are bound to the startDate and endDate properties of a Date Range component. To get a refresh to happen, I put a Button component on the screen which adjusts the Date Range’s startDate and then immediately changes it back. I named this my “Refresh Button.” Here is the code from my refresh button’s actionPerformed event handler.
[code]startDate = event.source.parent.getComponent(‘Date Range’).startDate
#Subtract one minute from the start time on the range so the Alarm Journal Table component refreshes its dataset.
startDate = system.date.addMinutes(startDate, -1)
event.source.parent.getComponent(‘Date Range’).startDate = startDate
#Add the minute back so our range is still the same.
startDate = system.date.addMinutes(startDate, 1)
event.source.parent.getComponent(‘Date Range’).startDate = startDate[/code]
Then, to get it to work automatically, I added a Timer component with the following code in its actionPerformed event handler.
event.source.parent.getComponent('Refresh Button').doClick()After that, it’s just a matter of modifying the Timer’s delay so that the Journal refreshes at the rate you want. You can even make the refresh button invisible if you don’t want users to know it’s happening. Or leave it visible and they will have the ability to refresh at their own pace in addition to the timed refresh rate.
Now that I think about it, you could probably have the refresh button directly modify the Alarm Journal Table’s startDate instead of doing it indirectly like I did. Probably would have the same effect.