Skip to main content
Solved

Transfer Work Assignments to Mobile database task

  • March 19, 2026
  • 4 replies
  • 31 views
JBurke-HexA
Sidekick (Customer)
Forum|alt.badge.img+4

My Org is looking to implement mWO for internal maintenance tasks, and we want to be able to automate the transfer to mobile process so an incoming fault report can be put into the pool quickly and without supervisor intervention (faults can occur on 2nd/3rd shift and there aren’t always supervisors then). Seemingly the only option for this is scheduling Transfer Work Assignments to Mobile task to run every 15 minutes.

when one manually transfers to mobile, there are the two sliders for pool and pool-keep, how can the database task Transfer Work Assignments to Mobile be configured to do either? Specify the “Allocated_To” setting as “pool”?

(I also wish the transfer window option wasn’t “beginning of time until today plus x days”)

or is there an API call I can make with a workflow or pl/sql event action to transfer on fault report creation vs. the scheduled task? I can’t find any obvious APIs to use for this.

Best answer by anmise

I attempted to make a workflow that used the WorkTaskHandling API call, but it doesn’t work due to a SAVEPOINT/concurrent execution issues - I could probably do the Fnd_Event_Action_API.Action_Executeonlinesql wrapper technique as a workaround, but I think it will be easier to build the REST call into the external app that triggers the fault report to begin with vs. the workflow script convolutions required to build the REST string.


 

We’ve changed the mechanism slightly so that it’s possible to use in a BPA from 25R2 and beyond. 

 

4 replies

skullk
Hero (Employee)
Forum|alt.badge.img+11
  • skullk
  • Hero (Employee)
  • March 20, 2026

The existing schedule task only considers the assigned work. It does not consider unassigned tasks so cannot transfer them into pool through the scheduled task. 

Can you please raise this as a request for future considerations?

Regarding the API calls, I don’t have much information. ​@Bandula have you got any ideas? 

Thanks

Sampath

JBurke-HexA
Sidekick (Customer)
Forum|alt.badge.img+4
  • JBurke-HexA
  • Author
  • Sidekick (Customer)
  • March 24, 2026

I attempted to make a workflow that used the WorkTaskHandling API call, but it doesn’t work due to a SAVEPOINT/concurrent execution issues - I could probably do the Fnd_Event_Action_API.Action_Executeonlinesql wrapper technique as a workaround, but I think it will be easier to build the REST call into the external app that triggers the fault report to begin with vs. the workflow script convolutions required to build the REST string.


 

A
Superhero (Employee)
  • anmise
  • Superhero (Employee)
  • Answer
  • March 25, 2026

I attempted to make a workflow that used the WorkTaskHandling API call, but it doesn’t work due to a SAVEPOINT/concurrent execution issues - I could probably do the Fnd_Event_Action_API.Action_Executeonlinesql wrapper technique as a workaround, but I think it will be easier to build the REST call into the external app that triggers the fault report to begin with vs. the workflow script convolutions required to build the REST string.


 

We’ve changed the mechanism slightly so that it’s possible to use in a BPA from 25R2 and beyond. 

 

    JBurke-HexA
    Sidekick (Customer)
    Forum|alt.badge.img+4
    • JBurke-HexA
    • Author
    • Sidekick (Customer)
    • March 27, 2026

    I ended up just doing the REST call from my companion app which works perfectly. Not really any help to anyone else who runs into this and finds this thread though, sorry.

    (Funny coincidence that it was Paul Harland who requested that API change, as I saw how many extra cleanup steps and script blocks he had to make for a different workflow that was another instance where the API method didn’t work and he had to fall back to a REST call. I felt his pain 😂)

    Terms & ConditionsCookie settingsAccessibility statement