pelagia-portal

History

Hardik b2bfa63f61 fix(export): show approver as signatory on PDF and XLSX reports The left signature block on generated PO documents (PDF and XLSX) was showing the submitter's name as the authorized signatory. The signatory should be the manager who approved the PO, since they are the one authorizing the expenditure on behalf of the company. The approvedBy name was already extracted from the APPROVED / APPROVED_WITH_NOTE action at the top of the export route — it just wasn't being used in the signature block. Now both the PDF and XLSX templates use approvedBy for the left sig block, falling back to the submitter only if the PO has not yet been approved (e.g. when exporting a draft). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-16 15:57:39 +05:30
..
pelagia-portal	fix(export): show approver as signatory on PDF and XLSX reports	2026-05-16 15:57:39 +05:30

Hardik b2bfa63f61 fix(export): show approver as signatory on PDF and XLSX reports

The left signature block on generated PO documents (PDF and XLSX) was
showing the submitter's name as the authorized signatory. The signatory
should be the manager who approved the PO, since they are the one
authorizing the expenditure on behalf of the company.

The approvedBy name was already extracted from the APPROVED / APPROVED_WITH_NOTE
action at the top of the export route — it just wasn't being used in the
signature block. Now both the PDF and XLSX templates use approvedBy for
the left sig block, falling back to the submitter only if the PO has not
yet been approved (e.g. when exporting a draft).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-16 15:57:39 +05:30

pelagia-portal

fix(export): show approver as signatory on PDF and XLSX reports

2026-05-16 15:57:39 +05:30