In my Application, I just wanted to show images in the Appian interface as a preview that are actually in google drive
Discussion posts and replies are publicly visible
I believe, storing an a file using file upload component, and fetching all the files from the drive folder can be achieved easily using different operations of GDrive API, whats different here is that you want to bring the contents(images) to the appian interface but want it as view only. If you want any GDrive content then you have to create a batch process which will bring the contents(images) from that folder to appian interface as preview and then you will have the complete control over the interface. Later you can manage the recurcive process as per your requirements.
OK. As you found out, this brings along some technical difficulties. I suggest to bring this up and refine that requirement.
The requirement is like that, I have to store them in the drive.
Why do these images need to be stored in google drive? Why do not just upload them to Appian?
what if the user goes for the preview at the time of initiating the process for deletion?
then the user can't see the preview and also there is a choice of getting errors also.
we have to download the image every time the user goes for a preview. right?
Then the application will run slowly if the downloaded images increase.
In such cases, I typically do the download in a process which deletes the file after a grace period.
we can download the images to Appian to show as a preview. but the thing is when will you delete those?
Unknown said:So your user needs to be logged in to Google drive to see any image.
I think it's unreasonable to assume that this functionality would have anything to do with an end user's specific Google / Google Drive account. Clearly for this sort of thing to work the designer would need to stage artifacts in their google drive, or a special one they establish specifically for this project, then provide that those images are accessable to an Appian application. In other words, I think all comments here relating to whether the end user is logged into Google Drive are miles off-target.
But of course, OP also hasn't been very clear what the overall use case is, so who knows...
I understand, but this is how it works.
The alternative is, to download these files into Appian.
BTW, what is your use case?