SE50 Device Secured but not Associated with its Terminal

Problem:

During a mass deployment when more than one user is accessing and making changes to device information in the Pharos Administrator, some devices might appear to work for an immediate test but then later fail. It was observed that once the device began to fail, the device and terminal association had disappeared.

Cause:

If while in the Pharos Administrator you forget to make a setting change (e.g. Add Copy as a device function), and go back to the Admin and try to set that without having refreshed the device record since you secured it (e.g. Changed context, closed Admin), you will get a message that 'Someone else is making changes...' and your changes will be lost.

When dismissing this message the Admin should refresh the record and it should then show the associated station in the device record. If the station info does not get refreshed onto the screen for some reason, when you try to make the change again, the device info will be overwritten and the association between the station and the device will be lost.

The admin is supposed to refresh the data in that scenario, but it may only update the timestamp and not properly refresh the data.

Solution:

Avoid making changes to device records in the Pharos Administrator or ensure that the changes are completed prior to securing any device.