Evaluation Guide

Integrations

Integration is essential when building advanced enterprise solutions. Your company data will naturally be owned and maintained in separate systems and should be accessed from where they originated to avoid duplicated data. Further, you will want to exchange data with customers, partners, governments, and third-party services. 

Genus can integrate with external services and applications on several levels. Our platform provides built-in web service options, dedicated actions for file import/export, and supports database integrations through views or ETL procedures. 

  • Both REST and SOAP services can be modeled and maintained in Genus Studio. Genus supports both consumption and exposure of data through these standards.

    Genus-modeled web services provide lightweight, data-centric access to resources in the application model. Web services are made up of a sequence of effects that perform the desired actions to send, receive, create or modify data based on the request.

  • REST services support all CRUD4-operations, using standard HTTP-verbs (e.g. POST, GET, PUT, DELETE, PATCH). The REST service definition may be exposed using the OpenAPI Specification (Swagger). The specification may be represented in JSON or YAML, while request/response data elements may be in JSON or XML. Content of type “multipart/form-data” when consuming REST services is also supported.

  • The SOAP Service definitions will automatically be generated based on the application model and can be exposed using the Web Services Description Language (WSDL).

  • Web service authentication is managed through the security model in Genus Studio, effectively securing your company data while opening for integrations.

  • Although most modern integrations are service-oriented, Genus also supports traditional techniques for batch file import and export. File integrations can be tailored in the Task and Action tools, giving the Business Engineer full flexibility to define file formats, targets, and sources, and to include more advanced logic.

    If you wish to integrate on a database level, we recommend using a suitable script or ETL tools for your database platform.

  • Calendars and contact lists can be configured in your application model and shared by a URI. Your users may subscribe to calendars by adding a subscription to their mobile device, in Microsoft Outlook, or similar. Calendar sharing is based on the Webcal scheme for accessing iCalendar files. Calendars are shared read-only, but each shared item contains a link, so your user can open your Genus app and inspect or edit the calendar item. Contact sharing is based on a read-only CardDAV service. Both integrations are available through the Genus Start Page on Genus Web.