The Set hierarchy path flow element





The Set hierarchy path element allows you to modify the hierarchy location path (stored in the internal job ticket). This is useful to organize processed jobs in a folder hierarchy, for example based on the result or the date of processing.

How does it work?

This element provides particular actions to change the hierarchy location path. You can add, remove, or reverse segments (i.e. parts) of the location path. Note however that you cannot combine different actions in one Set hierarchy path flow element. Hence, you may have to combine different elements of this type in order to build the new hierarchy path.

Example

  • Original hierarchy location path: Server\CustomerX\Input
  • New path (to be used to store the processed files): Server\Customer X\Output\dd-mm-yy

In this example, the highest levels (Server (0) & CustomerX (1) ) must remain unchanged; there are two new sublevels; one with a fixed name (=Output (2) ), the other with a variable name (indicating today’s date) (3).
To create the new location path as in the example, two instances of the Set hierarchy path element are needed:
  • Set hierarchy path1 will be used to remove the Input segment (level 2) from the location path. This results in Server\Customer X.

    Properties:
    • Action: Remove
    • Start index: 2 (subfolder level)
    • End index: 2 (subfolder level)
  • Set hierarchy path2 will be used to add two new segments: Output (level2) and today’s date. This results in Server\Customer X\Output\dd-mm-yy.

    Properties:
    • Action: Add at the bottom (= the new segment should be attached to the end of the current hierarchy path).
    • Path segment 1: Output (= entered as an inline value)
    • Path segment 2: The [Switch.FileCreationDate] variable (entered using the Define single-line text with variables editor)