Core Terminologies of Workmaster

Before building an application, it is important to understand the structure of the Workmaster platform. The platform is organized into distinct tabs, each serving a specific role in the development process. These tabs provide a step-by-step path from initial design to final deployment.

Design

The Design Tab defines the visual identity of the application. It is the starting point for establishing the overall look across pages and devices.

• Logos, fonts, and color palettes can be uploaded or customized.

• Colors can also be extracted from an image and applied to the design.

• Saved changes are applied consistently throughout the application.

Page

The Page Tab is used to build the interface of the application. This includes all elements visible to end users.

• Pages can be created using templates or by designing layouts from the beginning.

• Widgets such as buttons, input fields, charts, and images can be added to the canvas using a click-to-place interaction.

• A Property Editor allows adjustment of appearance, layout, and behavior for each widget.

• The Widgets Tree provides a hierarchical view of page components for easier management.

To introduce interactivity, the Rule Panel is included:

• Events define what triggers a workflow (e.g., a button click, page load).

• Conditions control when an action should occur.

• Actions specify the result (e.g., open a popup, update a record, navigate to another page).

Data

The Data Tab manages the application’s data and its structure.

• Data objects such as Users, Products, or Orders can be created, each with defined fields.

• Relationships between objects, such as linking an Order to a Customer, can be established.

• Records can be viewed and managed directly.

• Queries can be defined to retrieve and use data across the application.

Bot

The Bot Tab provides tools for creating no-code chatbots.

• Bots can answer questions, guide users through steps, or perform actions based on stored data.

• They operate within the same framework as the application’s rules and data, providing responses aligned with the current context.

Process

The Process Tab is used to design workflow-based business processes.

• Processes are modeled visually using click-to-place tools, with elements such as swimlanes, connectors, and event blocks.

• These workflows support multi-step tasks such as requests, approvals, onboarding, or reviews.

• Processes can be connected to the application using widgets such as:

  • Process Inbox for displaying assigned tasks,

  • TrackId for monitoring progress,

  • Process Containers for initiating workflows.

This integration allows tasks such as submitting a request, approving items, or checking status to be carried out directly in the application interface.

Run

The Run Tab provides testing and deployment options.

• A built-in simulator previews the application in desktop, tablet, and mobile views.

• Rules can be set for what users see before and after logging in.

• Applications can be previewed on devices through QR code scanning or shared via a public web link.

• Deployment tools allow applications to be submitted to the Google Play Store and Apple App Store without separate build processes.