DRD Test cases

User Tools

Site Tools

Trace:
tc-34

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
tc-34 [2025/07/31 02:50]
20.171.207.163 old revision restored (2025/05/26 21:32) 		tc-34 [2025/08/18 03:19] (current)
20.171.207.181 old revision restored (2025/08/01 12:23)
Line 1: Line 1:
-TRK Dispatch: Automatic filling of the location at "Deadhead" type stops+====== TRK Dispatch: Automatic filling of the location at "Deadhead" type stops ======
  
-The document loada has a stop of a special type "deadhead". One of its uses is to indicate the location of the track before making the first stop. Usually this placement coincides with the placement in the last stop of the previous executed document for this truck.+The document load has a stop of a special type "deadhead". One of its uses is to indicate the location of the track before making the first stop. Usually this placement coincides with the placement in the last stop of the previous executed document for this truck.
  
 To make it easier for the operator to create a deadhead stop without having to manually open loads, an automation feature has been created to find the previous truck placement. To make it easier for the operator to create a deadhead stop without having to manually open loads, an automation feature has been created to find the previous truck placement.
Line 7: Line 7:
 In the DRD system for each truk, at the time of creating a new load, there may be several documents in the Dispatch state. The dates of loadings, unloadings from different documents may overlap or coincide, so it is difficult to automatically determine the current position of the car only on the basis of data from the stops. In the DRD system for each truk, at the time of creating a new load, there may be several documents in the Dispatch state. The dates of loadings, unloadings from different documents may overlap or coincide, so it is difficult to automatically determine the current position of the car only on the basis of data from the stops.
  
-To automatically determine the last location, the event of transferring the load to the "dispatch" state is used. Thus, the logic of the program is simplified, but it becomes necessary to monitor the correct sequence of transferring documents to the “dispatch” state. This is an important nuance and must be remembered by operators.+To automatically determine the last location, the event of transferring the load to the "dispatch" state is used. Thus, the logic of the program is simplified, but it becomes necessary to monitor the correct sequence of transferring documents to the “dispatch” state. 
  
 +   This is an important nuance and must be remembered by operators.
 +
 +===== Preparing =====
 To enable the automatic detection of the previous location of the track, check the box "Show Deadhead location prompt" in "Settings/Trucking preference/Preference". To enable the automatic detection of the previous location of the track, check the box "Show Deadhead location prompt" in "Settings/Trucking preference/Preference".
 +{{ :deadhead_settings.png?nolink&900 |}}
  
-When the “Show Deadhead location prompt” checkbox is checked, each change of truck in the load causes a dialogue with the question “Set Origin / Deadhead Location?”, And then, if agreed, the “Set Trucks Origin (Deadhead)” window. In this window, in the "City" "ST" Zip" fields, the location taken from the last stop of that load of this track, which was transferred to the "dispatch" state last, will be entered.+When the “Show Deadhead location prompt” checkbox is checked, each change of truck in the load causes a dialogue with the question “Set Origin / Deadhead Location?”, 
 +{{ :deadhead_question.png?nolink&400 |}} And then, if agreed, the “Set Trucks Origin (Deadhead)” window.  
 +In this window, in the "City" "ST" Zip" fields, the location taken from the last stop of that load of this track, which was transferred to the "dispatch" state last, will be entered.
 These fields can be changed manually right in the dialog or later by editing the stop line. These fields can be changed manually right in the dialog or later by editing the stop line.
  
-Test order:+===== Testing: =====
  
 1. It is necessary to prepare 2 loads for a certain truck, in which it is necessary to fill in the driver, truck, customer, gross pay and fields with placement in stops. 1. It is necessary to prepare 2 loads for a certain truck, in which it is necessary to fill in the driver, truck, customer, gross pay and fields with placement in stops.
 +{{ :deadhead_load1.png?nolink&600 |}} 
 +{{ :deadhead_load2.png?nolink&600 |}}
 Fields with dates in the stops do not need to be filled in. Fields with dates in the stops do not need to be filled in.
  
 2. We transfer the first of the created documents to the dispatch state. 2. We transfer the first of the created documents to the dispatch state.
  
-3. Create another document. After selecting a truck, a dialog should appear that should show the location of the last stop of the document from point 2.+3. Create another document.  
 +After selecting a truck, a dialog should appear that should show the location of the last stop of the document from point 2. 
 +{{ :deadhead_set_truck_location.png?nolink&600 |}} 
 +{{ :deadhead_load3.png?nolink&600 |}}
  
 4. We transfer the second document to the dispatch state. 4. We transfer the second document to the dispatch state.
tc-34.1753919409.txt.gz · Last modified: 2025/07/31 02:50 by 20.171.207.163

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki