How to create a Global Rule that stores a document’s folder path in a custom metadata field

Efficiency purists would argue that redundancy is not necessary. In real life, we are willing to pay a price for performance –i.e. to have information at our fingertips. We have run into customers opting to store a document folder path as a document metadata field. They have their reasons, half of the ECM community will agree with them, and the other half would raise an eye brow. In the end, they are getting creative to achieve their document management goals.

The below steps outlines how to create a Global Rule that would store a document’s folder path in a custom metadata field:

Create a Global Rule via Configuration Manager > Rules Tab > Add

Then check “Is global rule with priority”.

Then check “Use rule activation condition”.

The go to “Edit” and check the actions for this Script Properties:

Then click OK, and the following rule activation condition will appear:

Then Goto to the Fields Tab and add a Rule Field:

Select the target Custom Metadata Field and click Ok, then check the “Is derived field”, then “Edit”, then go to the Custom Tab in the Script Properties window and enter the below custom script:

<$if #active.dCollectionPath$>
<$dprDerivedValue=#active.dCollectionPath$>
<$else$>
<$dprDerivedValue=#active.xCollectionIDPath$>
<$endif$>

For more information on the dCollectionPath property, check Section 8.2 Folder Services from the Oracle® Fusion Middleware Services Reference Guide for Oracle Universal Content Management 11g Release 1 (11.1.1)

http://docs.oracle.com/cd/E21043_01/doc.1111/e11011/c08_folders002.htm

The above rule will keep the Custom Metadata Field updated with the Folder Path information when a document is checked in via the Content Server (CS) Web Interface or the Desktop Integration Suite (DIS).