uxtechnicianownerfilter query update for work execution work center

this is in response to case TS013850145 where it was indicated this would not be accepted as a bug but rather needs to be submitted as an enhancement. We are still of the opinion this is a bug, however.

summary is as follows:

The data issues are summarized as follows:

Current query is

istask=0 and owner = :&personid& or ownergroup in (select persongroup from persongroupteam where respparty=:&personid&)

• history workorders are displayed. should this be the case? I would assume these should be filtered out otherwise the listing will build and build.

• if you set up a test record where you take a task workorder and set the ownergroup to one of the persongroups that the user belongs to, you will see that it now shows in work execution. I am assuming the desired functionality is that this should not display.

login as wilson

choose a persongroup in the persongroups application and add wilson as a member

go to activities and tasks and choose an activity workorder and set ownergroup to the persongroup noted above

launch work execution and note that this workorder above now displays

• if you set up a workorder that is woclass other than WORKORDER and add the user as owner then that workorder will display where I am assuming the desired functionality is that you would not want it to display. For example in our system we have icd with Maximo together. Thus, if I go to the changes application and set a change record to be set to myself as the owner when I launch work execution, that record will display.

We have found that the query

(woclass =(select value FROM synonymdomain where domainid ='WOCLASS' and maxvalue = 'WORKORDER') and historyflag=0 and istask=0 and (owner=:&personid& or ownergroup in (select persongroup from persongroupteam where respparty=:&personid&)) )

resolves the above issues. Additionally with the current query running on a workorder table with millions of records (30M+) we found significant performance issues with the load of the application due to this query utilizing full table scans and taking a very long time to run. With the updated query above the query will utilize the workorder_ndx3 index in the execution plan and for us personally decreased load time from minutes to seconds.