x Want to participate? Join the group to interact
New

Automatically clear disconnected logins

One of the cases we get most often, which I imagine is the same for almost every BP, are disconnected logins stopping a client from doing something. I believe having something built into the software that automatically detects a lock and shows this in the Disconnected Logins screen is great, but having to manually intervene with this seems a bit redundant. If the system is aware the user is disconnected, why not clear the record rather than keeping it in a table and requiring user input?

John Dunn
Parents

  • I observe that many disconnected logins are associated with network failures to maintain contact, and/or users switching off their PC without properly logging out of Sage.  The record lock/s that are left behind are frequently an indication of what the user was trying to do at the time of disconnection - and partially-updated records can cause considerable problems.  Whilst I recognise that if the user wasn't doing anything (e.g. just had a menu open) then no locks are relevant - but if the user was part-way through entering a new sales or purchase order then you are likely to end up with corrupt sales orders (starting with ###) and stock allocated to that corruption.  Sage removed the ability to see what the user was doing at the time of disconnection - and so we lost the ability to forecast data corruption.

    I have to vote against your idea.

Comment

  • I observe that many disconnected logins are associated with network failures to maintain contact, and/or users switching off their PC without properly logging out of Sage.  The record lock/s that are left behind are frequently an indication of what the user was trying to do at the time of disconnection - and partially-updated records can cause considerable problems.  Whilst I recognise that if the user wasn't doing anything (e.g. just had a menu open) then no locks are relevant - but if the user was part-way through entering a new sales or purchase order then you are likely to end up with corrupt sales orders (starting with ###) and stock allocated to that corruption.  Sage removed the ability to see what the user was doing at the time of disconnection - and so we lost the ability to forecast data corruption.

    I have to vote against your idea.

Children
No Data

*Community Hub is the new name for Sage City