We’re trying to understand how the licensing model works for hosted Epicor ERP customers – specifically the consumption of user licenses for those folks who use the client application vs. those who use the Kinetic web-browser interface.
As I understand it, licenses for users running the client application get consumed from the pool of available licenses for the duration the client application is open and running.
But, since the nature of web-browser communication is disconnected/state-less, can we assume that licenses are only consumed from the allocated pool when the browser makes a call to the server vs. for the whole duration the browser tab is open?
We have some users who just pop-in and out and the client is too cumbersome for that, so we setup browser access for them. Yet, I don’t want them to eat up a license just because they left a tab open.
… does this mean that user’s who leave their client applications open also timeout and release their license? I’m not sure I’m seeing that … seems like open clients stay consumed for the duration; but not 100% sure on that. I can understand the web-interface releasing it after a timeout, sure. Just confirming before I action this.
Another annoyance to me is that closing the browser does not log you out.
I mean, sure we could argue the pros and cons, and I don’t know that I care either way.
But my point is, my users assume that closing the browser is the same as logging out. And Classic was like that, where closing the client freed up the license. So that is different now.
It is true for me on 2022.2.10… closing classic client makes the session drop off from Admin Console. Sessions drop off that list upon client closing or user timeout expiration (we set all users at 15 minutes).
Note: Now that we have many different types of employees using browser-based Kinetic. We are seeing odd time outs. I have not confirmed this, but I’m suspecting that if a person has multiple browser tabs open and one of these tabs is “static,” that orphaned window will time out and boot people out of their “active” tab. But, I’m not sure yet… regardless, some timeouts are happening while people are actively inside of an Epicor browser window.
Something to be aware of, when a Manager or Supervisor jumps on a MES and quickly goes into Incognito mode and opens a new client to do something temporary as him/she. Might need some extra buffer licenses, or will it auto-consume his already active session that he has on his PC in his office.
We are seeing this as well since the update to .10 the other weekend but our users only have one tab open — in a way it is relieving to know we’re not the only ones experiencing this.
Reviewing the network traffic I’m not seeing any ‘keep alive’ events firing when doing transactions on our data collection licenses, so they keep getting logged out due to inactivity.
