|
|
|
|
|
by solardev
698 days ago
|
|
Internal stakeholders are still users, and if they have a constant need to change business logic flexibly and without involving the devs every time, maybe it's time to build them a configurable workflow? It might be worth taking a look at other self-service flow builders like the kind commonly used in marketing & analytics, where you set up a customer journey tracking page to page and write different rules depending on it, or where you set up an email drip campaign based on various configurable criteria. The more generic and less usage-specific version of that is something like Zapier (for non-devs) or Make.com (for devs). With that sort of abstraction, I guess your devs end up making a rules engine with a GUI and a bunch of modular nodes and integrations, like "if marketing software sends this webhook" or "send transactional email" or "increase customer value in CRM" or "notify staff to call this person", etc. that the powers that can then clobber together in whatever way they like. |
|