HomeGuidesAPI Reference
Log In
Guides

Release Jun 2024 - v7.9.0

Suggest Edits

LBMS V7.9.0 Release Notes

New Features & Enhancements

Communication Queue Optimization

  • Efficiency Improvements: Significant optimizations have been implemented to improve performance and reduce system load, including:
    • Payload Size Reduction: The payload size for communication jobs has been reduced from 17KB to 0.5–1.5KB.
    • Redis Pool Enhancement: Redis pool size has been increased from 10 to 20.
    • `Configuration Changes:
      • `Introduced Swap memory.
      • Set a memory threshold to prevent exceeding set limits.
      • Enabled job persistence in Redis to prevent data loss during server or service restarts.
  • Bulk Communication Handling:
    • During testing, the system processed 1 million communications with a 100-millisecond delay per email, simulating SMTP lead time.
    • With a single pod for email and job processing, it takes approximately 3 days to send 1 million communications.
    • Priority Mails: Critical communications like OTPs and redemption confirmations can be prioritized to ensure they bypass the queue and reach members promptly.

This optimization is crucial for handling high-volume communications efficiently, ensuring faster email processing and delivery without overloading the system.

Enabling CRD File Integration

  • Mandatory Fields: The following fields are now required for CRD file integration: RelationReference, LastSixDigits Status, ProgramId, and ProductCode.
  • Sub-Relation API Limitations: There is no delete API available for member sub-relations.
  • Product Code Validation: Validation ensures that product and sub-product codes are valid and exist within the LBMS system.
  • Duplicate Sub-Relation Handling: Users can now pass duplicate sub-relation references.

This ensures a seamless integration of CRD files into LBMS, facilitating more robust and accurate member management.

Encrypting & Hiding Communication Previews for Data Protection

  • Protected Events: Communication events like lbms_member_otp, forgot_password, and giift_card_redemption now have no preview options in the member section to enhance data security.
  • Variable Handling: Sensitive variables such as OTP and passwords in non-protected events remain visible unless linked to these specific events.
  • Encryption: By default, all emails are encrypted, providing an additional layer of security for member communications.
  • Template Previews: Hiding previews applies to both email and SMS templates.

These enhancements address client concerns around data security, ensuring that sensitive information is properly protected within the system.

Supporting Member-Preferred Languages in Communications

  • Preferred Language Setting: Users can now set a preferred language for communications at the program level. This applies to both promotional and transactional templates.
  • Language Integrity: Once set, the preferred language cannot be edited or removed.
    • For existing members, preferred languages can be updated via the update member API or CPD upload.
    • If no preferred language is set, English (EN) is the default, or the field can be left blank.
    • Invalid or special characters are not accepted in the language code field.
  • Template Handling: If the preferred language is not available for a member, the system defaults to English.

This feature allows for greater personalization in member communications, delivering messages in the member’s preferred language.

Data Exports for User Access Management & Audit Trail

  • Export Capabilities: Users can now export user, role, and audit trail data from the system.
    • User & Roles Export: All users and roles are exported, as they are not program-specific.
    • Audit Trail Export: Program-specific data is exported from the audit trail.
    • The export logs can be found in the Reports → Administrative Data section.
  • Permissions Required:
    • Users must have view access to the User Access Management and Report modules to download the data.
    • Creator Information: The createdBy column will show the username for users but will not appear for roles.

These improvements provide administrators with easy access to audit and user management logs for compliance and reporting purposes.

Member-Level Activity & Audit Logs Export

  • Consolidated Export: Users can now export both member-specific activity logs and a consolidated report for all members’ activities.
    • Activity logs include profile changes, member actions, and more.
    • Exported logs are available in the Reports → Administrative Data section.
  • Permissions Required: Similar to user and audit trail exports, users must have view access to both the Member module and the Report module.

This enables administrators to track and analyze member behavior efficiently for audit and reporting purposes.

Extended Search Based on Custom Member Fields

  • Custom Attribute Search: Users can now search based on custom member attributes by enabling "Include in member search" during attribute creation.
  • Global Attribute Search: Searching by global attributes (e.g., Relation Reference, Full Name, Email, Phone Number) is also supported.
  • Non-Editable Settings: Once an attribute is created, its inclusion in member search cannot be changed, making this feature useful primarily for new programs or attributes.
  • Performance Improvement: Point-related information has been removed from initial search pages and filters to improve search speed.

This enhancement provides a more flexible and efficient way to search for members based on specific criteria.

Maker-Checker for Program Configuration - Point Settings

  • Expanded Maker-Checker: The Maker-Checker process now includes Point Configuration.
  • Program-Level Enabling: Once enabled at the program level, it cannot be disabled. Any requests will follow the Maker-Checker flow, except for programs where this module is not enabled.
    • The latest approved request will take precedence in case of multiple pending requests.
  • Notifications: Email notifications for pending actions will now include point configuration requests.
  • Field Removal: Purchase Rate and Cashback Rate fields have been removed from point configuration, though they may still appear when creating a new program. These fields will not appear during edits.

This provides added oversight and approval steps for point-related settings in the LBMS system.

Refinements

  • Reports: Added a new column to track which LBMS user performed a redemption on behalf of a member.
  • Point Purchase Report: Introduced refinements to track and manage point purchases.

Updated 6 months ago