Navigation: -> Multi Back-Office
One instance of Dime.Scheduler can connect with multiple back office applications (ERP, CRM, LOB, etc.). Many of these systems allow you to create multiple companies, business units, operational units, etc. Each of these organizational entities can be a data source application for Dime.Scheduler.
In order to send data back from Dime.Scheduler to these source applications, connection strings need to be specified.
The following fields can be managed in the connections setup view:
|Source Application||This code is sent by the back office application to identify itself as the source of a job and task and allows Dime.Scheduler to determine how to send data back to the back office application. This code must be the same in both the back office application and Dime.Scheduler. If the source code sent by the back office application couldn't be matched by any of the entries in Multi - back office, then Dime.Scheduler will not be able to send any data.|
|Send appointments to back office||Select to send the appointment data to the back office application.|
|Web Service||The URI that indicates the back office application to connect to.|
|Back Office||The type of back office application you are connecting with.|
|Login||The credentials with which to connect to the back office's web service. |
|Password||See above. |
One of the key takeaways of Dime.Scheduler is that the application has no specific knowledge of the back office system. In fact, it is not even aware of its presence. Using a set of well-defined interfaces, systems are able to communicate with each other without knowing the actual implementation. That is partly why Dime.Scheduler has such a vast ecosystem as it's architecture is built on popular open source technologies.
One area where this information becomes apparent is in the action URIs feature. These are merely URIs templates that are populated with data from tasks and appointments. All jobs must have a reference to a source application and type. At runtime, this information is populated into the template, which gives the remote application enough information to work with. The result of this is that data may originate from multiple sources, as long as the data is correct.
When left blank, the credentials of the
Dime.Scheduler Back Office Windows Servicewill be used. Consult the application administrators docs to retrieve the correct information. ↩