Attachments Variables in Workshop

Hello,

When creating a action(new object) in my object type i set up couple of fields(properties). One of those is “attachment”, where the user would store attachments when submitting a form through an action button in the workshop app. Most of the input widgets in Workshop have the option to use variables which you can then reuse as input to the form as seen in screenshot 3 so for example if user writes something in input text widget into a variable , you can use that variable(which now contains the user text, screenshot 1 and 2) as input to the form property(screenshot 3). Attachments unfortunately don’t have a widget similar to “text input” where you would put a attachment and use the variable(containing the attachment) as the input to one of the input fields of a submission form. There is the widget “media uploader” but that’s for uploading directly uploading files into ontology which is something different. My purpose is for the user to populate couple of fields and then clicking “Submit”(which would be action backed) and then the form will be prepopulated by the variables provided see (screenshot 3), problem is all variables are prepopulated but it pops up the window of the action to insert attachment. It takes from the user experience and i think its a functionality that would be very nice for a lot of workshop applications, i think the challenge is a way how to store the attachment in a variable which might make this hard to do(given the range of all possible attachment types). Is there a capability how to do this or will there be in the future?

Thank you very much

Kind Regards,

It’s a valid point!

A quick workaround I’ve done is to have your object created in the first step, and then have a second tab in your modal that then adds attachments. You can create a separate action for that, and embed that action form in that next step.

It doesn’t have that native look, but it might be a useful workaround until we get more control over Workshop’s config.

1 Like

didn’t think of that, thanks Jake

In my case i played a bit with having the object created first with just the attachment and then at the end there would be “Create request” (from user POV) but the action in the backend would be EDIT object(which already has the attachment) and populate the other values with the variables

But as you mentioned its not a native look, it could be cool to have more control over attachments, i still think attachments in workshop are good but from time to time feel a little bit clunky but that might be just me

Fully agreed, Workshop needs some more love to look expensive. It’s an ongoing struggle!

Glad you were able to at least find a solution that moves your use case forward.