Filing path (ArcPathDef)
The action for generating the filing path applies the following configuration structure:
Filing path actionAction, filing pathArcPathDef- ArcPathDef: Action = { path1, path2, path3, …, pathn }
- ArcPathDef.Path: Pathi = { Sordi,1, Sordi,2, Sordi,3, …, Sordi,m }
- ArcPathDef.Path.Part: Sordi,j = { parti,j,1, parti,j,2, parti,j,3, …, parti,j,k }
In other words, a filing path action defines a list of paths, each of which defines a list of path components (or SORDs). In addition, it is possible to string together multiple list entries to build the path components, which is exactly what occurs when a part (k+1) is not separated from the predecessor part (k) (ArcPathDef.Path.Part.Separator=false). In this case, the SORD is generated by both parts (k and k+1), although only the keywording template of the first part can be used, since the SORD that is to be generated can only have one keywording. However, the standard assumption is that each path component also defines its own SORD.
Path components can be defined with a constant value (SourceType="constant"). Alternatively, element fields can be used (SourceType: "fieldname", "cachedname"). Finally, the filing path action can use predefined action variables ("SimpleTypesDef.PathPartVarType"), which differ depending on the type of data source (see following table):
| Variable | Meaning | Exchange |
| DeliveryTime | Time of receipt | X |
| JobStart | Start time of the current processing job | X |
| BoxName | displayName of the mailbox owner | X |
| BoxAccount | samAccountName of the mailbox owner | X |
| BoxUPN | UserPrincipalName of the mailbox owner | X |
| BoxAlias | SMTP of the mailbox | X |
| SndName | Sender name | X |
| SndAddr | Sender address | X |
| SndDomain | Sender domain | X |
| RcptName | Recipient name | X |
| RcptAddr | Recipient address | X |
| RcptDomain | Recipient domain | X |
| BoxAddr | Mailbox address | X |
| AccessUrl | Access URL | |
| RootPath | Path in the data source | X |
| ParentName | Name of the parent element/container | X |
You can also modify the values or character strings determined for the path components by using consistent upper and lower case and/or transferring subsets of the values determined to the path. Please note that the database can limit the lengths of the SORD names. ELOxc always handles these special cases for an instance in the same way by using the switch "TruncateStrings" ("InstanceDef.IX.TruncateStrings") for ELOix interface calls. If the switch is set in the instance configuration, SORD names (and index field values) are shortened to the appropriate length. However, if the switch is not set, this leads to processing errors, meaning that the affected elements cannot be archived.
The rule for using the filing path action is to determine the filing path of a data source element that is prepared in the export action. This action is therefore necessary so that the data source elements can be archived. The first path defined is therefore also interpreted as the main path. You can also define additional paths (from the second path) that you could use if you want to create logical references in these paths as well as in the main one. You need to distinguish between whether the existence of these referencing paths is forced with Force="true", meaning they may be created during the archiving process or if a logical reference to the archived data source element is only to be created if the referencing path already exists. The main path is always created.
Click the Advanced button in the Options area to open the advanced configuration settings.
Root: Select what ELOxc will interpret to be the repository root here. If you do not select an option here, "Archive" is used by default. This means that the folder path you created uses the repository root as its starting point. If you select the "User" option, the path is created using the corresponding user folder as its starting point.
KeywordingTemplate: Enter the name of the keywording template here.