Azorus provides an HTTPS web service which receives requests from SITS StuTalk containing an XML payload. Requests are processed in real time, and the HTTP response code is meaningful, indicating the nature of the operation performed. The response body provides full details, including which Azorus and SITS identifiers were affected.
The Azorus Admin UI also provides a historical request log, with full visibility into data received from SITS. This gives a full audit trail for all data received.
The integration for SITS:Vision into the Azorus CRM product is via three component parts:
1) Azorus Core Connector
All reference data noted in this section are stored as List type fields in Azorus. This means that viewing and manipulating such data is done through drop-down list boxes, as opposed to storing them as text fields which would require an administrator to know the code (key) associated with each value. As such, administrative functions such as creating Filters or Reports are a simple matter of selecting the appropriate value.
2) Azorus Enquiry Connector
Azorus can be configured to only send, receive, or both send and receive Enquirer Student Details (ESD) data to and from SITS. This depends on the needs of the institution.
3) Azorus Application Connector
This functionality is focused on the ability to transfer Student (STU) and Application (CAP) data into Azorus. This data can then be used for example, to drive E-mail communications plans or deliver relevant content such as application status within the Azorus Portal.
e:Vision Portal Integration
For institutions utilizing the e:Vision portal for online applications, Azorus can be configured to feed applicants into the web-based application form – pre-populating it with data stored in Azorus. From that point forward, Azorus can then perform Single Sign-On into e:Vision for any User having gone through this process. It is then possible to identify students who have begun the application process through Azorus, and have gone on to complete an application.
What are the benefits?
When integrated with the co-developed template, SITS:Vision and Azorus are setup for two-way data exchange using STU Talk. The data exchange is controlled by the STU Talk Monitor, which can be set to exchange data every minute, every hour, every day, every week or whatever you choose. Every data exchange is logged and can be viewed in detail within Azorus at any time.
How often is data transferred?
SITS to Azorus transfer is dependant on how frequently the StuTalk monitors are run on the SITS side. We have found that a relatively short interval such as 1-5 minutes works well in practice and allows for a near real-time synchronization of data.
Azorus runs a persistent process that checks for data to send to SITS every 5 seconds by default. All queued requests will be sent serially in the order that they arrived in the queue.
What is the primary identifier used for data from SITS?
Azorus uses the SITS Master (MST) Code to identify both enquirers and applicants.
What is the typical process to get up and running?
- Azorus requires the URL and authentication credentials for communicating with SITS, and also to configure credentials that SITS will use to communicate with Azorus.
- Azorus will collaborate with the institution to examine default data mappings and make any adjustments or additional mappings as required.
- Testing of data exchange between an Azorus-provided test environment and an equivalent SITS environment.
- Propagation of configuration to production environment.