Extended Crew Size Always Set To 1 When Activity Is Being Updated
(Doc ID 2529080.1)
Last updated on DECEMBER 05, 2019
Applies to:Oracle Utilities Mobile Workforce Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 2.3]
Information in this document applies to any platform.
On : 184.108.40.206.0 version, System Wide
Crew Size always being set to 1 when Activity is being updated i.e. Activity Status changes
Currently, we are encountering a base issue where the Crew Size (Override Capabilities of the Activity) that we extended is ALWAYS being set to 1 when the Activity is updated i.e. Activity status changes from Being Scheduled to Queued for Dispatch. We noticed that this is being done by the base Pre-Processing Algorithm M1-DFTACTDTL in the M2-Activity BO. The base algorithm contains a logic that will ALWAYS update the crew size to 1 regardless if the action is ADD or UPD. The existing code should only be applicable during ADD action. If its during UPD action (e.g. updating the Activity Status to Queued For Dispatch) the base code need to READ first the activity details and that is what they need to check if its BLANK instead of ALWAYS using the values on the parm/hard/request/ regardless if action is ADD or UPD.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!