Remix

Make your own version of CineWave Ticket Booking

Get an exact, working copy in your account, then change anything with chat.

Original by anusuyap2697

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

# CineWave Entertainment – Movie Ticket Booking Management Application

Create a complete **Movie Ticket Booking Management application** for **CineWave Entertainment** on the **Pega Platform** using Case Management, Data Modeling, Business Logic, Routing, SLA, and Notifications.

## Application Goal

Build an application that allows customers to request movie tickets, enables staff to manage movies, theatres, shows and seating availability, calculates booking costs, obtains customer confirmation, processes the booking, tracks the booking status, and sends confirmation notifications.

## Main Case Type

Create a case type named:

**Movie Ticket Booking**

## Case Lifecycle

Implement the following lifecycle:

**Submit Movie Ticket Request → Check Show Availability → Calculate Booking Cost → Customer Confirmation → Review Booking Details → Process Ticket Booking → Notify Booking Confirmation → Completed**

Include appropriate alternate paths for unavailable shows, rejected requests, and cancelled bookings.

## US-001: Submit Movie Ticket Request

Create a customer-facing booking request form with:

* Customer Name
* Email
* Phone Number
* Movie Name
* Theatre
* Location
* Booking Date
* Show Time
* Number of Tickets
* Show Type
* Preferred Seats

Show Type options:

* Regular
* 3D
* IMAX
* Premium

When submitted, create a Movie Ticket Booking case with status **Requested**.

## US-002: Check Show Availability

Create a staff step to verify:

* Movie
* Theatre
* Show Date
* Show Time
* Show Type
* Total Seats
* Available Seats

Create an availability decision:

* If Available Seats > 0 → continue the booking process.
* If Available Seats = 0 → mark the request as **Not Available** and notify the customer.

## US-003: Calculate Booking Cost

Create fields:

* Ticket Price
* Number of Tickets
* Total Cost

Calculate:

**Total Cost = Ticket Price × Number of Tickets**

Automatically update Total Cost when the number of tickets or ticket price changes.

## US-004: Confirm Booking Request

Create a customer confirmation step displaying:

* Movie
* Theatre
* Date
* Show Time
* Number of Tickets
* Selected Seats
* Total Cost

Provide:

* Confirm Booking
* Cancel Booking

If confirmed, continue to review and processing.

If cancelled, update the case status to **Cancelled**.

## US-005: Maintain Movie and Show Data

Create data objects for:

### Movie

* Movie Name
* Genre
* Language
* Duration
* Rating

### Theatre

* Theatre Name
* Location
* Screen Number
* Total Seats

### Show

* Movie
* Theatre
* Show Date
* Show Time
* Show Type
* Ticket Price
* Total Seats
* Available Seats

Allow authorized staff to create, update and maintain movie, theatre and show information.

## US-006: Review Booking Details

Create a staff review step showing:

* Customer information
* Movie information
* Theatre information
* Show information
* Seat information
* Number of tickets
* Total cost

Provide:

* Approve
* Reject

If approved, continue to ticket processing.

If rejected, close the request as rejected and notify the customer.

## US-007: Process Ticket Booking

When the booking is approved:

1. Validate seat availability.
2. Reserve the selected seats.
3. Reduce the available seat count.
4. Generate a unique Booking ID.
5. Set Booking Status to **Confirmed**.
6. Store the final booking information.

Booking ID format:

**CW-10001, CW-10002, CW-10003...**

Booking statuses should include:

* Requested
* Under Review
* Available
* Awaiting Confirmation
* Confirmed
* Cancelled
* Rejected
* Not Available

## US-008: Notify Booking Confirmation

After successful booking, automatically send an email notification to the customer.

The notification should contain:

* Customer Name
* Booking ID
* Movie Name
* Theatre
* Date
* Show Time
* Selected Seats
* Number of Tickets
* Total Cost
* Booking Status

Use a clear confirmation message such as:

**Your CineWave movie ticket booking has been confirmed.**

Also send an appropriate notification when a booking is unavailable, rejected, or cancelled.

## US-009: Define Booking SLA

Configure an SLA for booking requests.

Use:

* Goal: 30 minutes
* Deadline: 60 minutes

If the booking is not processed within the deadline, trigger an escalation or notification to the responsible staff/team.

## US-010: Route Booking Request by Show Type

Implement routing based on Show Type.

Use the following routing:

* Regular → Booking Staff
* 3D → 3D Show Staff
* IMAX → IMAX Staff
* Premium → Premium Booking Staff

Use Pega routing/decision logic so that the booking request is automatically assigned to the appropriate team.

## User Roles

Create appropriate access/roles for:

### Customer

Can:

* Submit booking request
* View booking details
* Confirm or cancel booking
* Receive booking notifications

### Booking Staff

Can:

* View booking requests
* Check availability
* Review bookings
* Process bookings

### Admin/Manager

Can:

* Maintain movie data
* Maintain theatre data
* Maintain show data
* Monitor bookings
* Manage configuration

## Business Rules

Implement these rules:

1. Number of tickets must be greater than 0.
2. Booking date cannot be in the past.
3. Selected seats cannot exceed the requested ticket count.
4. Booking cannot proceed if no seats are available.
5. Total cost must be calculated automatically.
6. Seats must be reserved only after customer confirmation.
7. Available seat count must decrease after successful booking.
8. Every confirmed booking must have a unique Booking ID.
9. Customer must confirm before final booking.
10. Confirmation notification must be sent after successful booking.
11. Booking requests must follow the configured SLA.
12. Requests must be routed based on Show Type.

## User Experience

Create a clean and simple Pega interface suitable for a movie ticket booking system.

Provide:

* Customer booking form
* Staff booking dashboard
* Availability view
* Booking review screen
* Booking confirmation screen
* Booking status tracking
* Movie/show management screens

Use clear labels, validation messages, status indicators and action buttons.

## Final Testing Scenario

Create a complete test flow:

1. Customer submits a booking request.
2. Staff receives the request.
3. System checks show availability.
4. System calculates booking cost.
5. Customer reviews and confirms.
6. Staff reviews the booking.
7. System reserves seats.
8. System generates Booking ID.
9. Booking status becomes Confirmed.
10. Customer receives confirmation notification.
11. Case is completed.

Also test:

* No seats available
* Customer cancellation
* Staff rejection
* Invalid number of tickets
* Past booking date
* SLA escalation
* Different Show Type routing

## Final Deliverable

Generate a complete Pega application design containing:

* Application
* Movie Ticket Booking case type
* Case lifecycle
* Stages and steps
* Data objects
* Forms and fields
* Business rules
* Decision logic
* Routing
* SLA
* Notifications
* Booking status tracking
* Customer and staff interactions
* Validation
* End-to-end booking workflow

The final application should demonstrate a complete working flow from **Movie Ticket Request → Availability → Cost Calculation → Customer Confirmation → Review → Booking → Notification → Completion**.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.