Page Comparison

...

Scheduled Tasks

The Scheduler page lists a variety of actions that the system performs regularly to aid the System and Order Administrators. These actions are referred to as “system cases”. In the Scheduled Tasks section, you can view the following:

• System Case: The designated system case

• Execution Time: The next time the system case action is scheduled to be performed

• Interval: The time intervals at which the task is repeated

• Enabled: The current status of the system case. It can either be enabled (“True”) or disabled (“False”).

• Edit: Click

  the Image Removed

  the Image Added button to enable or disable a system case.

• Delete: Click the

  Image Removed

   Image Addedbutton to remove a system case. To recover a system case, you must edit the Scheduler configuration file.

• Execute: Click the

  Image Removed

  Image Added button to perform the action immediately. 

Tasks Execution History

In this section, you can view all system cases that were previously executed. You can filter the list by clicking the Image Removed Image AddedSelect Date button and selecting a date. Alternatively, you can enter a date manually in the field. You can also change the list organization as follows:

• Click Date to organize the list chronologically (newest to oldest) by the date and time the task was last executed.

• Click SystemCase to organize the list alphabetically (A-Z) by the name of the system case.

• Click IsSuccessful to organize the list alphabetically (A-Z) by whether the system case was executed successfully or not. There are only two possible conditions in this field: “True” or “False”.

System Case Processes

The following list describes the system cases and the specific tasks each case performs during execution:

SC1 – Collect

...

Network Daily Usage

• System parses logs in order to determine traffic values (grouped by devices).

SC2 – Charge

...

Network

• System checks incomplete Traffic Invoices:

  • If an invoice is associated with a Grace Subscription or with no subscription, it will be skipped.

  • If

    an account’s billing mode

    the billing mode of a network is set to “Manual”, all pending Traffic Invoices will be marked as paid.

SC3 – Suspend

...

Network

• System checks all active

  accounts

  networks that are in the Pending Suspension state.

  • If the deadline has been reached, the

    account

    network will be moved to the Suspended state.

  • Each

    account suspended

    network suspended using this case receives a notification E-mail.

SC4 – Handle Subscription Expiration

• System checks all Grace Subscriptions.

  • If the deadline for a Grace Subscription has been reached, it will be deactivated.

• System creates a Traffic Invoice and marks the subscription as deleted.

• The Order Administrator receives an E-mail notification of this action.

SC5 – Charge Subscription

• System checks all active subscriptions that were not charged in the last month.

• System calculates traffic and creates a Traffic Invoice for each subscription.

• The newly created Invoice is marked as “Unpaid”.

• Traffic counters of all processed Subscriptions are dropped.

SC6 – Suspend Subscription

• System checks all active Subscriptions that are in the Pending Suspension state.

  • If the deadline has been reached, the Subscription will be moved to the Suspended state.

  • Each

    account Suspended

    network Suspended by this case receives a notification E-mail.

SC7 – Device Inactivity Warning

• System checks for all active devices where the following conditions apply:

  • The “Last Connect Time” is older than the “Device Inactivity Timeout”

  • The “State” is set to “Not Notified”

• System checks appropriate

  account

  network profiles and determines whether the “Device Inactivity ­Notification Enabled” property is set.

• System sends an

  E-Mail

  Email notification to the appropriate accounts indicating all inactive devices.

• The state of these inactive devices is updated to “Notified”.

SC8 – Device Logs Parser

• System checks the Device Logs Queue for incoming files

  • For any file found, the device owner is determined and the header is validated.

• System determines the record type for each file.

• System validates and checks each record for Filter Expression.

• System populates the records and separates lists according to type.

• System compiles an XML spreadsheet for each list.

• System deletes the incoming Device Log file.

SC9 – Device Logs Report Builder

• System checks for parsed Device Logs stored by the SC8 process.

• System determines whether the new information is included in existing reports.

• System generates new daily, weekly, and monthly reports for data not included in existing reports.

• System updates the affected existing reports, keeping sorting records in the report.

• For each affected report, the “Last Updated” date is changed to the current date.

• System saves new reports in the determined directory.

• System registers the new reports in the database, making them accessible to users.

SC10 – Generate Thumb (content_id)

• System generates thumbnails for video files as a temporary task.

  • This task does not appear in the task list until it is triggered by the Web Services node for a specific media item, which is identified by its content_id.

  • This task disappears from the list after execution.

SC11 – Handle Content Expiration

• System searches for HTML page assets and deletes them after 24 hours if they appear orphaned.

SC12 – Handle Dynamic Playlist Validity Dates

• System updates (rebuilds) the .xml files for Dynamic Playlists, applying validity dates to items in each playlist.

SC13 – Handle Live Text Feed Validity Dates

• System updates (rebuilds) the .xml files for Live Text feeds, applying validity dates to items in each feed.

SC14 – Handle Live Media Feed Validity Dates

• System updates (rebuilds) the .xml file for Live Media feeds, applying validity dates to items in each feed.

SC15 – Handle Obsolete Device Screenshots

• System deletes device screenshots, beginning with the oldest, once the number of image files for a device reaches 500.