To fast-track solving any unexpected issue, relevant information is essential. For our support team, it usually comes from a log file that you can send from both the Resco Mobile CRM app and the Woodford configurator.
But why send a log? Isn’t the error message enough? Well, log contains much more information than an error message. Continue reading
“Which version of the Resco Mobile CRM application should I use? And while we’re at it, what do the digits separated by the dots stand for?” These are also the questions Resco’s support team receive from time to time, both from customers and partners. So what can the numbers in the version label actually tell you? Continue reading
In this example we’ll take a look at a situation when you don’t want the Resco Mobile CRM app to save changes the user makes to a record, unless there is other particular data associated with it.
When can this be useful?
Ever noticed that the behavior of the Save button in Resco Mobile CRM can vary? And did you know, you can choose from multiple Save button actions for the entire app and even individually for each form? Continue reading
Resco Mobile CRM speaks your language – you can choose from 16 default languages in the application’s Setup section and even add new ones via the Woodford configurator. But localization can be used not only to completely translate Mobile CRM texts to another language, but also to modify existing items – so that users are instantly familiar and comfortable with the app. Because, just as people, different organizations use different vocabulary, and the same thing can have various names across multiple businesses. Continue reading
Did you know that you can easily set your Resco Mobile CRM application to expand or hide individual fields or a whole section of fields? This handy little feature will help you achieve a clutter-free user interface, as the fields will appear only when needed. Continue reading
You might have encountered the following situation: You’ve created a mobile project in Woodford, but the changes are not applied to the Mobile CRM application when a user synchronizes it. So what can you do? Should the app misbehave like this? Continue reading