Element Path: <cwt><SCHEDULE>
The schedule element can be used to set up periodic scheduling of certain activities in the CWT. One SCHEDULE tag needs to be added for each action that shall be performed. Multiple SCHEDULE elements can be defined for the same action, for Example: if the terminal shall be rebooted twice each day.
attributes
action
| Value: | Restart,
Reboot,
CodeOnTicket,
Collection,
CleanDatabase,
CommunicationPowerSave,
CommunicationReConnect |
| Description: | The action that shall be performed when the schedule is executed. |
| Restart means that the terminal restarts the application. |
| CodeOnTicket stores the value of schedulerData in var v651 |
| Reboot means that a complete reboot of the terminal is performed. |
| Collection means that a collection of an external pay unit is performed according to the set up. |
| CleanDatabase defines a job that will remove data that is running old from the database at a given time. |
Note: <CORE><dataCollection timeLimit=”X”> MUST be set to define what data in the database that should be considered old data.
|
|
| CommunicationPowerSave defines a job that will change communication configuration attributes’ (see section actionproperties) |
| CommunicationReConnect defines a job that will reset the modem and reconnect. |
name
| Description: | Name that describes the scheduled action. The name is logged when the scheduled element is executed. |
scheduleId
| Description: | Identifier of the scheduled action. Set the first schedule to id 0 and increment for each additional schedule element. |
schedulerData
| Description: | Data to be printer on the Ticket. Value is stored in v651 after executing the schedule |
startDate
| Value: | A valid date (YYYMMDD) |
| Description: | The date the schedule shall be executed. Used together with action=”CodeOnTicket” |
startTime
| Value: | A valid time (24h time) in the format HH.MM |
| Description: | The time of the day when the scheduled action shall be executed. |
The action=”CodeOnTicket” will set the value of the schedulerData in v651 so it can be printer on the ticket using @v651 in the layout attribute in the TICKET element
|
Setup with a system reboot scheduled to occur 23.00 every night:
<SCHEDULE scheduleId="0" name="DailyReboot" startTime="23.00" action="Reboot"/>
Setup with a Database cleaning scheduled to occur 12.00 every day and removal of all data older than ten days.
Note: that <dataCollection timeLimit=”X”> has to be set to define when data in the database should be considered old:
|
<CORE …>
…
<dataCollection timeLimit=”10”>
</CORE>
…
<SCHEDULE scheduleId="1" name=”CleanDatabase” startTime=”12.00”
action=”CleanDatabase”/>
| Example: | action=”codeOnTicket” |
The following example shows a configuration where the value “1234” is set to variable v651 when the schedule is executed. This option is usefull when you want to print e.g. a port code to a garage on a ticket
<SCHEDULE scheduleId="1" name="CodeOnTicket" startDate="20150101" startTime="03:00" action="CodeOnTicket" schedulerData="1234" everyXDay="0" />
Example: CommunicationReConnect
Note.
If startDate is set in a daily reoccurring schedule it will be executed every minute until the the next execution date has passes current date. For every execution the next execution date is increased by 24h.
Do NOT use a start date in the schedule
|
<SCHEDULE scheduleId="0" name="ReConnectModem" startTime="00:15" action="CommunicationReConnect"/>
