Extend Custom Business Object Instance Shows No Task Runner When Clicked
The error no task runner
What does "Extend Custom Business Object Instance Shows No Task Runner When Clicked" mean in Workday Extend?
Clicking an instance of an Extend custom business object from outside your Extend app does nothing useful. Workday has no view task registered for that object, so it cannot route anywhere and shows a no task runner message instead of opening a page.
Quick fix
Inside your PMD, render the instance as a link or button widget pointing at your own view page and passing the instance id as a parameter, rather than relying on Workday to route the bare instance click.
Permanent fix
Treat Extend custom business object instances as unroutable outside your app. Surface them only through Extend pages that define their own navigation, and where users need to reach one from a report, give the report a link column built from your app page URL instead of the bare instance.
Troubleshooting
- Note exactly where the instance was clicked from. A custom report, a search result or a delivered Workday page all sit outside the Extend app context, where no route exists.
- Reproduce the same click from inside your Extend app page. If it works there and fails elsewhere, the object and its data are fine and the missing piece is the route, not security.
- Check whether the business object has a model component task defined and whether that task is actually exposed as a related action.
- Confirm the user has access to the Extend app and its security domain, so you can rule out a permission problem presenting as a routing problem.
- If the click has to work inside a PMD, stop relying on Workday to route the raw instance and render it as a link or button that carries an explicit route.
Was this helpful?