Sign a certificate
Signing is the quality gate in DASH. When a certificate is signed it moves from Awaiting approval to Approved for submission, and its data is locked for release. Only a Quality Person, Admin or Account Owner can sign.
What must be true before you can sign
Section titled “What must be true before you can sign”DASH enforces three hard gates when you sign. If any fails, signing is refused and the reason is shown:
- Required fields are complete — every property mapped as required must have a value.
- Validation rules pass — all error-severity rules on the definition map must pass. Warnings do not block signing. See Validation rules.
- Signature matches your name — the text you type must exactly match your full name on your profile.
Sign the certificate
Section titled “Sign the certificate”- Open the certificate from the Certificates list. Confirm the status chip reads Awaiting approval.
- Review the mapped data one last time in the document view. If anything is wrong, send it back to draft and correct it before signing — see Review & edit mapped data.
- Select Sign. The signing dialog opens and lists any unmet gates at the top.
- Type your full name exactly as it appears on your profile into the signature field.
- Select Sign certificate to confirm.
The status changes to Approved for submission and the signature — your name, the timestamp and the account — is recorded on the certificate and in the Audit log.
After signing
Section titled “After signing”- The certificate is ready to submit to its data channel — see Submit & track status.
- If a gate blocked you, fix the underlying issue (a missing value, a failing rule) and try again. A persistent failure usually points at the definition map — see Validation failures.