Probably just something I am missing but here goes. We have just recently rolled out EES to a group of sites and users have discovered they can no longer download/export their CSV files (submision logs from custom forms) as they have previously been able to in SEI. Is there a way to do this in EES? We can give them the direct _admin link to download if they have admin permissions but what if they dont? Thanks for your help. Paula
Hey Paula
Do you have any screenshots or old reference material (like training steps/manual) for how the user accessed and downloaded the CSV form submissions from the old SEI? Before maing any suggestions I'd like to get an idea of the user experience and how the download was accessed and presented to the user.
Cheers
Scotty
Sure do.
This is the screen the user currently uses to download the CSV.
Thanks
Paula
[quote]
Sure do.
This is the screen the user currently uses to download the CSV.
Thanks
Paula
[/quote]
Looks like that image isn't public… Could you upload it again?
[quote]
Looks like that image isn't public… Could you upload it again?
[/quote]
Here is the image as an attachment.
The direct URL for the image is - http://www.csu.edu.au/special/validate/paula/templates/csv-download.jpg
(Public) So not sure why it was not displaying in the post insert image.
csv-download.jpg (310 KB)
[quote]
Here is the image as an attachment.
The direct URL for the image is - http://www.csu.edu.au/special/validate/paula/templates/csv-download.jpg
(Public) So not sure why it was not displaying in the post insert image.
[/quote]
The attachment worked, but the link to http://www.csu.edu.au/special/validate/paula/templates/csv-download.jpg requires HTTP auth.
If you don't want to give them them _admin access you could also make them only be a simple edit user, that would just allow them to access the _edit screens.
[quote]
The attachment worked, but the link to http://www.csu.edu.au/special/validate/paula/templates/csv-download.jpg requires HTTP auth.
If you don't want to give them them _admin access you could also make them only be a simple edit user, that would just allow them to access the _edit screens.
[/quote]
Thanks for the reply Nic. The problem is there is no screen for this in the EES that we have just installed. So advise on setting up somehting similar in EES from the _edit URL.
Hey Paula
Looks like some custom work to accomodate this feature from EES. That appears to be a standard simple edit layout keyword replacement in there which might translate (without too much thought) to one of a couple options:
1 - Maintain the use of the existing simple edit layout work, but open that page in a new window and apply a user defined design to show it without the rest of the design around it, if you have an existing 'blank' (asset contents only) design that might work well. Open the page from a button on that form assets details screen, which would require a custom ees plugin that would execute: after screen load AND screen equals 'details' AND current asset id matches the form asset's id THEN add button to bottom of details screen with hardcoded href to the form asset URL appended with /_edit?SQ_DESIGN_NAME=blah. You would have to make sure to leave the frames on the open page to avoid losing the locks.
2 - Look at applying a new section to the details screen of that asset in EES, using custom ees plugin that executes similar to above (screenload event) but would require the use of the JS API (getkeywordreplacements function) and potentially some other trickery when changing it's selection options. This solution would essentially display the same 'export' table you see in the screeny into it's own section at the bottom of the details screen.
Both of these require a bit of work, but option 2 more so, as it would involve direct interaction with matrix via the JS API. Don't try to use core EES functions (this will just get you inhot water come upgrade time) instead make direct calls to the functions available in the same JS API that is referenced by EES. More info on EES plugins can be found here http://manuals.matrix.squizsuite.net/ees/chapters/javascript-plugins and more info on how to use the JS API (enhanced mode examples) can be found here: http://manuals.matrix.squizsuite.net/web-services/chapters/basic-javascript-api-implementation
I'm going to add this as a new feature request in our Roadmap system for Edit+, I think exporting form submissions easily falls into the realm of what standard (non technical) editors might require, specially marketing/comms teams.
Cheers
Scotty
Thanks Scotty for the detailed information, as always very helpful.
Yes, we have many non technical editors who currently use this facility and this creates a bit of a road block to rolling this out to the rest of our site until we have an alternative in place.
Will examine our options internally then go to Rachel if we need help.
Thanks again!