The "immutability" of documents put to IBM FileNet.

When documents are put into FileNet their permissions, as set at that moment, may never change. There is an independent metadata class with differing permissions for each file and these classes, these "POCO" objects if you will, may have permissions updated, but not the IBM FileNet documents themselves. To redo the permissions on a FileNet document, destroy and reupload the document anew. Some files may be nested under other files and a queried file will drag along all of its children unless a child is permissions-forbidden and in those scenarios it appears as if the parent just does not have the child without any warning whatsoever. If you use Word docs instead of PDF files you can have macros updating things like dates on the page and that means that Word docs are not so wonderful for these sorts of undertakings. (remediate that!) A sample PDF to use in testing is:

%PDF-1.5 %âãÏÓ
228 0 obj <</Linearized 1/L 273205/O 230/E 264876/N 1/T 272865/H [ 582
      215]>> endobj

 
 

This simple PDF cannot be reopened. It is just a dummy "use me" document for testing.