HomeGuidesAPI Reference
Log InTalk to Sales
Guides

Release June 2025 - v7.17

1. Providing ability to configure SMS & Email Provider separate for each program

Loyalife now supports multiple email/SMS accounts per deployment.
This configuration resides with the dev-ops and not exposed in UI Program level configuration overrides the default settings If the Program level configuration is not configured properly then the email/sms will fail and in this case default configuration will not be considered.

2. LDAP Service Account Configuration for Organization Unit Fetch in Member Login

LDAP user present in different Organization Unit are able to login to application, create program and do all activities.
User can be present across different Organization Unit but same user cant be present in multiple OU’s LDAP user part of nested Organization Unit are also able to access the application As is the practice reset password, change password is not seen when the LDAP is enabled LDAP user is able to access the marketplace as member

3. Point expiry changes

Old expiry point API "ProcessExpiredPoints" is stopped and going forward "ProcessBulkExpiredPoints" would be used.
In quarterly expiry, expiry API had to be triggered only at the starting month of the quarter. Now that limitation is fixed Ex: For points expiring in jan-march month, expiry had to mandatorily triggered in April month. Now with the above fix, the API could be triggered in any month from april to june for the points expiring in Jan-march

4. OTP Length Configuration with config variable

New config "OTPLength" is added in the config. This takes value in the form of integer with range being 4-8.
If any value is set outside the range, OTP with default length (4) is sent. The OTP length configuration impacts following API’s. GenerateOTP and GenerateOTPByRelationReference along with OtpType": "LOGIN" and "OtpType": "ACTIVATION". Core OTP functionality remains same. OTP would be Encrypted and stored in DB. While sending the OTP via Email it would be decrypted and sent to end user If user resends the OTP via member section, old OTP would be sent and present configuration would be ignored

5. Automate Monthly Report Email for ABC Bank with Custom Fields

All transactions (Spend points, Tier bonus, campaign bonus, manual points, BNS file and BNS API ) with transaction_type=1 are considered as accruals and will be shown in the report
Report will be generated based on the program’s expiry schedule(i.e monthly or quarterly) In case of monthly, 1 year future expiry schedule in terms of months (i.e 12 months data)would be seen in the report In case of quarterly, 1 year future expiry schedule in terms of quarter(4 quarters data) would be seen in the report All members present in program irrespective of their status are included in the report Program id and recipient’s email address needs to be passed in the API and this API would be configured as cron based on the clients schedule. If this statement needs to be generated for multiple programs then multiple cron needs to be configured. Time taken to generate a report for 1 Million members was 10 minutes.

6. Showing Date Range Based Transaction History Selection in Self Serf Portal of the Worldia

In the transaction history last 5 transactions will be shown. Transactions can be searched based on Processing date.
If user wants to view more transactions, then user needs to navigate to “view all“ section which shows all the transactions of the members from his inception to the program. In this case the date range filter will not be applied by default. Now date range is provided for the user to filter transaction based on his requirement Additionally pagination and row per page is provided for seamless user experience With this ticket now pending transactions (Txn_type=5) will be shown in the member transaction summary section at Loyalife admin portal.

7. Allowing unique names while creating & editing a module

With this improvement, user can create programs with the same name. internal IDs for programs remain unique despite name duplication.
User can create multiple product entries with the same name but different product codes. User can create duplicate rule names within the same program. This is applicable for old and new programs

8. Redemption on Behalf Integration with Eastwest Bank storefront

User with edit platform configuration permission will be able to configure custom storefront URL. And once the storefront url is configured only then on behalf of redemption option will be seen in the member section Along with above permission user must have following permissions in member module “view member details“ , “view member“ and “on behalf of redemption” to redeem on-behalf of member. Also member status should be Active for the redemption on behalf option to be enabled. Audit trail is logged with the necessary information when user logs on behalf of member. On successful redemption if redemption event is configured, then confirmation mail is sent to member. Narration would be “Redemption GiftCard” for on behalf redemption The generation of logs when a user logs in on behalf of a member under "Member Activity" in the Audit Log within the Member section has not been implemented. This functionality needs to be implemented by the storefront team. A column(on behalf user) is added to reports, displaying the username of the user who made redemptions on behalf of members. A filter is present in transaction reports: "On behalf redemption" filter which will exclusively display data for redemptions made on behalf of members, while the existing "Debit by redemption" filter will display data for regular redemptions and redemptions made on behalf of members.

9. Implement Maker-Checker Process for Email Template Changes

Maker-checker is introduced for communication module
The user can send for approval for promotional, transactional and custom event and the user can verify/apparove the request. Existing maker checker permissions of campaign in enhanced to handle communication module requests as well. Maker checker pending mail captures pending actions for both campaign and communication requests

10. Implement Maker-Checker Workflow for Member Suspension Actions

New maker checker permission "verify suspension action" and "approve suspension action" is introduced to handle member's suspend flow
Now new module "Suspension actions" is included in the Program settings → Modules With the above flow only suspend and reactivate of member status who is suspended is handled via maker checker Member who is blocked and trying to reactivate will be immediate and will not go through maker checker process Audit trail captures checker-approver's action (approve/reject), timestamp, and user info. Maker checker pending mail captures pending actions for this module as well.

11. Maker-Checker for Business User Lock/Unlock, Archive/Unarchive

New maker checker permission "verify suspension action" and "approve suspension action" is introduced to handle Rbac user's lock/unlock and archive/unarchive flows
Now new module "Suspension actions" is included in the Program settings → Modules Earlier lock/unlock of user was handled via user access management maker checker process. With this improvement, user needs to use "Suspension actions" module for the same. Audit trail captures checker-approver's action (approve/reject), timestamp, and user info. Maker checker pending mail captures pending actions for this module as well.

12. Enhancing Segment Naming: Unique Names & Tag Field Removal

With this improvement, system does not allow duplicate segment names (case-insensitive). Attempting to create a segment with an existing name triggers an error.
Segment Tag field has been completely removed from the segment creation and in all other places where it was used as a means to select/identify segment. Segment ID which is a unique value across the segments are not displayed in the segment listing page Existing segments continue to function as expected and no change in the core functionality due to this change.

13. Building member PI data such as email, phone report download as config

New section "Advance Config setting" is introduced and is available only for the "Admin" user. He would be able to enable this setting at program level only once.
Once enabled PI data (email, phone number, custom PI attributes) are included in the Member Report Ensured only users with report creation permission can access and export PI data. No audit trail is present (as per current scope).

14. Providing Recurring Date-based Rules in Rule Engine

Introduced new date-based recurring rule attributes in Rule Engine such as Day of the Week, Month of the Year and Day of the Month
This is compatible with existing date logic and reward calculations. These new attributes are introduced only in rules and not in rule groups

15. Redefining the Report Setup Process

Now all report types allow entering a non-unique report name and description field is made non-mandatory.
Popup is provided on clicking report name which shows report name, description, selected columns, and applied filters. "Select All" and "clear All" option is available for Global Columns and Custom Columns across all report types. Selected columns are displayed in alphabetical order with a search option.

16. Add Compact Number Formatting Across Modules

New toggle “Enable Abbreviated Numbers” is introduced in the program settings → Points Definition → Point terminology & Rates
When user disable the Abbreviated Numbers toggle then the points are shown in the normal format without conversion When user enable the Abbreviated Numbers toggle then the points are shown in the abbreviated numbers such as K(Thousand), M(Million), and B(Billion) formats

17. Improving success logs for the SFTP files

Tooltip icon is shown beside each success log entry and hovering over the icon displays the correct number of rows processed
This message is only shown for logs with successful status. Download option in the action dropdown is introduced for all status(Successful, Failure and incomplete processing) using which user can download the logs. Download option is available only if the file exists on the server. If the log file has been deleted, clicking download shows an error toast