v7.5.0 — March 2024
Released: March 2024Transaction Processing
Queuing for Unregistered Members
- TXN file uploads and API calls are now accepted even without a matching member in the system
- Transactions are stored and processed when a matching rule exists; they appear in reports and dashboards (excluding member reports)
- When the member later onboards, the UI allows manual mapping of orphaned transactions
- Stored transactions are excluded from segments, tiers, and campaigns until the member is created
Member Management
Structured Member Status Flow
Five status values are supported in CPD uploads, with defined transition rules:| Code | Status | Description |
|---|---|---|
| N | New | Initial onboarding; unique reference required |
| B | Suspend | Active → Suspended |
| C | Closed | Member closure |
| A | Un-suspend | Suspended → Active |
| U | Update | Demographic update; valid for any status |
- Welcome emails are triggered on first onboarding or when a closed member is reactivated
- Members activated via a new Member Activation API that accepts a relation reference parameter
Reports
Auto-Generated Legacy Reports
Monthly system reports are now automatically generated for all programs:- Accrual, Redemption, Expiry, Reversal, Cancellation, Bonus, Member, Communication
- The Member report is system-generated by default; custom reports continue to support variable time periods
- New transaction report filters: Debit by Cancellation, Debit by Reversal, Credit by Reversal
- The obsolete cashback filter has been removed
Communications
Priority Queue for Events
Communication events are now classified into five priority levels for ordered processing: Critical, High, Medium, Normal, Low New communication events added: Redemption OTP, shop orders, flight/hotel bookings, package bookings, miles exchange, forgot password Rate limiting:- Configurable hourly limits per event/member
- Daily limits per member
- Plain text character limit increased from previous to 2,000 characters; HTML templates to 100,000 characters
- Special characters are allowed in templates
Configuration
- Session token expiry is now externally configurable via the
token_expiryproperty - Timestamps throughout the application display as stored in the database — no timezone conversion is applied
- Rule Engine selection dropdowns are restricted to existing valid values only