Question

What causes the Entry Changed starting event to trigger?

Workflow

Updated June 30, 2020

asked on June 30, 2020 • Show version history

I have a workflow with one entry in the monitored folder. I have renamed the document and I have also tried changing a value in the metadata (which changed the Last Updated date), but neither action triggered the Entry Changed starting event. I have verified that the file is in the correct path, it is a Document, and the Created By user is FORMS. I have also tried removing the User condition and changing metadata but it still doesn't trigger the event.

Please advise.

0 0

Replies

replied on June 30, 2020

To expand on Miruna's note about the user, your rule says that the change has to be made by a user named Forms. Assuming you're logged in as yourself or any other account not named Forms, that would be why your actions don't trigger the WF.

1 0

replied on June 30, 2020

Update: Editing the metadata didn't trigger it after removing the User condition, but renaming the document did finally trigger the event.

0 0

replied on June 30, 2020

There is a 30-second delay between the rule publishing and it becoming active on the server. You're likely running into that.

The user who created the document is irrelevant. The user condition in your entry changed rule will apply to the user making changes to the document.

The Subscriber Trace will show you what events came in and how they were evaluated.

0 0

replied on June 30, 2020

Thanks Pieter and Miruna. I was able to consistently get Change and Move events to trigger by removing the User condition.

0 0

You are not allowed to follow up in this post.

Question

Question

What causes the Entry Changed starting event to trigger?

Replies

Sign in to reply to this post.