Test and Verify the Application Foundation

Before building the Process Flow, run the Purchasing app and test the application foundation from a user’s perspective. For each test, perform the action, observe the application, and compare what happens with the expected result.

1. Run the Purchasing app

1. Return to the main studio editor.
2. In the Modules sidebar section, locate the Purchasing app and check its status:
   • If the application name is blue, wait for the build to complete.
   • If the application name is red, click the red exclamation mark to view the build errors. Correct the reported errors and wait for the application to rebuild.
   • If the application name is green, click the application name to open the app in a new tab.

Expected result:

The Purchasing app opens without a runtime error and displays its application shell.

If this does not happen:

Check the Monitor -> General Log on the Lowgile platform and the browser’s Developer Tools —> Console for errors that identify the cause of the runtime failure. Resolve the reported errors before continuing with the remaining tests.

2. Verify the sidebar navigation

1. In the application sidebar, expand Purchase Request.
2. Confirm that Create New appears as a child navigation item.
3. Select Create New.

Expected result:

The Create Purchase Request screen opens in the main content area.

If this does not happen:

Confirm that the app’s sidebar navigation item links to Purchasing.PurchaseRequestCreate. If the parent item expands but its children remain hidden, see Sidebar Navigation Items Do Not Display.

3. Verify the application shell

With the Create Purchase Request screen open, observe the application header, sidebar, and main content area.

Expected result:

The page displays a single application header and one sidebar. No additional application header or sidebar appears within the main content area.

If this does not happen:

Confirm that the embedded Purchase Request Include screen does not retain its own MainLayout. If a second header or sidebar still appears inside the page content, see Duplicate Navigation Appears in an Embedded Screen.

4. Verify the Create Purchase Request screen

Before entering any data, observe the initial screen contents.

Expected result:

The screen displays:

• The instruction to enter information for a new purchase request.
• The Cost Center dropdown.
• The Add Item button.
• The Submit Request button.

If this does not happen:

1. Open the Create Purchase Request screen and select the Variables tab.
2. Confirm that the request variable has the following configuration:
   • Context: Local
   • Type: This.PurchaseRequest
   • Default expression: new This.PurchaseRequest({}, true)
3. Confirm that the embedded Purchase Request Include screen receives screen.request through its request input variable.

5. Verify the Cost Center dropdown

1. Open the Cost Center dropdown.
2. Compare its options with the values configured when creating the Cost Center Static Entity.
3. Select one of the values.
4. Observe the selected value before continuing.

Expected result:

The dropdown contains the values Marketing, Operations, Finance, and IT, and the selected value remains visible.

If this does not happen:

Confirm that:

• The dropdown’s options list uses the Purchasing.CostCenter static entity and that its binding is screen.request.costCenter.
• The static entity contains the correctly configured values.

6. Verify Purchase Request items

Use temporary test values to test the item controls.

1. Click Add Item.
2. Observe the item that appears.

Expected result:

An item card appears with the following controls:

• Description
• Quantity
• Budget Amount
• Currency
• Remove

3. Enter a description, quantity, and budget amount.
4. Select a currency.
5. Confirm that the entered and selected values remain visible.

If this does not happen:

Confirm that:

• The For Loop array in Purchase Request Include screen uses screen.request.items.
• The Add Item action adds a new PurchaseRequestItem to that array.
• If an item Card title does not evaluate dynamically (for example, as Item 1), confirm that the Card’s Title property is in expression mode (E) and enter `Item ${itemIndex + 1}` with the surrounding backticks. Without the backticks, the template literal will not evaluate correctly.
• The PurchaseRequest to PurchaseRequestItem relationship is configured as described in Define Entity Relationships.

7. Verify multiple items and removal

1. Click Add Item again.
2. Enter different test values in the second item.
3. Compare both item cards.

Expected result:

A second item card appears. Both cards remain visible and can be edited independently.

If this does not happen:

Confirm that:

• The Add Item action adds a second item card below the first card.
• The For Loop renders the items in that array.

If adding a second item replaces or changes the first item, confirm that each iteration of the For Loop is bound to the current PurchaseRequestItem.

4. Click Remove on one item.
5. Observe the application response.

Expected result:

Only the selected item is removed. The other item remains visible with its values intact.

If this does not happen:

Confirm that:

• The Remove button is inside the item card generated by the Purchase Request Include screen’s For Loop.
• Its action removes the current item using screen.request.items.splice(itemIndex, 1).

8. Submit the purchase request

After verifying the screen interactions, test the Submit Request action.

1. Confirm that the purchase request has a Cost Center and at least one completed item.
2. Click Submit Request.
3. Observe the application response.

Expected result:

The Submit Request action attempts to submit the purchase request.

If this does not happen:

At this stage, the Access Denied based on Access control error confirms that the Submit Request action is working as expected. Access to start the Process is configured later in Build the Process Flow. If a different error occurs, see Access Control Errors to identify the cause.

9. Confirm the application foundation is ready

Use this checklist to confirm that the application foundation has been tested and is ready for the next stage.

• The Purchasing application builds successfully and opens without a runtime error.
• Purchase Request → Create New opens the Create Purchase Request screen.
• The app displays only one application header and one sidebar.
• The initial Create Purchase Request controls display correctly.
• The Cost Center dropdown displays the configured values and retains a selection.
• Add Item creates a purchase request item with editable fields.
• Multiple items can be edited independently.
• Remove deletes only the selected item.
• Submit Request returns the expected Access Denied based on Access control error.