blocks:dashboard:technique
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
| blocks:dashboard:technique [2017/08/11 20:19] – [Capabilities] admin | blocks:dashboard:technique [2026/01/13 07:58] (Version actuelle) – modification externe 127.0.0.1 | ||
|---|---|---|---|
| Ligne 1: | Ligne 1: | ||
| + | < | ||
| ===== Technical guide ===== | ===== Technical guide ===== | ||
| ===== Dashboard block ===== | ===== Dashboard block ===== | ||
| Ligne 11: | Ligne 12: | ||
| Thus it is **largely preferable the dashboard block instances be setup my a Moodle admin or a manager** and provided to the statistics "end users" using standard enroll methods. Dynamic filters and parameters should allow administrators to give useful and sufficient behavior control to end users for their daily needs. | Thus it is **largely preferable the dashboard block instances be setup my a Moodle admin or a manager** and provided to the statistics "end users" using standard enroll methods. Dynamic filters and parameters should allow administrators to give useful and sufficient behavior control to end users for their daily needs. | ||
| - | ==== Tâches programmées | + | ==== Scheduled tasks ==== |
| - | * [[: | + | In spite of the new programmable schedule of tasks in Moodle after version 2.7, the dashboard block keeps his own trigger scheduling programming. the block uses a single task to process all blocks that need export data. You should not use this task to schedule a single export output, as this will limit all other instances in the future. |
| - | [[: | + | * [[: |
| + | |||
| + | [[: | ||
blocks/dashboard/technique.1502482783.txt.gz · Dernière modification : (modification externe)