@Sajith D : Do you see any issues with using PRAGMA AUTONOMOUS_TRANSACTION on a method that gets executed on an event in a table like Customer_Order_tab? Thanks for your help.
Thank you very much Johan for your reply. It looks like this is an issue which other users had also encountered. Please let me know if you hear anything back.
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!
Thank you very much KATHLK. Please let me know what you find. Stay safe!
Thank you very much, IbrahimN for your answer. I will try this out. Stay safe!
Thank you once again Johan. I was able to identify all the cleanup jobs. And thank you for suggesting the workaround for out messages. Stay safe!
Thanks again Johan. I did open a case G2255153 on 4/14. Still waiting for an update. I will follow-up with IFS support. Thank you very much for answering almost all my questions. We finished rolling out IFS Time Tracker 9 iOS version to all our field technicians. We are getting ready for IFS 10 upgrade project at the moment. Moving technicians from Time Tracker 9 to 10 will be the next challenge. Hopefully it will be seamless transition.
Thanks Johan. Just now I tried Internet Explorer and I got same results.
Thank you Johan and Nick. We identified a BUG in the IFS Time Tracker 9 in 2021 February. If I am not mistaken, IFS Support released Time Tracker 9 version: 2.1.9.64 which fixed the BUG which we reported. Also gave us below instructions. (ref case id: G2227021) =======================================================================Cloud resource for IFS Time Tracker 9 version 2.1.9.64 has been released and deployed in the IFS Cloud. Now you can use the existing version and please do the below configuration in TAS.1. Go to TAS environment2. Select configure in system ID3. Deploy META data related to Time Tracker 2.1.94. Validate META data5. Finally, tick the Time Tracker 2.1.9
FWIW, if you are cloud hosting your touchapps then it should indeed be the right version. We host ours on-prem so there is always a risk of using the wrong version, hence my initial thought. Appreciate your help, Nick.
Hi In the Technical documentation under IFS Administration & Confiuration Guide / Touch Apps / Configuration / Background Processing. you will find the different jobs that are run at a certain schedule, like Clean Up Touch Apps Logs,. Please have a look there and then see in your application if you have those running or not. The out messages is a bit special. The purpose with that is that when a message has been retrieved by the device it should be deleted from out messages. The reason that you still have out messages left is that you have several devices that are inactive. What you can do to decrease the number of out messages is to deactivate the device and then it should be removed from this table. You could also delete disabled devices. You can read more about it in the technical documentation under IFS Administration & Configuration Guide / Touch Apps / Installed Apps Devices Regards Johan Johan: What should we do about out messages such as this one? As you can see
I will check internally with some of my colleagues to see if they know right away what it can be. Johan: Thanks again for your help. Just FYI, I entered the case G2256973 since you categorized this as a possible error.
Hi, This is expected because there are no configurations for Time Tracker in that version, that is why the page is blank. You only need to deploy and validate metadata. Regards, Tinashe Thank you for the reply Tinashe. I am also waiting for a reply from IFS support regarding this.
Hi, my customer is facing the same challenges with Android 10 devices and Time Tracker 9. I’d be grateful if you update this thread with any information about the release of a Time Tracker 9 version that supports Android 10. Thx Klas Sure Klas. I will update the thread as soon as I hear anything back.
@Thanushi Jayaweera : Thank you very much for your reply. The field technician who was having this error is currently on vacation. I will check with him once he is back from vacation.
@Thanushi Jayaweera Your fix worked. Thanks for your help!
Thank you @Minoshini Fonseka for your reply. I was not using any formatting. I copied my element from an already existing element called “Project Team Member My Activities”. I tried removing the icon columns and the error went away. So I guess icon columns is what was causing the issue? Do you know how these icon columns work? It’s not a problem even if you don’t.
@anmise Thank you very much for that explanation. After doing what you’ve mentioned above, the error went away. And now I know how to use icons. Brilliant!
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
