Last updated on FEBRUARY 17, 2017
Applies to:Siebel Field Service - Version 22.214.171.124.16 [IP2014] and later
Information in this document applies to any platform.
On : 126.96.36.199.16 [IP2014] version, Field Service
Customer upgraded and employees are no longer seen on the dispatch board
All employees in the service region should be seen on the dispatch board
The issue can be reproduced at will with the following steps:
- Added a custom PDQ for the FS Dispatch Board which is named as '1' so is
invoked upon opening the Dispatch Board.
The custom PDQ is:
'Employee'.Search = "[First Name] = ""Employee1""" << Please note Employee1
is one of the employees in the service region
'Employee'.Sort = "First Name, Last Name"
'Service Region'.Search = ""
'Service Region'.Sort = "Name"
'Action'.Search = ""
'FS DB Unplanned Activity'.Search = ""
'FS DB Unplanned Activity'.Sort = ""
- This opens the Dispatch Board and shows all employees in the
employee.search part of the PDQ; no issue so far.
- The customer then fires a second PDQ by using the PDQ dropdown.
As noted in bug # 22923888 - DISPATCH BOARD GANTCHART APPLET DOES NOT GET
REFRESHED ON CHANGING THE PDQ
the child applet changes to show the activities in the child list applet
This works as expected.
However, when the zoom buttons (1/4, 1/2, 1, 2, 4) are pressed, the dispatch board shows all the
employees from the new PDQ.
So the employees are not updated upon PDQ but only when the dispatch board is
This is incorrect and should update the employees in the PDQ in the dispatch
board, it does not therefore compare with the outcome of bug # 22923888, which has now been deemed incorrect
The issue has the following business impact:
Due to this issue, users cannot select any employees via a PDQ to assign activities to them
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms