Hi

1. What do  you mean with time out? Is it when the user is logged out and need to login again or is it when it selects the data and times out? The latter is usually set to 60 seconds and you can’t change it yourself. The first depends a bit on what authenoication mechainsm you are using. I need to check it up a bit becuase I don’t remember when we introduced several different mechanism. 
2. I need to check this up. I don’t remember how this was done in IFS applications 9 
3. Client Error handling cannot be changed is a fixed value. It indicates how the error handling will be. The other value is Server Error handling and then you handle any errors in Failed Transaction.  For Time Tracker it is Client Error handling and you get a message about what the error is and can resolve it from client side. 

Thanks again Johan for your response.

By “time out” I meant below scenario which is common for our field technicians:

The technician logs into the app and does his clock-in.  

After 2 hours, the technician opens the app again to clock-out. During those 2 hours the technician does not use the app (inactive).

But now the technician must enter login info again to perform clock-out.

So we are wondering whether this “time out” of the app due to inactivity can be controlled. Please let me know what you find. 

Stay safe! 

(1) You are referring to TAS session timeout and default is 30 mins. But I don’t think this is configurable. But will verify.

(2) Allow multiple device is design time setting from the cloud resource and cannot be changed at the runtime.

(3) Johan already answered. 

Thanks

Kapila 

Thank you very much KATHLK. Please let me know what you find. 

Stay safe!