Hello,
I’m wondering if there are good design practices for using Layers, BPMs, Functions, BAQs etc. We are brand new with Epicor Kinetic Cloud and will be beginning developing customizations to meet our business needs. Coming from software development we used different design patterns such as MVVM. Is there a good ‘design pattern’ for building customizations in Epicor?
Hey Ben! Welcome to the group!
Kinda surprised that nobody has jumped in yet. I’ll let others correct me, but this is how I look at it:
REST calls are like controllers. They get and set data in the model. These calls can be Business Objects, Functions, or Updatable BAQs.
The UI receives the data and generally stores them in a Data View in browser memory.
UI elements are bound to view models (like the grid model) but sometimes to the data views.
As for a layer strategy, this is an excellent question. I, too, don’t feel like I’m taking full advantage of the concept. I never modify base layers. But we can have more than one layer and the top layer overrules lower layers. Do I use a layer for development and then flatten? Do I keep the layers in case I want an undo?
Maybe someone like @hmwillett, @dcamlin, or @bconner have some thoughts or could correct my understanding. 
Thanks for the input! That framing helps and is what I’m looking for.