Content Previous Next |
Topic Content | |||||||||||
|
| ||||||||||
This option defines action properties for a SMS message which is sent via an Android-powered smartphone connected to a computer via WiFi, Bluetooth, or cable (provided that it has its own unique IP address). | |||||||||||
|
| ||||||||||
| Select a name or multiple names of pre-configured Recipient List(s) by checking appropriate items. If there is none, or you need to create a new one, access Recipient List account properties as described below. | ||||||||||
| Click the 'Configure' button to access the Recipients List manager where you can create and configure your mobile accounts. Detailed information about this can be found here. | ||||||||||
|
| ||||||||||
AnyFileBackup connects to an Android smartphone via HTTP protocol and, therefore, uses HTTP Accounts manager to create and manage smartphone-related accounts. | |||||||||||
| Select a name of a pre-configured HTTP account from the drop down list. If there is none, or you need to create a new one, access HTTP account properties as described below. | ||||||||||
| Click the 'Edit' button to access the HTTP Accounts manager where you can create and configure your HTTP accounts. Detailed information about this can be found here. | ||||||||||
|
| ||||||||||
This option is visible and applies if, and only if, the action is a PART of the Backup step of the Task Scenario.
Additional File Filter distinguishes files by mask determining to which file(s) this particular action will or will not apply. In all other respects it is no different from the Additional File Filter that exists in every Target. | |||||||||||
| A list of file masks that describe files to which this particular action will apply.
Please note, that these masks should somehow overlap with masks specified in SOURCE > Additional File Filter > Included Files (if in use) and should not be completely excluded by masks specified in SOURCE > Additional File Filter > Included Files (if in use). Otherwise, this action will not apply to any files. | ||||||||||
| A list of file masks that describe files to which this particular action will not apply. | ||||||||||
|
| ||||||||||
| A text of an SMS message. | ||||||||||
| The maximum length of an SMS message. This helps to ensure that no lengthy messages (which are in fact several standard messages which look like one) are sent and also to control the budget. | ||||||||||
|
| ||||||||||
| This option is visible and applies if, and only if, the action is located BELOW the Backup, Two-Way Synchronization, Monitoring, or Clean-up step of the Task Scenario.
This is a description of an event upon occurrence of which this action will be performed. The event relates either to Source or to task generally. The following events are covered:
-- Backup stage (all files have been transferred from Source to Target(s) and other actions within Backup have been performed), or -- Two-Way Synchronization stage (Source 1 and Source 2 have been synchronized), or -- Monitoring stage (Source parameters that are being monitored are exceeded their threshold limits or relevant changes have occurred).
When any of these stages is completed properly (depending on the task type), action with this condition will perform.
| ||||||||||
| Press the 'Start' button to direct AnyFileBackup to immediately launch this action. This will verify whether all above settings were entered correctly; all errors, if any, will be displayed in a log window. | ||||||||||
| If enabled, this action is active and will be used in Scenario. If disabled, it will remain in the Task Scenario but will be completely ignored by task. To distinguish it from enabled actions, disabled actions are strokeout and coloured in gray. | ||||||||||
| This is a custom name that will be displayed in the Task Scenario instead of the default title. Press the 'Apply' button for changes to take effect. |
Content Previous Next |