Release2 May 2024 - v7.8.0
LBMS V7.8.0 Release Notes
New Features & Enhancements
Tier Progression Based on Aggregated Attributes
- Custom Aggregate Attributes: Users can now create aggregate attributes from transactional (TXN) attributes. These attributes can be global or local (mandatory/optional). Supported aggregations include:
- Min, Max, Avg, Sum, and Count
- Once Created, No Edits: After an aggregate attribute is created, it cannot be edited.
- Attribute Deletion Rules: If a transactional attribute is used to create an aggregate tier attribute, that transactional attribute cannot be deleted.
- Conflict Management: If conflicting tier conditions are created, the higher tier will take precedence during member progression.
This feature enables more dynamic and tailored tiering strategies based on comprehensive data.
Assisted Points Redemption (Storefront Integration)
- Storefront Integration for QA: We’ve integrated a dummy storefront with the LBMS dev/QA instance, allowing redemption to be performed on behalf of members through the storefront.
- Active Member Restriction: This feature is enabled only for members with an Active status.
- Audit Logging:
- Redemptions performed on behalf of members will not appear in the LBMS audit logs.
- When a member performs the redemption directly, their activity is recorded in the LBMS member audit log.
- Redemption Emails: LBMS sends a redemption email to members using the "LBMS points redeemed" event. Any additional communication must be handled by the storefront.
- Report Filters:
- Redemptions handled on behalf of members will not appear under the "Debit By On Behalf Redemption" filter.
- All redemptions (including Giift card and normal redemptions) can be found under the "Debit by Redemption" filter.
- Session Handling: Closing the LBMS browser or session will not log the user out of the storefront. The user can continue using the storefront for redemption.
Enhanced Error Codes for CheckMembershipCredentialsByRelationReference API
- Error Messaging Based on Member Status: The API now returns more granular error messages and codes based on the status of the member.
- Auto-Blocking for Incorrect Password Attempts: If an incorrect password is submitted more than the system-configured threshold, the member will be automatically blocked.
- Password Counter Reset: If the correct password is entered before the threshold is reached, the incorrect attempt counter resets.
- Unblocking: Blocked or suspended members can be unblocked via the LBMS Member Section.
Custom Events for Communication Service
- Create Custom Events: Users can now create custom events and associate them with transactional templates.
- Unique Event Keys: Event keys must be unique across programs.
- Special Characters Supported: Characters such as “-” and “_” can be used in event labels and keys.
- Audit Logs: Changes to events (creation or updates) are tracked via audit logs.
- Priority & Rate Limiting: New events will have low priority by default, with no rate-limiting.
This enhancement allows more tailored communication strategies through custom events.
Maker-Checker Process for Rule Engine
- New Maker-Checker Flow: The Maker-Checker process has now been extended to the Rule Engine.
- Program-Level Enabling: Once enabled at the program level, it cannot be disabled. If not enabled, requests follow the normal approval flow.
- Maker-Checker Actions Covered:
- Group Update, Rule Create, Rule Update (Priority Change), Enable/Disable Rule, Archive/Unarchive Rule
- Excluded Actions:
- Transaction attribute creation/edit/deletion, group creation, and product/sub-product code addition.
- Automatic Permissions: Users with maker-checker access now automatically receive rule engine view permissions to allow them to verify or approve requests.
This feature provides added governance over the rule engine’s changes, ensuring that modifications are carefully reviewed and approved.
Manual Points Enhancement for Better Reconciliation
- Enhanced Audit Fields: Users are now required to provide more detailed information when issuing manual points (credit or debit), improving audit trail transparency.
- Mandatory Attributes: Global/custom TXN attributes marked as mandatory must be provided for manual points.
- Non-Mandatory Attributes: Users can include non-mandatory TXN attributes by enabling a flag.
- Deletion of Attributes: If an attribute used in manual points is deleted, it will not appear in reports, though the transaction will still be present in the transaction summary.
- Reports & Manual Points:
- Points issued via Redemption Reversal will appear under the “Debit By Redemption” filter.
- Reversals handled via the Redemption Reversal API will appear under “Credit By Reversal.”
Customizable Brand Layout for Emails
- Template Customization: Users with “create template” access can now create custom base templates.
- Cross-Program Applicability: The base or custom template will apply across programs and can be used for promotional, transactional, and system-generated emails.
- Template Guidelines: Base templates must comply with mandatory tag guidelines to be saved.
- Email Preview: The base template configuration will not appear in the email preview under Communication, but it will appear in the Member → Communication section.
Resolved Issues in LBMS
No issues were reported by customers or during the UAT phase for this release.
Updated 6 months ago