Override Folder Path

Add the Override Folder Path task from the drop-down on your job. Not sure how? Check here.

A sample pattern has been provided for you by default. You can also leverage the 3Sixty expression language when modifying your path. More information on the 3Sixty Expression Language can be found here. Click the Done button when you have finished modifying your job task.

Configuration

To use this task go to the task tab in your job. Select the task from the drop down and click the plus circle to configure the task. Click done after making any changes to save.

Condition check

It will execute the task when the condition's result is 'true', 't', 'on', '1', or 'yes' (case-insensitive), or run on all conditions if left empty. This condition is evaluated for each document, determining whether the task should be executed based on the specified values.

Example: If I only want to run this task for PDF documents I would use the expression: equals('#{rd.mimetype}',"application/pdf")

Pattern

List the fields and or words in a pattern that you want to use to rename the folder path

Examples

Simple Use Case

Changing the destination folder name

If you would like to change the destination folder name to 3Sixty for example, you can use the pattern '/3Sixty'.

On example of a useful pattern is:

'/' + '#{rd.filename}' + '/3Sixty'

Using this configuration if we have the following two files in the folder C:\3Sixty Sample Docs\Test From Repo

Sample File 1

Sample File 2

After running the job you will get two separate folders with each file in their own folder in the output location.

C:\3Sixty Sample Docs\Test Out To\Sample File 1.txt\3Sixty

C:\3Sixty Sample Docs\Test Out To\Sample File 2.txt\3Sixty

Using the 3Sixty Expression Language you can see that rd. are internal 3Sixty Fields.

However, you may want to use metadata from the source system to generate your path.

Use field in place of rd to accomplish this or leave off the prefix entirely.

The best way to put your path together is to know what fields are available and what the field values look like. We suggest running the BFS output with no mappings and Include Un-Mapped Properties set to True. This will generate a xml file such as:

<entry key="document.name">Alfresco Ingestion.pptx</entry>

<entry key="type">document</entry>

<entry key="folderpath">test3Sixty_Partners</entry>

<entry key="document.Category">legal</entry>

</properties>

Advanced Use Case

Now let's say we want the actual folder path to be a combination of folderpath + Culture + Category + Customer ID. To do that we just reference each field like:

'/' + '#{rd.path}' + '/' + '#{document.Culture}'+'/' +

'#{document.Category}'+'/' + '#{document.CustomerId}'

API Keys

Key	Display Name	Type
use_condition	Check a condition before executing this task.	Boolean
task_condition	Condition	String
task_stop_proc	Stop Processing	Boolean
jt_folderpath_pattern	Pattern	String