Jump to content

Communication with external applications: Difference between revisions

From Resco's Wiki
No edit summary
Line 1: Line 1:
{{Integration TOC}}
In some cases you might want to start a process in [[Resco Mobile CRM]] app, but continue in a third-party application. For this, you need to be able to
In some cases you might want to start a process in [[Resco Mobile CRM]] app, but continue in a third-party application. For this, you need to be able to
* Send data from Resco app to the third-party app
* Send data from Resco app to the third-party app

Revision as of 11:00, 16 July 2019

In some cases you might want to start a process in Resco Mobile CRM app, but continue in a third-party application. For this, you need to be able to

  • Send data from Resco app to the third-party app
  • Receive reply (data) from third-party app and process it in Resco app.

We support this kind of inter-application communication via URL schemes. The third-party application also has to support URL schemes to use this kind of data exchange.

We are using Offline HTML with JavaScript to accept the answer from the third-party application. It also requires that you use UI replacement or home screen replacement in the app.

See this part of one of our webinars for more information.

Example of the URL scheme

To open a specific record in Resco Mobile CRM app from other external application, it is possible to use this URL scheme link:

mobilecrm://open?{entity_logicalname};{entity_id}

Where {entity_logicalname} represents the entity name (case sensitive) and {entity_id} represents the GUID of the record itself.

An alternative URL for Android (which works from e.g. email apps) is:

http://resco.net/schemes/mobilecrm?{entity_logicalname};{entity_id}
Note The record that the URL scheme is pointing to must be available in Mobile CRM app’s offline database.