Comments and Query

From UG

Revision as of 16:03, 31 May 2012

Intro

This CT2 component covers functionality of Com, ICom, Query Tabs

Business Needs and Requirements

A tool is needed in order to preform queries and update all parties on current shipment status.

The jaguar user should be able to have a comment form where users can:

• add comments from a customizable predefined list.
• update comments for individual ct or grouped ct's.
• have the ability to email those comments to any parties.

The Jaguar user should be able to query info from an e-mail form where users can:

• e-mail a query to any parties listed on a predefined contact list.
• have a record of the history of their query attempts.

Component Specs

Comments Tab

• Drop Down Menu containing 13 predefined shipment status which once selected populates the same status on a Comment Text Box.

• Comment TextBox is an editable alpha-numeric text field where a user can type in their comments.

• Insert Comment Button posts the comment on a the comment form with operator name & time/date stamp.

• Post entries are a 2 cell table that contain the following:

Cell 1:

• Non-editable
• 24h time format with time zone
• Mon-DD-YYYY,
• First Name, Last Name of the comment poster.

Cell 2:

• Non-Editable Comment that was posted.
• Where the post was sent to.
• Vertical Scrolling

Post entries are visible once comments are added. Subsequent Posts are added directly below the previous post. Default is Blank.

• Dropdown Menu listing all Jaguar users that can be added added or removed to an empty send list TextBox

v2.0

Add admin panel (for now to Admin > Client App):

• User Accounts - non-jag User prof events
• Authorization - non-jag autorisation/MOT of CT event
• Comm Center - for Client App
• Shipment Queries - for Jag App

v2.0.a

Spec is updated for E-mail Query Log history.

• See figure below
• To: Operator of last change, unless it is a reply message to client (refer # 1 from the figure)
• Message is submitted from Query tab via operator, it MUST show on the E-mail log history ONLY (do not show on comm center tab in client interface) unless if it is a reply message from operators to clients.
• Message is submitted from Comm Center tab via client, it MUST show on the the E-mail log history for BOTH comm center tab in client interface AND query tab in Internal interface
• Message is submitted from client MUST show on the query log history on Query tab with "reply" button

Step: when operator would like to reply a query to client

• Operator clicks "reply" button
• Email changes from "To:" section to a specific client
  • Ex, If operator clicks reply button on # 2 from figure, "To:" client email address will be automatically replaced as tirarenfrew@yahoo.com
• operator submits the query
• message will be sent to client's email and also shown on Comm center and Query tabs' query log history
• then "To:" email is automatically updated back to operator of last change

NOTE:When operator add a message comment, message comment MUST be sent to:

• • Client (receiver)
  • Operator of last change (sender)
  • BCC list (blind copies to people at Jaguar such as Simon and Marc. This should be set in Internal App>Admin mode)
  • CC list for Jaguar user(s)

• There is a case of the operator of last change and the sender are 2 different person.

Please check to include both of them for the case of the operator of last change and the sender are a different person but for the case of the operator of last change and the sender are the same person, send it once(one copied email).

Dev Links

• Related mantis: ...

SOW 3

0003499: Add - Pre-Alert Ck box to Icom Tab & Pre-Alert DB report

This request was received from Marc and is for 2 separate components - first is the Icom Tab & second is a DB report for this added Icom functionality.

Add Check box to ICom tab & name it - Pre-Alert Sent

Add read only textbox and log the Users Name, Date & Timestamp of when the checkbox was set

Add Pre-Alert DB Report that is for ALL MOT Air & Ocean CT records that these 2 conditions:

• Actual departure date (Ocean CT_bo#Port_Of_Loading_Actual_Date / Air CT_bo#Airport_Of_Departure_Actual_Date) is set

AND

• Pre-alert checkbox is unset

• • MOT Air – Report immediately after CT_bo#Airport_Of_Departure_Actual_Date is set and Pre-Alert checkbox is unset
  • MOT Ocean – Report 72 hours after CT_bo#Port_Of_Loading_Actual_Date is set and Pre-Alert checkbox is unset

3. Marc asked for possibly having the following - insert comment “Pre-Alert Sent” – to be added manually by export user and user also sending this comment via e-mail. Then upon them sending the system auto checks the Pre-Alert Checkbox and business team can use the sent comment e-mail to forward onto their business c/part with their full pre-alert attached.