Ops Admin (supercomponent)
From UG
(Difference between revisions)
(→Comments from Systems Analyst / Technical Requirements) |
(→Business Requirements) |
||
| Line 19: | Line 19: | ||
* We need different levels of access to different parts of Admin | * We need different levels of access to different parts of Admin | ||
| - | * Admin is shared by all offices, but some settings are office specific | + | * Admin is shared by all offices, but some settings / views are office specific |
Revision as of 20:02, 21 January 2010
Contents |
Prerequisites, Classified As, Parent Mantis
- Classified As: supercomponent
- Parent Mantis: tbd
- Prerequisites:
- read ...
- ...
Business Needs
As any large System CT2 should be configurable through the user interface. So that superuser who is not IT specialist could change setting as required during the system operation.
Business Requirements
- We would like to have ideally all dropdowns to be managed through the Admin (create/edit/delete/archive)
- We need different levels of access to different parts of Admin
- Admin is shared by all offices, but some settings / views are office specific
Technical Requirements
- We need to created Look and Feel for this component at some point
- Archived feature needs to be standardized
- For shorter lists I recommend using drop down not combo box
Technical Specification
Summary
User Interface and Functionality
Entities and Attributes
Special Cases and Misc
Look And Feel
Figures
Figure 1:
Questions and RFC
Known Non Critical Bugs
Links to Archived / Old specs
History
This doc has been created
--Alex 18:47, 21 January 2010 (UTC)
Re-design (Tweak) (Spec Update): ..... <summary> .....
<wiki date/signature>
- mantis: <link>
- Biz Req updated? N/Y
- Tech Spec updated? N/Y
