Override Filename

The task uses the 3Sixty Expression Language to override the file name of each document. The functionally of this task is identical to the Override Folder Path Task except that it focuses on file names instead of folder names.

---

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 you want to use to rename the file

Deep Change

If the file has versions, 3Sixty will update the current version name as well.

---

Examples

In this example we will take the files in our source repository and update the file names to include the last modified date during the integration. Deep change is not checked so other versions of the file will not be updated.

Pattern: '#{rd.filename}' + '-' + '#{rd.modifieddate}'

Deep Change: (Unchecked)

This configuration will update the Sample Doc that was last modified on March 2, 2024 and change it to Sample File – March,2 2024.

---

API Keys

Processor: overrideFileNameTask

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_filename_pattern	Pattern	String
jt_deep_change	Deep Change	Boolean

---