Can Sugar Mobile be restricted to read only?

Question

Can the Sugar Mobile app be restricted to read-only across the board?

Francesca Shiekh · Accepted Answer

Hey Francesca, Currently there's no mobile sdk, although SugarCRM are developing one. You can view the preview here - The specified item was not found. . If you don't mind the edits just simply not working (rather than the edit button being removed). In theory I'd suggest the following: Create a new field on any module (e.g. Accounts), call it stop_save. Make it default to checked. Do not put it on any views. Write a script in custom/modules/Accounts/clients/base/views/record/record.js that unchecks it (you'll also have to override the create actions, listview, etc.) on the model after render In the before_save logic hook, call sugar_die(); if the checkbox is checked In an after_save logic hook, call the DBManager and write a sql script that checks it again In theory, this would prevent saving in mobile - the sugar_die would kill any api call that doesn't come from mobile. It'd also stop anything other than sidecar updating sugar (unless you remember to uncheck stop_save). This is also a massive hack, and it could cause unexpected behaviour all round. If you want to make a unsafe non-upgradeable customisation, I'd suggest start digging around in the /mobile/ folder. I'd loop in Greg Khanlarov and Joe Mao as they'll know more. Unfortunately you also just missed Sugar Online User Group: SugarCRM Mobile with Joseph Mao . But Sarah Friedlander Garcia and Sravanthi Bellamkonda attended, maybe they know more about what's about to happen? Hope this helps, Alan