Replace content shouldn't ask to unlock document when document is under edition locally.

This is related SR-6672.
Created by Juliano Correa on Behalf of Daniel Hunziker


Change Description

Customer reports that, when you start a workflow (Start Change), the document is locked locally, by this way, if you need to replace the content of a document, you need to unlock the document first.
They request that this shouldn't be necessary, to avoid additional clicks.

Steps to reproduce
1 - Start a Workflow

2 - Drag and drop a new content to this document

3 - You will receive a message related to document locked, this is not OK.

4 - To be able to replace the content, you need to unlock the file first

Expected result
Content should be replaced when you start the WF without need to unlock before replacing

Actual Result
You need to unlock the document which is locked on your own workstation.

  • Oct 19 2018
  • Attach files
  • Guest commented
    November 14, 2018 15:40

    Please make this change, we have the same situation and wish


    Stefan Bronsgeest

    Vector Eyes 

  • Suzanne van den Berg commented
    November 16, 2018 06:28

    We are also experiencing this issue. Our document controllers use replace content so often, the issue is preventing us from using the web client.
    Please fix it.

    Suzanne van den Berg
    Van Oord