Difference between revisions of "Resco platform"

From Resco's Wiki
Jump to: navigation, search
(User interface)
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
== What is Resco Mobile CRM platform ==
+
== What is Resco platform ==
  
Resco Mobile CRM as a platform allows you to create apps that are connected to cloud services like Microsoft Dynamics, Salesforce, or the Resco Cloud. Choose one of the ready-to-use app templates for sales, field service, inspections, or routes. Or start from scratch.
+
Resco as a platform allows you to create apps that are connected to cloud services like Microsoft Dynamics, Salesforce, or the Resco Cloud. Choose one of the ready-to-use app templates for sales, field service, inspections, or routes. Or start from scratch.
 +
 
 +
Resco platform consists of:
 +
* [[Resco Cloud]] - the backend of our system; it handles data. You can connect your data server to Resco Cloud through integrations (or use Resco Cloud only). It also hosts data management and customization tools.
 +
* [[Resco mobile apps|Application]] - you can manage your data in the application, even when you are offline. We offer mobile, desktop, and web-client applications, and all of them are fully customizable.
 +
* [[Woodford]] - a tool that allows you to customize your mobile applications ([[app projects]]). It is hosted on Resco Cloud.
 +
* Other tools - also hosted on Resco Cloud. These don't affect how the mobile application looks like, but rather work with data.
 +
 
 +
== Configuration and design ==
 +
 
 +
Application configuration and design are performed via the [[Woodford]] tool.
 +
 
 +
# To create an app, you create an [[app projects|app project]]. You can create an unlimited number of projects. By associating the project with a user role (profile), the correct app will be available for your users.
 +
# The next step is to create the data model. Woodford connects to the cloud-service and imports the metadata. Simply by selecting which entities and fields you want to have available in the app the data model is created.
 +
# To design the UI components like views, forms, and home-menu, simply use the provided designers.
 +
# Finally, publish the app. A published project is a data package that the app downloads and reads to configure itself.
 +
 
 +
Your users can now download one of [[Resco mobile apps]], enter your cloud-service login and enjoy the app you have just created.
 +
 
 +
== Configuration variants ==
 +
 
 +
If you don't have a backend server, you can create your organization on [[Resco Cloud]].
 +
 
 +
[[File:Resco Cloud.png|600px]]
 +
 
 +
If you are using Microsoft Dynamics, you can benefit from a tighter integration than with other backend servers.
 +
 
 +
[[File:Resco with Dynamics architecture.png|600px]]
 +
 
 +
If you are using Salesforce, your organization data resides at Salesforce and your project data is stored in Resco Cloud. See [[Resco for Salesforce]] for more information.
 +
 
 +
[[File:Resco_with_salesforce_architecture.png|600px]]
 +
 
 +
For other third-party backend systems, Resco Cloud is kept in sync with your backend.
 +
 
 +
[[File:Third party.png|600px]]
  
 
== Mobile app ==
 
== Mobile app ==
Line 17: Line 52:
 
An entity is a set of [[field]]s. For example, for Contact entity, fields are First name and Last name. A special type of entity field, called the lookup, represents a relationship between entities. For example, a Contact can have a parent - Customer.
 
An entity is a set of [[field]]s. For example, for Contact entity, fields are First name and Last name. A special type of entity field, called the lookup, represents a relationship between entities. For example, a Contact can have a parent - Customer.
  
The data model of a particular app is created by selecting a subset of cloud metadata. Later, you will be able to expand the data model by by adding mobile-only entities.
+
The data model of a particular app is created by selecting a subset of cloud metadata. Later, you will be able to expand the data model by adding mobile-only entities.
  
 
The app includes a universal connector that allows you to perform read, create, update, delete operations on the cloud service.
 
The app includes a universal connector that allows you to perform read, create, update, delete operations on the cloud service.
  
Universal sync engine is also available out of the box. It allows a subset of the cloud-service data to be synchronized in local (offline) database. The sync process is extensively configurable. For example, synchronization filters allow you to restrict records and entities that are available offline.
+
A universal sync engine is also available out of the box. It allows a subset of the cloud-service data to be synchronized in the local (offline) database. The sync process is extensively configurable. For example, synchronization filters allow you to restrict records and entities that are available offline.
  
 
Depending on whether the app accesses the local database or cloud-service directly we talk of offline/online mode.
 
Depending on whether the app accesses the local database or cloud-service directly we talk of offline/online mode.
Line 27: Line 62:
 
=== User interface ===
 
=== User interface ===
  
The user interface of an app is built from '''components''', such as views, forms, dashboards, maps, calendars, etc. An unlimited number can be created. An app's logic can interact with services like email, phone call, bar code, camera, microphone, or GPS.
+
The user interface of an app is built from '''[[User interface components|components]]''', such as views, forms, dashboards, maps, calendars, etc. An unlimited number can be created. An app's logic can interact with services like email, phone call, bar code, camera, microphone, or GPS.
  
An '''entity view''' displays a list of items, each representing a single record of an entity. The view filter determines which records. Choosing which entity fields are displayed and in which design is determined by the view-row design.
+
An '''entity [[view]]''' displays a list of items, each representing a single record of an entity. The view filter determines which records. Choosing which entity fields are displayed and in which design is determined by the view-row design.
  
Clicking on an item in the item opens the default '''entity form'''. The purpose of entity form is to display and edit a single record. Conceptually, it is a combination of sub-components.
+
Clicking on an item in the item opens the default '''entity [[form]]'''. The purpose of an entity form is to display and edit a single record. Conceptually, it is a combination of sub-components.
  
* The main sub-component is the detail: a table of controls bound to entity fields. App chooses the correct control type (numeric vs checkbox) by the type of the field. The selection, position and design of each control is configurable.
+
* The main sub-component is the detail: a table of controls bound to entity fields. App chooses the correct control type (numeric vs checkbox) by the type of the field. The selection, position, and design of each control are configurable.
 
* The second sub-component is an associated view. This component is an entity view, that is pre-filtered by the relationship of the form’s entity and the view’s entity. The purpose is to present records related to the form’s record.
 
* The second sub-component is an associated view. This component is an entity view, that is pre-filtered by the relationship of the form’s entity and the view’s entity. The purpose is to present records related to the form’s record.
  
The app recognizes lookup-fields, and allows the user to navigate to the related record by clicking the lookup-control on the entity-form.
+
The app recognizes lookup-fields and allows the user to navigate to the related record by clicking the lookup-control on the entity-form.
  
 
When the app starts the first thing the user sees is the [[home screen]]. End each item of the menu can open an entity view, form, calendar, or dashboard.
 
When the app starts the first thing the user sees is the [[home screen]]. End each item of the menu can open an entity view, form, calendar, or dashboard.
  
== Configuration and design ==
+
== Content tools ==
 
 
Application configuration and design is performed via the [[Woodford]] tool.
 
 
 
To create an app, you create an app project. You can create an unlimited number of projects. By associating the project with a user role (profile), the correct app will be available for your users.
 
 
 
The next step is to create the data model. Woodford connects to the cloud-service and imports the metadata. Simply by selecting which entities and fields you want to have available in the app the data model is created.
 
 
 
To design the UI components like views, forms and home-menu, simply use the provided designers.
 
 
 
Finally, publish the app. A published project is a data package that the app downloads and reads to configure itself.
 
  
Your users can now download the Resco Mobile CRM app, enter your cloud-service login and enjoy the app you have just created.
+
Resco offers additional web-based tools, usually aimed for system administrators and managers, that help them design and customize more functions or supervise and manage users, devices, or app projects.
 +
* [[Automatic Dashboard]]
 +
* [[Location Monitor]]
 +
* [[Questionnaire Designer]]
 +
* [[Report Designer]]
 +
* [[Results Viewer]]
 +
* [[Schedule Board]]
 +
* [[Sync Dashboard]]
  
 
[[Category:Core concepts]]
 
[[Category:Core concepts]]

Revision as of 07:48, 17 March 2020

What is Resco platform

Resco as a platform allows you to create apps that are connected to cloud services like Microsoft Dynamics, Salesforce, or the Resco Cloud. Choose one of the ready-to-use app templates for sales, field service, inspections, or routes. Or start from scratch.

Resco platform consists of:

  • Resco Cloud - the backend of our system; it handles data. You can connect your data server to Resco Cloud through integrations (or use Resco Cloud only). It also hosts data management and customization tools.
  • Application - you can manage your data in the application, even when you are offline. We offer mobile, desktop, and web-client applications, and all of them are fully customizable.
  • Woodford - a tool that allows you to customize your mobile applications (app projects). It is hosted on Resco Cloud.
  • Other tools - also hosted on Resco Cloud. These don't affect how the mobile application looks like, but rather work with data.

Configuration and design

Application configuration and design are performed via the Woodford tool.

  1. To create an app, you create an app project. You can create an unlimited number of projects. By associating the project with a user role (profile), the correct app will be available for your users.
  2. The next step is to create the data model. Woodford connects to the cloud-service and imports the metadata. Simply by selecting which entities and fields you want to have available in the app the data model is created.
  3. To design the UI components like views, forms, and home-menu, simply use the provided designers.
  4. Finally, publish the app. A published project is a data package that the app downloads and reads to configure itself.

Your users can now download one of Resco mobile apps, enter your cloud-service login and enjoy the app you have just created.

Configuration variants

If you don't have a backend server, you can create your organization on Resco Cloud.

Resco Cloud.png

If you are using Microsoft Dynamics, you can benefit from a tighter integration than with other backend servers.

Resco with Dynamics architecture.png

If you are using Salesforce, your organization data resides at Salesforce and your project data is stored in Resco Cloud. See Resco for Salesforce for more information.

Resco with salesforce architecture.png

For other third-party backend systems, Resco Cloud is kept in sync with your backend.

Third party.png

Mobile app

To create an app you need to:

Data model

The app data model is defined through importing the cloud-service structure, also known as metadata. Modern cloud service is described as a set of entities (objects, roughly equivalent to database tables).

An entity is a set of fields. For example, for Contact entity, fields are First name and Last name. A special type of entity field, called the lookup, represents a relationship between entities. For example, a Contact can have a parent - Customer.

The data model of a particular app is created by selecting a subset of cloud metadata. Later, you will be able to expand the data model by adding mobile-only entities.

The app includes a universal connector that allows you to perform read, create, update, delete operations on the cloud service.

A universal sync engine is also available out of the box. It allows a subset of the cloud-service data to be synchronized in the local (offline) database. The sync process is extensively configurable. For example, synchronization filters allow you to restrict records and entities that are available offline.

Depending on whether the app accesses the local database or cloud-service directly we talk of offline/online mode.

User interface

The user interface of an app is built from components, such as views, forms, dashboards, maps, calendars, etc. An unlimited number can be created. An app's logic can interact with services like email, phone call, bar code, camera, microphone, or GPS.

An entity view displays a list of items, each representing a single record of an entity. The view filter determines which records. Choosing which entity fields are displayed and in which design is determined by the view-row design.

Clicking on an item in the item opens the default entity form. The purpose of an entity form is to display and edit a single record. Conceptually, it is a combination of sub-components.

  • The main sub-component is the detail: a table of controls bound to entity fields. App chooses the correct control type (numeric vs checkbox) by the type of the field. The selection, position, and design of each control are configurable.
  • The second sub-component is an associated view. This component is an entity view, that is pre-filtered by the relationship of the form’s entity and the view’s entity. The purpose is to present records related to the form’s record.

The app recognizes lookup-fields and allows the user to navigate to the related record by clicking the lookup-control on the entity-form.

When the app starts the first thing the user sees is the home screen. End each item of the menu can open an entity view, form, calendar, or dashboard.

Content tools

Resco offers additional web-based tools, usually aimed for system administrators and managers, that help them design and customize more functions or supervise and manage users, devices, or app projects.