CT Group
From UG
(Difference between revisions)
(→Dev and History) |
(→Dev and History) |
||
| Line 59: | Line 59: | ||
* See [[Media:List_CT_Groups.JPG]] and [[Media:Edit_Group.JPG]] | * See [[Media:List_CT_Groups.JPG]] and [[Media:Edit_Group.JPG]] | ||
| - | == | + | == History == |
* Old article: [[CT Groups Ops Component]] | * Old article: [[CT Groups Ops Component]] | ||
| + | |||
| + | == Implementation == | ||
| + | * Edit GRP: | ||
| + | ** http://mantis.jaguarfreight.com/svn/repo2/cybertrax/trunk/java/CyberTrax/proto2.0.1f/ops/ShipmentGroup.zul | ||
| + | ** http://64.115.223.6:8080/CyberTrax/ops/ShipmentGroup.zul | ||
| + | |||
| + | * List GRPs: | ||
| + | ** http://mantis.jaguarfreight.com/svn/repo2/cybertrax/trunk/java/CyberTrax/proto2.0.1f/ops/ShipmentGroups.zul | ||
| + | ** http://64.115.223.6:8080/CyberTrax/ops/ShipmentGroups.zul | ||
Revision as of 23:24, 8 December 2009
Contents |
Business Needs and Requirements
Several CT could be "grouped". Motivation behind that:
- to be able to apply "same operation" to every CT with one click. For example you could change value of one CT field on multiple CT's
- generate pdf documents that "desribe" combined "values" from multiple CTs
- post comments into multiple CTs with one click
- see P/L report for combined CTs
- etc
Air and Ocean and Truck CTs sometimes needs to be grouped under Ocean or Air mode.
Technical Specification
Summary
Groups functionality consists of:
- Create Edit and List Groups Functionality
- Group related functionality in different parts of the system
Create Edit and List Groups Functionality
- CT Group entity has the following attributes:
- Group number:
- system generated
- starts with GRP
- Transport Mode:
- possible values = {{all non-trucking modes}, Truck}
- Client:
- same entity as in Admin > Clients
- List of CT#s:
- the max # of CTs in the group = 40
- Group number:
- Group has a minimum of 2 members
- A group for which less than 2 CT's are attached to is "void" (no longer a group)
- [MOT lock] After CT becomes part of the group MOT on general tab must become read-only
- If a CT is added to a group then CT's client (E0), will be updated to client (E0) and Mode that the group is set to.
- Group with Transport Mode = any but "Trucking":
- can be formed based on CTs with MOT: any
- mode of CTs added: any
- group's "MOT(mode)" parameter could be changed. Then all groups member CT's Client are "force-changed" to new value
- If a CT is added to a group then CT's Mode, will be updated to client (E0) and Mode that the group is set to.
- Group with Transport Mode = "Trucking":
- can be formed based on CTs with MOT: only truck CTs
- mode of CTs added: only truck CTs could be added
- "change" CT mode after CT is added to the group: no change
- can we change to another MOT, say "air"? Yes
User Interface
History
- Old article: CT Groups Ops Component
Implementation
- Edit GRP:
