What You Will Build
Key Lesson: This doc introduces the Purchasing application workflow used throughout the tutorial, the Lowgile components it relies on, and the sequence in which the workflow is built, tested, and extended.
This tutorial uses a Purchasing application to demonstrate how Lowgile platform components work together in a business workflow, comprising the end-to-end lifecycle of a purchase request from creation through approval, rejection, revision, and procurement.
The application is built progressively. The first stages create the purchase request data model and entry Screens. The Submit Request action and persistence path are connected and tested before Approve Request is connected to the Process; the earlier Screen checks cover data entry only.
Insight
For a broader introduction to the platform and its capabilities, see What is Lowgile?.
1. Business case
Section titled “1. Business case”The purchasing workflow involves three business roles: Requester, Approver, and Procurement.
Before the Process starts, the Requester creates a purchase request by completing the required information. The Process begins when the Requester submits the purchase request for review and approval.
From this point:
- The Approver can approve or reject the request.
- A rejected request can be returned to the Requester for revision and resubmission.
- An approved request can be passed to Procurement.
- Procurement can prepare quotation information before the request reaches the end of the Process.
This business case demonstrates how structured data, reusable and task-specific Screens, role-based work, Process routing, and Access Control can be combined in a single Lowgile application.
2. Application setup
Section titled “2. Application setup”In Lowgile, an application is created as a Module. The Purchasing Module represents the application built throughout this tutorial and acts as the container for its components, such as Screens, Entities, Processes, and configuration.
When you create the app, Lowgile automatically includes a set of default Screens that provide the application foundation. These are the Home, MainLayout, MainLayoutHeader, MainLayoutSidebar, and UserProfile Screens.
The MainLayout forms the foundation for most application Screens, except for Include Screens, which are reusable components designed to be embedded within other Screens.
The application is added to the build configuration and built for the first time. This initial build verifies that the application is configured correctly before additional components are added.
3. Application components
Section titled “3. Application components”3.1. Data model
Section titled “3.1. Data model”The data model defines the Entities, properties, and relationships used to represent a purchase request and its related data.
The initial model consists of:
Static Entities (lists of reference data)
Section titled “Static Entities (lists of reference data)”CostCenterCurrency
Entities
Section titled “Entities”PurchaseRequestis the main data structure for the request. It holds information that applies to the purchase request as a whole.PurchaseRequestItemrepresents an individual item being requested, such as a laptop. APurchaseRequestcan contain one or morePurchaseRequestItemobjects.
The Procurement Screen uses quotation data to record the vendors that should receive a request for quotation (RFQ). The following Entities are added when the Request Quotations stage begins:
QuotationQuotationItem
Relationships
Section titled “Relationships”Relationships define how records from different Entities are connected across the data model. For example, a PurchaseRequest is linked to its PurchaseRequestItem records.
3.2. Screens
Section titled “3.2. Screens”The Purchasing application starts with two Screens:
PurchaseRequestIncludePurchaseRequestCreate
PurchaseRequestInclude is a reusable Include Screen that contains the UI fields relevant to the PurchaseRequest and related PurchaseRequestItem data. PurchaseRequestCreate embeds this reusable Screen to provide the user interface for creating a new request.
The MainLayoutSidebar is also configured to add navigation to the purchase request Screens.
Later in the tutorial, additional Screens are added for approving or rejecting requests, updating them, and entering quotation information.
3.3. Application configuration
Section titled “3.3. Application configuration”The application uses several supporting objects to configure where Entity data is stored, control access, and manage shared settings:
- Server Data Store for configuring where Entity data is stored.
- Access Control for controlling access to application data and Processes.
- User-Defined Configuration used by the application navigation.
3.4. Process
Section titled “3.4. Process”A BPMN-based Process coordinates the purchase request lifecycle. Its swimlanes group tasks by participant. Each swimlane’s Assignee expression references a role created separately in Studio to identify eligible users.
The Process defines:
- The Requester, Approver, and Procurement swimlanes
- Process input data
- User Tasks
- Task-specific Screens
- Task inputs and outputs
- Approval and rejection routes
- Revision and resubmission
- The handoff to Procurement
- Process completion
4. Prerequisites
Section titled “4. Prerequisites”To complete the tutorial you need:
- Access to a Lowgile evaluation or development environment.
- A valid Lowgile Studio username and password.
Note
5. Completed result
Section titled “5. Completed result”The completed Purchasing application can:
- Create a purchase request.
- Capture purchase request and item data.
- Submit the request for approval and start the Process.
- Route work between the Requester, Approver, and Procurement roles.
- Allow an Approver to approve or reject the request.
- Return rejected requests to the Requester for revision and resubmission.
- Pass approved requests to Procurement.
- Capture quotation information to complete the Process.