v7.14 — March 2025
Released: March 2025Data Security & Privacy
Member PII Encryption
Email addresses, mobile numbers, and all PI-tagged custom attributes are now encrypted at rest in the database:- Encrypted data is automatically decrypted when sent to members
- Downloaded member detail files show decrypted or masked data
- Custom attributes tagged as PI are excluded from reports
- Deletion from storage is permanent and cannot be reversed
- Available and used storage information is visible on the Loyalife UI
PII Toggle for PI Attributes
- Attributes can be marked as Personally Identifiable (PI) by admins
- UI visibility of PI-tagged attributes is controlled by the “Show PI Details” privilege
- Access to PI data is recorded in the audit trail
File Processing
SFTP File Upload via the UI
Transaction and CPD files can now be uploaded directly from the Loyalife application — previously only available via SFTP:- Maximum file size: 10MB
- All validation rules from SFTP apply (file name, length, data type constraints)
- Error logs are viewable in Reports → Logs
- Requires “Edit platform configuration” permission
Access Control
Role Deletion and Permission Management
- Unused roles can now be deleted; default roles (Program Admin, Program Manager, Customer Executive) are protected and cannot be edited or deleted
- Role permissions are viewable without requiring edit access
- If maker-checker is enabled, user management follows the same approval flow
- Existing customers require an upgrade script to apply default role permission protection
Dual-Mode Login (Username or Email)
- Users can log in and use the “Forgot Password” flow using either their username or email address
- Applies to non-LDAP, LDAP, and Cloud authentication
- Generic error messages are shown for invalid username/email combinations
Configurable Password Strength
- Password length is now configurable per program
- Common or easily guessable passwords are rejected
- Passwords with a strength score above 3 are accepted
Member Portal (Storefront)
Self-Service Hub
Members can now register, claim transactions, view history, and initiate redemption through the storefront:- Registration supports: email address, first name, last name, and mobile number (optional)
- OTP verification is required upon registration
- For existing members, the relation reference must match their email address
- Points are displayed in whole numbers only — decimal points are not supported on the member portal
Points
Conditional Points Release
Programs can configure a delay between when points are awarded and when they become redeemable:- A Date Attribute and Delay Time define when the release begins
- Points are awarded per rule engine logic but remain non-redeemable until the delay has elapsed
- Only transactions with confirmed status are eligible for redemption
Post-Transaction Claims
Programs can require members to explicitly claim transactions before points are credited:- Configuration sets a Field to Validate Purchase and a Date Attribute
- Once a transaction is claimed by a member, it cannot be re-claimed by anyone
- Unclaimed transactions remain in the queue indefinitely
Campaigns Without Compulsory Points
- Campaigns can now be configured to send communications without issuing any points
- Audience targeting, delivery logs, and analytics remain fully functional
Tiers
Manual Tier Update via API
- Members can be directly mapped to any tier using a batch API (maximum 1,000 members per request)
- Tier bonus is issued after the next tier cron execution
- Deleting a higher tier automatically downgrades affected members to the base tier at the next cron run
Tier Custom Benefits
- Non-base tiers can have up to 10 custom benefits (welcome bonus or point multiplier)
- Default values if not set: welcome bonus = 0, point multiplier = 1×
- Sequencing of benefits is configurable but functionally irrelevant
Tier Retention Policy
- Rolling Year evaluation only — retention does not apply to upgrades
- Minimum retention period: 30 days; maximum: 365 days
- Members remain in their higher tier even if their current points fall below the tier threshold during the retention window
Reporting
Rule ID and Rule Name in Transaction Columns
- Four new optional columns are available in all transactional reports: Rule ID, Rule Name, Rule Group ID, Rule Group Name
- These are blank for Tier Bonus, Campaign Bonus, Expiry, and Redemption transactions
- These columns do not apply to records from legacy (pre-v7.14) programs
Claimed/Unclaimed Transaction Reporting
- A “Pending transaction” filter is available for
transaction_type = 5 - Pending transactions are excluded from accrual and reversal reports
- Unclaimed transaction reports are available to users with “Create Rule Engine” permission
Segments
Extended Filter Capabilities
- The same filter can now be applied multiple times in a segment definition
- Import/export functionality is supported for segments
- Conflicting filters are allowed (e.g., “within 1 day” AND “not within 1 day”)
- Decimal values are not accepted in numeric filters — integer values only
Rule Engine
Rule Preview
- Before saving a rule, users can preview the point calculation based on the last record in the transaction table
- Group and product capping, and anomaly detection are excluded from the preview
- If no transactions exist, a new transaction can be added for preview purposes
- Includes transaction type 5 (pending state)
UI Improvements
- Program Logo: Images are auto-adjusted for dimensions; images larger than 500×500 require manual crop/zoom
- Pending Transactions on Storefront: Visible with a “Credit Pending” tag regardless of whether the value is positive or negative
- Country Code Rendering: Configurable per client; France is pre-configured as default for the self-signup registration flow
- Multi-Language Storefront: Language selection via Weglot configuration; French and English tested; text briefly displays in English before switching