So, why not using functions instead?
Most / a lot of these existed before functions existed. Also functions don’t (easily) allow you to have a ready built data / dataset. The nice thing about a UBAQ /BAQ is that you can pull data and then act on it vs a function you’d have to either Take the DataSet as an input or generate it with code.
2 Likes
Got it, Thx!
We went line in January of this year… we have 2 data directives and zero method directives. Vanilla Epicor babyyyy!!!
…on that note, if anyone has some suggestions for BPMs that we may wanna set up I am all ears! Just now getting to the point where I understand how all of this stuff works. Still struggling to set up alerts that filter to the plant though, so still more learning to do! Figuring this stuff out is quite daunting. I wish there was just a repository of BPM examples.
2 Likes
As with every modification, as few as you possibly can. Look for ways to improve the utilization of base features, and improve business processes. In other words, don’t look for cool ways to modify the software, look for ways to make peoples jobs and lives better. My two cents.
6 Likes
Method: 69
Data: 66 (34 change log)
UBAQ: 4
All widgets, baby!
Well, actually that’s not entirely true. There’s a small handful from consultants that are all code. 
2 Likes
Method: 217
Data: 253
UBAQ: 103
And around 50/60 more all combined in Pilot(soon to be moved to LIVE). That’s it 
1 Like
Method: 99
Data Directive: 28
UBAQ: 189