- markashtonAsked on July 23, 2013 at 08:38 AM
The Jotform Filepicker Integration ultimately consists of the following workflow ...
Jotform submission >> Filepicker Upload >> Storage In Amazon S3
For any Jotform User using this function ... there are two file management issues.
1) The logical management of the files in folders in Amazon S3 - so that they represent the forms being used.
2) The deletion of the files once their lifetime is up.
Now ... with the filepicker integration that has been successfully implemented... the following is in place ....
Jotform submission with filepicker upload .... the file is uploaded, via the filepicker service, to an Amazon S3 Bucket and put into a logical folder. Great ;-)
Not so great is the deletion of files. It is a broken process .... Deleting a jotform submission does not remove the reference in Filepicker ... which in turn actually removes the file from Amazon S3.
Note ... removing the file reference from the filepicker console removes the file from Amazon S3 .. if you have the security policy set-up properly. I have .... but the bottom line here is this ....
The Filepicker Integration needs to address the fact that if a submission is deleted from jotform ... this deletion is also observed in the filepicker console ... and ultimately Amazon S3 ... so that it is automatic.
Otherwise, the whole thing is a disaster area in file management.
What needs to happen? the API integration needs to address this deletion from jotform also deleting corresponding reference in Filepicker.
- KadeJMAnswered on July 23, 2013 at 10:04 AM
Hi Mark, thank you for pointing this out to us. We're aware that you are always testing our integrations to find if corrections are needed. Thank You for your help with pointing out areas that are in need of improvements to make our platform better as it is very much appreciated.
I started looking for a way to test this myself further but it seems that Amazon S3 requires a credit card to fully sign-up incase an account goes past the free limit that then is charged extra for this so unfortunately at the moment I am unable to test this more for myself on my end since I do not have a credit card to use for this. Because of that I'm just going to turn this one straight over to our development team to provide the details about your input for this request for improvement of yours. And I already know that you test these things on your end yourself pretty well. If I am able to figure out something for this to help then I will additionally note it alongside your initial details.
- markashtonAnswered on July 24, 2013 at 05:20 AM
I've discussed this with Filepicker directly ... they state ... Jotform can implement the deletion of files through your API key
As you have Inkfilepicker live on your form builder ... this needs to be implemented ... the reality otherwise is that a form user will have no method to delete stored files except for manually cross-checking each file from his/her filepicker app with Amazon S3 ... difficult to say the least.
- JotForm SupportEltonCrisAnswered on July 24, 2013 at 05:55 AM
That's helpful. Thanks for your continued cooperation with us. We will add that details on the request ticket.
You will be informed here for any available updates.
- markashtonAnswered on July 26, 2013 at 05:38 AM
Can this be done please ... I'll test stratight away
- KadeJMAnswered on July 26, 2013 at 09:33 AM
Hi Again Mark, I can see that this one's been assigned to your favorite person again - Kenneth :D. I'm very certain he'll respond back to you here about this as soon as he can. If we find out anything sooner before that though we will definitely inform you.
- markashtonAnswered on July 29, 2013 at 04:19 AM
I can't use this ***** filepicker integration but you lot wasted stacks of my time testing it to a point where it's one task away from usable ...I absolutely don't get it ....
Look back on all the stuff that has been done on this issue ....
I note the filepicker function is still there on the site builder ready for people to go down a massive red herring only to find they can't manage any of their files at the filepicker/S3 end becuase you lot didn't finish the Filepicker API integration properly.
Any chance we can finish this so it is world class? Or is it staying broken for all your hapless customers to waste loads of their unvalued time over going down the route of integrating it ... and then to hit a communication blackspot.
Thanks ... I'm ready to test in a live scenario
PS I'm not going away until this is done ... I need it
- JotForm SupportWelvinAnswered on July 29, 2013 at 06:06 AM
Thanks for your feedback. We know how important this function with FilePicker. This thread is already assigned to Kenneth so I am sure he's already working on this. Our developers are doing their best to accommodate a request, please have us your patience. Please, don't waste your time testing it. You should know if the function is already added because we will inform your about it.
If the file deletion process is possible with the API, our developers will surely implement that. We just need time to implement this so with your patience waiting for the function.
Thank you very much.
- markashtonAnswered on July 29, 2013 at 08:13 AM
"Don't waste your time testing it" ??
I've already done the testing ?? What would I be testing now?
The file deletion is possible with the API as I've spoken directly to Filepicker as per my thread above that you haven't read.
I haven't got time ... I'm losing money .. I don't have a solution for this because you abandoned it right at the last minute.
- jefreylandichoAnswered on July 29, 2013 at 09:17 AM
We sincerely apologize for this inconvenience that has caused you. We have not received any updates from our developers yet but we would should to inform you once we do.
- markashtonAnswered on July 31, 2013 at 09:36 AM
I can't use this?
Casn you implement it please?
- KadeJMAnswered on July 31, 2013 at 10:43 AM
Hey Mark, I've notified Kenneth who is assigned to this Thread to try to find out how things are coming along in this thread. As soon as we find out how it's doing we'll update you about the status of it.
- JotForm SupportkennethAnswered on August 14, 2013 at 03:21 PM
This should be okay now. We managed to removed all signs of filepicker links attached to a submission. Whether it uses s3 or not, any traces will be removed instantly, so better be careful it can't be undone.
-Delete a file after upload ( X button at the form )
-Delete a single submission - all filepickers files will be removed from jotform and InkFilepicker server
-Delete all submissions - same as above
Please confirm if its working from your end. If you face any problems, let us know!
- markashtonAnswered on August 14, 2013 at 03:51 PM
I have done a preliminary test and can confirm that deleting a single submission from the jotform submissions bin successfully deletes the reference in filepicker console and consequently deletes the file from the Amazon S3 bucket.
That's great. If it goofs for any reason I shall open a new thread.
In the meantime ... many thanks
- KadeJMAnswered on August 14, 2013 at 04:32 PM
Thanks for the feedback about this Mark, much appreciated. Hopefully it continues to work as intended. However, it's very known that programs aren't always perfect since this is the nature of technology sometimes though we do our best to prevent issues. But do keep us informed as you normally do in that case if any.
- markashtonAnswered on August 15, 2013 at 04:53 AM
I can confirm that with further testing that this is working properly.
Note that if one deletes all submissions in one go (via the Delete All button in submission bin that pops up a password prompt) this succeeds in deleteing all the file references in filepicker application and thus deletes the files in Amazon S3 bucket.
Thanks Ken. Consider this is closed