- Specify the page=<name> parameter on the URL
- For security, the page must have the property “Allow Direct Invocation” set (defaults to no)
- You will likely wish to pass other parameters on the URL
- Set the property “Pass in parameters”
- It is recommended (but not mandatory if you wish to UrlEncode any links) that any directly invoked page name should be a valid URL (e.g. only contains letters and numbers, with no spaces)
- Set the property “Pass in parameters” within the WebPage node, any parameters given on the URL will be passed through to the page generation, and therefore will be available for processing by any models etc.
- The value of each parameter will be stored under the name specified in the URL.
- Set the property “Protected” within the WebPage node
- Easiest… Template approach
- Add a panel to the page Panel/<name>
- Add a Action at the end of the page to invoke a model which will fetch the format the content, also supply in the template for the content to be formatted in
- This model will fetch the data, apply the template and do a Screen Refresh of that panel, thus filling in the info
- When submitting values, use Parameter/<name>* to submit all variables that start with <name>
- Add an action to the initial / index screen
- Invokes a model (e.g. Initialise Values)
- Pass in a variable (e.g. “initialised”)
- First thing model does if check is variable has is set or not (or is unknown)
- if unknown - do whatever required, remember when exists to store some value in there…
- if seen before - do something else, in this case nothing
- Consider order - i.e. does this need to be something done before other things (put at top of screen definition, i.e. top node after root), or afterwards? - can then go at bottom of root node