ASN 20 Solution
From UG
(Difference between revisions)
(→Preliminary Work) |
(→Add Role Type attribute: Built In vs User Defined User Roles) |
||
| Line 24: | Line 24: | ||
Add column | Add column | ||
| + | |||
| + | === Add Generic Shipper and Generic Planner Built In User Roles === | ||
| + | |||
| + | Currently the only Shipper and related Planner roles defined in the system are "EA Shipper" and "EA Planner". Th | ||
== SOWs and Change Requests == | == SOWs and Change Requests == | ||
Revision as of 16:52, 1 August 2012
Contents |
Info
Preliminary Work
Add TMS E0 attribute
Currently "TMS solution" supports only one Client Company (E0) at a time - we can not send shipments to TMS that are identified by more than one E0 - this case is not defined - no code or business process exists.
We need to add parameter to the system that defines what E0 "is linked to" TMS currently. This will help in :
- reporting
- validation (to make sure we do not send CTs with other E0s to TMS)
Add Role Type attribute: Built In vs User Defined User Roles
We have to distinguish between Built In and User Defined User Roles.
Also this should make it obvious for the user - what role is Built In and what is User Defined.
User Defined Role is a role that can be created and fully defined by user through Open Admin > Security > User Roles.
Add column
Add Generic Shipper and Generic Planner Built In User Roles
Currently the only Shipper and related Planner roles defined in the system are "EA Shipper" and "EA Planner". Th
