Submission logs and workflow

We've been having a bit of an issue with viewing submission logs on forms that have workflow applied. Users don't have access to acquire the locks to export the logs if the asset is live, it would seem.


Has anyone else noticed this… is it a bug… is it fixed in a newer version (we're on 3.24.1 at the moment)? Depending on feedback will decide if I venture into the bug tracker (although I've already done a quick search which didn't turn anything up)!

This is because the workflow prevents Live Edit. Users have to go through workflow process in order to make changes to the asset.


The user has to switch the form to Safe Edit status and then he can acquire locks and make changes, and then he has to go through workflow and apply to make live.



This is expected behavior.

Expected, but worth changing I think. I thought we actually did change this in the past so you didn't have to acquire locks to be able to export form submissions. If not, we should change it.

Considering that I just had to export a whole bunch of form submissions, I can confirm that on 3.28.3 you still need to acquire the locks. :slight_smile:

[quote]
This is because the workflow prevents Live Edit. Users have to go through workflow process in order to make changes to the asset.



The user has to switch the form to Safe Edit status and then he can acquire locks and make changes, and then he has to go through workflow and apply to make live.



This is expected behavior.

[/quote]



But you're not making changes to the asset when exporting log files - you're reading from it. Unless you subscribe to the Heisenberg uncertainty principle!



Greg - do you want me to log it on the bug tracker?

[quote]
But you're not making changes to the asset when exporting log files - you're reading from it. Unless you subscribe to the Heisenberg uncertainty principle!



Greg - do you want me to log it on the bug tracker?

[/quote]



Yeah, go for it. Hard to miss when posted there.

We should change it so Export Submission section doesn't require a lock. It will only need read permission.


If you can submit a bug report, we shall fix it.