Salesforce admins: Urgent action required!

Resco Platform: Difference between revisions

Jump to navigation Jump to search

Resco Platform (view source)

Revision as of 09:03, 18 November 2024

7,423 bytes removed ,  18 November 2024
Redirected page to Mobile App Development Toolkit
No edit summary
(Redirected page to Mobile App Development Toolkit)
Tag: New redirect
 
Line 1: Line 1:
Build digital solutions to handle any service job – from asset maintenance to work order automation. Deliver results quickly with a powerful combination of capabilities and usability. Create products fully customizable to your client’s needs, mobile-first, working even offline.
#REDIRECT [[Mobile App Development Toolkit]]
 
[[File:Demo.jpg|alt=request a demo button|224px|link=https://www.resco.net/request-a-demo/?product=service-platform]]
 
Resco Platform allows you to create apps that are connected to cloud services like Microsoft [[Dynamics]] or other Microsoft Dataverse-based system, [[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.
 
The Resco platform consists of:
* [[Resco Cloud]] - the backend of our system; it handles data. You can connect your data server to Resco Cloud through [[integration]]s (or use Resco Cloud only). It also hosts data management and customization tools. (Other cloud services can be used instead of Resco Cloud.)
* [[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.
* [[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.
* Mobile devices - Run your apps across phones, tablets, laptops, desktops, smartwatches, AR headsets, and systems including iOS, Android, or MS Windows.
 
== 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 [[view]]s, [[form]]s, and the [[home screen]], 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 their 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|alt=Resco Cloud architecture|600px]]
 
If you are using Microsoft Dynamics or Dataverse, you can benefit from a tighter integration than with other backend servers.
 
[[File:Resco with Dynamics architecture.png|alt=Resco with Dynamics architecture|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|alt=Resco with salesforce architecture|600px]]
 
For other third-party backend systems, Resco Cloud is kept in sync with your backend.
 
[[File:Third party.png|alt=Third party architecture|600px]]
 
== Mobile app ==
 
To create an app you need to:
* define a [[data model]],
* design the [[User interface components|user interface]] by combining components and services,
* configure [[business logic]] [[Rules editor|rules]] (formulas),
* and optionally add [[Offline HTML|custom HTML]] and/or JavaScript code.
 
But you don't have to start from scratch. You can select a scenario with suitable entities, user interface, and logic preconfigured, for example, field service or mobile sales.
 
=== 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 [[entity|entities]] (objects, roughly equivalent to database tables).
 
An entity is a set of [[field]]s or attributes (similar to table columns). 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 [[Online versus Offline|offline/online mode]].
 
=== User interface ===
 
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.
 
Clicking on an item in the list 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.
* [[Automatic Dashboard]]
* [[Location Monitor]]
* [[Questionnaire Designer]]
* [[Report Designer]]
* [[Results Viewer]]
* [[Schedule Board]]
* [[Sync Dashboard]]
 
== See also ==
 
* [https://www.resco.net/platform/ Resco Platform website]
* [[Integration]] - discover how to connect Resco with other services
* [https://www.resco.net/blog/three-unique-customer-demands-solved-with-the-resco-platform/  Challenge accepted: Three unique customer demands solved with the Resco platform] {{Badge|Blog}}
 
 
 
 
 
 
 
{{Feedback}}
[[Category:Core concepts]]
[[Category:Resco Cloud]]
Retrieved from "https://docs.resco.net/wiki/Special:MobileDiff/11779"

Navigation menu