Decline (Report To User) Status Reason Usage Always Creates Missing Capability To Do (Doc ID 2346934.1)

Last updated on SEPTEMBER 03, 2024

Applies to:

Symptoms

On : NA version, System Wide

ACTUAL BEHAVIOR
---------------
Decline (Report to User) Status Reason Usage always creates Missing Capability To Do

In recent versions of MWM, the base M1-AsmtDclnd Script was updated to provide more flexibility with the Decline Status Reasons used by Mobile Workers. Previously, “Missing Capability” and “Unable to Reach” were hardcoded with specific actions. “Missing Capability”, for example, would always create a To Do, while “Unable to Reach” would not.

The “Return Assignment Rules” (M1-AsmtDclnd) Script was updated to reflect the newer Status Reason Usages of “Decline (Report to User)” and “Decline” in place of the prior two options. “Decline (Report to User)” is the one that can be used to create a To Do when the Mobile Worker selects this option.

It’s very helpful that this was updated for flexibility. It looks like the subsequent Script, M1-DeclnShft, still references the hardcoded options. More importantly, it calls a To Do Type “M1-TSKDC”.

Since this To Do Type is hardcoded for use on an “Decline (Report to User)” Status Reason Usage, it should also be generic like the other Scripts were modified to be. Instead, it had a description of “Activity Decline – Missing Capability”. This Description would be much more helpful if it was simply “Activity Declined by Crew” to create less confusion for dispatchers about what the Assignment was declined.

Additionally, the To Do Message should be updated to say something along the lines of “Crew <CREW NAME> has declined this Activity due to %1”, where “%1” is replaced by the Status Reason Description.

Changes

Cause