We heard your feedback and we’re taking action! We have added your long awaited subscription plans. Now you can split payments to smaller ones: monthly or quarterly.
The new subscriptions come with great benefits. Once subscribed, you will have free minor and major updates available without any additional fees. You can upgrade and downgrade anytime you want. Everything just works!
We also have deprecated OpenSSL libraries. From now Automation Workshop uses Windows built-in TLS/SSL solution, that guarantees that all security and feature updates are automatically included in the Windows Updates.
Security of communication channels are important for businesses, and we have introduced a setting to control the version of TLS/SSL used. You can now opt-in to use insecure and outdated SSLv3 for legacy systems, or to use industry standard TLS 1.2 to connect to modern systems in the most secure way possible.
Automation Workshop 4th version is another major milestone that brings a completely redesigned user interface along with new cloud actions and triggers. As Windows 7 EOL is approaching rapidly, we have aligned the user experience to the new UI paradigm that matches Windows 10 and Windows Server 2016/2019 user experience. While the new interface looks very modern and gorgeous, it does not add significant overhead to the very small memory footprint Automation Workshop has. We have even improved some code, so the newest version require event less memory while running complex tasks.
We have crafted four new triggers that can monitor Amazon S3 file service or any FTP server, be it Linux or Windows based, with the latest security standards right out the box.
With our new FTP & Cloud action you can manipulate remote files in easy and secure manner. These actions are solid addition to Automation Workshop’s already existing comprehensive set of file and folder manipulation actions.
We have heard your feedback! It is now possible to create a shortcut to the task on your desktop. Launch a task with a simple click on your desktop, without opening Automation Workshop every time you need to run a task.
As the Windows versions rapidly move on, we have also dropped support for .NET 2.0 and .NET 3.0 frameworks. Official support for Windows Vista and Windows Server 2008 R2 are also ended.
As you may already noticed, the febooti.com website has also been fully redesigned, it has more pleasant typeface and it is fully compatible with the latest mobile browsing standards.
Stay with us, the year of 2020 will bring many more new features!
It was just four years ago when we launched freeware version of Automation Workshop and at that moment the download count of commercial version passed over 300,000 mark.
Today Automation Workshop passed one million downloads (Free+Commercial). That’s about 700,000 downloads in 4 years.
We are very excited about accelerated growth of our flagship product. It took more than 3 years to achieve 100,000 downloads. And our free software offering clearly expanded our user-base behind what we have initially planned. What now? Setting a new goal – 2,000,000 🙂
We have just released Automation Workshop v3.0.0 which introduces 18 new actions in three categories – addition to the File / Folder category, as well as brand new – Loops and Text categories. Long requested actions for text string manipulations and loops are finally there. Now it is possible to use custom named variables and tokens from Split text action. This release also focuses on many improvements and a few bug-fixes. Read detailed information in Release notes for v3.0.0.
Here is a screenshot from Split text action, that is very handy when extracting data from CSV (comma-separated values) files, or when need to get values embedded into filenames.
Introduces Operations manager which collects all the important data in one place, and provides summary overview on Automation Workshop status and overall performance. There are numerous other fixes too. See the Release notes for the full list.
We have just fixed one nasty bug in the Setup file for Free Edition of Automation Workshop. It prevented running Example Tasks, and tasks that uses Dialog Boxes under Windows 8, 8.1 and Windows Server 2012, 2012 R2, if Microsoft .NET Framework 3.5 was not manually installed. Version number stays the same 2.3.0 – there are no other changes, only the Setup process was affected.
This version adds two new Wait actions. Wait for file and Wait for time. See the screenshots below. Also, improvements for the PowerShell scripts – it is not necessary to change Execution Policy to run PowerShell scripts from the Automation Workshop, Execute Script action.
Automation Workshop v2.2.0 features three new Folder actions – Duplicate, Move and Clear folder. Also, some improvements and new features here and there. View gallery below with screenshots of new actions.
There are certain limits of file name and path lengths in the Microsoft Windows. These limits are very high for most practical purposes, thus not encountered very often, and because of that, are somewhat vaguely understood. In this discussion I am mainly going to refer to NTFS file system as the currently most advanced file system supported by Windows (some parts or this article may also be true for FAT32 or exFAT); and Unicode as UTF-16 or in some places may be UCS-2 (only 65,535 chars). One well known limit is that filename cannot be longer than 255 Unicode symbols. Another popular limit is 260 Unicode characters – maximum whole path length under Windows.
By putting these two constants together you can model various examples of path limits, for example, you can create the following paths:
C:\1\2\3\4\5\6\7\8\9\0\a\… [about 16,383 similar folders] …\your-file.txt
C:\[Folder name consisting of 255 chars]\[Another long folder]\some-file.txt
So how many is these 65,535 symbols/characters? As you can see in the above examples, the whole Wikipedia article (average English) fits into path name, even when every word is separated with backslash character (\). And actually you need to separate words in the path with backslash, because of each file / folder name has a limit of 255 characters.
If you try to create such file, folder or path in the Windows Explorer, you won’t succeeded. Windows Explorer won’t let you do that, and it may not show any error, it simply may limit how many symbols you can enter. But this part depends on the Windows version. For example, Windows 8.1 Pro sometimes show an error:
Even latest Microsoft OSes – Windows 8.1 and Windows Server 2012 R2 cannot display / manage these folders correctly. It won’t allow you to click on the last folder that is visible, and it does not show path longer than ~512 chars. It simply does not show up, but it is there. Also, it does not refresh the folder content, so it shows the last “state”. In our case it is the same folder that we are inside. See the screenshot below:
Also, Windows Explorer does not allow you to delete such folder. It shows the following error on Windows 8.1 Pro:
Also, it says “The source file name(s) are larger than is supported by the file system…”, which is a bit misleading. It is not supported by Windows Shell, not the file system. But perhaps that message is meant for novice users, not administrators and PC experts.
Windows Shell is not the only sub-system that can’t handle such paths. For example, CMD.exe, also can not:
Even newest PowerShell gives up:
There are plenty of situations where 260 characters is not enough. For example, HTTP request has limits from 2,083 to 8,192 characters, and you want to use file system directory structure for your web application. Or perhaps your a backup application is configured to backup all user files to location “C:\Username\2014-Aug-27\Some-other-folder\” and what happens when user have already created path with a maximum of 260 characters? A Backup program should never fail, and so we must be able to overcome this limit.
What about Automation Workshop?
All file / folder actions and triggers, and many other actions and services of Automation Workshop support very long file and path names. Even more, the free edition also supports this all right out of the box. There are some limitations here and there. For example, it may be cumbersome to enter very long path in the standard input fields. However, there are very handy means to overcome this. The Variable Wizard’s “Read from file” is one of them:
Filename length of 255 characters is not hard-coded. Windows API GetVolumeInformation can return greater values in future, however I have never seen lpMaximumComponentLength to be more than 255.
Another program that supports very long paths is newer versions of Far Manager (open source application). I believe, that most file managers are not limited as Windows Explorer, but I have not tried them.
Microsoft article about File naming, Paths, including 8.3 filenames, reserved characters, Namespaces. Read here.