View source for EST 339969 LFS Control POD Email Send

{{#vardefine:Year|2017}}{{#vardefine:Client|LFS}}{{Estimate_Head
|Client={{#var:Client}}
|Project=AUS
|Site=AUS-MEL
|ClientRef=NO REF
|OBSRef=339969
|Version=1.0
|Author=AN Walker
|PONum=&nbsp;
|Priority=3
|Date=23/03/17
|Customer=&nbsp;
|SysVer=1.4
|ClientRequest=The auto-email POD at Customer level is sending through POD's for both the scan onto the van and for delivery to the final delivery legs. However, the scan onto the van time is not something that the customer should know.
Would like to suggest that the proposed solution looks at the emailing of triggers in a complete and comprehensive way to allow for flexibility as all of our customers have varied expectations and requirements and this is only increasing with new customers.
|Solution=A customer-level, location-level and location type-level configuration will be added to C-TMS, used when sending jobs to C-ePOD.

For customers, the settings mean:
*	POD Only - any orders owned by that customer will send a POD to the customer's contact email address at completion of the job at the final destination location only.
*	POC Only - any orders owned by that customer will send a POC to the customer's contact email address at completion of the job at the origin location only.
*	Both - any orders owned by that customer will send a POC to the customer's contact email address at completion of the job at the origin location, and will send a POD to the customer's contact email address at completion of the job at the origin location.
*	Neither - no POD or POC emails will be sent to the customer's contact email address at all.
The configuration will be added to the ''EPOD'' tab on the ''Customers'' maintenance screen.


For locations, the settings mean:
*	POD Only - any order with a To Loc of this location will send a POD to the location's contact email address at completion of the job at the final destination location only.
*	POC Only - any order with a From Loc of this location will send a POC to the location's contact email address at completion of the job at the origin location only.
*	Both - any order with a From Loc of this location will send a POC to the location's contact email address at completion of the job at the origin location, and any order with a To Loc of this location will send a POD to the location's contact email address at completion of the job at the final destination location.
*	Neither - no POD or POC emails will be sent to the location's contact email address at all.
*	Default - the location type will be checked instead.
The configuration will be added to the ''EPOD'' tab on the ''Locations'' maintenance screen.


For location types, the settings are:
*	POD Only - any order with a To Loc of locations of this type will send a POD to the location's contact email address at completion of the job at the final destination location only.
*	POC Only - any order with a From Loc of locations of this type will send a POC to the location's contact email address at completion of the job at the origin location only.
*	Both - any order with a From Loc of locations of this type will send a POC to the location's contact email address at completion of the job at the origin location, and any order with a To Loc of locations of this type will send a POD to the location's contact email address at completion of the job at the final destination location.
*	Neither - no POD or POC emails will be sent to locations of this type's contact email address at all.
The configuration will be added to the ''EPOD'' tab on the ''Business Data/Location Types'' maintenance screen.


All email addresses sent through on the jobs would then be set against the origin job and/or final delivery job based on these settings.


Email addresses are configured against contacts linked to locations or orders.

For Customer emails:
* Link a location to a customer
* Add a contact against this location with an email address.

For Location emails:
* Add a contact against this location with an email address.

For Order emails:
* Add a contact against the from and/or to locations with an email address.


For example:
* if the supplier is configured to receive both, to be sent to cust@lfs.com.au 
* the collection address is configured for both, to be sent to origin@cust.com.au
* the destination address is set to both, to be sent to final@gmail.com
* the order has a From Location email address set to order_to@gmail.com
* the order has a To Location email address set to order_from@gmail.com


In this example, the jobs sent through (in normal configuration) would be as follows:
* Customer to LFS depot.	- cust@cust.com.au; origin@cust.com.au; order_from@gmail.com
* LFS Depot to Airport	- (None)
* Airport to Airport	- (None)
* Airport to LFS Depot	- (None)
* LFS Depot to final destination	- cust@lfs.com.au; final@gmail.com; order_to@gmail.com


So the rules are:
*	Never populate email if the job being sent is not an origin or final destination location.
*	Only add customer email to origin if configuration is Both or POC.
*	Only add customer email to final destination if configuration is Both or POD.
*	Only add address email to origin if location configuration is Both or POC or Default and location type configuration is Both or POC.
*	Only add address email to final destination if configuration is Both or POD or Default and location type configuration is Both or POD.
*	Add order From Loc email to origin if present.
*	Add order To Loc email to final destination if present.

The email lists will be curated when created to ensure that only one entry per email is generated.


For Job Swaps, the systems will be configured to remove the emails from the job at the swap point, and will be copied to the new jobs, ensuring that the emails will only be sent at final destination.


This mechanism will be used in preference to the Job Group mechanism is C-ePOD. The C-ePOD Site email address (for LFS contact information) will still be used to send emails to LFS contacts.


{{Note}} If addresses are free-typed on orders through the Portal screens rather than a location found for that location that already exists, a new location will be created. The contact information will not be stored against the location, only against the order. The configuration for this new location will be set to ''Default''.


{{Note}} If a location is configured to ''Both'', this means that the location email address is used when the order is delivered or collected from that location. This does not mean that the email address will be used for the POC or POD at the other location.

For example:
When delivering an order from RDCMEL direct to customer MYCUST, if location MYCUST has a contact email address and the configuration is ''Both'', the email address will be used on the POD to MYCUST - the email will not be used for the POC from RDCMEL.

The reverse is also true: When delivering an order from MYCUST to RDCMEL, the email address will be used on the POC from MYCUST - the email will not be used for the POD to RDCMEL.
}}{{EstimateCostDetails{{#var:Year}}
|REQ=0.0
|EST=1.0
|FS=1.75
|TS=0
|DEV=8.5
|ST=1.5
|IMP=0.5
|PM=1.0
|Client=LFS
|Year={{#var:Year}}
|FOC=N
|NOFOOTER=Y
}}

<table width="100%">
<tr><td align="center"><font size="1">
Copyright © OBS Logistics {{#var:Year}}.<br />
This estimate has an expiry date of 30 days from the specified Estimate Date.<br />
The information contained herein is supplied without liability for errors or omissions.
</font></td></tr></table>
[[Category:{{#var:Client}} EST]]