Skip to main content
Question

mWO : UI of Request task changed to Pickup task

  • Apr 21, 2026 6:36 AM UTC
  • 8 replies
  • 77 views

Forum|alt.badge.img+8

Hi,

 

My customer is experiencing this problem where in the my work l → Assignment details, they are seeing Pickup task information instead of Request task information.

This is how the UI used to be 

 

Now they are seeing pickup task information.

Any idea how this can be resolved?

checked in MAUI app and classic app both.

8 replies

Forum|alt.badge.img+9
  • Hero (Employee)
  • Apr 21, 2026 11:44 AM UTC

Is the task you are looking at in this case not a Pickup-Task?


Forum|alt.badge.img+8
  • Author
  • Sidekick (Employee)
  • Apr 21, 2026 12:22 PM UTC

This is not a pick up task.  The above image was what it used to look like


  • Superhero (Employee)
  • Apr 21, 2026 12:59 PM UTC

​@NEJANO which cloud version is this for?  There used to be an issue like this a long time back, but have not seen it since.

 


Bandula
Hero (Employee)
Forum|alt.badge.img+13
  • Hero (Employee)
  • Apr 21, 2026 5:58 PM UTC

Hi ​@NEJANO 

We can observe all tasks appearing as pickup tasks when there is a problem in the PL/SQL view JT_TASK_MOB_ALL, which is the base for the JtTask entity.

In PL/SQL, check whether the view is valid and whether its columns match those in an internal (working) environment.

 


Bandula
Hero (Employee)
Forum|alt.badge.img+13
  • Hero (Employee)
  • Apr 21, 2026 6:10 PM UTC

You may check IFS Cloud Solution Manager/Mobile Apps/Logs and Queues/Logs  and filter for entity JtTask and see whether any errors 


Forum|alt.badge.img
  • Do Gooder (Partner)
  • Jun 10, 2026 3:52 PM UTC

Hi ​@NEJANO were you able to find the root cause for this issue?


Forum|alt.badge.img+8
  • Author
  • Sidekick (Employee)
  • Jun 15, 2026 6:04 AM UTC

​@ERMECA This was due to a problem with a custom field. Try unpublishing and republishing the relevant entity

 


Forum|alt.badge.img
  • Do Gooder (Partner)
  • Jun 15, 2026 2:25 PM UTC

Thanks for getting back ​@NEJANO, issue is resolved now. In our case also root cause was a custom field.