Comments
We clearly need this too in realtime .. as before in OM.I don't understand why this "basic" standard behavior has changed.And like Tori explains ! Even not allowing us to stop and continue existing journeys at all!This is not workable!!If a segment is to be updated (add / remove members), it should be updateable even for live segments and live journeys.Why else do we set frequency settings in a journey on a segment .. I can image there's a challenge in a setup to allow it but this should have been a no-brainer to have it included from the start.
Working with a client that has also expressed concerns about this. When digging into the multi-level standard cost details, it appears that consistently all "Direct manufacturing" or "Indirect costs" of type "Setup" are not included (values are all zero even though the cost details for just that level are non-zero).
It is a real problem on BC.In the real life, it is commun to have pick a component for a production order and detect a problem on this component. this component must be moved to a quality control bin and a new warehouse pick is then needed. But at the production order level, this movement is not considered.