Currently, the platform allows users to save or print Payment Certificates directly from the Maintain workflow; however, operational efficiency is significantly bottlenecked by the system's failure to generate unique, identifiable file names upon export. Unlike other standard outputs generated from the Portal which utilise dynamic naming conventions, Payment Certificates default to a static, generic file name which is the same every time so must be manually adjusted before you can save it.
The examples below outline the functional challenges and the proposed solution:
Lack of automatic unique file naming in downloads or export - Current behaviour:
When a user attempts to save or print a Payment Certificate from the Maintain workflow, the system assigns a generic, hardcoded default file name to the export. Because the system does not dynamically pull unique file names, users are forced to manually adjust the file name for every Payment Certificate before saving it to their local directory.
Suggested enhancement:
Update the export and save functionality within the Maintain workflow to automatically generate a unique, context-aware file name for all Payment Certificates. The system should dynamically append relevant variables to the default file name upon generation.
A proposed naming convention could be:
Payment_Certificate_[Contractor_Name]_[Certificate_ID]_[Date].pdf
Implementing this change would bring the Payment Certificate export feature in line with other standard Portal outputs. It will instantly eliminate the need for manual file renaming, drastically reduce administrative overhead, and ensure accurate, error-free file management when routing documents to accounting teams and software.
Reference:
A reference screenshot has been provided privately to illustrate the current generic "Save As" behaviour, highlighting the default "Payment Certificate" file name and the resulting file management difficulties
