Tour: Configuring the error task route

In the second part of the tour, you will learn how to set up an error task route. This task route moves the metadata file to a location that is not monitored by the collector so that problematic documents can be reprocessed. In addition, it provides recovery tasks for the content files that were routed to the error task route.

To configure the error task route:

1. Click the Switch between main and error task route icon to switch to the error task route.
   The text in the task route toolbar tells you whether you are currently looking at the main task route or at the error task route.
2. Include an audit log task as the first task to record everything that was routed to the error task route.
   Configure the audit log task.
   1. To create a separate log file for this task, specify a unique file identifier for the audit log.
   2. Select to record at least the following metadata properties:
      • <File, Full Path>
      • <Task Status, Task Success>
      • <Task Status, Task Result>
      • <FSC Metadata, Content File Line Number>
      • <FSC Metadata, Content File Order Number>

      Recording these properties can make it easier to determine what went wrong and to recover from this error.
3. Include a decision point with three rules.
4. Configure rule number one, which is the rule for processing the metadata file.
   Tip: Use a name that lets you easily identify the purpose of the rule.

   The expression to be evaluated is <FSC Metadata, Is Metadata>. Use the Expression Editor to configure the expression:
   1. Select Advanced and start the Expression Editor.
   2. Select Replace as edit action.
   3. In the Prototype Expressions section, double-click MetadataReference.
   4. Select the FSC Metadata source and the Is Metadata property.
   5. Click OK to save the expression.
5. Configure processing in this branch:
   1. Include an FSC Post Processing task in this branch.
   2. Configure the task to move the metadata file to an error location.
   3. Connect this branch to the end of the error task route.
6. Drag the rule to the left to make room for the other rules.
7. Add and configure rule number two, which is the rule for processing content files that were successfully filed in a folder.
   The expression to be evaluated is:

   And(TestMetadataReference(<P8 File Document In Folder>, <File Paths>),
    <Task Status, Task Success>)

   Do not include any tasks in this branch.
8. Add and configure rule number three, which is the rule for processing content files that were not yet filed in a folder.
   The expression to be evaluated is:

   And(TestMetadataReference(<P8 Create Document>, <Connection Name>),
    <Task Status, Task Success>)

   1. Include a P8 File Document in Folder task in this branch.
   2. Configure the task exactly as in the main task route.
      Tip: You can also copy and paste the task between the main and the error task route.
9. Join the second and the third branch and include a postprocessing task to replace the files with shortcuts.
   Configure it exactly as in the main task route.

   Tip: You can also copy and paste the task between the main and the error task route.
10. Connect the postprocessing task that you added in the previous step to the end of the error task route.
11. Move the task so that the whole task route is visible in the Task Route Designer.
12. Include an audit log task in this branch to document the results.