9,280
edits
Resco Cloud: Difference between revisions
Jump to navigation
Jump to search
→Integration with other servers: new section
(→Integration with other servers: new section) |
|||
| Line 71: | Line 71: | ||
* Amazon (servers located in the European Union: Germany) | * Amazon (servers located in the European Union: Germany) | ||
* Azure (servers located in the United States: Iowa) | * Azure (servers located in the United States: Iowa) | ||
== Integration with other servers == | |||
Resco Cloud can serve as a standalone backend server, but you can also integrate it with other systems. | |||
[[File:Third_party.png|600px]] | |||
'''[[Resco CRM Connector]]''' consists of a set of REST web service methods and serves as a universal way of connecting. | |||
'''[[Resco CRM sync]]''' is an example of tighter integration with [[Dynamics|Microsoft Dynamics CRM]]. You create a connection between an organization on Resco Cloud and an organization on Dynamics. Metadata can flow from Dynamics to Resco Cloud, and data can be exchanged in both directions. | |||
'''[[Admin_Console#Environments|Connected environments]]''' is another integration option that allows you to clone and connect multiple Resco Cloud organizations. In this case, the focus is less on continuous synchronization but instead on having production and test environments with the option of pushing data or metadata changes to the other organization. | |||
== See also == | == See also == | ||