Idea Description
Currently, when attempting to cancel a Work Activity in WACS that has already been sent to OFS, the cancellation fails if the activity status in OFS is “Not Done.”
The system returns the following SOAP error:
“Activity with this status cannot execute this action.”
According to OFS behavior, activity cancellation is only allowed when the activity status is Pending or En Route. Because of this restriction, WACS cannot cancel activities once they are marked Not Done in OFS.
Current Behavior
When users attempt to cancel a Work Activity in WACS after the technician has marked the activity as Not Done in OFS, the cancellation request fails and an error is displayed.
As a result:
- The activity cannot be cancelled from WACS.
- The systems become operationally inconsistent.
- Users must manually manage the activity status.
Business Impact
This limitation prevents users from cancelling activities that are no longer required once they reach the Not Done status in OFS.
Impacts include:
- Increased manual effort to manage activities.
- Potential inconsistencies between WACS and OFS.
- Operational inefficiencies for dispatch and work management teams.
Example Scenario
- Create a Work Order in WACS.
- Create a Work Activity and submit the Work Order for approval.
- Approve the Work Order, which sends the Work Activity to OFS.
- In OFS, the technician starts the activity and marks it as Not Done.
- The user attempts to cancel the Work Activity in WACS.
- The system returns the error:
“Activity with this status cannot execute this action.”
Requested Enhancement
Enhance the WACS–OFS integration to support cancellation of activities from WACS when the OFS activity status is Not Done, or provide configurable handling for this scenario.
Possible solutions:
- Allow WACS to cancel the activity and synchronize the appropriate status in OFS.
- Provide configurable mapping or logic to handle cancellation for Not Done activities.
- Handle the OFS API error gracefully and allow WACS workflow to proceed.