What's the expiration time before you get logged out because of inactivity?

[JohnCHill]

Now that I’m using my Autodesk ID to log into PLM 360, what is the session expiration time before you get logged out because of inactivity?

[JohnCHill · Accepted solution]

The session expiration time when using your Autodesk ID to log into PLM 360 is 12 hours.

[admin]

I have users who's sessions are expiring withing 2 hours and when they start typing they are not getting an alert that their session has timed out until they hit save. Which is very frustrating because they spend time filling out an entire form. Is there a way to get an alert?

[gasevsm]

It's not 12 hours for PLM 360.
12 hours is for AutodeskID session, whereas for PLM 360 session is 15 min.
After 15 min of inactivity, your session has expired. Any event that refreshes/updates/saves a page should effectively relogin the ppl user in automatically provided the AutodeskID session is still active. If there isn't an active AutodeskID seasion, then user will land on the login page and asked to manually login to provide user credentials anew.
However, this automatic silent relogin to PLM iff an active AutodeskID session is determined as present is not without consequences. Edit/create/clone forms that have been started before PLM session expired and user wishes to continue after it expired would be cleared on an event that happens after the 15 inactivity interval.
There is no alert for this in the product presently. One possible way around this I can guess of to test is open a new tab and trigger a page refresh there which would auto-relogin the user; come back to the current tab and see if that would allow you to continue and persist the save. If this doesn't work, I think it allows the user to at least preserve the in progress change and repeat then easier in the new session.
I am planning to address this in the long term via draft-style capability where user can continue where left off. I was exploring the draft to last a single session eg. Start a create item, then switch contexts to do something else and later come back to it, all in one loon session. However, this issue is spawning ideas to persist the draft across sessions. Also, we've already spec-ed the idea of prompt user with a countdown of when current session is about to expire and let force logout, renew timer or let it expire automatically. This is also an enhancement we've explored and planning to incorporate in future releases.
HTH,

[rania]

Hi there,

Our tenant too is suffering from this feature. Many people are complaining that they fill out a form, not knowing they are logged out and hit save and all their work is gone. We definitely could use an alert of some type or at least extend the time past 15 minutes.

[PLM-Sylvain.Bailly]

Hello @gasevsm ,

Do you have planned to fix it by implementing one of your suggestions?

---

@gasevsm wrote:
I am planning to address this in the long term via draft-style capability where user can continue where left off. I was exploring the draft to last a single session eg. Start a create item, then switch contexts to do something else and later come back to it, all in one loon session. However, this issue is spawning ideas to persist the draft across sessions. Also, we've already spec-ed the idea of prompt user with a countdown of when current session is about to expire and let force logout, renew timer or let it expire automatically. This is also an enhancement we've explored and planning to incorporate in future releases.
HTH,

---

Thanks,

Regards,

Sylvain