Changes between Version 5 and Version 6 of Drupal HowTo Write Cron Tasks for CiviCRM
- Timestamp:
- 11/19/13 11:37:30 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Drupal HowTo Write Cron Tasks for CiviCRM
v5 v6 12 12 == GENVASC 'mark as available' activity == 13 13 14 '''This has been applied to test, but not production.''' 15 14 16 The code is located in the ''genvasc_labels'' module and uses the CiviCRM API. The process is as follows: 15 17 … … 22 24 1. Update the 'Mark available for cohorting' activity status to be completed. 23 25 26 '''This change requires the amended Case API that has been submitted to CiviCRM as a patch.''' The original version of the {{{civicrm/api/v3/Case.php}}} has been renamed to {{{civicrm/api/v3/Case.php.old}}}. 27 24 28 == Note regarding Cron System == 25 29 By default, the activities and entries created by automated jobs in this way are assigned to whichever user triggered the cron job, in a similar way to the user who accesses an API call in a module being assigned to the results of that API call.