Stadium Web Application Tool

New Release: Stadium 5.14

The latest version of Stadium is out. This release contains some nifty new features that will make building your next great web application even easier.

The new features are;

Session Variables

Stadium has two types of variables – ‘script variables’ and now also ‘session variables’. Script variables have been around for quite a while and are defined in a script by dragging the Variable action onto the script. Once this has been done, the variable can only be used throughout that specific script and ceases to exist as soon as the script completes. Session variables, on the other hand, are defined on the Application level. They can be used across all of the application’s pages and exist for as long as the user’s session is active in the application.

Application Properties

Set both the HTTP Response Headers and the Maximum File Upload Size for your application from within the Designer. This allows you to set them up as you are building the application and removes the need for you to remember to set them up when eventually deploying your application to the Stadium Server.

Find References

Where did I use that query in my application? Where is the control value being changed? ‘Find References’ answers all these questions by displaying all locations where a specific control, action, setting, page parameter, script parameter, etc. is used or accessed.

Preview Logging

Preview was added in the previous release. It not only allowed you to quickly and easily view the application you built on your local computer, but also logged some basic information to the browser dev console while a script was executing. In this release, we improved the logging by adding detailed logs when a web service is executed. Before now, when a web service call failed, you were pretty much left guessing what could have gone wrong. With the new web service logs, you are able to see in detail what Stadium did and where it failed. Information like  authentication details, URL, headers, querystring, response, etc are all logged to the browser dev console allowing you to easily investigate and pinpoint the problem. If you need to resend the request, simply use the logged information to feed it into a tool like Postman and resend it.

See more of Stadium’s future plans on the roadmap

Scroll to top