What is the best practice mechanism for creating a new temporary work object from a REST service endpoint in Pega?
I'm working in Pega 8.3.1 writing a headless application which is only accessed via REST service call (Service REST defined in Pega). I've been digging through all the documentation I can find, but so far, everything I see is based on using the app studio to create a temporary work item. I need to create a temporary work item to minimize unnecessary Pega code and DB transactions so that the service responds as quickly as possible. Also, we will not be persisting the result anyway.
My Question: What is the best practice mechanism to instantiate an instance of the work class, making all of the 'usual' work resources available (declarative network, decisions, flows, activities, data transforms...all of the core platform components) to the temporary object, which we then discard once the response has been sent?