As of version 22.02, Dispatch form Extended Menu contains a “Check Dispatch Close” option.  This process will run a series of checks and prevent putting a call in POST status unless the Call can be closed based on the dispatch close logic.  This works similarly to Check Project Close–it will present a Modal listing any close errors on a Dispatch, but the close errors will present as error messages, instead of a grid.

Note:  There will be no zoom function on the error handling form, but it will indicate which record is preventing close.

Checks on the Check Dispatch Close:

• Check for linked GL Journal Entry (See Check Project Close logic)
• Check for unpaid expenses
• Check for open Quote/Orders
• Check for RMATestQ items that have not yet been processed
• Check for RMA items that have not yet been processed
• Check for invoices that are not posted
• Check for PO’s that have been received but not vouchered
• Check for PO’s that have line item that have not yet been received
• Check for vouchers that have not been posted
• Check for Orders’s that have line item(s) that have been picked
• Check for Orders’s that have line item(s) in DATAENTRY status
• Check for linked Unposted time bills

Note: User must have HELPDESK permission to access this menu option.

In addition, General Codes for Call Status that have the value for “Closing Entry” set to Y, will not allow a call to move to that status if the closing logic fails. This may prevent a call from programmatically moving to a status if a final invoice is created but not yet posted. Users may need to adjust their workflow to take advantage of this feature.

Common Questions:
Is there a way to lock down service calls so that they cannot be closed out or completed if items are still in data entry?
Can we prevent calls from being closed if they still have active items?
Can we require calls to be in a certain state before closing?