Build a Meeting Room Booking System in 3 Days with Chengwu Low-Code: Conflict Detection, Approvals, Multi-Role

Core Requirements Analysis

Based on research across multiple mid-sized enterprises, the article identifies six core requirements for a meeting room booking system:

Basic information management: register meeting rooms (name, capacity, location, status, supported equipment).

Booking workflow: employee submits booking → conflict detection → approval → notification.

Conflict detection: prevent multiple bookings for the same room in overlapping time slots.

Permissions and roles: different departments have different booking permissions; administrators can configure approval rules.

Notification mechanism: automatic notifications on approval/rejection and pre-meeting reminders.

Usage records archiving: monthly statistics on meeting frequency and departmental occupancy.

Platform Overview: Chengwu Low-Code Platform

The Chengwu low-code platform (accessible at https://admin.cwcode.top) provides the following core capabilities:

Data-driven modeling with MySQL 8 including field comments.

LogicFlow process engine for custom workflows, conditional approvals, and state transitions.

Pebble templates for dynamic parameter input/output and logic service invocation.

Multi-role permission system with field-level and data-level control.

Built-in notification service supporting email, Enterprise WeChat, and webhooks.

Step 1: Database Schema and Page Generation

Meeting Room Table

CREATE TABLE meeting_room (
  id bigint PRIMARY KEY AUTO_INCREMENT COMMENT 'Meeting Room ID',
  name VARCHAR(100) COMMENT 'Meeting Room Name',
  location VARCHAR(100) COMMENT 'Floor/Area',
  capacity int COMMENT 'Capacity',
  device_list VARCHAR(255) COMMENT 'Supported Equipment',
  status VARCHAR(20) COMMENT 'Status (Available/Under Maintenance)',
  remark TEXT COMMENT 'Remark'
);

Booking Record Table

CREATE TABLE meeting_booking (
  id bigint PRIMARY KEY AUTO_INCREMENT COMMENT 'Booking ID',
  room_id bigint COMMENT 'Meeting Room ID',
  user_id bigint COMMENT 'Applicant ID',
  start_time datetime COMMENT 'Start Time',
  end_time datetime COMMENT 'End Time',
  purpose TEXT COMMENT 'Purpose',
  status VARCHAR(20) COMMENT 'Booking Status (Pending/Approved/Rejected)'
);

After uploading the SQL to the platform, Amis automatically generates CRUD pages for immediate use.

Step 2: Booking Workflow Construction with LogicFlow

The workflow is built by dragging components in LogicFlow:

[Submit Application] → [Conflict Detection] → [Manager Approval] → [Notify Applicant] → [Meeting Start Reminder]

Conflict Detection Logic (Database Service + Pebble Parameter Passing)

A database service checks for existing approved bookings in the target time slot:

SELECT COUNT(*) FROM meeting_booking
WHERE room_id = {{ record.room_id }}
AND status = 'Approved'
AND (
  (start_time <= '{{ record.start_time }}' AND end_time > '{{ record.start_time }}')
  OR
  (start_time < '{{ record.end_time }}' AND end_time >= '{{ record.end_time }}')
)

If the result is greater than 0, a conflict is detected, the workflow halts, and a failure message is returned.

Step 3: Approval and Reminder Mechanisms

Pebble Template Examples

Approval stage notification:

{
  "content": "You have a new meeting room booking request: {{ record.purpose }}, time: {{ record.start_time }} - {{ record.end_time }}, please approve promptly."
}

Approval result notification:

{
  "content": "Meeting room booking [{{ record.status }}]: {{ record.room_name }}, time: {{ record.start_time }} - {{ record.end_time }}"
}

Automatic reminder 10 minutes before meeting: Implemented using a scheduled task node combined with a Pebble template for content generation and a notification component.

Permission Configuration

Chengwu supports multi-role permissions with data-level and field-level control:

Employee: Can only book and view their own booking records.

Department Manager: Can approve bookings from their department employees and view departmental usage records.

Administrative Staff: Can view/manage all meeting rooms, perform maintenance, approvals, and scheduling.

System Administrator: Manages permission configuration, workflow nodes, data archiving, and notification channels.

Data Statistics and Export

The system provides the following statistical views:

Monthly usage count and utilization ranking per meeting room.

Departmental booking frequency and average duration statistics.

One-click export of all booking records to Excel.

Pebble templates format the exported report, handling field formatting, pagination, and cell merging automatically.

Deployment Efficiency and Timeline

The article estimates the following effort for each phase:

Schema design: 0.5 days (using DeepSeek to generate SQL).

Page generation: 0.5 days (Amis auto CRUD).

Workflow configuration: 1 day (LogicFlow drag-and-drop).

Parameter passing: 0.5 days (Pebble template writing and debugging).

Permission configuration: 0.5 days (multi-role access control and data isolation).

Total: approximately 3 days for delivery. Mobile or mini-program support can be added as an extension.

Conclusion: Low-Code Reduces Administrative Burden

While a meeting room booking system sounds simple, achieving automatic conflict detection, process automation, multi-role collaboration, and traceable data is non-trivial. The Chengwu low-code platform's advantage lies in using minimal time to get core business processes "done right, done thoroughly, done flexibly."