Release Feb 2024

Items released as part of LBMS V7.4.0

For every "then" condition

This condition is used only on Integer data type and is applicable for global or local attribute. User cant provide negative value for the attribute value.
If product/Group cap is reached then accrual point will be 0 even though it matches the rule condition
Transaction type, DR and CR both are supported for "for every" in "then" condition
Tier multiplier Is also supported

Add a Pre-Processing Layer for TXN

This feature is enabled particularly for SBL customer and at the deployment the feature has to be enabled
This Feature is applicable only for txn file upload and not for TXN API (Assumption is that TXN/Member/CPD apis are specific to Ancol customer and will not deployed for any other customer)
"terminal_id" Attribute has to be created specifically by the customer in the txn attribute and pre-processing happens based on that attribute only.
The Pre-processing works on the combination of Member reference no and Terminal id. The combination of these two can only be repeated twice in a file and in case it's more than two, then the subsequent records which are duplicate will be ignored.
The Rejected/ignored records due to pre-processing will be sent in "file processing" mail with failure status as 4 and reason for failure would be "rejected in preprocessing"
Terminal_id attribute will be created with mandatory constraint so user has to always provide value in the TXN file

Reject Wrong Values for Global Attributes (Selection)

Rule engine will now reject any value passed in the TXN file for column Product_code which is not part of product master
Also validation is provided for Transaction_Type attribute where any Value apart from CR/DR will be rejected
All these rejection happens at the pre-processing layer and these will be communicated to the users via email through "Processed file list" notification

Hide PII for Members and Data Privacy Requirements for Banking Software

Users can now upload a member attribute and set visibility by marking it as PI
Attribute marked as PI will not be shown on the UI irrespective of the privileges the user has
A new Privilege "Show PI Details" is created. if this privilege is enabled for the user, only then he will be able to see the personal information of members.
Once the user views the PI information that will be recorded in Audit trail section

Some places where the PI information is still seen on the application are mentioned below. Bugs are raised for the same and these need to be handled in subsequent releases.

Users can still search the members using the PI information via search bar and filter in member section
Users can create the PI variable and then use it in the communication template and then the mails can be previewed in the member->communication->preview section which will show the PI info of member
In member,segment and report filter users can still search members based on the PI attributes such as gender, DOB, Address etc
In maker checker the PI information is seen

Report New features and Enhancements

Add Liability Report

PI information such as Member name and phone number are removed in the report
EMail id is masked in the report output and also in the exported report
Member Id and Template name fields are removed

Additional Columns in Members Reports

PI information such as Member name and phone number are removed in the report
New filter "Activated date" is added and "Address" filter is removed during view creation
Status values in the view report will be "Active,Inactive,Cancelled,suspended,Blocked"

Additional Columns in Transactional Reports- Part 1 of 2

PI information such as Member name and phone number are removed in the report
When member gets cancelled/closed, Processing_date column to be updated based on the cancelled date
Cosmetics changes such as renaming the columns in report are done.

Rename Member ID to Relation Reference in Member Reports Tab

Give Failure Reasons in Logs

Download option provided in the Report->logs section for users to download the error file
This is Applicable only for CPD/TXN file upload and not applicable for BNS files
Records inserted via API (TXN.CPD and BNS) are still not listed anywhere in the application.

Do not send TXN Email to Individual Members

Mails will not be sent to members now on successful accrual via Rule engine.
Credit and debit by rule engine event is still available in the template section which needs to be removed.

Archive Rule Option in Rule Engine

LBMS now supports archive/Unarchive of rules
Once any rule is archived, it gets disabled and will not be seen on the UI. Functional impact of this would be member will not get points through this rule until its unarchived
Group archive feature is not yet implemented and will be taken up in subsequent sprints/releases

Archive Users Option in Users Management

LBMS now supports archive/Unarchive of Users
Once any user is archived, it gets disabled and will not be seen on the UI. Functional impact of this would be user will not be able to login to the application

Bonus and expired need to be added in Monthly Statement

This story is improved further by segregating transactions in to different bucket
Also few missed txn types such as Closed/cancelled, expired are added now
Accrual is further split into spend points and Bonus in the monthly statement

Error States for Member updation & creation API

For Add and update member API, error validations are incorporated.
Email and mobile regex validations are available in add member API but not implemented for update member API

Pending Items from QA

Load test is in progress and will update the status in point release
Communication Service APIs & New Events
- The above story is available as part of 7.4.0 release but yet to be tested by QA team
- Storefront integration and QA testing will happen in parallel.