Skip to main content
Nintex Community Menu Bar

Please provide a solution for this issue. This issue is causing us major problems and every OOO solution we come up with is 10x the work only because the workflow can’t handling waiting for file to be unlocked by user to move forward or allow us to add an error handling action for this particular action (update items action for files in a library). 

We need to store status, reviewer feedback, approval information, commentary etc on files that get opened and closed on a regular basis. We can’t update metadata or columns in library when files are open.

We resorted to tracking document information in a list but this causes more challenges the more we begin using it:
 

  1. If someone moves a file the link breaks for the link we push to the list for association.
  2. Users have to learn how to manage files from a list vs just having the information accessible in the library for each file
  3. If business requirements require both list and library to be linked, we have to lock the library down from editing up front and provision each file after we have added the list item ID in a column in the library then unlock the file. 

 

The list solution for 1 list item per file is just not sustainable for document management and review and approvals of documents. WE NEED A SOLUTION FOR THIS LOCKED BY SHARE USE OR OUR AUTOMATION SOLUTIONS ARE SUFFERING FOR OUR CUSTOMERS!

Hi @brandiwoodson ,

 

To find out if a file is checkout you could query the item and check the value of the “Checked out to” column.
If it is not null then pause for a period of time and loop again and check until it is null.


Ok. This will work.

What about for when its locked for shared usw and check out required is not turned on. We don't always use that feature. 

 

In this case when a file is opened....there will never be a checked out to ID. It is always null.....


Hi @brandiwoodson 

 

Unfortunately I cant see where SharePoint handles sharing apart from versioning.  Versioning is not helpful in this case.  

Going back to your request for error handling, you could do the update using the Lists.asmx web service. If the update is unsuccessful this would be returned in the response.  You could then look at the response and either continue the workflow or pause and loop again until you get a successful response.


Thanks for your feedback. 


Reply