Two master rules constrain the PDCertificate issuance:

1. If course completion is enabled where the PDCertificate instance sits, then the course must be completed in order to generate the document.

1. In the general case, the certificate instance must simply be “available to the user” to be able to generate the certificate. So all moodle standard availability, grouping and visibility strategies can apply to drive issuability of the document.

If delivery lock is enabled on the PDCertificate, the end user cannot retrieve the document by himself even if it copes with all deliverability conditions. When the lock is activated, any new document is generated in the locked state, and is waiting for some operation to get the lock released. This might be done by the certificate management screens, or resulting of a workflow of the Integrated Moodle shop f.e.

• Capability index

• Integration of variable data into certificate templates

• Web services index

Server scripts can be activated in console mode on the operating server. These scripts are compatible with VMoodle virtualization.

• Migration from Community certificates (mod_certificate)
• Massive document regeneration

• Valéry Frémaux (Valery@activeproLearn.com): Development & testing
• Florence Labord (Florence@activeproLearn.com) : Functional Review, Documentation

—-

Back to PDCertificate index - Back to plugins - Back to catalogue