Obsolete Detection

The obsolete detection task can be used to identify obsolete documents when reading them from the source repository. This can be used either in the federation view for identifying documents that are obsolete based on the definition set in the task for the job by adding metadata or skipping/processing the documents which are obsolete. You can define what obsolete means for your organisation - you can define it based on the date created or updated and the content before what time frame is considered as obsolete.

Note:  The Obsolete Detection tasks uses the system time of the 3Sixty server when calculating date/time scenarios.

Mapping

Start by mapping the tasks metadata fields

  • isObsolete: Yes/No

  • obsoleteField: Date Created or Date Updated

  • obsoleteBefore: Date after which the content is considered obsolete

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")

Filter on which date field

Chose which field you want 3Sixty to look at to determine if the file is obsolete. Map this field as instructed above.

  • Date updated: 3Sixty will look at the last modified date

  • Date created: 3Sixty will look at the date the file was created

Before

Chose how far back the search should go. You can select 5, 10, 15, or 20 years.

  • Custom: You can also choose a custom date where you will either enter the date or click the calendar icon to select the date and time.

Action

When 3Sixty comes across a document the matches the set time period you can chose what it should do.

  • Continue: 3Sixty will continue to integrate the files regardless of the filter conditions.

  • Skip: 3Sixty will skip over the file and continue with the job run. You can see how many files are skipped in the job run results. Click on the number to see the list of files skipped.

  • Fail : 3Sixty will stop the job

Examples

In the following example documents that have been updated before March 1, 2018 will be marked as obsolete in the audit while the job processes.

API Keys

Processor: obsoleteCheckTask

Key

Display Name

Type
use_condition Check a condition before executing this task. Boolean

task_condition

Condition

String

task_stop_proc

Stop Processing

Boolean

beforeWhen

Filter on which date field?

String

before

Before

String

customDate

Custom Date

String

action

Action

String