Known Issues
The known issues at the time of this integration release are:
Even after the supervisor locks an activity, assistant mobile worker is able to perform the asset level operations.
Undo use item is getting displayed in day2 when the item is used for day1 in multiday activity.
Error message is not displayed in the Oracle Field Service mobile screen when the crew member starts the successor activity before the predecessor activity.
In the Oracle Field Service mobile screen, when the crew navigates to the Activity Dependencies tab, the same activity is displayed on the Successor and Predecessor tab.
Admin Sync known issue:
The enumeration “wam_actType_psh” to maintain the relationship between the activity types and PSH associated with the activity types. It stores the PSH details as part of the name for the enumeration label. In Oracle Field Service, there is a restriction on the size of the name. If there are more than 5-6 PSHs for that activity type, Oracle Field Service displays a 500 error.
User cannot click the Calendar in IOS (all date-time and date fields).
Warning message is not displayed when an issued asset is already installed at the location and the tries to install an asset from the truck. The asset is getting replaced. Since the asset should not get replaced, perform the undo install operation for the asset which is already installed and then perform other operations.
The Issued Component label is not displayed in the existing pool of components that are issued to activity.
User should not refresh the activity in the Admin console, as resource preferences are not displayed after refresh activity.
Refresh activity operation is creating duplicate locations in the existing pool when an asset from the truck is installed, the activity is refreshed, and then undo the installed asset.