My question is about thin client. I've got feadback from my clients. They suggest that the session should be longer. The thin client 1C application is opened in background and the user does something else and for some time comes back to the 1C application. There he sees the message like this: "sesion expired" and has to rastart app and log on again. It's about after 30 min inactivity.
Rating:
27
Joined: Apr 5, 2012
Company: 1TÇ Şirketi - Merv Bilgi İşlem Otomasyonu Yazılım Ltd. Şti.
kris try to upd ate 1C:Enterprise platform to 8.3.5 version. Because there in platform is there standart mechanism that follow up this skill.
Quote
The Hibernated session state is implemented, which is intended for preserving sessions after unexpected connection losses. Sessions that require licenses release the occupied licenses once they are hibernated. If a connection is assigned to a hibernated session, the session loses its Hibernated state. During the recovery from hibernation, sessions that require licenses attempt to obtain licenses. If a license cannot be obtained, the session is terminated. The option to set a timeout for automatic shutdown of hibernated sessions is implemented. If a connection to the client is closed by the 1C:Enterprise server, the session is hibernated(instead of being terminated). For the ISessionInfo object, the following properties are implemented: Hibernate, PassiveSessionHibernateTime, and HibernateSessionTerminateTime. New global context methods are implemented: SetPassiveSessionHibernateTime(), GetPassiveSessionHibernateTime(), SetHibernateSessionTerminateTime(), and GetHibernateSessionTerminateTime(). The hibernation timeout and the timeout for closing hibernated sessions can be se t in Designer, in the infobase parameters dialog box.
