Let’s take a look in the ‘Low-Code Design Guide’ in the section ‘Building a custom EIS connector’ which gives us a head start, but you’ll see that more will be covered in this post to get you better knowledge and a proper example. This last role is needed to see the EIS connector when using it…You’ll see that later…Trust me! Spin up your machine, login to your workspace and make sure you are logged in with a user that has a developer role applied as well as the administrator role. With an EIS connector we do a bit the same, but now the entity is called an ‘external’ entity and as we are more in control on what is happening we also need to custom code some things (in Java) to make it all happen…Not hard to do, but it’s always difficult if you don’t have a good example… We already saw something similar with the post about ‘Simple steps on importing entities from database table’ where we could create new instances from a ‘linked’ entity where the data is directly updated in the linked database location…Also great stuff! Would it not be great that our AppWorks users can create new invoice documents in the AppWorks runtime and that our external invoice system is updated with all the relative information?…That is what an EIS connector can do for you!! Let’s say that our external system is an invoice system with an old user interface. Let me explain the use-case: We have our new AppWorks platform available in our organization, but we also have some an external legacy system we still want to manipulate or even keep in synch with our new platform. Is it important to know? Yes it is! As it makes it possible to represent external data via entity modeling to our beloved platform users…Huh?…What!? Today we start with a more advanced topic and that’s the creation of a brand-new Enterprise Information System connector. Welcome to a new installment of AppWorks tips.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |