Build Your First App

This guide walks you through designing and configuring your first purchasing application in Lowgile Studio. You will build an end-to-end purchase request workflow covering request creation, approval, rejection, revision, and resubmission.

The application combines a structured data model, task-specific screens, Access Control, and a Process that coordinates how purchase requests move between the Requester, Approver, and Procurement roles.

Throughout the tutorial, you will work with core Lowgile concepts such as modules, entities, screens, and Processes. These concepts are introduced in context as they become relevant.

By the end of the tutorial, you will have built:

• A structured data model for purchase requests and related information
• User-facing screens for creating, reviewing, and updating requests
• A BPMN-based Process that routes requests between roles
• Access Control rules that determine who can start the Process and work with application data

1. Prerequisites

Before you begin:

• You need a Lowgile Studio username and password.
• You must be logged into Lowgile Studio.

2. Working in the Design area

Most of the configuration work in this tutorial takes place in the Design area of Lowgile Studio.

The Design area contains the object types used to build an application, including Modules, Entities, Screens, User-Defined Configurations, and Processes.

As you work through the tutorial, each section explains which object type to select and how to configure it.

✅

Tip

When you create a new object, Lowgile automatically opens its editor.

3. Tutorial roadmap

Follow these four stages to build and test the purchasing application.

1. Build the application foundation

Create the Module, define the data model, configure Access Control, and build and verify the initial screens.

2. Build the task screens

Create the screens used by the Approver, Requester, and Procurement roles during the Process.

3. Build the Process flow

Configure the purchasing roles, build the BPMN Process, connect its routes, and define its task inputs and outputs.

4. Test the complete workflow

Verify request creation, approval, rejection, revision, resubmission, and handoff to Procurement.