Dolibarr ↔ Moodle data synchronisation runs in both directions, on registers belonging to specific developments in Dolibarr, and from data produced by third-party plugins dedicated to training follow-up in Moodle (LearningTimeCheck).

1. Performed by Dolibarr
2. Uses the standard Moodle WS
3. Stores the Dolibarr id in the user's identification number

1. Performed by Dolibarr
2. Uses the standard Moodle WS

Feeding information back to Dolibarr sets up event listeners to capture particular course events and transmit states or values to Dolibarr through the Dolibarr web services API. As a control, Moodle records a specific trace of these events in a dedicated table/register.

Determines the moment when the training sequence was completed (all mandatory activities finished and accomplished according to the completion criteria).

Fired each time an activity module sees its completion state modified and influences the overall training completion rate.

Only the first entry into the training is considered, thus marking the start of the learner's activity in the training programme.

Fired each time a tracking item is modified (marked or unmarked), computing the mandatory completion rates and the accumulated flat-rate times. Transmits a time of “acquired” mandatory items.

The CLI script update_course_hours.php scans a course to transmit the hours of a session for a number of users:

  Refreshes and sends to dolibarr course hours from sessions

 Options:
 -h, --help            Print out this help
 -H, --host            the virtual host you are working for(*)
 -c, --course          the course to process
 -s, --session         the session (group) to process
 -u, --userlist        The user list to restrict processing for
 -v, --verbose         Set verbose mode on
 
 Example:
 \$sudo -u www-data /usr/bin/php local/dolibarr/cli/update_course_hours.php

(*) This script is compatible with VMoodle virtualisation.

• Component type: Local plugin
• Name: Dolibarr CRM feedback
• Technical name: local_dolibarr
• Supported versions: to

Back to the LTC component technical summary - Plugins index - Catalogue home

Note: a “Failing” status does not necessarily mean that the plugin does not work. This status reflects the result of automated tests checking the code against Moodle's strict standards. We are continuously working on bringing all supported plugins progressively into compliance with these development rules.

Branch	Continuous integration tests
405
501