This is an interesting talk about a different ERP company’s journey to low Code.
I liked it. The breakdown between knowledge and mechanics is something I’ve been fairly successful with here in the redevelopment of the configurator. As we move to full kinetic, we’ll do the same with process versus code for all the customizations we’ve done in the past. And our other big project is taking 20+ year old mathematics tied up in GWBASIC, COBOL, VB, and C# code and consolidate into a single “app”. This same process will be how we go about it, so we have an enduring knowledge model regardless of the next code-base that comes along.
2 Likes