SO logic - Behind the scene

I am used to working with the old model of P4210. (App, Business functions)

Can someone please explain some of the changes, especially the MVC structure that is being in the new SO app. (8.12 onwards)

At an extremely high level it basically looks something like this:

-------- APPL and View Controllers -----------
P42101, P421001, P421002, P421007, etc.
B4210610, B4210620, etc.
-------------- Model -------------------------
B4210900
B4210000, B4210030, etc.
-------------- Legacy SOE MBF ----------------
B4200310/B4200311, etc.


You still have the SOE MBF (B4200310/B4200311), but it has been decoupled from the APPL by a layer of BSFNs that make up the SO model and another set of BSFNs that make up the view controller for the P42101 and each of its subforms.

The APPLs and view controllers are responsible for controlling the UI, displaying data from the model and passing data to the model. The model is responsible for some business logic and making all the necessary calls to the SOE MBF where most of the business logic exists.

I made a very rough simple spreadsheet that shows the call stacks for some of the SOE MBF calls that I used as a quick reference when retrofitting our Xe P4210 mods to 9.0 P42101. I will attach it. Again it is pretty simple and rough, some what incomplete and has a couple of notes referencing our mods, but you might find it helpful (just ignore anything that says Acme).

Thank you sir for the detailed post. This should get me started on it.

~Striker

Thanks Helpful reply for me even though this thread is 6 years old. Thanks.

Thanks, for the brief description this indeed is very helpful.