Veröffentlicht Tue, 01 May 2018 18:34:38 GMT von Jon Weston File IT Solutions Sr Application Developer and RIM specialist

Twice in the last month I've had a workflow error out because right when it was trying to update an index entry it found that a user had locked the document.  We've talked to the users and they don't report doing anything that I would think would cause a problem.  For example, in one case the user said that they'd simply viewed the document from their Folders list and tried to delete it, which they can't.

The FC is in the default ad-hoc edit mode so I'm assuming that DW should only be locking the document if they try to update it.  Does this also mean that it will lock it if a user tries to edit the index entries?

This isn't a huge problem ("twice in the last month"), but we're about to push another bunch of departments live with this workflow so the amount of documents flowing through is about to increase a lot so I'd like to tidy this up somehow.

Veröffentlicht Tue, 17 Jul 2018 16:40:41 GMT von Nathan French ComDoc Systems Analyst

For various customers we have seen this happen, especially when multiple users are assigned tasks on the same document.  If there can possibly be a way for workflow to WAIT for a lock to be released and then carry on, this would be highly preferable.  The current state is that the workflow just exits with an error.  Then the workflow has to be manually restarted via editing index entries.  This leads to confusion especially when stamps have already been applied from decisions that have been taken on the document.

Sie müssen angemeldet sein um Beiträge in den Foren zu erstellen.