Done/ Send Notification Button comes clean

A Shipping function originally coded to support sites using the Fulfillment Order function has grown into broader application.

As it has, several updates were made to the function to support different requests. Last week in support of a new site we made yet another “tweak”. Then that new site had the audacity to ask me to confirm exactly what the code was doing. Well darn them! I couldn’t with any certainty.

I was however able to kidnap our lead developer and peel back the onion. Finding out exactly what went to who under the various Project Type scenarios was most illuminating.

The function uses two separate distribution engines. The first is the standard Tasking engine, which based on the individual user profile will also release a Task email with Login Link. The second engine is an email server; as there is no registered user to Task and yet we want that user to receive the appropriate tracking and delivery data for the shipment. Below is a listing of what happens for each of the three Project Types.

E-Info Project
Internal Project Owner 1: Yes- Standard Task email with Login Link

Go2Show Project
Internal Project Owner1: Yes- Standard Task email with Login Link
External Project Owner 1(Go2Show order placer): Yes – Text Email with shipping info

Fulfillment Shipment
Requester (Ship To: Address Person): Yes – Text Email with shipping info
User who clicked Confirm Fulfillment Order: Yes- Standard Task email with Login Link
Internal Project Owner 1: Yes- Standard Task email with Login Link

The Fulfillment Shipment has a related distribution function on the Confirmation of the order itself.

On the Click of Confirm Fulfillment Order
User clicking Confirm Fulfillment Order: Yes- Standard Task email with Login Link
Internal Project Owner 1: Yes- Standard Task email with Login Link
Requester (Ship To: Address Person): Yes – Text Email with shipping info