One of the major advantages of low-code is the speed with which applications can be developed that also work well in terms of user experience. For example, read the success story of one of our customers here. It concerns a health insurance fund in Belgium with 4.5 million members.
For this customer, our colleagues, together with a Belgian partner, contribute to a 40% speed gain. Speed gain in the development of a platform that digitizes incoming mail, indexes it and distributes it to the right departments. Speed gain and user friendliness are the reasons why we have OutSystems as low-code application in our product and service portfolio. Enterprise Information Management (EIM) applications often have the disadvantage that the user interface is given a lower priority. As a result, screens age and become unfriendly. Nowadays, content services are on the rise. The EIM system provides the possibilities for document management through an API (*). This API can be consumed by any application. This is why OutSystems is an excellent addition to our extensive Enterprise Information Management services.
The pain of integrations
However, we also see that building integrations between a low-code platform such as OutSystems and an EIM system such as Documentum is quite time-consuming. In addition, it is desirable to link the front-end application as loosely as possible to the EIM system. To make it easy to link an additional application to the EIM system. Or to prevent a lot of rebuilding in the application when the EIM system is replaced. To solve these issues, we at Informed Group have developed a service-oriented architecture that makes the most of OutSystems and any EIM system.
What does that look like
An example of EIM in OutSystems. From the user’s point of view, it opens an application built in OutSystems. For EIM specific functions in the application, the EIM system is not directly addressed. Because a generalized services layer is addressed which can orchestrate all EIM systems. By keeping the link between the front-end application and the services layer loose, there are no direct dependencies. As a result, the service layer can be easily supplemented. As a result, the services layer addresses the desired EIM systems through the APIs of the EIM systems. Based on this it is recommended to place a gateway between the services layer and the EIM endpoints. Because in this way you guarantee maximum security.
Learn more
Do you have questions about what benefits low-code and a service-based architecture can bring your organization? Or are you already convinced that you are looking for specialists in the field of Enterprise Information Management, low-code and integrations? Please contact us.
*API: a collection of definitions that allows a computer program to communicate with another program or component(Source: Wikipedia on 13-7-2021)
id=”25940″][/contact-form-7]
Want to know more about EIM in OutSystems?
