Session timeout changes in 2022.2?

No argument there Alisa.

24 hours

1 Like

No user likes to lose their work.

If anyone has any additional input or ideas for how Idle Timeouts should be handled more gracefully, checkout the Epicor Idea:

Graceful Session Idle Timeout | Epicor Kinetic Ideas (aha.io)

It has my vote. I’m not against session timeouts totally. From a security standpoint that makes sense, but from a user-experience side of things a ‘crashed’ session doesn’t make sense. This behavior flummoxes some people on our shop floor who are just using a station to clock in. If they see an error they will not mentally process it, they’ll simply walk away. Sometimes I’ll be told the tablets we punch in on are “broken” and I have to go out and “fix them” (swipe the tab and re-open it) and I have to add: as an IT guy, I don’t belong on the shop floor.

Our mes stations are “broken” often as well :joy:

Thanks for this post. Still not a knowledge based item or an update to the upgrade guide. Thanks for adding the Idea (I have added my vote).

If I changed this timeout value would a reset of the application pool put it into effect or do I need to redeploy my app server?

1 Like

I think just recycle the app pool.

You can try it with you dev environment, you should see that setting in your app.config file I believe.

So if you open your app config file right now you’ll see the current value of X. Then if you make the change you should open that file again and see Y.

recycling the app pool should do it for you.

Thanks Utah!

When I changed this parameter I got a dialog that I needed to restart the application pool so I guess that answered the question.

Additional note that this value was nowhere in the config files in C:\inetpub\wwwroot{appserver}\Server. By the way I only have host.config, appserver.config and web.config. I don’t not have an app.config file. None of these were modified by changing this parameter.

Kind of wonder if this value is now in the database?

1 Like

yes, Ice.GlobalSetting table

1 Like

Great well there is the answer, thanks @Olga !

Is there anything we need to do @Olga to ensure that the value is now used in future sessions? recycle app pool, etc.?

recycle should be fine

1 Like

Thanks Olga. I did notice the parameter missing but after changing it then it appeared in the table.

1 Like