Trial Requests
1. Request Overview
Trial requests are submitted by potential customers through the public trial form and processed into subscriptions.
Fields
- Name - Contact name (required, tracked)
- Company Name - Customer's company (required, tracked)
- Email - Contact email (required, tracked)
- Mobile - Contact mobile number (required, tracked)
- Company Size - Employee count range (required, tracked):
1-5,6-10,11-30,30-100,100+
- Trial Package - Associated trial package (required, tracked)
- Partner - Auto-created customer partner record (tracked)
- Subscription - Created subscription (tracked)
- Database Template - Database template override (optional)
- State - Request status (tracked):
New- Pending processingProcessing- Subscription being createdDone- Subscription created successfullyCancelled- Request cancelled
- Notes - Internal notes
2. Request Lifecycle
New → Processing → Done ↓ Cancelled → New (reset)
3. Actions
| Action | Description |
|---|---|
| Create Subscription | Manually create a subscription from this request |
| Cancel | Cancel the request |
| Reset to New | Reset a cancelled request back to New |
| View Subscription | Open the related subscription |
| View Partner | Open the related customer partner |
4. Automatic Processing
When a request is created and the trial package has Auto Run Subscription enabled:
- A
res.partnerrecord is created (or linked if email already exists) - A
sadeem.subscriptionrecord is created with:- Customer = created partner
- Packages = from trial package
- User/storage/stage limits = from trial package
- Trial duration and grace period
is_trial = Trueflag- Model limits (if configured)
- The subscription is confirmed and queued for deployment
Duplicate Prevention
Each email + trial package combination is unique. Submitting the same email for the same package will be rejected.