cron batch automatic change

Batch actions

Since Tiki6, and extended in Tiki9.

This feature allows you to do some actions in batch. You still need to set up a cron job or other tools to activate the features described here.

Email sending from Daily reports
Email sending from Newslettters
Trackers
Updating advanced rating

Email sending from Daily reports

Using tiki-user_send_reports.php

See Daily reports

Email sending from Newslettters

Using tiki-bach_send_newsletter.php

See Newsletters and
http://doc.tiki.org/Newsletter+User#Sending_newsletters_with_a_cron_batch_job

Trackers

It is possible to specify automatic item status change for a tracker after
a certain period of inactivity. Moreover, some emails can be sent to warn the user about that change at some predefined time before the status item change is planned to happen.

The task that must be run is

cron command

cd /path_to_tiki_root; php tiki-batch_todo.php

In the modification/creation panel of a tracker, you can specify a change of status from one status (optional) to another after a certain time from the creation or last modification of an item. You can also specify if you wish to send a notification to the item creator. The subject of the message is a string. The body of the message is a smarty resource, either a wiki page or a template, which can use a few variables inside:

{$todo_itemId}
{$todo_tostatus}
{$todo_fromstatus}
{$todo_after}
{$todo_desc} , which is fed with the first "isMain" type of field from that tracker, which could be the "title" or "name" assigned to that tracker item at item creation, etc.

Example:

wiki page changeStatus

In about {$todo_after|duration}, the item {$todo_itemId} ("{$todo_desc}") will change
from the status {$todo_fromstatus} to {$todo_tostatus}

In this example open items older than one day will have their status changed to pending. The item creator will receive a notification 23 hours before the change.

The status change is done before considering to send notification.
The time the event is approximate as it depends of the frequency of the cron