Cargo Due Date Feature

From UG

(Difference between revisions)
Jump to: navigation, search
(→Released Solution)
 
(43 intermediate revisions not shown)
Line 18: Line 18:
*This feature is for Non Jag users that have role, Planner set in their non jag user profile - see [[Cybertrax_2.1_Client_(requirements)#Core_Planner_Functionality]].
*This feature is for Non Jag users that have role, Planner set in their non jag user profile - see [[Cybertrax_2.1_Client_(requirements)#Core_Planner_Functionality]].
-
**If Non Jag user has planner role with Cargo Due Date Field on AND basic planner role, this date field is mandatory and must be completed.
+
**If Non Jag user has planner role with Cargo Due Date Field on, AND Double Approval Process = basic planner, this date field is mandatory and must be completed .
**Also, the system should prevent non jag users with basic planner role from changing the Cargo Due Date set by super planner.
**Also, the system should prevent non jag users with basic planner role from changing the Cargo Due Date set by super planner.
-
**If Non Jag user has planner role with Cargo Due Date Field on AND super planner role, this date field is also mandatory and must be completed.
+
**If Non Jag user has planner role with Cargo Due Date Field on, And Double Approval Process = super planner role, this date field is also mandatory and must be completed. But they also can confirm the date that was already set by basic planner, by approving and/or placing on hold with an approved for pickup date.  They do not need to reset the date value, unless its in the past.
-
***They also can confirm the date the was already set by basic planner, by approving and/or place on hold with an approved for pickup date.  They do not need to reset the date value.
+
*The Cargo Due Date set, needs to be displayed:
*The Cargo Due Date set, needs to be displayed:
Line 56: Line 55:
*System should only allow the cargo due date to be = or > than the [[CT_bo#Cargo_available]] & [[CT_bo#Approved_For_Delivery_By_Date]] & [[CT_bo#Approved_On]]
*System should only allow the cargo due date to be = or > than the [[CT_bo#Cargo_available]] & [[CT_bo#Approved_For_Delivery_By_Date]] & [[CT_bo#Approved_On]]
-
== Suggested Solution ==
+
== Solution Provided ==
=== Summary ===
=== Summary ===
Line 68: Line 67:
* For every "PO Issued by" can be set type of approval process (single or double).
* For every "PO Issued by" can be set type of approval process (single or double).
* For every company with double approving "Cargo Due Date" feature can be switched on/off.
* For every company with double approving "Cargo Due Date" feature can be switched on/off.
 +
** 8/24 Change = Add On/Off switch for "Cargo Due Date" feature for single approval process planner users
-
[[File:CargoDueDate_POIssuedBy.jpg]]
+
[[File:Cargo Due Date PO Issued By.JPG]]
-
[[File:CargoDueDatePopup1.jpg]]
+
'''Click to set Double Approval Status'''
 +
[[File:Cargo Due Date Popup 1.JPG]]
-
[[File:CargoDueDatePopup2.jpg]]
+
 
 +
'''Click to set Single Approval Status'''
 +
[[File:Edit PO Issued by that has Cargo Due Date set.JPG]]
 +
 
 +
 
 +
'''Click to set Cargo Due Date for Double Approval'''
 +
[[File:Cargo Due Date Popup 2.JPG]]
==== Where and when to add Cargo due datebox ====
==== Where and when to add Cargo due datebox ====
Line 80: Line 87:
Please note that check box will be unchecked and read only (grayed out) if "PO issued by" is associated with "Single approval" process.
Please note that check box will be unchecked and read only (grayed out) if "PO issued by" is associated with "Single approval" process.
-
[[File:CargoDueDate_NonJagUser.jpg]]
+
'''Super Planner Role'''
 +
[[File:Non Jag User Profile for Super Planner.JPG | 800px]]
 +
 
 +
'''Basic Planner Role'''
 +
[[File:Non Jag User Profile for Basic Planner.JPG]]
=== Client part ===
=== Client part ===
Line 116: Line 127:
[[Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status]]
[[Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status]]
-
==== Not Correct "Mandatory to set for basic but not for super" Changed 8/18 to Mandatory for both ====
+
=== When super planner sets status to basic planner records that has Cargo Due Date values set ===
-
'''This was not correct:''' Note: in this case some CTs will have empty date (if super approves without setting this date before basic does anything).
+
There are two different ways for planners to set a status for a CT record and the system must consider them both to allow.
-
8/18 this is feature mandatory for both basic & super planner users.
+
'''Super Planner to set status: “Approved” for an already Approved Basic Planner CT record, that has the Due Date Set in the “72 hr window”  Allow super planner to continue or change/reset the "Cargo Due Date” to a current future date'''
-
If non jag user who has planner role with Cargo Due Date field on, then show this field when planner sets approval status to:
+
[[File:Approval 72 hrs.JPG]]
 +
 
 +
 
 +
'''Super Planner sets status: “Approved” for an already Approved Basic Planner CT record that has the Due Date Set in the past  Make super planner change & reset the "Cargo Due Date” to a current future date'''
 +
 
 +
[[File:SP Approve to BP CT has the Due Date Set in past.JPG]]
 +
 
 +
 
 +
'''Super Planner sets status: “Approved” for an already Approved Basic Planner CT record that has the Due Date Set in current / future  Allow super planner to keep the current date value set by basic planner or replace to a current future date, tab view'''
 +
 
 +
[[File:SP Approve to BP CT has the Due Date Set in future.JPG]]
 +
 
 +
 
 +
'''Allow super planner to keep the current date value set by basic planner or replace to a current future date, record view'''
 +
 
 +
[[File:SP Approve to BP CT has the Due Date Set in future b.JPG]]
 +
 
 +
=== When super planner sets status for record without Cargo Due Date ===
 +
 
 +
'''Super Planner sets status: “Approved” for a new record, that does not have a Cargo Due Date set  Not allow the user to proceed, CT view'''
 +
 
 +
[[File:From Tab super planner sets approved status for basic planner appvd with cargo due date.JPG]]
 +
 
 +
'''Not allow the user to proceed, Tab view'''
 +
 
 +
[[File:From Tab SP tries to appvd staus without any due date already set.JPG]]
-
* Cybertrax_2.1_Client_(requirements)#Approve_Status OR
 
-
* Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status
 
==== This date Must visible / editable on appropriate CT details panels ====
==== This date Must visible / editable on appropriate CT details panels ====
Line 141: Line 175:
* super planner (until status set to Approved)
* super planner (until status set to Approved)
-
==== Integration with Descartes ====
+
=== Integration with Descartes ===
-
'''Denise's comments'''
 
*Earliest & Latest Delivery Date = Cargo due date with time window from 9am to 5pm.   
*Earliest & Latest Delivery Date = Cargo due date with time window from 9am to 5pm.   
-
*There is no need to increase the # of days to this date as it is a date that says that cargo cannot be delivered any later than that date set.   
+
**There is no need to increase the # of days to this date as it is a date that says that cargo cannot be delivered any later than that date set.   
-
*The TMS will consider the latest delivery date when creating the load and use that as the estimated delivery date for cargo. 
+
-
*It is ok to deliver '''before''' the Cargo Due Date is is '''NOT''' ok deliver '''after''' the cargo due date.
+
 +
*The TMS will consider the latest delivery date when creating the load and use that as the estimated delivery date for cargo.
 +
 
 +
*It is ok to deliver '''before''' the Cargo Due Date it is '''NOT''' ok deliver '''after''' the cargo due date.
-
Cargo due will be forwarded to TMS and 2 fields in TMS will be set accordingly - see below:
+
==== Cargo due date sent to TMS ====
-
* set Earliest Delivery Date equal to Cargo Due Date set by EA Stamford planner
+
-
* set Latest Delivery Date equal to Cargo Due Date set by EA Stamford planner
+
-
== Released Solution ==
+
[[File:TMS Shipment view with Cargo Due Date.JPG]]
-
=== Admin part  ===
+
== History ==
-
==== "PO issued by" management panel ====
+
 +
=== 0002295 [TMS (OSDS)] (Cargo Due Date) Add this feature & date fields to CT2 internal & client app shipper/planner view ===
 +
WU? YES --[[User:Denise|Denise]] 12:46, 23 August 2011 (EDT); completed --[[User:Denise|Denise]] 12:56, 23 September 2011 (EDT)
-
==== Where and when to add Cargo due datebox ====
+
=== 0003002 [TMS (OSDS)] (Cargo Due Date) Add cargo due date to shipment import under xml attribute EarliestDelDate & LatestDelDate ===
 +
 
 +
WU? Yes
 +
 
 +
=== Suggested Solution ===
 +
 
 +
==== Summary ====
 +
Cargo Due Date feature is entered to allow better optimization of truck utilization. It is a last possible date of shipment delivery and allows to Jaguar operator to know how long can be delayed shipment.
 +
 
 +
It is "PO issued by" specific. Showing the Cargo Due Date is an option for every "PO issued by" and can be managed from Admin section. It can be switched on/off only for double approval CT process which implies approving from Regular Planner and SuperPlanner. For single approval the showing of Cargo Due is not needed.
 +
 
 +
==== Admin part  ====
 +
===== "PO issued by" management panel =====
 +
"PO issued by" admin section contains a list of  Companies that considered as "PO issued by".
 +
* For every "PO Issued by" can be set type of approval process (single or double).
 +
* For every company with double approving "Cargo Due Date" feature can be switched on/off.
 +
 
 +
[[File:CargoDueDate_POIssuedBy.jpg]]
 +
 
 +
[[File:CargoDueDatePopup1.jpg]]
 +
 
 +
[[File:CargoDueDatePopup2.jpg]]
 +
 
 +
===== Where and when to add Cargo due datebox =====
Planner is a such user that can work with Cargo Due Date feature. So Non-Jaguar user should get Planner role and also should have a list of selected "PO Issued By". Planner can be assigned as Super Planner for "PO issued by" with double approval process.
Planner is a such user that can work with Cargo Due Date feature. So Non-Jaguar user should get Planner role and also should have a list of selected "PO Issued By". Planner can be assigned as Super Planner for "PO issued by" with double approval process.
Line 168: Line 224:
[[File:CargoDueDate_NonJagUser.jpg]]
[[File:CargoDueDate_NonJagUser.jpg]]
-
== History ==
+
==== Client part ====
 +
===== Add field at the point of setting status (planner user) =====
-
=== 0002295 [TMS (OSDS)] (Cargo Due Date) Add this feature & date fields to CT2 internal & client app shipper/planner view ===
+
Cargo Due Date must be set during approval CT process which can be performed through:
 +
* change CT status from any status to Approve status
 +
* change CT status from any status to Hold with Approved for Pick Up On Date status
-
WU? No
+
[[File:CargoDueDate_ApprovalComment.jpg]]
-
=== 0003002 [TMS (OSDS)] (Cargo Due Date) Add cargo due date to shipment import under xml attribute EarliestDelDate & LatestDelDate ===
+
===== Becomes Read only for Basic planer after Super updated =====
-
WU? Yes
+
===== Must be in Log =====
 +
 
 +
* Individual CT records updates log
 +
 
 +
* Shipper/Planner History log
 +
 
 +
===== Must appear on reports and xls download =====
 +
 
 +
* xls downl for list CTs, planner role
 +
* KPIs (future)
 +
* anything else? - '''Yes'''
 +
** In Transit Report - Add to list of Output
 +
** Main Report - Add to list of Output
 +
** TDS http://ct.jaguarfreight.com/internal/Index.zul#reportsTDSForm (as filters/columns)? - '''Both filters & columns'''
 +
*** Filters - add Date range for Cargo Due
 +
*** Columns - Add Header named Due Date, place in between "Appr on Date" & "Pickup Location".  List on ALL 3 Tabs (Approved, Routed & Picked Up) with the date values set by planner user, if no value, leave blank
 +
 
 +
===== Date range validation =====
 +
 
 +
x? < date < y?
 +
 
 +
[[Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status]]
 +
 
 +
===== Not Correct "Mandatory to set for basic but not for super" Changed 8/18 to Mandatory for both =====
 +
 
 +
'''This was not correct:''' Note: in this case some CTs will have empty date (if super approves without setting this date before basic does anything).
 +
 
 +
8/18 this is feature mandatory for both basic & super planner users.
 +
 
 +
If non jag user who has planner role with Cargo Due Date field on, then show this field when planner sets approval status to:
 +
 
 +
* Cybertrax_2.1_Client_(requirements)#Approve_Status OR
 +
* Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status
 +
 
 +
===== This date Must visible / editable on appropriate CT details panels =====
 +
 
 +
Read only:
 +
* Client role, (?) Not yet approved for client role
 +
* Shipper role - on CT Shipment View (see IE below)
 +
* Planner role - On CT Shipment Vie (see IE below)
 +
 
 +
[[File:Shipper and Planner View IE.JPG]]
 +
 
 +
Editable:
 +
* operator role (internal) (until CT has load assigned)
 +
* basic planner (until status set to Approved or date is changed by Super)
 +
* super planner (until status set to Approved)
 +
 
 +
===== Not Correct "Mandatory to set for basic but not for super" Changed 8/18 to Mandatory for both =====
 +
 
 +
Editing of this spec was done after release as we found a spec bug.  It was corrected by developer Andriy under mantis [http://ct.jaguarfreight.com/mantis/view.php?id=3147 3147]
 +
 
 +
'''This was not correct:''' Note: in this case some CTs will have empty date (if super approves without setting this date before basic does anything).
 +
 
 +
8/18 this is feature mandatory for both basic & super planner users.
 +
 
 +
If non jag user who has planner role with Cargo Due Date field on, then show this field when planner sets approval status to:
 +
 
 +
* Cybertrax_2.1_Client_(requirements)#Approve_Status OR
 +
* Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status
 +
 
 +
=== 3150: [TMS (OSDS)] (Cargo Due Date) Change: Add Due Date checkbox for planer users who have single approval process  ===
 +
 
 +
WU? YES - completed --Denise 12:56, 23 September 2011 (EDT)

Current revision as of 23:04, 9 August 2012


Contents

[edit] Info

  • parent: 0002539: [OSDS] ..... <proj>

[edit] Glossary

[edit] Business Needs

[edit] Core need

This feature would allow for better optimization, by knowing the number of days to put off picking up shipments; to be able to add more pickups, in the future, to maximize the trucks capacity.

[edit] Requirements

This date feature should not be hard coded; it should be allowed to be managed in CT2 >> Admin >> Client App Admin - TMS tab, as an option to display or not to display. (This would be to allow for the scalability of our current TMS solution, for us to provide to other client companies.)

  • This feature is for Non Jag users that have role, Planner set in their non jag user profile - see Cybertrax_2.1_Client_(requirements)#Core_Planner_Functionality.
    • If Non Jag user has planner role with Cargo Due Date Field on, AND Double Approval Process = basic planner, this date field is mandatory and must be completed .
    • Also, the system should prevent non jag users with basic planner role from changing the Cargo Due Date set by super planner.
    • If Non Jag user has planner role with Cargo Due Date Field on, And Double Approval Process = super planner role, this date field is also mandatory and must be completed. But they also can confirm the date that was already set by basic planner, by approving and/or placing on hold with an approved for pickup date. They do not need to reset the date value, unless its in the past.
  • This date needs to be sent to the TMS on the Shipment Import File. (xml mapping, see Data Dic mapping here 2229)
  • Allow the Approved for date to the same as the cargo due date, but it cannot be in the past.
  • This date will also be required for KPI reporting/analysis.
    • Avg Time KPIs

[edit] Functionality

  • Provide option to turn on/off the Cargo Due Date Field on each planner role.
  • This cargo due date field is a Datebox

Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status.

[edit] Solution Provided

[edit] Summary

Cargo Due Date feature is entered to allow better optimization of truck utilization. It is a last possible date of shipment delivery and allows to Jaguar operator to know how long can be delayed shipment.

It is "PO issued by" specific. Showing the Cargo Due Date is an option for every "PO issued by" and can be managed from Admin section. It can be switched on/off only for double approval CT process which implies approving from Regular Planner and SuperPlanner. For single approval the showing of Cargo Due is not needed.

[edit] Admin part

[edit] "PO issued by" management panel

"PO issued by" admin section contains a list of Companies that considered as "PO issued by".

  • For every "PO Issued by" can be set type of approval process (single or double).
  • For every company with double approving "Cargo Due Date" feature can be switched on/off.
    • 8/24 Change = Add On/Off switch for "Cargo Due Date" feature for single approval process planner users

File:Cargo Due Date PO Issued By.JPG

Click to set Double Approval Status File:Cargo Due Date Popup 1.JPG


Click to set Single Approval Status File:Edit PO Issued by that has Cargo Due Date set.JPG


Click to set Cargo Due Date for Double Approval File:Cargo Due Date Popup 2.JPG

[edit] Where and when to add Cargo due datebox

Planner is a such user that can work with Cargo Due Date feature. So Non-Jaguar user should get Planner role and also should have a list of selected "PO Issued By". Planner can be assigned as Super Planner for "PO issued by" with double approval process.

Please note that check box will be unchecked and read only (grayed out) if "PO issued by" is associated with "Single approval" process.

Super Planner Role

Basic Planner Role File:Non Jag User Profile for Basic Planner.JPG

[edit] Client part

[edit] Add field at the point of setting status (planner user)

Cargo Due Date must be set during approval CT process which can be performed through:

  • change CT status from any status to Approve status
  • change CT status from any status to Hold with Approved for Pick Up On Date status

File:CargoDueDate_ApprovalComment.jpg

[edit] Becomes Read only for Basic planer after Super updated

[edit] Must be in Log

  • Individual CT records updates log
  • Shipper/Planner History log

[edit] Must appear on reports and xls download

  • xls downl for list CTs, planner role
  • KPIs (future)
  • anything else? - Yes
    • In Transit Report - Add to list of Output
    • Main Report - Add to list of Output
    • TDS http://ct.jaguarfreight.com/internal/Index.zul#reportsTDSForm (as filters/columns)? - Both filters & columns
      • Filters - add Date range for Cargo Due
      • Columns - Add Header named Due Date, place in between "Appr on Date" & "Pickup Location". List on ALL 3 Tabs (Approved, Routed & Picked Up) with the date values set by planner user, if no value, leave blank

[edit] Date range validation

x? < date < y?

Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status

[edit] When super planner sets status to basic planner records that has Cargo Due Date values set

There are two different ways for planners to set a status for a CT record and the system must consider them both to allow.

Super Planner to set status: “Approved” for an already Approved Basic Planner CT record, that has the Due Date Set in the “72 hr window” Allow super planner to continue or change/reset the "Cargo Due Date” to a current future date

File:Approval 72 hrs.JPG


Super Planner sets status: “Approved” for an already Approved Basic Planner CT record that has the Due Date Set in the past Make super planner change & reset the "Cargo Due Date” to a current future date

File:SP Approve to BP CT has the Due Date Set in past.JPG


Super Planner sets status: “Approved” for an already Approved Basic Planner CT record that has the Due Date Set in current / future Allow super planner to keep the current date value set by basic planner or replace to a current future date, tab view

File:SP Approve to BP CT has the Due Date Set in future.JPG


Allow super planner to keep the current date value set by basic planner or replace to a current future date, record view

File:SP Approve to BP CT has the Due Date Set in future b.JPG

[edit] When super planner sets status for record without Cargo Due Date

Super Planner sets status: “Approved” for a new record, that does not have a Cargo Due Date set Not allow the user to proceed, CT view

File:From Tab super planner sets approved status for basic planner appvd with cargo due date.JPG

Not allow the user to proceed, Tab view

File:From Tab SP tries to appvd staus without any due date already set.JPG


[edit] This date Must visible / editable on appropriate CT details panels

Read only:

  • Client role, (?) Not yet approved for client role
  • Shipper role - on CT Shipment View (see IE below)
  • Planner role - On CT Shipment Vie (see IE below)

File:Shipper and Planner View IE.JPG

Editable:

  • operator role (internal) (until CT has load assigned)
  • basic planner (until status set to Approved or date is changed by Super)
  • super planner (until status set to Approved)

[edit] Integration with Descartes

  • Earliest & Latest Delivery Date = Cargo due date with time window from 9am to 5pm.
    • There is no need to increase the # of days to this date as it is a date that says that cargo cannot be delivered any later than that date set.
  • The TMS will consider the latest delivery date when creating the load and use that as the estimated delivery date for cargo.
  • It is ok to deliver before the Cargo Due Date it is NOT ok deliver after the cargo due date.

[edit] Cargo due date sent to TMS

File:TMS Shipment view with Cargo Due Date.JPG

[edit] History

[edit] 0002295 [TMS (OSDS)] (Cargo Due Date) Add this feature & date fields to CT2 internal & client app shipper/planner view

WU? YES --Denise 12:46, 23 August 2011 (EDT); completed --Denise 12:56, 23 September 2011 (EDT)

[edit] 0003002 [TMS (OSDS)] (Cargo Due Date) Add cargo due date to shipment import under xml attribute EarliestDelDate & LatestDelDate

WU? Yes

[edit] Suggested Solution

[edit] Summary

Cargo Due Date feature is entered to allow better optimization of truck utilization. It is a last possible date of shipment delivery and allows to Jaguar operator to know how long can be delayed shipment.

It is "PO issued by" specific. Showing the Cargo Due Date is an option for every "PO issued by" and can be managed from Admin section. It can be switched on/off only for double approval CT process which implies approving from Regular Planner and SuperPlanner. For single approval the showing of Cargo Due is not needed.

[edit] Admin part

[edit] "PO issued by" management panel

"PO issued by" admin section contains a list of Companies that considered as "PO issued by".

  • For every "PO Issued by" can be set type of approval process (single or double).
  • For every company with double approving "Cargo Due Date" feature can be switched on/off.

File:CargoDueDate_POIssuedBy.jpg

File:CargoDueDatePopup1.jpg

File:CargoDueDatePopup2.jpg

[edit] Where and when to add Cargo due datebox

Planner is a such user that can work with Cargo Due Date feature. So Non-Jaguar user should get Planner role and also should have a list of selected "PO Issued By". Planner can be assigned as Super Planner for "PO issued by" with double approval process.

Please note that check box will be unchecked and read only (grayed out) if "PO issued by" is associated with "Single approval" process.

File:CargoDueDate_NonJagUser.jpg

[edit] Client part

[edit] Add field at the point of setting status (planner user)

Cargo Due Date must be set during approval CT process which can be performed through:

  • change CT status from any status to Approve status
  • change CT status from any status to Hold with Approved for Pick Up On Date status

File:CargoDueDate_ApprovalComment.jpg

[edit] Becomes Read only for Basic planer after Super updated
[edit] Must be in Log
  • Individual CT records updates log
  • Shipper/Planner History log
[edit] Must appear on reports and xls download
  • xls downl for list CTs, planner role
  • KPIs (future)
  • anything else? - Yes
    • In Transit Report - Add to list of Output
    • Main Report - Add to list of Output
    • TDS http://ct.jaguarfreight.com/internal/Index.zul#reportsTDSForm (as filters/columns)? - Both filters & columns
      • Filters - add Date range for Cargo Due
      • Columns - Add Header named Due Date, place in between "Appr on Date" & "Pickup Location". List on ALL 3 Tabs (Approved, Routed & Picked Up) with the date values set by planner user, if no value, leave blank
[edit] Date range validation

x? < date < y?

Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status

[edit] Not Correct "Mandatory to set for basic but not for super" Changed 8/18 to Mandatory for both

This was not correct: Note: in this case some CTs will have empty date (if super approves without setting this date before basic does anything).

8/18 this is feature mandatory for both basic & super planner users.

If non jag user who has planner role with Cargo Due Date field on, then show this field when planner sets approval status to:

  • Cybertrax_2.1_Client_(requirements)#Approve_Status OR
  • Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status
[edit] This date Must visible / editable on appropriate CT details panels

Read only:

  • Client role, (?) Not yet approved for client role
  • Shipper role - on CT Shipment View (see IE below)
  • Planner role - On CT Shipment Vie (see IE below)

File:Shipper and Planner View IE.JPG

Editable:

  • operator role (internal) (until CT has load assigned)
  • basic planner (until status set to Approved or date is changed by Super)
  • super planner (until status set to Approved)
[edit] Not Correct "Mandatory to set for basic but not for super" Changed 8/18 to Mandatory for both

Editing of this spec was done after release as we found a spec bug. It was corrected by developer Andriy under mantis 3147

This was not correct: Note: in this case some CTs will have empty date (if super approves without setting this date before basic does anything).

8/18 this is feature mandatory for both basic & super planner users.

If non jag user who has planner role with Cargo Due Date field on, then show this field when planner sets approval status to:

  • Cybertrax_2.1_Client_(requirements)#Approve_Status OR
  • Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status

[edit] 3150: [TMS (OSDS)] (Cargo Due Date) Change: Add Due Date checkbox for planer users who have single approval process

WU? YES - completed --Denise 12:56, 23 September 2011 (EDT)

Retrieved from "https://wiki.jaguarfreight.com/Cargo_Due_Date_Feature"
Personal tools