You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user adds an incorrect gateway, what is the appropriate method to correct the mistake? Most gateways can have the status changed to "Discarded" (System Ref Id 196) so the gateway is not active.
What happens if the Will Call or Delivered gateway is mistakenly added? A user added Will Call by mistake and setting the status of the Will Call gateway to be Discarded did not correct the issue and no gateways were available for the user when right-clicking in the Tracking grid.
The only way to force the correct gateway to be added is to use the API InsertJobGateway call.
The text was updated successfully, but these errors were encountered:
In the image below, the Will Call gateway is marked as Discard but the job is marked as delivered. When right-clicking in the Tracking grid, no gateways are available.
1. Adds Route to the "RevertGateway" context menu
2. Adds condition in scripts for context menu clicked and adds of logic to redirect into RevertGateway action of JobGatewayController with Job ID as parent ID
3. Adds of action method with required parameter
If a user adds an incorrect gateway, what is the appropriate method to correct the mistake? Most gateways can have the status changed to "Discarded" (System Ref Id 196) so the gateway is not active.
What happens if the Will Call or Delivered gateway is mistakenly added? A user added Will Call by mistake and setting the status of the Will Call gateway to be Discarded did not correct the issue and no gateways were available for the user when right-clicking in the Tracking grid.
The only way to force the correct gateway to be added is to use the API InsertJobGateway call.
The text was updated successfully, but these errors were encountered: