Submissions use approved versions only
Why a submission needs approvals before it can be frozen, and the version and approval record in the package.
A submission can be frozen only when everything it relies on has an approved version: the product, the knowledge groups its submission type reads, its documents and its files. When it is frozen, exactly those approved versions are pinned to it.
Who can use this
- Owner
- Admin
- Compliance
Steps
1. Freeze the submission
Click "Freeze". If something is not approved yet, the card "Not approved yet" lists each object with its type and a link. Approve them or request approval, then freeze again.
2. Check the pinned versions
A frozen submission shows "Pinned versions": the approved versions it relies on. Later changes to the objects never change what goes out.
3. Download the package
Click "Download package". Besides the documents and files it contains the "Version and approval record" as a PDF in the language of the package, and the same data in the manifest.
4. Reopen
Click "Reopen" to go back to draft. The pins are removed and set again at the next freeze.
Fields and options
- Version and approval record
For every object: the approved version, who approved it and when, the reviewers with their decisions, the commit messages since the previous approved version and the matching audit log entries with their hash values, so the record can be checked against the audit log. Times are in UTC.
Good to know
- Advisor warns on the Product side when a submission that has not been filed is due within 14 days.
Related
- Versions of compliance objects
Save drafts with a commit message, approve them as a major version and start a new draft when something must change.
- Requesting and giving approval
Ask one or more reviewers for approval, decide as a reviewer and keep track of open reviews.