Veröffentlicht Mon, 19 Nov 2018 18:03:38 GMT von Steve Shriver Application Specialist

Several workflow tasks are "chained" together so that the second one triggers after the first exits and the third triggers after the second etc. The tasks are accessed by the users from a link received in an email. Sometimes another page or document needs to be clipped to the current one, but since the option is not available when the task is accessed from a link, the user uses the client to add the page. However this triggers the task again and creates a duplicate task. The triggers for each task are configured for changed index values only.

Is this expected behavior? Does anyone have any ideas for a work-around? Or do I need tech support?

Many thanks,

Veröffentlicht Mon, 19 Nov 2018 18:07:07 GMT von Phil Robson DocuWare Corporation Senior Director Professional Services, Americas

Steve,
Please detail your Trigger conditions. Clipping a document to another should not trigger a workflow unless an index entry is also modified.

 

Phil Robson
Senior Director Support Americas

Veröffentlicht Mon, 19 Nov 2018 18:48:41 GMT von Phil Robson DocuWare Corporation Senior Director Professional Services, Americas

Screen cap 1.
Before index modification Status is empty OR not empty - meaning we don't care what status is.
After index modification: If Status is Assigned to Tech or Tech Exam Delayed.
Therefore, because you have said the Status can be anything to start with, but as long as Status is Assigned, or Delayed after the index change then the workflow will trigger.
What id does NOT mean is that the Status field has to change to trigger. Any field change will cause a Trigger because your Trigger condition is too loose. Clipping a document to a document that meets the criteria will Trigger because the DWMODDATETIME has changed.

Your other 2 Trigger conditions have a similar problem.

 

Phil Robson
Senior Director Support Americas

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