1. What is Woodford?
Woodford is an application that enables you to create customizations of the app, manage licenses and mobile devices.
How does it work?
Start Woodford and connect to the CRM server. Create a mobile project (customization—the way you want the Mobile CRM application look and work). Once you save the changes you make, these are saved on the CRM server in custom Resco entities, which are created at the first start of Woodford.
When you publish the project, the customization becomes active and available to be downloaded to Mobile CRM application. When Mobile CRM app synchronizes with your back-end system (be it Microsoft Dynamic, Salesforce, Oracle CX), it downloads the project, available for the user’s security role and downloads/uploads data.
2. Running Woodford
First, you need to download/install Woodford. You can get Woodford here!
Hint: Details about the installation process and difference between the standalone and imported solution, are described in detail in the Woodford guide.
To log in, fill in the URL of your server, your username and password. Woodford will connect directly to your server and automatically create custom entities on it, so whenever the application connects to the server, it will recognize the customizations made in Woodford.
Note: To be able to install Woodford, you need a system administrator role. To work with Woodford (create customizations, manages users…), you need either a system admin or a system customizer role.
3. A Mobile Project – A customization of the Mobile CRM application
A mobile project contains all customizations of the Mobile CRM application. This is where you can add/remove/change fields, entities, views, forms, etc.
Open Woodford -> In the section “Mobile Projects” click on button “New“.
3.1 Mobile Project’s Properties
Type: For internal CRM users, set the project’s type to “Standard User“.
Name the project however you’d like (As you can create more projects, the name will later help you identify them).
Priority: When more projects for the same security role are created, the one with a higher priority is used. For example, if you create two mobile projects for a role “Salesperson“, one with the priority number 10 and second with 100, the second one will be used when the application synchronizes (since it has a higher priority number).
Note: The same principle applies when a user has multiple security roles assigned and there are mobile projects created for these roles.
Security role: Select the security role(s) for which you want to create the mobile project. You can create different mobile versions (projects) for different users based on their CRM role.
To start customizing the app, double click on the project to open it (or select the project and click on “Edit“).
Note: Mobile projects are stored as Note attachments to resco_mobileproject’s records.
Warning: When you do a bulk delete of your Notes, please note you might also delete your mobile projects. To avoid this, please exclude Note attachments to resco_mobileproject’s records from the bulk deletion.
3.2 Enable an Entity
You can see a list of entities that are on your CRM server on the left side, in section “Entities“. By default, only the main sales entities are enabled, the rest are disabled (enabled means that the entity can be used and its data viewed in Mobile CRM application).
To enable a disabled entity, select the entity and click on “Enable” button.
When an entity is enabled, you can expand the options available for this entity either by double clicking on the entity name or by clicking on the arrow next to the entity name.
3.3 Enable Fields
For enabled entities, you can define which fields will be available in the app.
Hint: To learn more about field option, permissions, formatting, check the full Woodford manual.
3.4 Create a View
To create a view (or see a list of existing views), click on “Views”  under entity options.
To create a new view, click on “New” . In “Type”  label row select “Public View” and choose a template (shows the number of fields on the view, you can add more fields later on when designing the view).
To add a field to a view, just drag and drop it from the “Fields Explorer” (list on the right side) onto the “Designer”.
To change a field to a different one, double-click on it.
Once you’re done editing the view, hit “Save & Close“.
3.5 Create a Form
On a form, you can:
- Display and edit record’s fields,
- View records, which are related to the record
- Show special tabs; such as iFrame, Map, Media tab (signature, photo capturing, attachments…)
There are 2 types of forms: Contact Information Form and Edit Form.
- Contact Information Form allows displaying of fields and associated records.
- Edit Form is what you know from your CRM, i.e. the form, where you can enter and edit data.
If you want to use only the “Edit Form“, you can simply delete the “Contact Information Form” from the entity.
Click on the “Designer” area, to see the list of available fields in the “Field Explorer” section.
Select the “Add Field” button on the toolbar, double click on the field in the “Field Explorer“, or drag & drop a field to place it on the form.
To add a list of related records, click on the tab area. Then double click on the List that you’d like to add on the form.
Once you finish editing the form, “Save & Close” it.
3.6 Add items to Home section
To be able to access newly enabled entity from the home screen of the app, you need to place it on the “Home” item.
All you need to do is to drag and drop the entity from “Available Items” section to “Home” section. You can also rearrange the order of items.
Don’t forget to save the changes you’ve just made.
3.7 Publishing a project
Once you’re finished making your changes, publish the project. This will upload the project to a custom entity on the CRM server and when a user synchronizes Mobile CRM app, the app will download the customization as well as the data.
When a mobile project is published, at the first synchronization of the Mobile CRM app after publish, the message “Application was updated” is shown. If it is not, most likely the user’s role does not match the role for which the mobile project was created.
If you experience any difficulties, errors or crashes, contact us for help. Ideally by sending a Log from Mobile CRM app’s “About” section.
4. Advanced Customizations
If you want to continue customizing Mobile CRM application (move onto more advanced topics), please proceed to the Woodford Guide (http://www.resco.net/mobilecrm/downloads/WoodfordGuide.pdf).
5. Visual Glossary