Tasker 4.0 December 18, 2020
|Tasker||v4.0||Dec 18 2020||1 MB||e0b99c9f4ffdb2294dab5596c9d9613f|
- [+] removed the requirement for the schedule start day.
- [+] fixed the schedule reloading so that the new schedule takes effect and does not require a reboot.
- [+] Added a user.alert message.
- [+] Added a tasks.get handler.
- [+] Added a tasks.list message.
3.7, 02 oct 2020
- [+] Added tracking the parent workspace name so that all of the tasks can be removed from the collection that belong to a workspace that is updated or removed.
3.8, 07 oct 2020
- [!] fix error for only handling 8 output triggers.
- [!] fix error where a temp probe couldnt be assigned to a variable.
- [+] added http post functionality.
3.9, 18 nov 2020
- [!] fix error where parameters used to have to be named starting with $.
4.0, 10 dec 2020
- [+] variables that start with $$ are global variables. These are global WITHIN the workspace.
- [+] added Control Panel Switch implementation
- [+] added a tasks.get WebSocket handler
- [+] added a task.list WebSocket handler
- [+] added http post functionality
- [!] scheduling changes take effect immediately when a workspace is reloaded
- [+] validation on task names, device names, logger names, signal names, trigger names, and schedule names to prevent spaces and bad characters. Names can only be alphanumeric and can include underscores.
|Tasker||v3.3||Jul 30 2020||1 MB||5783b3bda071222b48775e5ffb9e4b3d|
- [+] adding duplicate instance check
- [+] variables that start with :: shall be global
- [+] add TCP Recv
- [+] add TCP Close
- [+] new execute script action
- [+] uses new scripting engine
- [!] fixed issue where dst timezone was not being logged
- [+] adding action to prepend to file
- [+] adding retry logic to external identifier objects. included creating external identifier parent class
- [+] adding action to copy file
- [+] adding action to move file
- [+] add ascii tcp and serial servers for tasker control
- [~] now preventing spaces in workspace names. current workspace files with spaces will be renamed with an UNDERSCORE
|Tasker||v3.2||Jun 18 2020||958 KB||953712536000b330ad267047b7ee274d|
- + added 4-20ma modules
- + added 10v modules
- + added email send attachment option
|Tasker||v3.1||May 05 2020||942 KB||47e03374e8a8791ec0a922f38e62f174|
- Added If / Else Block Task Action
- Added While Loop Task Action
- Added SNMP Trap Task Action - Tutorial
- Help pages are in progress
- Upload and download workspaces
- Delete a workspace (Workspace is backed up)
It has been a while since Tasker was released. Tasker was a quick attempt at making a replacement for the Task Manager application that has been around for more than a decade, starting on the Series 3.
Ample time has now been taken to create a fully capable application that will be every bit as functional as Task Manager but offer the benefits of a rewrite, using configuration files and the latest web technology.
Some of the changes and new features are as follows:
- Faster– The tasks are executed much faster and the triggers and schedule are monitored in real-time instead of once every 5 – 10 seconds.
- Workspaces - Separate configuration logic into multiple workspaces. Then multiple workspaces can be loaded on the JNIOR at the same time.
- Tasks are now separate from triggers. In Task Manager a Task was created and a Trigger was configured to get the Task to execute. In Tasker 3.0 Tasks are a separate entity that can be executed several different way including manual execution from the configuration page and being requested via an ASCII TCP connection.
- Tasks can now send data via an Ethernet connection. To do this, a Device must be created so that the action can specify which device to send the data to. Multiple devices can be configured.
- New Actions – We implemented actions that were previously available in Task Manager but are introducing many new actions like external module control, TCP communication and control structures.
- Drag n Drop – Drag and Drop functionality makes it easier to design your Task logic.
- Signals are now created to assign a specific property of a I/O point or sensor a name. The name can then be used in Tasks, Triggers or Loggers.
- Loggers can be created to define the file name and schema or what data should be logged to that file. Each line in a Logger will be prepended with a timestamp followed by a comma. Loggers also allow you to define the number of files that should be kept with the given naming pattern. Name patterns can include date patterns. This will help you create a file per day for example.
- Schedule – The schedule has additional options.
- JSON Configuration files are used now instead of registry keys. Registry keys were limiting in size. The Series 3 could only store 255 characters in a registry key. It is much easier to upload configuration files to other JNIORs to replicate setups.
- User Interface – The User Interface is now a native HTML application that uses the latest web technology. The latest web technology uses native HTML controls and Web-sockets to communicate with the JNIOR from your browser. This will allow accessibility over remote connections as long as port 80 is available. This is now consistent with the communication method used by the DCP. Task Manager had always used Java Applets. The Java Applets have not been able to launch in browsers for several years as they became frowned upon as security vulnerabilities.
This was just a short list of changes and new features. The documentation for Tasker should explain these topics as well as many others. If there is anything you don't understand please reach out to us for help. Additionally, if you have any suggestions or need the JNIOR to do something specific for you, please let us know.
For more information go to the Tasker Page