68 lines
1.4 KiB
Markdown
68 lines
1.4 KiB
Markdown
# Task P.4.1 - PDFMe Product Item Template Runtime Verification
|
|
|
|
Before implementing Task P.4, perform runtime verification against the real codebase.
|
|
|
|
Do not implement yet.
|
|
|
|
Verify:
|
|
|
|
1. Current quotation PDF runtime
|
|
- document-preview
|
|
- pdf-preview
|
|
- pdf-download
|
|
- approved-pdf
|
|
|
|
Confirm whether they use the same active template/version/mapping pipeline.
|
|
|
|
2. Current template page structure
|
|
- load active quotation PDFMe template from runtime source
|
|
- dump page count
|
|
- dump schema names per page
|
|
- confirm topic/signature page index
|
|
|
|
3. PDFMe table capability
|
|
Create a temporary verification only.
|
|
Test official PDFMe table with:
|
|
- 5 rows
|
|
- 30 rows
|
|
- 100 rows
|
|
|
|
Confirm:
|
|
- repeat header
|
|
- auto page break
|
|
- multi-page behavior
|
|
- row height behavior
|
|
|
|
4. Product item mapping
|
|
Verify actual source fields for:
|
|
- product code
|
|
- description
|
|
- specification
|
|
- quantity
|
|
- unit
|
|
- unit price
|
|
- discount
|
|
- amount
|
|
- remark
|
|
|
|
If no field exists, document the gap.
|
|
|
|
5. Seed/runtime source
|
|
Confirm whether runtime uses:
|
|
- database active template
|
|
- JSON file template
|
|
- both
|
|
|
|
Explain whether seed scripts must be updated.
|
|
|
|
Output required:
|
|
- verified runtime findings
|
|
- evidence/log snippets
|
|
- final implementation strategy
|
|
- rollback plan
|
|
- regression test matrix
|
|
|
|
Do not modify production template files.
|
|
Do not create a new rendering pipeline.
|
|
Do not begin implementation until this verification report is complete.
|