Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deleting page-content does not remove WorkflowInstances #179

Open
phptek opened this issue Jul 9, 2014 · 2 comments
Open

Deleting page-content does not remove WorkflowInstances #179

phptek opened this issue Jul 9, 2014 · 2 comments
Labels
affects/v4 complexity/medium impact/medium type/enhancement

Comments

@phptek
Copy link
Contributor

phptek commented Jul 9, 2014

Even if a CMS user completely deletes content via batch-delete, or individually, if any of these had previousely been part of a workflow, any related WorkflowInstance objects and records are still left hanging around, cluttering-up the "Submitted Items" GridField.

Solution 1

Prevent "unattached" WorkflowInstance's from appearing in the GridField

Solution 2

Ensure attached WorkflowInstances are also deleted when related pages are deleted.
@nyeholt
Copy link
Contributor

nyeholt commented Mar 6, 2015

If a user tries to 'action' the instance, does it error out? Optional

Solution 3

A reaper goes through and 'completes' the workflows in a way that highlights that the content was deleted.

@phptek
Copy link
Contributor Author

phptek commented Mar 8, 2015

@nyeholt Genius.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects/v4 complexity/medium impact/medium type/enhancement
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nyeholt @phptek @maxime-rainville @emteknetnz @robbieaverill