Query (User Guide)

From UG

Revision as of 02:07, 7 February 2010 (edit) Alex (Talk | contribs) ← Older edit		Current revision as of 22:14, 27 February 2010 (edit) (undo) Alex (Talk | contribs)
(6 intermediate revisions not shown)
Line 7:		Line 7:
	== Location ==		== Location ==
-	It is located on "Query" tab of any CT. See [[#Figure 1. Query Tab]]	+	It is located on "Query" tab of any CT.
		+
		+	== User Interface ==
		+
		+	See [[#Figure 1. Query Tab]]
		+
		+	Query tab consists of 3 sections A, B, C. See below.
		+
		+	=== Section A: New Query form ===
		+
		+	Section A is a form for new query.
		+
		+	It consists of the following fields.
		+
		+	==== To ====
		+
		+	This field defines who will reseive this query.
		+
		+	It is read only. It always defaults to e-mail of the [[Operator Of Last Change]].
		+
		+	==== From ====
		+
		+
		+	This field defines "from" e-mail field.
		+
		+	It is read only.
		+
		+	It always defaults to e-mail of the [[Current User]].
		+
		+
		+	==== Jaguar CC ====
		+
		+	User may select a number of jaguar users that would receive a copy of Query through email.
		+
		+	==== Subject ====
		+
		+	This is a subject of e-mail. It always ha a form of: Query CT# <current CT num>
		+
		+	==== Query ====
		+	Textarea where user should enter a query.
		+
		+	=== Section B ===
		+
		+
		+
		+
		+	Section B has buttons Submit and Group Submit (this button is present only if CT is part of a group).
		+
		+
		+	=== Section C ===
		+
		+	Section C is a History. It presents all queries ever submitted for this CT.
		+
		+	It contains: date/time query has been submitted, Subject, to, from information
		+
		+	Edit and Delete buttons.
		+
		+	== Use Cases ==
		+
		+	=== Create and Submit New Query ===
		+
		+	=== Create, Submit and CC new Query ===
		+
		+	=== Edit Query ===
		+
		+	=== Delete Query ===
		+
		+
		+
		+	== Misc ==
		+
		+	=== Query Email Template ===
		+
		+	Header Example:
		+
		+	From:  alex@jaguarfreight.com [alex@jaguarfreight.com]
		+	To:  Montira Renfrew; Alex Dobrovolsky
		+	Cc:
		+	Subject:  Query: CT# 300012
		+	Attachments:
		+
		+	Body example:
		+
		+	Sent by Alex Dobrovolsky of Jaguar Freight Ltd
		+	http://64.115.223.6:443/CyberTrax?editShipment=300012
		+	------------------------------------------------------------
		+	Testing query. Test #1: no CC.
		+	------------------------------------------------------------
		+	Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
		+	Please ensure you have appropriate cover for all your domestic and international shipments.
		+	Please note that all business is transacted subject to our general business terms and conditions,
		+	as indicated on our freight invoices and HB/L, a copy of which is also available upon request.
		+
		+	=== Client Functionality ===
		+
		+	Client will not receive Query or see Query Log.
		+
		+	=== BCC New Query ===
		+
		+	Every Query will be sent to Query BCC list defined in [[Admin]]. See ....
	== Figure 1. Query Tab ==		== Figure 1. Query Tab ==
		+
		+	[[File:Query.JPG]]
		+
		+	== More ==
		+
		+	More information and technical details are provided in [[Query (Developer Guide)]]

---

Current revision as of 22:14, 27 February 2010

Contents 1 Purpose 2 Location 3 User Interface 3.1 Section A: New Query form 3.1.1 To 3.1.2 From 3.1.3 Jaguar CC 3.1.4 Subject 3.1.5 Query 3.2 Section B 3.3 Section C 4 Use Cases 4.1 Create and Submit New Query 4.2 Create, Submit and CC new Query 4.3 Edit Query 4.4 Delete Query 5 Misc 5.1 Query Email Template 5.2 Client Functionality 5.3 BCC New Query 6 Figure 1. Query Tab 7 More

[edit] Purpose

The purpose of this feature is to provide an easy way to ask Operator Of Last Change a question about a shipment.

[edit] Location

It is located on "Query" tab of any CT.

[edit] User Interface

See #Figure 1. Query Tab

Query tab consists of 3 sections A, B, C. See below.

[edit] Section A: New Query form

Section A is a form for new query.

It consists of the following fields.

[edit] To

This field defines who will reseive this query.

It is read only. It always defaults to e-mail of the Operator Of Last Change.

[edit] From

This field defines "from" e-mail field.

It is read only.

It always defaults to e-mail of the Current User.

[edit] Jaguar CC

User may select a number of jaguar users that would receive a copy of Query through email.

[edit] Subject

This is a subject of e-mail. It always ha a form of: Query CT# <current CT num>

[edit] Query

Textarea where user should enter a query.

[edit] Section B

Section B has buttons Submit and Group Submit (this button is present only if CT is part of a group).

[edit] Section C

Section C is a History. It presents all queries ever submitted for this CT.

It contains: date/time query has been submitted, Subject, to, from information

Edit and Delete buttons.

[edit] Use Cases

[edit] Create and Submit New Query

[edit] Create, Submit and CC new Query

[edit] Edit Query

[edit] Delete Query

[edit] Misc

[edit] Query Email Template

Header Example:

From:  	 alex@jaguarfreight.com [alex@jaguarfreight.com] 	  
To:  	 Montira Renfrew; Alex Dobrovolsky
Cc:  	 
Subject:  	 Query: CT# 300012
Attachments:  	

Body example:

Sent by Alex Dobrovolsky of Jaguar Freight Ltd
http://64.115.223.6:443/CyberTrax?editShipment=300012
------------------------------------------------------------
Testing query. Test #1: no CC.
------------------------------------------------------------
Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing. 
Please ensure you have appropriate cover for all your domestic and international shipments.
Please note that all business is transacted subject to our general business terms and conditions, 
as indicated on our freight invoices and HB/L, a copy of which is also available upon request.

[edit] Client Functionality

Client will not receive Query or see Query Log.

[edit] BCC New Query

Every Query will be sent to Query BCC list defined in Admin. See ....

[edit] Figure 1. Query Tab

[edit] More

More information and technical details are provided in Query (Developer Guide)