Cybertrax 2.1 Client (Q and A)
From UG
(Difference between revisions)
(→Appendix. Questions and Answers) |
|||
Line 1: | Line 1: | ||
[[Category:Cybertrax 2.1 Client]] | [[Category:Cybertrax 2.1 Client]] | ||
- | == | + | == --[[User:Alex|Alex]] 19:31, 19 June 2010 (EDT) == |
+ | 1] Do we need to limit # of lines on internal to 1 line? (blocking adding lines) | ||
+ | |||
+ | 2] Should jag users be able to edit commod table created by shipper at all? | ||
+ | |||
+ | == Original == | ||
* '''Q''': <!--Alex--> ''How to avoid situation when planners ignore some new shipments for a long time? '' | * '''Q''': <!--Alex--> ''How to avoid situation when planners ignore some new shipments for a long time? '' |
Revision as of 23:31, 19 June 2010
--Alex 19:31, 19 June 2010 (EDT)
1] Do we need to limit # of lines on internal to 1 line? (blocking adding lines)
2] Should jag users be able to edit commod table created by shipper at all?
Original
- Q: How to avoid situation when planners ignore some new shipments for a long time?
- A: Currently this is not required for phase 1 and will be addressed for possibly phase 2. Although, suggestion was given such as auto approve or auto reject, based upon a certain amount of time. Yet this is something that would need to be further discussed and defined by Elizabeth Arden.
- Q: When Jag operator may see or "start to move" CT?
- A: Once a record is approved by a planner or an E.M, that shipment will then show on the live tab for both the internal & client applications
- Q: What additional read-only fields edited by Jag oper Shipper will see?
- A: Trucker, Estimated Pick up date, Actual Pick up date, Estimated Delivery date, Actual Delivery date, Approved (with name of person who approved, including the date & time), Hold (with name of person who placed on hold, including the date & time), Rejected (with name of person who rejected it, including the date & time)
- Q: "EM" and "Planner" - same thing?
- A:No, not the same thing, but they are similar. They play the same role in the approval process.
- Q: Why 10? Why not make it flexible?
- A:This was not a phase 1 requirement. It will be further discussed for phase 2.
- Q: Any requirement for release date?
- A: ASAP