Hi @ganners, to sync a sql view via real time you need to use it together with an actual table so that the sync rule can get triggered when a change happens. So, in your case you might have to use the stock_bin_table sync rule (probably have to create it new) as your triggering point is ‘moving stock’ and refer/select your custom view data within the related query. But word of caution, due to the baseline way stock transactions developed in mobile, it uses a sql view ‘stock_bin’ with batch delta rather than the ‘stock_bin_table’, it will be bit tricky and can cause your mobile db size to increase. Couple of other avenues you can try,Change the business scenario and use a batch delta sync rule with 1-hour interval Using a XML BR when the stock moved via ‘perform_replication_for_tables’ (note: this will have performance impacts because it will keep running for every stock transaction) Using extension feature in sync rule screen (this might not be feasible in your use case as there isn’t
Hi @TatKkkkkR,There can be many reasons for the above behavior and the most probable culprit would be data related issue along with the configurations in mobile design.What I would suggest you to do is Try to replicate the issue/same scenario on a baseline mobile design where there aren’t any custom configs. If it is still occurring, I believe the way to go via through a support request as it can be a product defect. If the issue is not recreating on a baseline design, then extract the mobile device log when the app crashes and try to go through the critical errors present there (start from the bottom of the log towards up) and see any errors related to the client scripts used in Click events or Refresh events.
Hi @IniNimesK Do you have any idea how I can do this? Hi,Easiest way to do is by just hiding the icon from the xml file within the code (for android) because the requirement is just don’t allow the user to attach from device storage. I don’t know the exact file name, but a developer should be able to debug them.But do keep in mind that customizing the mobile application comes with some overhead such as uplifting the code during FSM version upgrades.
@rodrigocivil18 as far as i know this is not possible to do from Configurations so you might have to customize the mobile application and change it from the source code itself.
Hi @Chethana Following are the pointers off the top of my head,Delete the person_mobile record for a specific user and try to reinitialize the device again. Try restarting the IIS app pool for Mobile Server and try to reinitialize Check the mobile service web.config file for anything unusual in the entries such as DownloadUrl/Compare it with a working environment Check whether enough storage available in the application server and the mobile server Check the sync rules because it might be happening due to incorrectly configured sync rules which exports a larger number of records (which in fact can take more time to zip) Inspect the both server log and mobile server logs to if there are any exceptions presentCheers!
@irfana I’m not exactly sure what you are trying to do, but to change the type of existing step, as far as i know you need to remove the existing step and re-add as a question from the toolbox. To remove the existing body within a step you can right click over the body portion and delete the existing type. Do take backups before changing the existing workflow so you have a point to return.
@WilsonX if i understood your question properly, you can restrict the debrief workflow of the FSM Mobile task screen by setting the FSM app param ‘DEBRIEF_ALLOWED_STATUSES’.It accepts comma separated list of allowed task status as its param value and will only allow navigation in the debrief screen only for those status mentioned in the app param.
Already have an account? Login
No account yet? Create an account
Enter your 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.
