LO70180: ISSUE WITH USING CONNECTORS TO MOVE DOCUMENTS TO READ-ONLY DESTINATION FOLDERS IN ECM.

APAR status

• Closed as unreproducible.

Error description

• ENVIRONMENT:
  FileNet P8 Version: 4.5.1.7
  IBM FileNet Services for Lotus Quickr v1.1.0.3
  Quickr Connectors 8.5 HF12b 1620
  
  STEPS TO REPRODUCE:
  1. Within the IBM FileNet Services for Lotus Quickr server
  (FNQS), create a new Lotus Quickr application and library in an
  object store.
  2. As User A, start Lotus Quickr Explorer Connectors, connect
  to the FNQS server and add the new library.
  3. Using Connectors, create a new folder in that library called
  e.g. "Read_Only".
  4. Using Filenet Enterprise Manager, locate this new folder and
  open its Properties dialog.
  5. In Security tab, set a differrnt user's permissions (e.g.
  User B) to Read-only.
  6. Back in Connectors, add a new file (any type) to the root of
  the library.
  7. Log in to Connectors on a different client machine as User B.
  8. Click on the file created in step #6 and drag it into the
  "Read_Only" folder.
  9. User B receives the error: "Sorry, you might not have access
  to the content you are trying to reach.", which is correct.
  10. OK the message and refresh the Explorer Connectors.
  
  OBSERVED RESULTS:
  The file now disappears from Connectors. (It is not visible
  either in the library root or the "Read_Only" folder.
  In fact, the file now appears in the "Unfiled Documents" view
  under the obeject store in the Filenet Enterprise Manager.
  
  EXPECTED RESULT:
  After an unsuccessful move attempt the doucment should remain
  in the source folder.
  
  NOTES:
  This issue occurs in both the Lotus Notes and the Windows
  Explorer Connectors.
  Error does NOT occur when moving an entire folder to a
  read-only destination. In this case,
  the user is notified about the missing access right, but the
  folder including its documents remain
  at the source folder -> This behavior is correct.
  

Local fix

• Allow read/write access for the users to the FNQS folders.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# DAMC8VLMRD.
  The change team could not reproduce the problem or determined
   that the problem has already been corrected.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels