Using Form Submissions as Assets to "buy" in Ecommerce

(Andre) #1

Hi All, 

 

I am trying to explore a way to use form submissions as input for ecommerce items. In this case, bookings for rooms. 

 

So i have a custom form, where users put in their request. Then a human being will assess if the request is approved or not. The idea is then to have this approved request become an asset that can be purchased. Once the asset is purchased and paid for, I'd then like to create an event item on a calendar. 

 

I was thinking of applying a metadata schema to the form submissions, but they are Type-3's, so not easily usable as normal 1 and 2 type assets. This metadata would then have the price etc. But i can't find where to apply meta data on submissions. 

 

Should I perhaps use a SOAPservice call to itself as part of the submission action to then create a standard asset? Then apply a meta data scheme that allows me to set "approved: yes or no" and the price (the price is based on the booking, a variable to be entered by the admin person) once the admin person approves. This could be a JSAPI call, to adjust parameters in the asset an email the requestor a link to the ecommerce component. I'd like to make it so that user doesn't have to fill in their initial details again.. 

 

I have tested the form, i have tested ecommerce but I just haven't got both linked. or even linked to the calendar event. 

 

any ideas? 

(Joel Porgand) #2

You can use a metadata schema on form submissions no worries - just set up a trigger to apply it or have one set to cascade down from the submissions/incomplete submissions folder of the form.

 

Type 3 linked assets are just as usable as regular assets, with the exception you can't see them in the asset map. If you go to the linking page of the submissions folder and changed the dropdown to linked children you will be able to see them listed there & get to their details that way. That said, there are some restrictions on what you can link form submissions too - pretty sure it's folders only.

 

If you're using manual approval you can probably set up JS API calls to grab your submission information and create some new assets with the information you want, should be pretty simple.

 

That said, I'd urge a bit of caution. Just because you can whip something up entirely in matrix doesn't necessarily mean it is a good idea, especially once the scope of your project starts creeping.