Almost a month ago, aixigo was present in London at the FinDEVr, another format of the Finovate Group. In addition to many interesting presentations and dialogues, it was also a nice time in London. Marcus Gründler, Head of Portfolio Management Systems, and Jonas Pommerening, Software Developer, were out and about as a presenter team in London and have shown (‘there’ würde ich weglassen) in a short presentation how to quickly create individual customer solutions with aixigo’s Digital Wealth Management APIs and a workflow engine “off the shelf”. As an example of this served a process that identifies portfolios that fall below a performance threshold and realigns them based on the individual investment guidelines.
To ensure that everything went smoothly and aixigo’s presentation was a complete success, there was, of course, an appropriate and intensive preparation wave. Jonas Pommerening has recorded his impressions of the entire event for us – from the preparation to the event days.
“First steps and integration with the Portfolio Management API
To ensure that during the presentation on the FinDEVr the generating of the process can be executed quickly and smoothly, I was busy in the month previous to create a sample project, in which the process runs.
Because the PMS (Portfolio Management System) was still new to me, I got familiar with the software by using some internal documentation to start with. Yet, on the first day the PMS ran on my laptop and I was able to click through the API with Swagger UI.
At this point, Marcus already had a concrete idea with which API endpoints we could build our process and we have sketched the basic idea of the process – at the time, not much more than three boxes and two arrows.
Time for a plan! While Marcus was working on an introduction for the presentation, I thought of a “script” for the live coding part of the presentation.
We wanted to bring in a graphical tool for process modelling. In addition, the focus should be placed on the API. And since we were expecting a highly technically oriented audience at the FinDEVr, a bit of code should also be shown. So that we had enough time for explanations during our 15-minute slot; we wanted to get the process finished in less than 10 minutes.
Of course, it should not be a problem to configure a graphical process model, to copy an URL from the API documentation, write a bit of code, and start the process in a web-front-end, and meanwhile to explain everything in a clear way! However, for this to work I had to firstly integrate the software, which should run the process …
As a “workflow engine” Camunda should be used. I had already previously evaluated Camunda with a team colleague and we had a bit integration code from our test project left over, which made it easier for me to integrate the software into our PMS. In addition, an adapted version of Swagger UI was taken and all kinds of adjustments were made to be able to keep the sample code as simple as possible.
Practice, practice, practice
After I got everything finally running, as I had wanted, I started the first test runs for the live coding. There, I directly encountered two problems:
1) Time really elapses too fast. Everything together had lasted almost 10 minutes and left too little time for the rest of the presentation.
2) It is surprisingly difficult to talk and simultaneously type long Java-class names error-free..
A typing error when creating the process diagram could cause errors to appear at the end of the process, which do not look so nice during demonstration (at most as proof that it is really live). Partially, the problems could of course be alleviated by more exercise, but now a coaching-call with our contact person from the FinDEVr was already pending. And the time was just enough to rehearse the whole presentation for the first time together!
The coaching-call ran actually quite well despite little practice. Nonetheless, 18 minutes was definitely too long for the presentation!
However, we had one week left for last changes yet. Thus, we concentrated on placing the focus on the essentials and not to cut off resp. shorten such relevant things from the presentation. The process diagramme I prepared in such a way that only a small part had to be completed and instead of programming only an URL had to be inserted from the documentation. Thus, we had enough time for the presentation and could even add a guest appearance of Alexa.
On the 12th of June the FinDEVr began in good weather. Our presentation was only on the second day in the late morning, so we could still look at the presentations of the other presenters on the first day.
When it finally was time, everything went very fast. The smooth organization of the well-established FinDEVr team left nothing to be desired and before we knew we were already on the stage. In hindsight, I had the feeling that I had not said everything I wanted to say, but on the whole I was satisfied anyway that everything had worked out. After the 15-minute presentation, there was a 5-minute round of questions in which Marcus and I took it in turns to answer questions from the audience about our API and the technologies used. I was really amazed by the lively interest of the audience! A pity that no one directly asked where he or she can buy our API ;).
In conclusion, I can say that it was a lot of fun, both in the preparation and in the execution!”
Authors: Jonas Pommerening, Marcus Gründler
You will find the presentation of Marcus Gründler and Jonas Pommerening held on the FinDEVr here: http://findevr.com/videos/findevr-london–2017-aixigo/
And here we have some further impressions of the event:
For further information or questions, you can turn to Christian Neuenhaus:
+49 0241 55 97 09 – 28