This plugin allows you to post process files using a powerful set of tasks.  You can move files, rename them, copy them, execute external programs, write text files, use date variables, multithread operations, copy to FTP/FTPS/SFTP servers, etc.

[CrushTask Functions] helps explain some of the advanced string manipulation functions you can do in CrushTask, typically in a UserVariable task.

[Example Task Flow -- Folder monitor triggered task.|CrushTaskExample]\\
[Example Task Flow -- Find local files and copy them to remote servers.|CrushTaskExample2]\\
[Example Task Flow -- Expire users password and email password reset link.|CrushTaskExample3]\\
[Example Task Flow -- Import users from *.csv file.|CrushTaskExample4]\\
[Example Task Flow -- Allow username lookup on internal share.|CrushTaskExample5]\\
[Example Task Flow -- Delete subfolders but keep root folders.|CrushTaskExample6]\\
[Example Task Flow -- Self register and enable accounts.|CrushTaskExample7]\\
[Example Task Flow -- Notify users of expired password.|CrushTaskExample8]\\
[Example Task Flow -- Auto register and set password on first logon.|CrushTaskExample9]\\
[Example Task Flow -- Auto Update CrushFTP.|CrushTaskExample10]\\
[Example Task Flow -- Upload with approval and move files.|CrushTaskExample11]\\
[Example Task Flow -- Looping though files and delete copied files.|CrushTaskExample12]\\
[Example Task Flow -- Find new files and send a notification or process them.|CrushTaskExample13]\\

The source filter is on every task.  It will filter out items that don't match the source from being included in the current task item.  So you may want to apply certain actions to specific file types on a  per task basis.

MultiThreaded allows for tasks to run in parallel.  Be sure to add a Wait task to have things stop and wait for all the separate threads that a re running before allowing the entire job to complete.  This is useful to transfer a file to multiple external locations at the same time instead of sequentially.

The error jump field allows you to jump to a particular task item in the list if the current task fails for any reason.
The find task will scan a particular folder, or remote FTP, or SFTP server getting directory listings recursively up to the depth allowed.  These found items can then be used by future task items.  This task is often the starting item in a list of tasks.

You can enable verification that the files are not changing to prevent getting files that are still being written to.  If you want to preserve the folder path to the files for a future copy, enable the "Use absolute paths" option.

The last modified selection will only find files that are the specified age, either newer or older.

If no items have been found, it can continue scanning for up to the maximum minutes defined, with a pause of the defined number of seconds between scans.  If at the end of all of this, no files are found, you can cause the task to fail with the "Fail if no files are found" checkbox.

If the FindCache option is used, the items found will further be filters out so prior known items aren't found again.

This cache task allows you to load in a prior listing of items to be compared with a new listing.  This allows you to filter out prior known items that have already been processed without ever altering them on the remote server.

You first do a "read" mode on the FindCache, specifying the name.  Then in the copy task, you specify that same name.  If the Find task item finds an item already in the list, then its ignored.

Next you would do another FindCache and do a "write" mode so it saves the list back to disk with the updated listing.  Any items the FindCache knew about that are no longer on the server are removed from the list that is saved as well.

The copy task will take a collection of files that were either "Found" using the Find task, or passed into the plugin through an event defined in the user manager.  The files in the list can be filtered down using the "Source filter" field to limit what you are copying.  An example might be *.txt.  The destination can reference the {path} to the original file.

So you may do: /Archive/{path}  or  /Archive/{parent_path}/{name}

The wait amount is how long to wait to verify the file is no longer being written to by some outside process.  The modified date, and file size are both compared.  It will wait put o the max amount of time before giving up and aborting the job.

If you want to work with the copied files, you can have them added intuit he list of files that are being processed for future tasks.  Be careful with this because if you do this, and then do a delete, both the original and copy would then be deleted.

The move task is similar to the copy task but it will just move the file to the destination location.  If the move is across physical locations, it will copy, and then delete the source item to accomplish the move.

The delete task will delete items that are in the list of files being worked with.  So this includes items from the "Find" task, or items passed to the plugin through an event.  It will keep attempting a delete for x seconds in the event the file is in use, or locked, etc.

The email task can send customized emails out.  These emails could contain the custom form fields from an upload of a web browser, or information about the files being uploaded.  <LINE>{name}</LINE> can be used to repeat for each file item being listed.  Files can also be attached to the email message as well. (small files)

The body can also generate temporary share links.  Examples:\\{share_move_30}\\{share_move_15}\\{share_reference_45}\\{share_copy_7}\\{share_copy_22}\\

Where the middle part is the share type, and the ending part is the number of days.

This task allows for running an external process.  This can allow outside integration processes to be performed.  The output of these programs are fed into the log for this task to allow for monitoring of its results.  


*Command:     the name of (or full path to) the external binary. In case running scripts, here comes the script interpreter binary name, cmd.exe for a Windows batch script\\
              or sh , /bin/bash , etc. for a linux shell script, etc.\\
*Argument:    the list of arguments passed to Command, the list items separated by Separator character ";" (semicolon) by default. In case running scripts, here comes\\
              the script file name followed by any arguments to be passed to
*Working directory: the parent path of the binary or script file, we do a change directory into this folder before invoking Command. In case running scripts, here comes\\
                    the full parent path of the script file
*Environment variables: leave it empty, rarely needed
the task will feed it's output to the next task item, if any, can be referenced by the {execute_log} server variable
The list of items being processed is passed from task to task, growing when you use the Find task to add more.  The Exclude task allows you to remove these items from further processing.  once excluded, they are no longer referenced and future task steps will not process them in any way.  The source filter is used to find the items to exclude.  So excluding "*" would remove all items from the list.

This allows you to create a new folder at the specified location.  During normal copy operations, directories are created as needed.

This task will instantly pass in any found files to the [preview] worker inside of CrushFTP requesting for the files to have their thumbnails generates.  This is only useful if you are showing previews of image type files on the [WebInterface].

This task will rename a file in its current location to have a new name.

This task will jump to a specified job, and task item.  If the job is left empty, then the task in the current job will be located and used.  If a job is jumped to, the task that matches the name will be the starting point in that job.  Jumping to a job is only possible for enterprise licenses.  Once the jumped to job is complete, the task will continue on to the next step of the current job.

This allows you to make a variable that you will then reference in other future steps.  So you might make a "archive" variable, and then reference it in other steps as {archive} so that fi that changed, you would only need to change it in one location.

This will unzip a file that is in the list.  Its suggested you filter down on *.zip to only get valid items in case of a mixed list of items.  The external unzip method will call the OS's unzip utility to unzip.  This will only work on OS X, or Linux / Unix based systems.  Otherwise the internal method will work too.

This will take all items in the list and zip them into a single file.  Its suggested to then do an Exclude task to them remove all items, and then go Find the single zip you just made if you want to do further processing.

This task will pause for the requested number of seconds before going to the next step.  You can also enable the wait for previous threads, and it will wait indefinitely until the prior MultiThreaded tasks have all completed.

This task will write to a log file, or xml file, or whatever you like, information about the files being processed.  One example is to create an RSS feed of incoming files.  The RSS configuration is pre-filled in the fields by default.  You can have the task find a specific piece of text starting from the beginning of the file, and then insert the new data there, or find a specific piece of text going from the end of the file, and then append data there.  If the file doesn't exist yet, the New File section will be written to the file before it performs the searches and updates to the file.

This task allows for taking the items in the list and sending them on to a AS2 server.  You can configure all the typical AS2 settings for encryption and signing.

The HTTP task lets you post events to another HTTP server with information about files that were transferred.  You can control various aspects about how the connection is made and put in your variables for the data you want posted.

Files can be encrypted, or decrypted using PGP public/private keys.

This task allows you to scan a mail server finding matching emails based on subjects or senders, and pull out attachments from them.  You can optionally delete the messages after your done too.  These attachments can then be processed with CrushTask in additional methods.  This task type is only allowed for Enterprise licenses.


Here is a list of other possible variables:
subject, body, from, mail_index, mail_type, url, the_file_name, the_file_path, modified, from_prefix.

!Users List
This task can iterate through your users, and make calls to another task item for each user in the list.  A good use for this might be the popimap task if you wanted to monitor the user's email server and give them files that had arrived for example.

Here is a sample class that needs to be in the class path.  You then reference it directly in the job.  You need to include the library for CrushTask.jar for this.  Then in your java class, reference "task.MyClass"

package tasks;

import java.util.Properties;
import java.util.Vector;

public class MyClass extends Task

	public MyClass(Properties prefs, Vector items, Properties info, Vector threads)
		super(prefs, items, info, threads);

	public Task go()
		return null;

	public void run()
			newItems.addAll(items);//keep all the items for the next task.
			for (int x = 0; x < items.size(); x++)
				Properties p = (Properties) items.elementAt(x);
			Vector v = (Vector) prefs.get("prop_item");
			Properties prop_item = new Properties();
			for (int x = 0; x < v.size(); x++)
				Properties p = (Properties) v.elementAt(x);
				prop_item.put(p.getProperty("key"), p.getProperty("val", ""));
			Enumeration keys = prop_item.keys();
			while (keys.hasMoreElements())
				String key = keys.nextElement().toString();
				String val = prop_item.getProperty(key, "").trim();
		catch (Exception e)
			error = e;
This is a placeholder for custom tasks developers make in the future.