Is there an Entity Relationship Model for the Zellis Intelligence Platform?

Zellis have been working on an Entity Relationship Model for the Zellis Intelligence Platform schema.  This has been developed in Power Platform and requires Power BI to view it.  If you would like to obtain a copy of this please contact the Customer Help centre.

How does data get into your data platform?

Any interaction that occurs in ResourceLink that results in a change/amend/delete on a data table that we use in the Intelligence Platform will fire a database trigger.  That trigger will invoke the synchronization process that moves the data from the ResourceLink database in a holding schema that enables us to run our transformations on the data to shape and load that data into the Zellis Intelligence Platform entities. 

There are certain process and options within ResourceLink that can result in triggers being turned off.  If this happens then data won’t synchronize.   This is normally during Data Migration where bulk data is being loaded into ResourceLink and should not affect normal business processes.

In addition to ResourceLink data, we are building the capability to integrate data from Zellis T&A, Benefex, Zellis Background Checking and Zellis Compensate, further enriching the scope and capability of the Zellis Intelligence Platform.

Can we integrate with User Defined Field data?

The API suite caters for reads and writes in relation to User Defined Fields and Screens.

What is CountryAddressParameters?

ResourceLink has an option to customise which address fields are written to for different countries.  UK addresses will default to Line one, Line two, line three, line four and Postcode and is not affected by the parameters.  The CountryAddressParameters entity is related to a given Country and allows for additional fields to be included as part of a standard address format for that country (eg there are additional fields like Municipality which can be included).  It is important to reference these settings if you are expected to write non-UK addresses.

How do I load a document to DocStore using the UploadDocument API?

To load a Document via ZIP, you need to use the uploadDocuments endpoint and then include a multi-part request where;

 Part 1 = JSON Body;

  uploadDocumentRequest {  "DocumentCategory":"DEFLT",  "UserType":"OPERATOR",  "UserKey":"ALANKARP",  "WorkerId":5  }

 You would change the values in the request of course depending on what Object/record you want to load the document against.

Then the Part 2 of the request needs to be a binary type with JSON body element file that contains the local filename