Comments
We've developed our own solution for that bcs. of the limited usage.Some features can be activated per user and even per session, others may be activated only once because they have a "destructive" nature related to the data that may be converted etc (irreversible). Not to forget about (de-)activation-triggers (also for licensing) and so on.The existing feature-flag-implementation is not sufficient to cover these requirements.So the idea is good, but just opening the feature-flags to app-developers imho is not enough.
I have had several clients that would like to prevent reservation from receiving areas where material is waiting to be putaway (putaway separated from registration and work not open until user is ready to put away). Locations or location profiles should be able to be designated as "not reservable" to orders (similar to not being available for warehouse work), because the reservation to the order when material isn't in a location where it should be picked causes issues.