Hello,
I am observing an odd design pattern related to Policy reviews when you’re using an attachment as the source of the review (e.g. a PDF attachment)
When you use attachments for reviews, the expected behavior is that the PDF will appear/render in the policy portal and that “download” will provide a copy of the PDF.
However, if you conduct a “no update” review, where you maintain the same version number and do not attach anything, instead the Policy Portal will not render anything and the “download” provides a copy of the review but not a copy of the policy itself.
My expected behavior is that if you conduct a review, you should either:
- Require an attachment or block the review
- Provide the last PDF attachment to the most current review, especially if the version number does not change.
Right now, if you conduct a review without uploading a new attachment, you will break your PDF rendering without any warnings/errors.
Perhaps the easiest solution is to “require” an attachment to complete a review when the underlying Policy is set to “attachment” for the Policy Content.
A current workaround is to attach a PDF after completing the review and PDF rendering will work again.