Thread: Automatic Inbox Refresh in SC6.1 workaround!?

Automatic Inbox Refresh does not work in SC 6.x


Try this:

Add a timer to sc.manage.problem.g (Input=$xyz.refresh.time)
Add "$xyz.refresh.time=-120" to displayscreen "scm.advanced"

Attention:
This is not intensively tested - usage on own risk

Please give feedback, if it works on your site

Lars

P.S.
initial solution by Frank S.

Yeah, thanks, it works fine on my Service Center 6.2.

Not familiar with displayscreens what do I do with
"Add "$xyz.refresh.time=-120" to displayscreen "scm.advanced""

Yes I have got it working in our Dev system. I take it that no one has had problems since this was first posted?

Sorry folks, I tried this method and it was not good (old Peregrine ticket 707641). I used a timer object that uses "Refresh" for the Expiration event. Two problems occurred. I reproduced both in an out-of box 6.1.3 system for Peregrine. They are:

(1) When the inbox has many rows (e.g. more than 60 or so), eventually some of them go missing after a refresh. SCR 39486 was opened to address this. I have not heard back yet that it is fixed, so I believe it is not.

(2) A major problem when you leave the windows client (on XP) up for several consecutive hours showing a queue that is automatically refreshing. Eventually, all the windows on your PC get chaotic, and it takes a PC reboot to clear. This chaos is difficult to explain, unless you experience it firsthand; you cannot really see or get control of any window being displayed on your PC – even non ServiceCenter windows. I reproduced this one out-of-box for Peregrine, and the opened an SCR for this too. Sorry, I don’t have the SCR number handy. That and the other ticket details (exact steps to reproduce, exact symptoms, error codes, etc.) appear to be gone now that Peregrine closed the ticket part of their support.peregrine.com website.

(IT WOULD BE NICE IF HP MADE OLD TICKETS & SCR DETAILS AVAILABLE IN AN ARCHIVE.)

Thus, the only available workaround would be to manually click the “Refresh” button on a QBE list and/or make use of Favorites and Dashboards.

Having dashboards update automatically however, cannot replace the details of a QBE list (callback status, priority, category, short description, contact, time of opening, etc.) Having that list update automatically means a helpdesk operator can be confident to assess the relative parameters of those tickets without having to hit the refresh key every 3 minutes at the expense of attending to other critical systems.

Peregrine explained that table refresh was removed because of the change in technology with the Eclipse client. It would take a “major rewrite of the architecture” to get it working again.

So, we have reluctantly embraced dashboards and pressing refresh manually.