No clear way of scheduling jobs / doing anything outside the main transaction

Currently, there is no clear way of scheduling jobs, or doing anything other outside of the main transaction in every request. There has been a Issue on this, but it is no longer relevant due to changes in the OperationsDispatcher.

While there is an after_process_operations callback on the controller, how to get any data on the updated/created/viewed resource is not clear from the docs, and also not immediately clear from the source.

Any information on this would be greatly appreciated.

Start with the controller's after_process_operations callback and the OperationsDispatcher, then compare the current source with the existing documentation. Clarify how data for updated, created, or viewed resources can be accessed and how work can be scheduled outside the main transaction. Done means the documented guidance answers these use cases without relying on the superseded issue 503.