Current Functionality
The `ATW1CreateMobileWOInboundComm` Inbound Web Service (IWS) and its related Business Object (`W1-CreateMobileWOInboundComm`) are utilized to create mobile work orders and activities from another system. We found that this API needs to have an Asset ID and a Node ID (Asset Location) filled in so the transaction will be successful.
Business Use Case
We need a business requirement to create and finish activities from another external system (for instance, Oracle Field Service) that are associated with a particular location but not with a particular asset. For instance, routine maintenance or inspection activities with location-based activities. The user front-end interface in WACS currently accommodates this functionality, where a user can create a Work Activity with only an association with a Node ID without the presence of an associated Asset ID.
Yet, because the API requires both fields, we cannot automate this business process through integration, thus a technical workaround is required. This restriction blocks a straightforward, out-of-the-box integration for a typical utility use case.
Requested Enhancement
We ask that the `ATW1CreateMobileWOInboundComm` IWS be changed to support creation of a mobile work order or activity with only the Node ID (Asset Location) filled in, and have the Asset ID as an optional field. This would bring the API's functionality in line with the default behavior that is currently present in the WACS user interface and accommodate a common field service business need.
Such an improvement would facilitate more effective and compact integration for location-based work, making less of an occurrence for custom logic and encouraging use of out-of-the-box product features.