- Using Session Variables to Filter a GridLinker
/pages/Obsolete/Grid Linker Component/Using Session Variables to Filter a GridLinker.xml
Web publishing applications only. By default a gridlinker displays all of the records of the underlying grid components. To filter a grid (typically the primary grid) in a gridlinker, follow this procedure.
Assume you have a gridlinker that links the OrderHeader table (parent) to the OrderItems table (child), and you want to filter the OrderHeader grid so that invoice_number = session.invoice_number.
- Protected Variables
The Application Server supports 'protected' variables. Any variable name that starts with ' protected ' (e.g. ' protectedIsLoggedOn ') can only be set using Xbasic code in a page, and cannot be set from the URL. For example: *[xb:http://myserver/page1.a5w?session.protectedIsLoggedOn=yes]* will not create the variable ' session.protectedIsLoggedOn '.
- Using Addin Variables to Create a Multi-Database Application
/pages/Guides/Desktop/Design/View/Database/Using Addin Variables to Create a Multi-Database Application.xml
Our agency is responsible for administering many programs for the needy population in our county. For over 10 years, we have used Alpha Software to handle the task. The system is currently written in Alpha5 version 1 and it has performed admirably!
Our user interface is one where they sign into the system with a user-id and password. Once authenticated, the user is presented with a "Main Menu" application. Applications were a series of "card stacks", which are forms not associated with any table or set, only the application. From this Main Menu, a user can get to (provided they have appropriate security) whichever application they need. Application-to-application communication was fairly straightforward using an "app_run" command. We were also able to create "Global" variables that would be available to all called applications.
With the release of version 2 of Alpha 5, card stacks were no longer being used, and Xbasic, as we knew it, had changed. The methodology we used in our system design could no longer be used!
- Using Static Data to Display Events on a Calendar Control
/pages/Guides/Mobile and Web Components/UX/Controls/Data Controls/Calendar/Using Static Data to Display Events on a Calendar Control.xml
You can use static JSON data to populate the events on a calendar.
QR Codes are simply data. As with other data controls, you can the setValueFrom() to set the value
of a QR Code.
- Page Variables
You can reference page variables in the events in a dialog component by using the "PageVariables" prefix.
For example, assume that you have a page that is loaded using this URL:
- Desktop A5W
An Alpha Anywhere User Guide to the Desktop.
- ASK Variables
When you use variables in an expression, you can use a special type of variable that asks you for its value when the expression is evaluated. These variables, called ASK variables, can be used just like any other variable. When Alpha Anywhere encounters the ASK variable, an input dialog box appears requesting that you type in a value. The expression result will depend upon the value you enter. The outcome of a query, the filter expression for an export, or the value of an update expression are all examples of operations and expressions which can be based on an ASK variable.
- A5 Variables
The A5 variables, A_DB_CURRENT and A_DB_CURRENT_PATH
- Dim Variables
/pages/Guides/Desktop/Design/Platform/Xbasic Action Scripting/Dim Variables.xml
The Dim Variables action identifies variables dimensioned outside the current action script. For example, this action would be useful in the case where you are defining a filter for a record list control on an Xdialog and your filter references a variable that was previously defined.