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.

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

Marking a workflow complete does not save a copy in the workflow archive #211

Closed
scottvieira opened this issue May 9, 2017 · 5 comments
Closed
Labels
bug This is a bug (not an enhancement)
Milestone

Comments

@scottvieira
Copy link
Contributor

In testing the workflow archive I noticed that when marking a workflow complete, instead of marking individual steps in the workflow as complete, that the workflow did not show up listed in the archive.

@jsavell
Copy link
Contributor

jsavell commented Jul 9, 2018

We're currently experiencing this issue in master, and the #213 fix doesn't seem to be present there: https://github.com/coral-erm/coral/blob/master/resources/admin/classes/domain/ResourceAcquisition.php#L116

It looks like the fix may have gotten dropped somehow when the Workflow functionality was shifted from Resource to ResourceAcquisition: 801c751#diff-ff7cebafbff0c74330b18b40bb00d094R116

I can open a new PR restoring fix if someone can confirm that it's needed and that I'm not misreading this.

@veggiematts
Copy link
Contributor

As of today, I can see the fix in master.

@jsavell
Copy link
Contributor

jsavell commented Jul 11, 2018

Are you sure? I don't see it:
https://github.com/coral-erm/coral/blob/master/resources/admin/classes/domain/ResourceAcquisition.php#L116

I'm expecting to see lines 2004 to 2008 from this PR:
https://github.com/coral-erm/coral/pull/213/files#diff-8a0d6c3284dcd145d52d956effda2e8dL2003

I don't see isCurrentWorkflowComplete() checking for Resource completion anymore in master. Is the check for Resource completion no longer necessary or moved somewhere else?

@veggiematts
Copy link
Contributor

You're right, my bad. The commit containing the fix is in master, but the fix itself seems to have been lost when the code was moved from Resource to ResourceAcquisition. This is a bug.

@jsavell
Copy link
Contributor

jsavell commented Jul 11, 2018

Ok. I'll open a PR restoring the fix today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This is a bug (not an enhancement)
Projects
None yet
Development

No branches or pull requests

4 participants