Meridian Ideas

Add your voice to the dialogue; share your best ideas!
Vote for the ideas you like; it helps to set priorities.

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.
  • Daniel Hunziker
  • Mar 19 2019
  • Attach files
  • Admin
    Chris Tsangarides commented
    25 Mar 17:20

    Legacy ID: MER-I-169

    Idea created at: 2018-Oct-19

    Referenced customer:

    COMMENTS: Nov 14, 2018 Please make this change, we have the same situation and wish Stefan Bronsgeest Vector Eyes

    Suzanne van den Berg Nov 16, 2018 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 Jan 23, 2019 Why there is no comments from accruent on this item!!

  • Ronald Kock commented
    24 Sep 14:03

    I agree with this idea. In case a document is locked on your own name/workstation this should not be blocking. 

    2019R2: The command Replace Document is hidden in case you try to find it under Edit. However when you try to replace content using drag and drop it is visible but not working. 

    How can we explain this to the customers?