Update Sidebar Navigation
Key Lesson: Connect an application sidebar navigation item to a task-facing Screen.
Update MainLayoutSidebar so users can open PurchaseRequestCreate from the Purchasing application’s navigation.
1. Configure the sidebar entry
Section titled “1. Configure the sidebar entry”- In Design, open the
MainLayoutSidebarScreen. - Open the Layout tab.
- Configure the existing sidebar components as follows:
| Component | Property | Value |
|---|---|---|
| Functional Area | Text | Purchase Request |
| Text in the first Navigation Item | Text | Create New |
| First Navigation Item | Link to Screen | |
-
Save your changes before continuing.
The application sidebar now exposes the first purchase request workflow entry point. The verification section below checks the Screens, navigation, build, and initial user interface together.
Verify the first Screens and navigation
Section titled “Verify the first Screens and navigation”Verify the first two Screens before extending the Purchasing application. This checkpoint covers only the reusable Include Screen, the Create Screen, its navigation entry, and the first working request-entry controls.
1. Verify the navigation configuration
Section titled “1. Verify the navigation configuration”- Open
MainLayoutSidebarin Design. - Confirm that the Functional Area text is Purchase Request.
- Confirm that the first Navigation Item displays Create New and links to
Purchasing.PurchaseRequestCreate.
The application navigation contains a Purchase Request group with a Create New item linked to the PurchaseRequestCreate Screen.
If the labels or link differ, compare the components with Update Sidebar Navigation and save the Screen again.
2. Build and open the application
Section titled “2. Build and open the application”- Return to the main Studio editor.
- In Design, locate the Purchasing application.
- Wait for the application name to turn green.
- Select the Purchasing application, then select Play.
The Purchasing application builds successfully and opens without a runtime error.
If the application is blue, wait for the build to finish. If it turns red, select the red exclamation mark and correct the reported Screen, variable, or binding error. If the application builds but does not open, check Monitor → General Log and the browser console for the reported runtime error.
3. Open the first working user interface
Section titled “3. Open the first working user interface”- In the application sidebar, expand Purchase Request.
- Select Create New.
- Observe the application shell and the main content area.
The application displays one header and one sidebar. The main content area shows:
- The instruction to enter information for a new purchase request.
- The Cost Center dropdown.
- The Add Item button.
- The Submit Request button.
If Create New does not open the Screen, confirm that its navigation item links to Purchasing.PurchaseRequestCreate. If a second header or sidebar appears in the content area, confirm that PurchaseRequestInclude does not retain its own MainLayout; see Duplicate Navigation Appears in an Embedded Screen.
4. Verify the initial request controls
Section titled “4. Verify the initial request controls”- Open the Cost Center dropdown.
- Confirm that it contains Marketing, Operations, Finance, and IT, then select one value.
- Select Add Item.
- Enter a description, quantity, and budget amount in the generated item controls, then select a currency.
The Cost Center selection remains visible. Add Item creates one editable purchase request item with Description, Quantity, Budget Amount, and Currency controls, and the entered values remain visible.
If the Cost Center values are missing, verify the Purchasing.CostCenter static entity and the screen.request.costCenter binding. If Add Item does not create editable controls, confirm that the For Loop uses screen.request.items, its controls bind to the loop-scoped item, and the button action adds a new This.PurchaseRequestItem to the collection.
The Submit Request button is tested later in Connect and Test Request Submission, after its Process-start action and persistence route are configured.
5. Confirm the first Screens are ready
Section titled “5. Confirm the first Screens are ready”Use this checklist to confirm that this stage is complete.