Are Epicor Widgets Broken? šŸ¤

:point_up: So, I know the hypocrisy that I am about to engage in as I go on to defend us low-coders, but I think thatā€™s the idea, is that it should be as LOW code as possible, and preferably all widget-able.

I agree with this in a non-object-oriented language. I can do a VBA macro for Excel pretty easily and there is a ton of info out there for it.

But wow, do I disagree when it comes to BPMs.

Look, there is simply no manual that exists that explains how Epicor business objects tie into C# programming.

Those of you with insane programming backgrounds, I think you just canā€™t see the colossal leap that it takes to go from ā€œI want to do thisā€ to ā€œDid you use the right adapter?ā€

What on earth is an adapter?! Where is that in the trace logs?

Like, the barrier to entry from ā€œI see this happening in the UIā€ to ā€œthis is the code you needā€ is so steep! It is not a 20-hour cram sesh to become an expert. I do agree with that philosophy on a lot of things; I have done that repeatedly over the years. But BPM coding is not one of those 20-hour things; it is a like a college major or at least a minor.

Widgets are really wonderful. I have done so much with them over the last year. And I also totally agree with @hkeric.wci 's criticisms (the ones I understood).

But abandoning widgets because itā€™s ā€œsimpleā€ to learn how to code BPMs, that is not the answer.

3 Likes