Bulk Materials Ideas
Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.
Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.
Support for Multiple instances of Scale Tickets Screens should have native functionality.
Current Vulcan Materials solution involves a .vbs script ‘LaneApp.exe’ to start another instance of scale tickets with a separate ‘idn’ file to allow simultaneous loadout. Apex Program Security has to be setup to recognize ‘LaneApp’ as a native Apex program and enable it to be seen on the menu tree. This is a lot of ‘tribal knowledge’ setup that should really be built in to address what is probably a widespread need.
Chris, we are already doing what you suggest for Cash tickets. One of the things we would like to avoid is the use of File > Print Setup as it often doesn't get changed back and tickets get printed inside instead of outside and vice versa.
What we are looking for is the ability to have multiple instances open for the same scale. For example, truck tickets at the scale but for one reason or another, the clerk has to freeze the weight and the driver has to come inside. The clerk can't ticket the next truck until the current one is fixed.
There are other situations but they aren't coming to mind right now. I would be interested in exploring the duplicate scale concept but would that not involve a separate login?
Any updates on this?
Just following up on this..has there been any progress on this functionality?
This idea has been accepted. This is closely related to AP-I-30 Auxilary Program Launcher. Both ideas will be worked on. We will now begin prioritizing and planning the work required to implement your idea. You will be notified when the planning process is started.
Just as a comment, we have a need to specify a specific workstation ID when launching the scale tickets screen in addition to a unique identity (to restrict each screen to a specific scale number and load station...which is really locked down by calling the program with a specific workstation that has these restrictions). If a menu item shortcut could be created to specify both an ID and a workstation, it should eliminate the need for our custom vbs script.