- Getting Started
- Before You Begin
- How To
- Notifications
- Using VB Expressions
- Designing your App
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Value
- Rule: Start Process
- Rule: Reset Values
- Rule: Upload File to Storage Bucket
- Rule: Download File From Storage Bucket
- Rule: Create Entity Record
- Rule: Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Rule: Trigger workflow
- Leveraging RPA in your App
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Leveraging Media in your app
- Leveraging Actions in your app
- Application Lifecycle Management (ALM)
- Basic Troubleshooting Guide
Best practices
To build a high-performing app using VB expressions, consider the following recommendations and guidelines:
-
VB elements must respect the following naming conventions:
-
It must begin with an alphabetic character or an underscore.
-
It must only contain alphanumeric characters, and underscores.
-
If it begins with an underscore, then it must contain at least one alphanumeric character.
-
It must not be a reserved keyword.
-
Name length is limited to 128 characters.
-
-
Apps controls and pages must respect the following naming conventions:
-
Controls and pages cannot have same name
-
Pages cannot have the default name of controls (for example: button, label)
Note:Icons are identified as controls. Pages cannot have the default name of an icon.
-
Page names must be unique in an app.
Note:Page names are case insensitive, therefore "MainPage" and "mainPAGE" are considered duplicates.
-
Control names must be unique within the page.
-
Both control and page names must respect the naming conventions for a valid VB name.
-
-
Apps variables must respect the following naming conventions:
-
It cannot have the same name as a control or a page
-
It cannot have the default name of controls (for example: "button", "label")
-
It must be unique in an app.
-
It must respect the naming conventions for a valid VB name.
-