Docs Tab

From UG

Revision as of 20:59, 25 January 2010 (edit) Alex (Talk | contribs) ← Older edit		Revision as of 21:08, 25 January 2010 (edit) (undo) Alex (Talk | contribs) (→Figure: XXX) Newer edit →
Line 39:		Line 39:
	=== Figures ===		=== Figures ===
-	==== Figure: XXX ====	+	==== Figure 1: Docs Tab, Default state, No saved docs ====
		+
		+	[[File:Docs Tab Default state No saved docs.JPG]]
	== Questions and RFC ==		== Questions and RFC ==

---

Revision as of 21:08, 25 January 2010

Contents 1 Classified As and Parent Mantis 2 Business Needs and Requirements 3 Technical Specification 3.1 Summary 3.1.1 3 step process 3.2 User Interface and Functionality 3.3 Entities and Attributes 3.4 Special Cases and Misc 3.5 Look And Feel 3.6 Figures 3.6.1 Figure 1: Docs Tab, Default state, No saved docs 4 Questions and RFC 5 Known Non Critical Bugs 6 History 7 Ver 1.1 7.1 Requirements 7.2 Design 8 DB

Classified As and Parent Mantis

• Classified As: (large) component
• Parent Mantis: 1686

Business Needs and Requirements

Technical Specification

Summary

3 step process

There are 3 independent steps:

• step 1) generate template based on CT record data
• step 2) tweak template
• step 3) generate pdf (based on template values) and print it

Important observation: generated pdf is defined only by template and not by default state of the template you get after step 1.

User Interface and Functionality

Entities and Attributes

Special Cases and Misc

Look And Feel

Figures

Figure 1: Docs Tab, Default state, No saved docs

Questions and RFC

Known Non Critical Bugs

History

Ver 1.1

Requirements

Add ability for operator to "save work". Common case: operator selects pdf; clicks "show template"; edits some info; get's distracted; opens some other CT, etc; opens that CT again - all edits from pdf template is gone. We need to be able to save and keep last changes to template for every doc.

Design

Up to developer. Pls review with Sys Analyst before coding.

DB