Submission Process (End-to-End)
What happens next?
When a submission occurs, there are three outcomes:
After the event stops accepting submissions, we've built custom software to automate the creation of these assets:
How is the HUD configured?
If we have a weekly event, do we have to send a new HUD each week?
- We write transaction details to an encrypted website.
- Note: If this step fails, the Kiosk goes into error mode, and we get a SL Instant Message and a phone alert, then every 2h until the issue is resolved.
- The submitted inventory is then sent to the "Event Server" (another object on the grid).
- Then the inventory is deleted from the Sales Kiosk.
After the event stops accepting submissions, we've built custom software to automate the creation of these assets:
- A notecard and a set of textures for the index that drives how the HUD operates. (implemented)
- A folder export of all of the images named according to the order they appear in the event. (implemented)
- A notecard with a summary of the event, including embedded landmarks, notecard and object links. (coming soon)
- A specialized website specifically designed to enable favourites to be copied from the website. (future)
How is the HUD configured?
- !QQ Touch Panels Controller - Script - it detects touches and enables white-label solutions.
- !HUD - Script - runs the event for the HUD.
If we have a weekly event, do we have to send a new HUD each week?
- No. If we need to make a HUD change, we can expire the current HUD and replace it with something new.