Export connector behavior – Kofax Export Connector 8.2.0 for IBM FileNet Content Manager User Manual
Page 29
Export Connector Setup
Kofax Export Connector 8.2.0 for IBM FileNet Content Manager Administrator's Guide
29
You must also have the following security rights to use the document class:
▪ View all properties
▪ Modify all properties
▪ Create instance
▪ Read permission
Export Connector Behavior
The IBM FileNet Content Manager permissions may behave differently in this export
connector than in the IBM FileNet Content Manager Workplace Thin Client. For example, if
you give access permissions to the User-defined Document Class node and do not give access
to the Document Class node (also known as the system class node in IBM FileNet Content
Manager), the export fails with an error.
When permissions are denied to the Document Class node, the IBM FileNet Content Manager
system denies access to all the subclasses below the Document Class node in the hierarchy.
This problem occurs because the export connector uses a different API set than IBM FileNet
Content Manager. Notice that you do not see this behavior in the IBM FileNet Content
Manager Workplace Thin Client.
Note If information is changed in IBM FileNet Content Manager while export setup is
open, the export connector does not reflect the latest changes. Therefore, you must log out
of the export connector and log back in for the changes to take effect. When adding and/or
removing domain users, you may need to stop and restart the Content Engine Object Store
service on the Content Engine Server to see the latest changes.