Integration points for Rates DB
From UG
(Difference between revisions)
(Created page with 'Category:Rates DB == Info == * 0003167: (proj: Rates DB) Define integration points between CT2 and Rates DB software == Core need and more == We need to integrate CT2 an…') |
|||
| (One intermediate revision not shown) | |||
| Line 9: | Line 9: | ||
We need to integrate CT2 and external Rates DB software. | We need to integrate CT2 and external Rates DB software. | ||
| - | Main integration point is to send CT info to Rates DB and receive "rates data" (list of charges). At that point CT2 should populate CT2 | + | Main integration point is to send CT info to Rates DB and receive "rates data" (list of charges) for this move. At that point CT2 should populate CT2 database with this data on Save. |
Of course there are many cases that needs to be considered (as usual). Examples: | Of course there are many cases that needs to be considered (as usual). Examples: | ||
| Line 15: | Line 15: | ||
* what happens if operator changes some CT fields (origin, commodity table, etc) after rates has been populated | * what happens if operator changes some CT fields (origin, commodity table, etc) after rates has been populated | ||
* what if not all rates are available (origin trucking segment)? | * what if not all rates are available (origin trucking segment)? | ||
| + | |||
| + | Should we re-use existing "Estimated Charges Table"? | ||
== Requirements and Design Ideas == | == Requirements and Design Ideas == | ||
| + | |||
| + | |||
| + | == Solution ver 1 == | ||
| + | |||
| + | TBD | ||
Current revision as of 18:34, 12 October 2011
Contents |
[edit] Info
- 0003167: (proj: Rates DB) Define integration points between CT2 and Rates DB software
[edit] Core need and more
We need to integrate CT2 and external Rates DB software.
Main integration point is to send CT info to Rates DB and receive "rates data" (list of charges) for this move. At that point CT2 should populate CT2 database with this data on Save.
Of course there are many cases that needs to be considered (as usual). Examples:
- what happens if operator changes some CT fields (origin, commodity table, etc) after rates has been populated
- what if not all rates are available (origin trucking segment)?
Should we re-use existing "Estimated Charges Table"?
[edit] Requirements and Design Ideas
[edit] Solution ver 1
TBD
