Skip to main content

Understanding Dex Steps

Driver/rep guide to the DEX steps on Encompass Mobile (SendInvoice, SendTotal, StoreResponse, ErrorMessage) shown in the invoice DEX audit, to troubleshoot DEX failures. Requires v23.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 23.01

Steps

1. PFD Type

The type of device that is selected to be DEXed. This will include the serial number of the device and PFD if it was DEXed on a PFDex unit or GKP if it was DEXed on a Gimme Key device

2. SendInvoice

If DEX is connecting, SendInvoice status will appear in invoice DEX audit. SendInvoice represents the connected data and the current DEX status is connecting. If successful, it will enter the SendTotal state, and the data will be sent from the handheld to the DEX device. And the handheld terminal will prompt that the connection is successful. If it fails, the connection fails and ErrorMessage is added.

2. SendTotal

When the DEX connection is successful, it will enter the SendTotal state. At this time, the correct DEX operation should be that we view the invoice data to be modified in the DEX system and modify it. After the modification is completed. The handset will perform get response. At this time, the DEX system will send to the handheld terminal, and the handheld terminal will receive. Successful reception will lead to StoreResponse. Failure will prompt 'StoreResponse not received. The connection may have dropped, or the Duns and UCCI are not configured correctly. Please check your configurations and try to DEX again'。

3.StoreResponse

When the handheld terminal receives the data modified by DEX, it will be reflected by the StoreResponse status. At this time, the handheld terminal will update the data of the current invoice and recalculate the price according to the current invoice. After the StoreResponse is completed, the invoice will be locked.

4.ErrorMessage:

The function of ErrorMessage is to clearly know the reason of DEX failure. If we have problems in the normal operation of DEX, there will be an error message. At this point, we can learn why it failed from ErrorMessage. Therefore, in DEX operation, please do not close the connection or interrupt at will.

Fields And Definitions

If the data in invoice DEX audit is not present it is likely that the DEX operation was not performed. The connection has not been executed. It may be that the Bluetooth connection is not properly operated. Or customer and settings related DEX configuration is not added.

Did this answer your question?