Skip to main content

v7.9.0 — June 2024

Released: June 2024

Communications

Queue Performance Optimisation

The communication queue has been significantly re-engineered:
  • Payload size reduced from 17KB to 0.5–1.5KB per job
  • Redis connection pool increased from 10 to 20; swap memory and memory thresholds introduced; job persistence enabled
  • A single pod can now process approximately 1 million communications (at 100ms delay per email, ~3 days)
  • Priority delivery: OTPs and redemption confirmations bypass the standard queue for immediate delivery

Communication Security

  • Protected events (OTP, forgot password, card redemption confirmation) have no preview option in the template editor
  • All emails are encrypted by default
  • Privacy controls apply equally to email and SMS templates

Member Preferences

Preferred Language per Member

Programs can configure a default language for member communications:
  • Set at the program level for promotional and transactional templates
  • Once set, the preferred language cannot be edited or removed
  • Language can be updated for existing members via the Update Member API or CPD upload
  • When a member’s preferred language is not set, or a template in that language is unavailable, English is used as the fallback

Data Exports

User, Role, and Audit Trail Exports

  • All users and roles are exportable globally (not program-specific)
  • Audit trail data is exported program-specifically to the Administrative Data section in Reports
  • Member activity logs (profile changes and member actions) are exportable at both member-specific and consolidated levels
  • Access requires View permissions for the relevant module

  • Custom member attributes can be made searchable if “Include in member search” is enabled during attribute creation
  • Global attributes (Relation Reference, Full Name, Email, Phone Number) are always searchable
  • This setting is immutable once the attribute is created
  • Point information has been removed from the initial member search results to improve performance

Maker-Checker

Point Configuration Approval

Point configuration changes now require maker-checker approval:
  • Once enabled at program level, this cannot be disabled
  • When multiple requests exist, the latest approved request takes precedence
  • Email alerts now include point configuration change requests
  • The Purchase Rate and Cashback Rate fields are removed from the edit UI (they may still appear during new program creation)

CRD File Processing

  • RelationReference, LastSixDigits, Status, ProgramId, and ProductCode are now mandatory fields in CRD files
  • Product and sub-product codes are validated against system records
  • Duplicate sub-relation references are now accepted

Reports

  • A new column tracks which user performed a member redemption
  • Point Purchase Report has been enhanced with additional tracking fields