FileStoreProvider Rule Does Not Work Correctly with WebDAV Revisions (Doc ID 1083736.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Universal Content Management - Version: 10.1.3.3.1 to 10.1.3.5.0 - Release: 10gR3 to 10gR3
Information in this document applies to any platform.

Symptoms

You have a File Store Provider (FSP) rule set up as a File System Only, Webless rule. You have two partitions defined, part1 and part2. The Vault Path is something like:

$PartitionRoot$/$dDocType$/$dID$$ExtensionSeparator$$dExtension$

You check a content item in through the browser (into a Contribution Folder) using this FSP rule, and the content gets stored where you expect (let's say it is in part1).

You then open the file through WebDAV (Microsoft Web Folders). You make a change and close the file, saving it so a new revision gets checked in. However, this new revision never gets released, but stays in the GenWWW state even if you are not using Inbound Refinery or PDF Converter. The native file for this revision gets created in the other partition correctly (part2); however, the value of xPartitionID for this revision is still set to part1 instead of part2.

Note that if you do the same thing through the browser (check out an item and check in a new revision), everything works correctly and xPartitionID for the new revision is set correctly to the next partition.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms