...

Meridix Studio has a very extensive branding support, where the user interface can be changed per installation through our theme package model. This allows a customer to easily modify their installations user interface so that it matches their company profile. Logos, colors, fonts, icons and export appearance and much more can be customized without requiring custom binary builds of the system. This is ideal when the report system should be integrated in a portal or be sold as part of a suite of other products. Read more about or branding and theming support here.

Language support

Meridix has support for multiple languages (English and , Swedish, Danish, and at the time of writing Danish translations is being createdFinnish and Japanese) and can easily be translated to additional languages if required (more information about translations). Our current plan is to support all the Nordic languages in the near future.
But to a key feature to make a system easily integrable into other platforms or suites/portals etc. is that the vocabulary used in Meridix Studio can be modified on a per site basis. Each supported language is integrated into the compiled binary code to achieve the best possible performance, but the system has support for customer specific overrides. I.e. if a customer want to change the used vocabulary for a feature/section/page to match the vocabulary used in other products that they sell or work with or just want to use another definition for something than the default all the resources used in Meridix Studio can be overridden at runtime through Meridix Studios support for translation-override-packages and therefore no changes to the original translation files is required (which would require a new compiled version of the system to be deployed when a change has been made).
And by combining this override feature with a custom theme (see previous section) a customer can customize almost every aspect of the interface for the end users.

...

Meridix Studio can easily be integrated into an existing portal and the login can be transparent to the end users through the single sign on support. And with the branding and theming support the Meridix user interface can be restyled in a way so that users do not know that they left the portal. Example: if a customer/reseller has an existing customer portal an SSO can be setup so that existing portal users can be logged in into a Meridix Studio installation branded in the same way as the portal so that the end users wont know they left the portal at all, the login is handled automatically and Meridix can be opened in a iframe or as a new window depending on the portal design. Read more about our SSO support here.

HTTP API - Custom user requirements

No system can probably handle every single users requirements out of the box, there will always be end users with very specific requirements therefor Meridix Studio has an very extensive HTTP based API that allow end users and customers to integrate Meridix into other products or systems through its API (Application Programming Interface). Users can then create reports, edit users, handle scheduled reports through their program language of choice. Read more about our API support here.