WorkManager for CUD operations for an Android Room database based on "persistence" of work?

Question

I was looking at saving some data to my Room database and was reevaluating as there are some places in my repositories where I am extending AsyncTask (I'm still using Java) and wanted to check on the state of things to see if it was a good time to swap them out. I saw this reference in the Android developer site on Approaches to background work.

• All persistent work: You should use WorkManager for all forms of persistent work. Immediate impersistent work: You should use Kotlin coroutines for immediate impersistent work. For Java programming language users, see Threading on Android for recommended options.
• Long-running and deferrable impersistent work: You should not use long-running and deferrable impersistent work. You should instead complete such tasks through persistent work using WorkManager.

I started using WorkManager for an API which needed to be called, but for which I could not rely on network connectivity. Because I'm using Room, which is persistent, it seems like I should be using WorkManager.

It defines persistent work as:

• Persistent work: Remains scheduled through app restarts and device reboots.

A database insert/update/delete is persistent by this definition. Scheduled throws me off a little, as I want it to be immediate, but according to this chart that would still apply.

Is anybody using WorkManager as the mechanism for CUD operations in their repositories and if so, do they have an example?

It would be great to see how this all works in an update fragment. If a single item is selected and I am viewing it in a fragment, when changes are made I would need to update the database using a Worker class and view the data using a LiveData object, correct?

Inserts and returning the id (or object) would be interesting to see as well.