Hello @Dinidu Udana Thank you very much for your kind thoughts shared. Sure i shall try the option of Re-opening the Project Activity and perform a Project connection refresh for all connected Objects. Sure and thanks for your kind advice and i shall make sure to provide screen images as suggested since it will be convenient for you all to investigate and provide better insight. Thank you. 😀
Hello @PRODQ Thanks for your kind feedback and actually the transactions have been through to the GL and reflecting the correct values. Also, sure i shall verify if there are any Corrected Hours which are not yet transferred, and any transactions not Approved/Updated.Apologies for the confusion, there are no credit bookings until 31-5-24 as well.
Hi @James Ashmore Thanks for the clarification on Force Initialization impact on MWO pending transactions. Great to hear that IFS cloud version is having the capability to force the Acceptance of Pool Work Orders only when the device is Online. Thanks again for your kind thoughts and advice.
Hello @James Ashmore thanks for your kind attention. Exactly and when investigate through device logs the same Work Assignment has been ‘Accepted’ by 02 persons, while they were in ‘Offline’ mode and one user has cancelled the Work Assignment and the cancellation has synced to IEE end but the intended User (above device owner) when reporting in the Assignment, it is not in the backend. And we have got a Failed Transaction for the above user saying that the ‘Work Assignment has been removed by another user’With this kind of situations would you kindly assist with clarifying below?1. Will Force initialization only make reset the MWO App and impact(lost) pending document upload transactions or Only Initialization will do the most impact for the data loss?2. In IFS MWO upgraded versions is there any way to prevent double acceptance of Pool Work Tasks?3.In IFS MWO upgraded versions, is there are option to facilitate Offline ‘Acceptance’ and carryout the Work, after downloading the Pool work
Hi, Yes growing out queue will impact the data synchronization. It’s not the only reason but there are many. But in your case it’s good to address that first. 700k out queue messages can indicate that you have lot of installed app devices which are still active but no longer downloads data because of device might be physically offline. Which means back end data sync process keep filling out queue continuously . So you need to clean-up them. In the latest version we have a new functionality call ‘Inactive App Device’ which has been implemented to prevented this by automatically clear such out messages and other related data if a device has offline for a longer period. But for UPD9 you might need to do this manually. One way is check the last active time of the device from the Install device App and identify the user/Devices which are offline for a longer period and clean their data manually. Hello @kathlk Would like to have another clarification from you on clearing out messages.
Hi @ISD, You can try below to improve the performance: Data Volume: Identify how many records are synchronized to a user/device per entity. Use Synchronized Entities screen or DB query to identify. Apply Entity filters to the data to decrease the number of records that is synchronized down to each user and device. Sync Time Use Synchronized Volume screen or DB query to identify. Apply Entity filters to the data to decrease the number of records that is synchronized down to each user and device. This will decrease synchronization time. Check the performance of the “where” statement if custom field exists Bad “Where” statement on an entity needs to be reported to IFS for investigation where it’s necessary. Security - Security Groups If the customer do not use certain functionality, you should turn off that functionality. It is important to remove functionality that is not used as this will assist the overall system performance, App initialization, push and batch synchronization
Hi, Yes growing out queue will impact the data synchronization. It’s not the only reason but there are many. But in your case it’s good to address that first. 700k out queue messages can indicate that you have lot of installed app devices which are still active but no longer downloads data because of device might be physically offline. Which means back end data sync process keep filling out queue continuously . So you need to clean-up them. In the latest version we have a new functionality call ‘Inactive App Device’ which has been implemented to prevented this by automatically clear such out messages and other related data if a device has offline for a longer period. But for UPD9 you might need to do this manually. One way is check the last active time of the device from the Install device App and identify the user/Devices which are offline for a longer period and clean their data manually. Hello @kathlk Thanks for your kind inputs and suggestions. As you mentioned, sure we shal
Hi @James Ashmore Thanks for your kind thoughts and guidance. Sure, we shall investigate about the Inactive Users/Devices who are no longer in use. And thanks for the recommendations on entities and consider application of Permission Set filters. One more clarification, would you kindly advise if IFS support team will be able to provide performance and system improvements as a patch to apply in UPD 9 version until we move for an upgrade or updated version? Many thanks.
Hello @Rukmal Fernando very well noted and thanks for your kind thoughts and guidance. Thanks for the extra information on the edit/revise option behavior in MWO App. Sure will create a Support ticket on the same and request for further investigations. Thank you. 🙂
Hi @Rukmal Fernando thanks for your kind inquiry. I was referring to a community post quite a time ago and it's not currently available with me to quote. Nevertheless, do you think it's not a bug or anything could manage from IEE side? or something related to Permission?Furthermore, below is the error we see in MWO App side. Thanks for your kind thought and advice.
Hi @lopespetro & @ISD The fragment of the patch mentioned above resolved the ORA-00001error, but the synchronization time remained long. I’ll have to look into again as we have now few users facing this issue. Best regards, Hubert Hi @HubertZ Thanks for your kind feedback. Would be great if you could kindly share any findings and recommendations on further investigations. Good luck. Thanks. 🙂
Hi @Rukmal Fernando well noted and many thanks for your kind comprehensive explanation. Sure, I shall keep our IT team informed about this solution for future use. Thanks. 🙂
Hello @James Ashmore well noted and many thanks for your kind advice. 🙂
Hi @Rukmal Fernando Thanks for your kind advice. Sure, will attempt of having one device updated and see the progress. 😊Furthermore if possible, would you be kindly able to provide a brief idea about the MDM solution and how we could use in this scenario? 🙂 Many thanks.
Hi @Rukmal Fernando Thanks for your kind attention and advice. As you have suggested sure i shall try updating a one device and see how it goes since, we are aiming 07 updates at once. Apologies for the confusion and actually i meant having the App on minimize stage in the device, is possible when we are updating the App or all Users have to logout from the devices prior to update to the latest version.?As an extra question, we are having around 50 Mobile Users and all the MWO Apps need to be updated. Would you kindly advise if this has to be handled by each User by visiting to AppsStore and get the updates or do we have a way if we could handle it from the Backoffice to get all those devices updated? Thanks again for your kind thoughts and advice. 🙂
For DocMan there is nothing that I am aware of but I will check with the team. There are compression settings for MediaLibrary however. Cheers James Hi @James Ashmore I just noticed below values under Touch Apps > Configuration > Application Parameters. Would you kindly advise the values we have at the moment is relevant for what we are discussing above when uploading images (as document) from MWO App and or could be further increased? Thanks for your kind thoughts. 🙂
Hi @James Ashmore many thanks for your kind feedback. Well noted about the MediaLibrary compression setting. At the moment we are only using DocMan solution as we are using the images for Custom reports. Would be really glad if you could share if you hear anything from the team on capacity limits when using DocMan. Thank you so much for your help as always. 😊
Hi@d Go to Lobby View-> Mobile App Status-> App Name= mWorkOrder Hi @Dharshika Amaradasa Would you kindly advise, in order to activate the above lobby page, what are the changes we need to make from backend. Currently we are using MWO ServiceEng App and we would like to use the above lobby for the Application usage and analysis. Any scheduled data base task we need to implement, History log configuration etc. Many thanks for your kind thoughts. Best regards-ISD-
No technical limit to control the amount of pictures/videos that can be added to a single task Cheers James Hi @James Ashmore thanks for the information. Would you kindly help and advice if there is any image capacity (file size) limitation, when uploading images to Task/Step level from the MWO App end? We have enabled only Document Attachment option to add Pictures (DOC CLASS as PICTURES) Since we are facing some corrupted files or missing Attachments (Pictures) when we uploaded from MWO App and also experiencing a longer uploading time. Many thanks for your kind thoughts. Best regards Hi @James Ashmore would you kindly advise if there is any capacity limit when uploading images/Docs from MWO App, as we normally encounter long waiting time(01hr+) to upload approximately 30 images with a good data connection. Each image capacity is between 2.5- 3.8MB. Is there any way to increase the capacity and expedite the process or are we still using an incorrect process.? Many th
Hi This is normally the case when you have large no of Grouped Push data rows for MWO app. Can you check the data volume for your user device in the IEE screen in the back end? Or you can do a Dummy device init for your installed device app and check to out messages. If this si the case, then you can reduce grouped data by adding permission set filters. HI @kathlk Would you kindly advise the way i could check the data volume transferring to a specific mobile device from IEE back end? Furthermore, when attaching pictures as Documents from MWO end we are experiencing longer wait times. Would you kindly advise if this due to MWO image uploading capacity limitation or IEE Back-end restriction? (even with good data/Wifi connection) image sizes do not exceed 4MB) Many thanks for your kind advice and help. 🙂
There is also a Lobby page that can be configured to show you the performance of the sync process and which entities may be taking the time to complete the Init Cheers James Hi @James Ashmore would you kindly advise, which scheduled data base task should be active in order to have the above Lobby page updated? Many thanks for your kind help. 🙂
Hello @James Ashmore Thanks for your kind advice and the information. Sure, i shall add filters to above Entities as well and proceed with the testing. Thanks. :)
Hi, Indeed, there is a problem with Grouped Push. I’ve found almost 200 000 rows in mobile_transaction_offline_tab and seems like there is a problem with processing them due to ORA-00001 error in MOBILE_TRANSACTION_PUBLISH_SYS The procedure has been recently changed in standard, so we are going to apply the change (only in the procedure below as the change was marked as grouped patch to apply with a whole UPD) PROCEDURE Insert_Offline_Rows___ ( entity_ IN Transaction_Entity_Row, transaction_filter_id_ IN VARCHAR2, objkeys_ IN Objkey_Table, context_ IN Transaction_Context) IS tab_ Mobile_Objkeys_Type; -- Local PLSQL collections cannot bind into insert, update, delete, or merge insert_count_ NUMBER; BEGIN IF objkeys_.COUNT > 0 THEN SELECT column_value BULK COLLECT INTO tab_ FROM TABLE(objkeys_); --Only insert missing OBJKEYs to the table INSERT INTO mobile_transaction_offline_t
No technical limit to control the amount of pictures/videos that can be added to a single task Cheers James Hi @James Ashmore thanks for the information. Would you kindly help and advice if there is any image capacity (file size) limitation, when uploading images to Task/Step level from the MWO App end? We have enabled only Document Attachment option to add Pictures (DOC CLASS as PICTURES)Since we are facing some corrupted files or missing Attachments (Pictures) when we uploaded from MWO App and also experiencing a longer uploading time. Many thanks for your kind thoughts. Best regards
Hello @James Ashmore thanks to your kind guidance and advice. Based on the description in the Synchronization Rules > Permission Set Filters, decided to assign different Work types set for the same WO Site. And i followed below steps to add a Filter based on the Work Type. (we are using IFS Application 10 UPD 9)Work Type - 10Work Type - 10TBasic data set for differentiate WOs to appear on MWO App, by applying Permission Set filters.Filter adding process as below.1. Entity selecting process. Would you kindly advise if i should select Work Type or Active Separate Entity as i need to filter WOs based on the Work Type. From the ‘Column Picker’ i drag and drop the Work_Type_ID column and add the ‘SQL Where Expression’. And update the SQL Where Expression as below and save the New Permission Set Filter. &0.WORK_TYPE_ID like '%-T'Then add the Filter for ServiceEngApp node as below.Then i click on the ‘Refresh Security Cache’ and created two(02) WOs using above Work Types (10 & 1
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.
