340 likes | 597 Views
Resco MobileCRM. Technological overview Juraj Mojik. Agenda. Overview of Studio Woodford MobileERP introduction. Resco MobileCRM. 3 parts : Application Woodford Studio Source code + compilation = application Integrated tools Woodford. Application. iOS, Android, WM, W7, WP7
E N D
Resco MobileCRM Technological overview Juraj Mojik
Agenda Overview of Studio Woodford MobileERP introduction
Resco MobileCRM 3 parts : Application Woodford Studio Source code + compilation = application Integrated tools Woodford
Application iOS, Android, WM, W7, WP7 Different projects, but all in C# .NET Offline -> local database
Solution structure Layer architecture Top layer - platform independent Bottom layers - platform specific Interfaces for comunication between PI and PS code Top layer is common for all platforms Layers = Visual Studio projects
Projects MobileCRM: top level project (your custom application) Resco.UI, Resco.Data: set of UI and Data interfaces (CRM independent) Resco.UI.Platform, Resco.Data.Platform: implementation of those interfaces MobileCRM.UI, MobileCRM.Data: common CRM UI and Data logic and classes
Top layer structure Controllers – all lists (views) and forms Model – entity classes (custom) Model.meta – meta entity information (enums and schema names) Configuration – database definition files, language files, sync filter ... Images.Platform folder Files : Program.cs (main entry point), Resco.xcrm, ControllerRegister ...
Integrated Tools Tools integrated into VS help you with the most common customization tasks (adding entities and properties, designing) Resco.xcrm – select entities and properties List and form designers (rlist, rform) The application will automatically use the correct list and form, you only have to create and design them
Working with entities Dynamic entities (class DynamicEntity) Dynamic entity = dictionary property name + value Strongly typed classes for convenience and for certain situations (bussines logic code) Strongly typed classes are auto-generated from metadata
Compilation & deployment Version for each platform has to be compiled before deployment Conversion tool for getting different platform version (project files) from WM version Deployment is very platform specific WM, W7, Android – automatic deployment and updates can be made iOS, WP7 – first deployment manually, update using notification (appstore or enterprise program)
Woodford Woodford is a customization tool, that does not require compilation for changes to take effect The customizations are applied after successful synchronization Customizations are platform independent Integrated / Stand-alone version (identical) Administration functionality
Customizations Woodford customizations are stored on the CRM server in custom entities Mobile Projects for different User Roles within the organization Common customization tasks – add, remove entities & their properties, design lists and forms No code
Advanced functions Besides basic functions Woodford offers : Sync filters Dashboards Charts Multiple views Forms: Maps, IFrames Images
Administrative functions Mobile Devices Remote wipe Manage licenses
Woodford and Studio It is possible to use Woodford and Studio simultaneously Small changes made with Woodford don‘t require compilation and can be applied instantly Advanced customizations will be made with Studio and new version of app will be re-deployed When used simultaneously – Configuration folder, mobile entites and properties and lists & forms (but not code files) from Studio are overwritten by customizations from Woodford
MobileERP Different product, but similar to MobileCRM Developer solution for creating mobile applications for Microsoft Dynamics ERP products (NAV, AX, GP …) Full source code Integrated tools (designers) No Woodford yet (or similar tool) Very first version
MobileERP Application Platforms: iOS, Android, WM, W7 (Tablet), WP7 Look and feel – like a CRM application Lists, forms ... Offline client (Local db) Currently, no direct integration with ERP !
Current Architecture MobileERP Application Your ERP server (NAV, AX...) Provided by you MobileERP Server
Synchronization Application synchronizes with a „simple server“ provided by Resco Simple server = sql db + web services Sync (or mirroring) between Resco server and your ERP server needs to be implemented by you Resco server uses MS SQL db so the sync with ERP db can be done on database level Resco server can be left out, if you implement the web-services on your ERP server
Synchronization details Our synchronization mechanism is based on GUIDs and modification timestamps Timestamps – incremental syncing These two are integral for our solution If you are considering leaving out the Resco server, it might be a better idea to add those to your server, then trying to remove from ERP application
Working with MobileERP File erpschema.xerp (XML file) defines database schema and „metadata“ for the mobile application Classes are created for database entities Information from this file is used by Resco designers Also, local db and Resco server db schema is built from this file
Development DALConfig.xdog for generating classes List & form designers for convenient UI design Resco server sources (web services code) Similarly to CRM : Layer architecture Project for each platform Conversion tool & templates
MobileERP Future Collecting feedback from YOU Heavy development Tool (like Woodford) Integration & Synchronization Sample application