===2.3.68. Route Controller=== __Extension: Route Controller – Controls the Routes__ {{ :implementation:wms:ose:extensions:route_controller.png |Route Controller}} The settings below is to customize the grids on the route planning. There is a view to get the data to show on the grid. The order in which the columns are on the view, will also be the order in which they will appear in the grid. \\ Per view there are some mandatory fields, so the system knows what column to use for certain values. **//Pick list (proposals) without route (Bottom-left grid)://** Required fields: * DocType, DocEntry, PickListStatus, PmxWhsCode **//View name – Open pick list (proposals)//** \\ The name of the view that will be used. **//Order by – Open pick list (proposals)//** \\ The order by for the view. The text ‘ORDER BY’ does not need to be entered here. **//Localization key – Open pick list (proposals)//** \\ The localization key to use. This is used to translate the grid. \\ Below is a reduced translation tag for the standard grid. \\ It shows how to translate, or if needed how to hide a columns. False Logex.AddOn.RoutePlanningControl.GrdPicklistsWithoutRoute SBOGUIAP False Columns[1].HeaderText CONVSTR False Type 3 False Type 16 False Columns[13].Visible CONVBOOL False False 3 False False 16 **//Route details (Right grids)://** Required fields: * RouteDocEntry, RouteLineNum, Sequence, DocType, DocEntry, PickListStatus **//View name – Route details//** \\ The name of the view that will be used. **//Localization key – Route details//** \\ The localization key to use. This is used to translate the grid. **//Open routes (Top left grid)://** Required fields: * DocEntry, PmxWhsCode **//View name – Open routes//** \\ The name of the view that will be used. **//Order by – Open routes//** \\ The order by clause for the view. The text ‘ORDER BY’ does not need to be entered here. **//Localization key – Open routes//** \\ The localization key to use. This is used to translate the grid. **//Route header extra information://** \\ This will show additional information for the route in the route planning screen. \\ This view can contain multiple rows/columns for the route. \\ All that data will be combined into 1 line of text. \\ Values of rows/columns will be separated by the separators defined below. Required fields: * DocEntry **//View name – Route details header//** \\ The name of the route that will be used. **//Order by – Route details header//** \\ The order by clause for the view. The text ‘ORDER BY’ does not need to be entered here. **//Column separator – Route details header//** \\ The separator between columns. **//Row separator – Route details header//** \\ The separator between rows. **//Routes are by default POD? (Y/N)//** \\ When creating a new route, this setting will automatically set whether the route is used for the 'Proof of delivery' functionality.