10,853
edits
Salesforce admins: Urgent action required!
App projects: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→Managing entities: moving description of the values of the On Conflict parameter to Conflict resolution) |
No edit summary |
||
| Line 1: | Line 1: | ||
An app project is a customized version of mobile application dedicated | An app project is a customized version of the mobile application dedicated to a particular set of users. Or more precisely, the application remains the same, but each project may have a different set of data and functions available. | ||
Administrators use Woodford to create various projects and publish them. App users synchronize their mobile app to access the necessary functions and data. | Administrators use [[Woodford]] to create various projects and publish them. App users synchronize their [[Resco mobile apps|mobile app]] to access the necessary functions and data. | ||
== What's an app project == | == What's an app project == | ||
| Line 10: | Line 10: | ||
* [[Business logic]] | * [[Business logic]] | ||
App projects are represented as a set of metadata. The customizations are saved on the | App projects are represented as a set of metadata. The customizations are saved on the backend server. | ||
* For installations with Microsoft Dynamics, app projects are saved directly in Microsoft Dynamics. | * For installations with Microsoft Dynamics, app projects are saved directly in Microsoft Dynamics. | ||
* For installations with Salesforce and [[Resco | * For installations with Salesforce and [[Resco Cloud]], app projects are saved in Resco Cloud. | ||
App projects are designed for a particular user role. For example, you can create one project for field technicians and a different one for the manager. | App projects are designed for a particular user role. For example, you can create one project for field technicians and a different one for the manager. | ||
| Line 22: | Line 22: | ||
; Icon: The icon offers a visual clue about the state of projects. | ; Icon: The icon offers a visual clue about the state of projects. | ||
:* [[File:Active project.png]] Blue arrow-up sign: The latest version of the project has been published. | :* [[File:Active project.png]] Blue arrow-up sign: The latest version of the project has been published. | ||
:* [[File:Draft project.png]] Grey exclamation mark: If a project has a grey icon with exclamation mark, it means the project is ''dirty'', i.e. there has been a change in the project but it was not published after making these changes. | :* [[File:Draft project.png]] Grey exclamation mark: If a project has a grey icon with an exclamation mark, it means the project is ''dirty'', i.e. there has been a change in the project but it was not published after making these changes. | ||
:* [[File:Inactive project.png]] Red no-entry sign: Project has been deactivated. | :* [[File:Inactive project.png]] Red no-entry sign: Project has been deactivated. | ||
| Line 43: | Line 43: | ||
; 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. | ; 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. | ||
; Template: Select one of the pre-defined app templates, such as sales or field service. Templates come with pre-configured home screen and defined lists and views designed for a particular use case. | ; Template: Select one of the pre-defined app templates, such as sales or field service. Templates come with a pre-configured home screen and defined lists and views designed for a particular use case. | ||
== Toolbar functions == | == Toolbar functions == | ||
| Line 50: | Line 50: | ||
; New: Create a new project. | ; New: Create a new project. | ||
; Edit: Select a project and modify it. Alternatively, you can simply double-click a project. | ; Edit: Select a project and modify it. Alternatively, you can simply double-click a project. | ||
; Properties: Modify project's properties: Name, Role, and Priority. | ; Properties: Modify the project's properties: Name, Role, and Priority. | ||
; Show Users: Display the list of users who receive the customization, i.e., users with a security role that's assigned to this project. | ; Show Users: Display the list of users who receive the customization, i.e., users with a security role that's assigned to this project. | ||
; Delete: Delete the project. | ; Delete: Delete the project. | ||
| Line 58: | Line 58: | ||
; Export: Save a copy of the project to your local computer. This can be useful for backup. | ; Export: Save a copy of the project to your local computer. This can be useful for backup. | ||
; Clone: Create a copy of the selected project. You must enter a new Name, Role, and Priority. Cloning is useful when you want to duplicate a project for different users or when you want to experiment with Woodford and you don't want to lose your current project. | ; Clone: Create a copy of the selected project. You must enter a new Name, Role, and Priority. Cloning is useful when you want to duplicate a project for different users or when you want to experiment with Woodford and you don't want to lose your current project. | ||
; Restore: Return to the last published version of the selected project. If you accidentally delete Resco Mobile project’s note (or its attachment), which leads to losing your | ; Restore: Return to the last published version of the selected project. If you accidentally delete Resco Mobile project’s note (or its attachment), which leads to losing your project and there is no backup, you can use the Restore button. It will create the project’s note and attachment from the last published version of the project. Only changes made after publishing will be lost and you don’t have to rebuild the project from scratch. | ||
; Recover: If you for example accidentally destroy your CRM organization and recover it without Resco entities, it is possible to recover the project from data synced on the Windows device. In case such situation happens, please contact us on mobilecrm@resco.net for further steps, from which the last one is using the Recover button. | ; Recover: If you for example accidentally destroy your CRM organization and recover it without Resco entities, it is possible to recover the project from data synced on the Windows device. In case such a situation happens, please contact us on mobilecrm@resco.net for further steps, from which the last one is using the Recover button. | ||
; Derive: Creates a child project. | ; Derive: Creates a child project. | ||
; Flatten: Makes a standalone project from a derived project ("flattens" the hierarchy) | ; Flatten: Makes a standalone project from a derived project ("flattens" the hierarchy) | ||
| Line 82: | Line 82: | ||
See also: | See also: | ||
* For more information about project hierarchy, please check this section of one of our [https://youtu.be/2dM7TSdNGqU?t=1m59s webinars]. {{Badge|Webinar}} | * For more information about the project hierarchy, please check this section of one of our [https://youtu.be/2dM7TSdNGqU?t=1m59s webinars]. {{Badge|Webinar}} | ||
* For information about the child project’s parts, whether they are inherited or changed in the child project, please check this additional [https://youtu.be/iLZ43KxGEW0?t=37m10s webinar]. {{Badge|Webinar}} | * For information about the child project’s parts, whether they are inherited or changed in the child project, please check this additional [https://youtu.be/iLZ43KxGEW0?t=37m10s webinar]. {{Badge|Webinar}} | ||
| Line 164: | Line 164: | ||
After enabling an entity, you can select fields that you plan to use on this entity in the Resco Mobile CRM application. For example, you can pick some additional fields you want to use in your mobile project: City, Country/Region, Street and ZIP/Postal Code. Here you can also enable the custom fields for the entity. | After enabling an entity, you can select fields that you plan to use on this entity in the Resco Mobile CRM application. For example, you can pick some additional fields you want to use in your mobile project: City, Country/Region, Street and ZIP/Postal Code. Here you can also enable the custom fields for the entity. | ||
{{Note|Best practice: We recommend not to include too many entities and fields in your mobile project. | {{Note|Best practice: We recommend not to include too many entities and fields in your mobile project. Backend servers often include a large wealth of entities and fields, and most organizations only use a small subset. An even smaller subset of the data is necessary in the field. [[Sync Filter]] can further restrict which records should be downloaded to the mobile device. Careful planning can improve the performance of the app and satisfaction of the users.|Tip}} | ||
You can also configure some properties for each field. Select a row and modify the '''Properties''' pane on the right. | You can also configure some properties for each field. Select a row and modify the '''Properties''' pane on the right. | ||
| Line 171: | Line 171: | ||
; Formatting: Affects the appearance of the fields in the forms. | ; Formatting: Affects the appearance of the fields in the forms. | ||
:* Single line – Field is formatted to have the appearance of a single line field in the mobile app. | :* Single line – Field is formatted to have the appearance of a single-line field in the mobile app. | ||
:* Multiline – Field will have an appearance of a multiline field. | :* Multiline – Field will have an appearance of a multiline field. | ||
:* Email – Adds an action button to the field in the mobile app, activation of which will provide user with an opportunity to immediately create an email. | :* Email – Adds an action button to the field in the mobile app, activation of which will provide user with an opportunity to immediately create an email. | ||
:* Phone number – Field gets an action button that provides phone call functionality (the device will dial the number contained in the field). | :* Phone number – Field gets an action button that provides phone call functionality (the device will dial the number contained in the field). | ||
:* URL – Adds an action button to open the URL in the native browser of the device. | :* URL – Adds an action button to open the URL in the native browser of the device. | ||
:* Barcode – Adding an action button that activates a camera so user can scan [[Barcode]]s and [[QR code]]s. | :* Barcode – Adding an action button that activates a camera so user can scan [[Barcode]]s and [[QR code]]s. This function will only work on devices that have a camera with Autofocus. | ||
:* HTML – Formats the text field into a HTML type (bodies of email, signatures and etc). | :* HTML – Formats the text field into a HTML type (bodies of email, signatures and etc). | ||
:* DropDown, DropDownList, Multi DropDown, Multi DropDownList – this feature allows you to predefine input for users, so instead of entering a value, they can choose to use options from drop down list (or enter what is needed manually). More about this feature is shown in this [https://youtu.be/9vL4QRN_1dk?t=34m3s webinar section]. {{Badge|Webinar}} | :* DropDown, DropDownList, Multi DropDown, Multi DropDownList – this feature allows you to predefine input for users, so instead of entering a value, they can choose to use options from a drop-down list (or enter what is needed manually). More about this feature is shown in this [https://youtu.be/9vL4QRN_1dk?t=34m3s webinar section]. {{Badge|Webinar}} | ||
{{Note|If you disable any previously enabled field, please check all existing views and forms and remove any fields or lists marked by the sign “Invalid”, or enable the correspond field so that the field will no longer be listed as invalid. If there are any invalid fields or lists in the form or view, the application will crash when you try to open an entity list or record details. See [[Metadata changes in live projects]] for more information.|Warning}} | {{Note|If you disable any previously enabled field, please check all existing views and forms and remove any fields or lists marked by the sign “Invalid”, or enable the correspond field so that the field will no longer be listed as invalid. If there are any invalid fields or lists in the form or view, the application will crash when you try to open an entity list or record details. See [[Metadata changes in live projects]] for more information.|Warning}} | ||