When modifying overrides the notifications page doesn't currently wait for the effective processor to run and update the local Oracle cache. This means when making edits users don't see any effect and must currently click page refresh until the changes are propagated back to the Oracle cache.
In contrast, when modifying registration information edits are made directly to the Oracle database (and Kafka messages are then sent without waiting for the effective processor to run or Kafka to notify all clients). When inventory pages are reloaded on edit the feedback is therefore immediate as pages read directly from the Oracle database.
When modifying overrides the notifications page doesn't currently wait for the effective processor to run and update the local Oracle cache. This means when making edits users don't see any effect and must currently click page refresh until the changes are propagated back to the Oracle cache.
In contrast, when modifying registration information edits are made directly to the Oracle database (and Kafka messages are then sent without waiting for the effective processor to run or Kafka to notify all clients). When inventory pages are reloaded on edit the feedback is therefore immediate as pages read directly from the Oracle database.