Showing the google drive file in Appian as a preview

I think this should get you started:

www.labnol.org/google-drive-image-hosting-220515

Stefan, Please share the sample code with me,

and also, the thing is I just want to keep my files private.

I do not have any sample code or ever tried to do this kind of things.

Stefan, This Platform is very much familiar to you, if you try, then you can come up with a solid solution.

LOL ... If I would have the spare time, then yes ...

Please try it yourself and share your experience here.

For Startup its looks g-drive mapping is alright as you mentioned above. I guess we can have uid of image in URL and use this way to get image if I understood properly.

a!imageField(
  label: "Image",
  labelPosition: "ABOVE",
  images: {
    a!webImage(
      source:"https://drive.google.com/uc?id=0B9o1MNFt5ld1N3k1cm9tVnZxQjg",
    )
  },
  size: "MEDIUM",
  isThumbnail: false,
  style: "STANDARD"
)

i want to keep my files private

Mohan Reddy Kethireddigari said:

i want to keep my files private

I'm unclear why that's relevant here...

Mohan Reddy Kethireddigari said:

i want to keep my files private

I'm unclear why that's relevant here...

if the image in google drive is private and the drive account is already signed out, then a!webimage couldn't be able to get that image from google drive. right?

Appian is loading that image in the browser. So your user needs to be logged in to Google drive to see any image.

But I do not want to ask the user to sign in to his google account before using the Appian application.

I don't think this is the only way to do it.

I understand, but this is how it works.

The alternative is, to download these files into Appian.

BTW, what is your use case?

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...

we can download the images to Appian to show as a preview. but the thing is when will you delete those?

In such cases, I typically do the download in a process which deletes the file after a grace period.

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.

Why do these images need to be stored in google drive? Why do not just upload them to Appian?