I need a View created of encrypted Webform submissions for use by submission reviewers. The View should expose all submission data in a table with each column sortable.

The reviewers should be able to tag (via Taxonomy) and comment on each submission. My approach was to add these two additional fields to the Webform, but unset these when exposed to the user, and only show to appropriate roles or only in this View, etc. (exact implementation not too important as long as it's unset on the user-facing Webform).

Other details
– I'd like to be able to tag submissions from the table (via a select list), but if needed this can be done on the submission detail page

– There are also images and videos in one field (file upload); these are in the private file system. The actual video or image doesn't need to be shown on the table or submission detail page, just a link (but if it was integrated into either/both that would be great!

- Modules currently being used:
https://drupal.org/project/webform
https://drupal.org/project/webform_encrypt
https://drupal.org/project/encrypt

Some of the issues I've had:

- Getting Views to work with Webform submission data (needs to be 7.x-4.0-beta1 or you only get sid and links in submissions); fine to use 7.x-4.0-beta1 in solution

– Decrypting the data in the View (should be possible; the default Webform table does this just fine when browsing submissions); tried using a View template to decrypt() the data via the Encrypt module (which also encrypts the data), but was getting, "Notice: unserialize(): Error at offset 0 of 9 bytes in _encrypt_decrypt()"

Styling isn't needed, but it should take advantage of existing themes; for example I'm using Rubik, and the table in the View created should pull in styling from Rubik.

Compensation: $800 - $1000; based on responses received, timeliness (need ASAP if possible)

Please let me know if anything is unclear.

Thanks!

Comments

Hello,

I wonder how do you like the alternative of using Entityform?
The benefit is that your "webform" then would be an entity type and all of the submissions are entities of that type.
Let me consider this option thoroughly applying to each of the feature you need.

I need a View created of encrypted Webform submissions for use by submission reviewers. The View should expose all submission data in a table with each column sortable.

It makes much easier Views integration (in fact, it works out-of-the-box) while any customizations (such as decryption) could be done with additional modules (for example, Field Encrypt) with no (or just a little) additional coding at all.

The reviewers should be able to tag (via Taxonomy) and comment on each submission. My approach was to add these two additional fields to the Webform, but unset these when exposed to the user, and only show to appropriate roles or only in this View, etc. (exact implementation not too important as long as it's unset on the user-facing Webform).

That could be done using Views Bulk Operations (VBO).

There are also images and videos in one field (file upload); these are in the private file system. The actual video or image doesn't need to be shown on the table or submission detail page, just a link (but if it was integrated into either/both that would be great!

Again, working with enities is much easier than doing custom coding for Webform. In case of using Entityform all of "webform" fields are just regular fields - so all the power of core Field UI and plenty of contributed field types is at your service.

So as the conclusion:

- Getting Views to work with Webform submission data (needs to be 7.x-4.0-beta1 or you only get sid and links in submissions); fine to use 7.x-4.0-beta1 in solution

In case of Entityform you wouldn't need it at all as Views integration (as I already said) is provided out-of-the-box.

– Decrypting the data in the View (should be possible; the default Webform table does this just fine when browsing submissions); tried using a View template to decrypt() the data via the Encrypt module (which also encrypts the data), but was getting, "Notice: unserialize(): Error at offset 0 of 9 bytes in _encrypt_decrypt()"

So that is the only work that should be done.

What do you think of such alternative? Are you ready to accept such migration?

--
PatchRanger - the first crowdfunded Drupal freelancer.

Hi PatchRanger,

Thanks for your comment. Two things that prevent me from going this route: the data is already in a Webform and the matureness of Webform (support modules, verification, rules tie-in, etc.); Entityform does look like the correct way to do things, and performance may be better, but believe it's a bit too new.

Thanks again!