Schema-based auto-filing script

The Schema-Based auto-filing script has many configuration options compared to the other included auto-filing scripts. Documents can be filed based on:

A document schema name. The schema name is used as the level in the library hierarchy.
A metadata field value. The value in the metadata field is used as a level in the library hierarchy.
A fixed value. A fixed value is defined in the configuration and is used as a level in the library hierarchy.
A system value which includes 'created date', 'document schema name', or 'document name'

All filing methods can be used with any level in the library structure. For example, a cabinet can be a fixed value, the drawer can be the schema name, and the folder can be a metadata field value. Alternatively, a cabinet can be a schema name, the drawer can be a metadata field value and the folder is a fixed value. The script can be set to create the library structure as needed if the logged in user has a sufficiently privileged role.

Multiple regular expressions can also be used. If one fails to return a non-empty string, the next one is tried and so on until the first match is found.

The name of the script is called Schema-Based.dll and is located in C:\Program Files\FileHold Systems\Application Server\LibraryManager\AutoFiling. There is a separate configuration file for this script called Schema-BasedAuto-FilingScript.xml located in the same directory (do not attempt to modify the AutofilingMembersip.xml file for this script).

FileHold Professional Services can assist in the creation of auto-filing scripts if needed. Contact [email protected] for assistance.

Configuration of the Schema-BasedAuto-FilingScript.xml file

For each level in the hierarchy, there is an option in the configuration file to allow the level entity to be created automatically or not. If the level entity can be created, there must be a matching definition. The default schema is used in the definition when creating folder or cabinet entities. For example:

<Name>Schema-Based</Name>

Level entities based on schema name

When configured to use a schema name, the level entity will be the document schema name. For example:

Level entities based on fixed values

When configured to use a fixed value, the level entity will be defined the fixed value. For example:

<Value>Invoices</Value>

</Mapping>

Level entities based on metadata fields

For level entities based on metadata fields, text, drop-down, drill-down, numeric and date fields can be used.

Text and drop downs can be modified by a regular expression. For example:

<Field>textFieldName</Field>

</Properties>

</Mapping>

<Field>dropDownName</Field>

</Properties>

</Mapping>

Drill-down fields need to have the level specified in the configuration. In other words, if only the items in the 3^rd level of the drill-down menu can be used as the level entity, you will need to enter “3” in the configuration. For example:

<Field>drilldownFieldName</Field>

</Properties>

</Mapping>

Numeric and date fields can be modified by .NET formatting. For more information on .Net compatibility see: http://msdn.microsoft.com/en-us/library/vstudio/system.globalization.datetimeformatinfo(v=vs.100).aspx , http://msdn.microsoft.com/library/26etazsy(v=vs.110).aspx. For example:

<Field>dateFieldName</Field>

</Properties>

</Mapping>

<Field>numberFieldName</Field>

</Properties>

</Mapping>

Level entities based on system values

For level entities based on created date, document schema name, or document name.

Created date example:

<Field>CreatedOn</Field>

</Properties>

</Mapping>

Document name example:

<Field>DocumentName</Field>

</Properties>

</Mapping>

Document schema example:

<Field>DocumentSchema</Field>

</Properties>

</Mapping>

Defining cabinet and folder owners and membership

When creating cabinets and folders, their owners and members need to be defined in the Schema-BasedAuto-FilingScript.xml file. To generate the GUIDs that define the users and groups in the system, run the Export Guids function in FHIT. See Configuring the AutofilingMembership.xml File for detailed instructions.

Once the GUID file is created, use it to assign owners and members to folders and cabinets. For example:

</Members>

</Properties>

Weighting and folder colour

For cabinets, drawers, folder groups, and folders the weight for each level entity can be specified in the configuration file. The range of values is 10 to -10. The lower the weight (such as -10), the higher the folder name appears in the Library. The higher the weight (such as 10), the lower the folder name appears in the list. Leave the weight at 0 if you want the folder groups sorted alphabetically. For example:

</Properties>

For folders, the colour of the folder can be specified as yellow, blue, green or red. The default colour is yellow.

Regular expressions

Regular expressions is a special text string for describing a pattern. A pattern consists of one or more character literals, operators, or constructs. For a brief introduction, see .NET Framework Regular Expressions. Multiple regular expressions can be used in the auto-filing configuration. If one fails to return a non-empty string, the next one is tried and so on until the first match is found.

For example:

<Field>DocumentSchema</Field>

</Properties>

</Mapping>

</Properties>

</Drawer>

<Field>DocumentName</Field>

</Properties>

</Mapping>

<Owner>dddddddd-dddd-dddd-dddd-dddddddddddd</Owner>

<Color>Green</Color>

</Properties>

</Folder>

Example configuration

The following table outlines an example configuration:

For FileHold 15, if the Folder Group level is not going to be used, the level must be removed from the XML file altogether. In FileHold 14, leaving the parameter empty was valid.

Library Level	Scenario 1	Scenario 2
Cabinet	Document schema name	Fixed "Department"
Drawer	Fixed “Active Members”	Period metadata
Folder Group	Unused	Tax Code metadata
Folder	Badge # metadata	Area metadata

Sample code for the Schema-BasedAuto-FilingScript.xml file:

<?xml version="1.0" encoding="utf-8" ?>

<Name>Schema-Based</Name>

<Owner>dddddddd-dddd-dddd-dddd-dddddddddddd</Owner>

<Member>dddddddd-dddd-dddd-dddd-dddddddddddd</Member>

</Members>

</Properties>

</Cabinet>

<Value>Active Members</Value>

</Mapping>

</Properties>

</Drawer>

<Field>Badge #</Field>

</Properties>

</Mapping>

<Owner>dddddddd-dddd-dddd-dddd-dddddddddddd</Owner>

<Member>dddddddd-dddd-dddd-dddd-dddddddddddd</Member>

</Members>

</Properties>

</Folder>

</DocumentSchema>

<Value>Department</Value>

</Mapping>

<Owner>dddddddd-dddd-dddd-dddd-dddddddddddd</Owner>

<Member>dddddddd-dddd-dddd-dddd-dddddddddddd</Member>

</Members>

</Properties>

</Cabinet>

<Field>Period</Field>

</Properties>

</Mapping>

</Properties>

</Drawer>

</Properties>

</Mapping>

</Properties>

</FolderGroup>

</Properties>

</Mapping>

<Owner>dddddddd-dddd-dddd-dddd-dddddddddddd</Owner>

<Member>dddddddd-dddd-dddd-dddd-dddddddddddd</Member>

</Members>

</Properties>

</Folder>

</DocumentSchema>

</DocumentSchemas>

</AutoFilingScript>

</AutoFilingScripts>

Once the Schema-BasedAuto-FilingScript.xml is configured, then you can set up the auto-filing configuration for the schema in the library administration area. See Automatically Filing Documents into the System for more information.