I've worked with my VAR on both the Support and Consulting sides trying to resolve this issue, to no avail.
All of our documents with a certain Workflow template cannot have pages deleted. The "Entry Changed" starting rule on the workflow in question triggers BEFORE the page is deleted for some inconceivable reason. This causes users to get this message every time they try to delete a page:
Clicking "Yes" has no impact on the deletion action, so the page remains un-deleted. Permissions are set properly on the folder, and other documents in the same folder structure and volume, but that use a different template, do not have this issue, nor do any other documents/templates that I am aware of (I've tested several). I've altered the starting rule such that it's not SUPPOSED to be running on any change event that has to do with Page activity (we only really need it to run when metadata or tags are changed). Here are my starting rules as it stands right now:
I've tried changing the rules to run only when Entry Changes Include field actions (see picture below), but that resulted in the rule not triggering at all when metadata changes, so that's probably its own separate bug/issue.
If I turn the starting rule off, page deletion can be done without incident, but we do need that change rule for metadata changes.
This issue came to my attention some weeks after our LF 10.4 upgrade, so that may or may not be related. I have also tried the following (none of them worked):
- Renaming the template
- Deleting the starting rule and creating a new one
- Creating an entirely new workflow with its own set of starting rules
- Adding the functionality I need for this workflow to another workflow that doesn't implode when page deletion occurs, with a decision tree based on the template name
Our current workaround is to select the pages that need to be deleted, creating a new entry out of those pages, then deleting the entry. The fact remains, though, that the Entry Changed activity should not be triggering before the change actually occurs.
If nothing else, does anybody know if there's a way to find out exactly what entry change event it was that triggered the rule? That might at least give us a direction. I've spent so many hours on this...
Thanks in advance for any feedback or input!