Loymax, 2026

Wiki source code of lmxR4 Release Version

Show last authors
1 (% class="lead" %)
2 This article describes improvements of the new version of the Loymax system.
3
4 (% class="box infomessage" %)
5 (((
6 **Note: **Descriptions of the changes in the System Version lmxR4 that were made to the Information portal after the publication of this article are marked with the tag **Updated**.
7 )))
8
9 Major changes in Version lmxR4 relate to optimizations, general system improvements, and bug fixes:
10
11 * [[list of optimizations>>doc:Main.General_information.Update_history.2022\.2.2022\.2_optimization.WebHome]] in System version lmxR4
12
13 {{showhide showmessage="Show content" hidemessage="Hide content"}}
14 {{toc/}}
15 {{/showhide}}
16
17 (% id="H41E43144943843543843743C43543D43543D43844F" %)
18 = **General changes** =
19
20 == **Stores **renamed to **Points of sale** ==
21
22 Now the ARM section [[Partners ~> List of stores>>doc:Main.Using.MMP.Admin_panel.Partners.Store_setting.WebHome]] renamed to **List of point of sale**.
23
24 The Loymax System is used not only by Partners who own stores, but also, for example, pharmacies or other retail outlets. In points of sale (or a network of retail outlets) Partners' customers purchase goods and services using the Loyalty Program.
25
26 Points of sale may include:
27
28 * grocery stores,
29 * specialty stores,
30 * boutiques,
31 * pharmacies,
32 * supermarkets,
33 * hypermarkets,
34 * cafes, etc.
35
36 In all related sections  of the System **Stores** also renamed to **Points of sale**. For example, the filter [[Stores>>doc:Main.Using.MMP.Marketing.Offers.Filters.Other.Merchants.WebHome]], which is used when creating offers, since Version lmxR4 is called **Points of sale**.
37
38 |(% style="border-color:white" %) |(% style="border-color:white" %)(((
39 == Increased time period for which the LP Member will see the date of expiring bonuses in the Personal Account ==
40
41 Exact [[bonus expiry date>>doc:Main.Using.MMP.Marketing.Bonuses_life_time.WebHome]] in the Personal Account of the LP Member is now displayed six weeks before the expiry date, and not one week as it was before. For example, if two bonus amounts with a validity period of 5 days and 1 month are credited to the LP Member on 04.05.2022, then the Personal Account will display the exact expiry dates of both amounts — 09.05.2022 and 04.06.2022, for the first and second bonus amounts, respectively.
42 )))
43 |(% colspan="2" style="border-color:white" %)(((
44 (((
45 == Opportunity for Customers without linked cards to manage their bonus account ==
46
47 Members registered in the LP without linking a physical card and without issuing a virtual card now have an opportunity to make purchases, accumulate and withdraw bonuses and manage their bonus account.
48
49 In order to realize such a case, when no cards are bound to a LP Member during registration, certain values should be set in the configuration settings. With some settings a bonus card can be bound/issued later, after registration.
50
51 It should be remembered that in case when as a result of customer's registration in the LP no physical card is linked and no virtual card is issued, the only way to identify the customer at the cash register will be the phone number.
52
53 == Product groups search is performed by incomplete name match ==
54
55 If you set up the [[Dividing into sets>>doc:Main.Using.MMP.Marketing.Offers.Action_catalog.Sets_creation.WebHome]] in offers, as well as in the filters [[Product>>doc:Main.Using.MMP.Marketing.Offers.Filters.Cheque.Goods.WebHome]], [[Product availability in the receipt>>doc:Main.Using.MMP.Marketing.Offers.Filters.Cheque.Presence_of_the_product_in_the_cheque.WebHome]], [[Limitation on product>>doc:Main.Using.MMP.Marketing.Offers.Filters.Cheque.Goods_limit.WebHome]] (simple and with a counter), you can search for a group of goods if the name entered in the filter does not match the name of an existing group of goods. The filter works in the same way when searching in the [[Product groups>>doc:Main.Using.MMP.Marketing.Goods_groups.WebHome]] and** Personal Products** sections of the MMP, as well as when searching for [[Favorite Products in Call Center>>doc:Main.Using.Contact_center.Typical_processes.Favorite_goods_viewing.WebHome]].
56 )))
57
58 (((
59 == Use of any cash register identifier when referring to methods that support basic purchase-related transactions ==
60
61 When [[authorizing>>doc:Main.Integration.Ways_to_use_API.Authorization_Service.OAuth_authorization.WebHome]] through an OAuth application, you can pass the **X-Identifier** and **redirect **fields in the request, which are used only when referring to methods of the [[Processing Public API>>doc:Main.Integration.Ways_to_use_API.API_methods.Methods_of_public_api.Processing.WebHome]] .
62
63 (((
64 == Interface improvements ==
65
66 |(% colspan="2" style="border-color:white" %)(((
67 === Informing about the current loading process ===
68
69 Now all modal windows that allow you to import files now display the **Import **label when a file is being uploaded for a long time, which disappears after the file has been processed and uploaded.
70 )))
71 |(% colspan="2" style="border-color:white" %)(((
72 == Improved phone number input format ==
73
74 (((
75 In the CRM and Call Center sections, the phone number entry window has changed when searching for customers. Now a template for entering the number set in the System is displayed and the possibility to select a template, if several are provided.
76 )))
77 )))
78
79 |(% style="border-color:white; width:339px" %)(((
80 === __Updated__: The ability to unsubscribe from all types of subscriptions at once was added ===
81
82 In the **Call Center > [[Subscriptions>>doc:Main.Using.Contact_center.Typical_processes.Subscription_management.WebHome]]** and **Customer Profile > [[Subscriptions>>doc:Main.Using.MMP.CRM.Clients.Customer_profile.Subscriptions.WebHome]]** sections, the **Disable All** button has been added to unsubscribe a customer from all mailings at once or **Select All** to subscribe to all types of mailings. Also the ability to add/remove all subscriptions within specific communication channels was added. To do this, you should check/uncheck the checkbox directly under the name of the corresponding communication channel.
83 )))
84
85 == Plugins removed ==
86
87 The following plugins were removed from the System:
88
89 * Loymax.SmsTrafficIncomingSmsProcessor,
90 * Loymax.Plugins.PurchaseImitator,
91 * Loymax.Plugins.SocialNetworks.Devino,
92 * Loymax.Plugins.StatusSystem и StatusSystem.ManualChanges,
93 * Loymax.Plugins.SftpStatusUpload.
94 )))
95 )))
96 )))
97
98 = **CRM** =
99
100 == New in the section **Purchase Management** ==
101
102 When viewing information about purchases registered in the System, it is no longer the number of the LP Member card that is displayed, but the one [[id>>doc:Main.Using.MMP.CRM.Clients.Customer_profile.Identifiers.WebHome]], which was used in the purchase to identify the customer at the cash register. In the section [[Purchase Management>>doc:Main.Using.MMP.CRM.Purchases_management.WebHome]] using a filter by this identifier, you can find purchases in the System for further management.
103
104 The identifier used in the purchase is also displayed in the **Purchase history** of the customer** **in [[Contact Center>>doc:Main.Using.Contact_center.Typical_processes.Purchase_history.WebHome]] and in the customer card in ** **[[CRM>>doc:Main.Using.MMP.CRM.Clients.Customer_profile.Purchase_history.WebHome]].
105
106 = **Marketing** =
107
108 == New in the **Offers** section ==
109
110 === Specifying the logical name of the receipt item parameter that determines the product minimum price range ===
111
112 In the [[Setting the minimum price>>Setting the minimum price]] action, a new calculation method is available that allows you to specify the value of the receipt item parameter that determines the product MRC. Now there is no need to load the MRC in the catalog, because the action will work even when the cash register itself transmits the MRC value.
113
114 === Possibility to quickly select the attribute value in the Points of Sale Filter ===
115
116 A substring is available for searching by the name of a specific attribute in the [[Points of sale>>Points of sale]] filter (previously **Stores**).
117
118 |(% style="border-color:white; text-align:left; width:10%" %)(((
119 === __Updated__: Reading the QR code as a bonus card identifier ===
120
121 Now filters from the group [[Card>>doc:Main.Using.MMP.Marketing.Offers.Filters.Card.WebHome]] are triggered upon presentation of a QR code as [[bonus card identifier>>doc:Main.General_information.Loymax_Loyalty.Bonus_card.Bonus_card_identifiers.WebHome]].
122
123 === __Updated__: Setting the minimum price of the product from the additional parameters of the receipt position ===
124
125 In action [[Setting the minimum price>>doc:Main.Using.MMP.Marketing.Offers.Action_catalog.Minimum_price_setting.WebHome]] a method for calculating **The value of the check item parameter** was added, with which you can set the logical name [[of the receipt position additional parameter>>doc:Main.Integration.Cash_register_integration.Integration_methods.Exchange_protocol_with_cash_register.Additional_params.Additional_params_of_cheque_position.WebHome]] from the cash request, which will be used as a restriction of the minimum price of the product.
126 )))
127
128 == New in the **Counters** section ==
129
130 |(% style="border-color:white; width:25%" %)(((
131 === __Updated__: Creating counters for **Coalition Loyalty Programs** ===
132
133 When [[creating counters>>doc:Main.Using.MMP.Marketing.Counters.Counter_creation.WebHome||anchor="H42143E43743443043D43843544144743544244743843A430"]]it is now possible to select several Partners at once, to whom the counter will be available. Such counters can be used in offers that will be available to several Partners at once within the framework of [[coalition Loyalty Program>>doc:Main.General_information.Loymax_Loyalty.Coalition_loyalty_programs.WebHome]].
134
135 For example, such counters can be used when [[creating offers with a common product catalog>>creating offers with a common product catalog]].
136
137 == New in the **Status Systems** section ==
138
139 There are new fields in the window of editing additional [[status>>status]] parameters that allow you to add a more detailed description of the status itself, as well as information about preferences available for the current status. For example, you can specify in a separate line the type of preference (discount or bonuses, fixed amount or percentage of purchase), and in another line specify a numeric value.
140
141 These fields are necessary for displaying information in customer services. You can also change these fields via API methods.
142 )))
143
144 = **Admin Panel** =
145
146 == New in the **Users** section ==
147
148 |(% style="border-color:white" %)(((
149 === Filtering by **user status** ===
150
151 To simplify the search for users who are deleted or active, a filter by user status has been added. Now on the main page with [[users>>path:/xwiki/bin/view/Main/Using/MMP/Admin_panel/MMP_users/]] you can display:
152
153 * all users,
154 * only active,
155 * only deleted ones.
156 )))
157
158 == New in the section **Card issue** ==
159
160 |(% style="border-color:white" %)(((
161 === The logic of creating issuing cards and activating them has been optimized. Section **The issue of booklets** and the field ** of card activation **were deleted ===
162
163 Prior to version lmxR4 when creating [[card issue>>doc:Main.Using.MMP.Admin_panel.Cards_issue.WebHome]] with the passwords from the booklet, it was necessary to attach a password to each issued card to activate it. Without this password, the customer would not be able to activate the card. And when issuing a card without a password, it was necessary to select the option ** Without a password from the booklet** in the **Activation ** field.
164
165 Now, when creating a card issue, the **Activation ** field is missing. This field was an irrelevant functionality, because passwords were needed only when the card was activated for the first time, and if the card had (% style="background-color:transparent" %) a CVC code, the code itself also had to be used to activate the card, which was a duplicate functionality. Therefore, since version lmxR4, it is possible to generate only CVC codes when creating a card issue.
166
167 Since there is no need to issue booklets with passwords for cards, the section [[Issue of booklets>>doc:Main.Using.MMP.Admin_panel.Booklet_issue.WebHome]] has also been removed from version lmxR4.
168 )))
169
170 == __Updated__: New section **Additional attributes for entities** ==
171
172 |(% style="border-color:white; width:25%" %)(((
173 The section [[Additional attributes for entities>>doc:Main.Using.MMP.Admin_panel.Additional_Entity_Attributes.WebHome]] was added, with which you can create and edit additional attributes for:
174
175 * [[Offers>>path:/xwiki/bin/view/Main/Using/MMP/Marketing/Offers/General_information/Offers_life_cycle/Creating_offers/#H41443E43143043243B43543D43843543044244043843144344243E43243443B44F43043A446438439]],
176 * [[Product groups>>path:/xwiki/bin/view/Main/Using/MMP/Marketing/Goods_groups/Goods_group_creating/]],
177 * [[Marketing campaign>>path:/xwiki/bin/view/Main/Using/MMP/Marketing/Marketing_campaigns/Creating_a_marketing_campaign_and_actions_with_it/#H41443E43143043243B43543D43843543044244043843144344243E43243443B44F43C43044043A43544243843D43343E43244B44543A43043C43F43043D438439]],
178 * [[Target audience>>path:/xwiki/bin/view/Main/Using/MMP/CRM/Target_groups/Creating_and_editing_of_target_groups/#H41443E43143043243B43543D43843543044244043843144344243E43243443B44F44643543B43543244B44543044343443844243E440438439]],
179 * [[Mailings>>path:/xwiki/bin/view/Main/Using/MMP/Communications/Mailings/Mailing_creating/]].
180
181 Each entity has its own list of additional attributes. Additional attributes are used when compiling analytical reports in the module [[Loymax BI>>path:/xwiki/bin/view/Main/General_information/BI/]].
182
183 == New filter **Cash Register Type** in the **List of Cash Registers** tab ==
184
185 Since the System version lmxR4, a new filter Cash Register Type has been added to the [[Cash Register List>>Cash Register List]] tab in the Edit Partner section, which searches for cash register types provided in the System.
186
187 == __Updated__: New field in the **Attribute Creating** window ==
188
189 In the [[Attribute Creation>>Attribute Creation]] window, there is a new field **Order Number**, which specifies the order number of the attributes displayed in the [[Advanced Customer Search>>Advanced Customer Search]].
190 )))
191
192 = **Settings** =
193
194 == **__Updated:__ **New in the **Configurations section** ==
195
196 * [[Configuration parameters>>doc:Sandbox.Internal_settings.WebHome||anchor="Sessions"]] were added responsible for creating [[sessions for Marketing management platform (MMP) users>>doc:Main.Installation_and_configuration.System_configuration.Internal_settings.User_Sessions.WebHome]]. To configure these configurations, go to the [[System Setup~> Configurations>>doc:Sandbox.Internal_settings.WebHome]].
197 * [[Configuration>>https://docs.loymax.net/xwiki/bin/view/Main/Installation_and_configuration/System_configuration/Internal_settings/#IdentifierIsRequired]] responsible for mandatory transmission of the [[Customer identifier>>https://docs.loymax.net/xwiki/bin/view/Main/Using/MMP/Configurations/Cash_identifiers/]] in the cash request for Direct Discount Calculation has been added. The configuration is set up in the [[System Setup~> Configurations>>doc:Sandbox.Internal_settings.WebHome]] section.
198 * [[Configuration>>https://docs.loymax.net/xwiki/bin/view/Main/Installation_and_configuration/System_configuration/Internal_settings/#TargetGroups]] responsible for the maximum allowable number of target audiences involved in the calculation of the offer was added.
199
200 === New in the section **Regular tasks** ===
201
202 === Regular task to clean up calculations of Target Audiences ===
203
204 Data on all Target Audience calculations are stored in the database. To reduce the amount of stored information and increase the System performance [[this regular task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Regular_Task_Setting_on_Target_Audience_Calculation_Clearing.WebHome]] leaves data on the last Target Audience calculation only and deletes data on all previous calculations. Configuration of the regular task is not required, as it is configured in the default MMP in the [[System Setup ~> Regular Tasks>>https://docs.loymax.net/xwiki/bin/view/Main/Using/MMP/Configurations/Regular_tasks/]] section.
205
206 = **Changes in API methods** =
207
208 == **New API methods** ==
209
210 * There is a [[method that allows you to transfer created coupons to the state **In the queue for issuance**>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.CouponEmission.WebHome||anchor="H41F43544043543243E43443844244143E43743443043D43D44B43543A44343F43E43D44B43244143E44144243E44F43D4384352241243E44743544043543443843D43043244B4344304474432243843243E43743244043044943043544243D43E43C43544043043A44343F43E43D43E432"]] , and also allows you to get a list of coupon numbers that have changed states;
211 * In the [[group of methods for working with entity attributes>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome]] the following methods have appeared:
212 ** The method that [[archives the entity attribute>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome||anchor="H410440445438432438440443435442A0430442440438431443442A044144344943D43E441442438"]];
213 ** A method that [[restores an entity attribute from the archive>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome||anchor="H41243E44144144243043D43043243B43843243043544243843743044044543843243043044244043843144344244144344943D43E441442438"]];
214 ** Method for [[updating the name of an entity attribute>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome||anchor="H41E43143D43E43243B44F43544243D43043743243043D438435430442440438431443442430A043843543343E43E43F43844143043D438435"]];
215 * There is a new group of [[methods for working with client attributes through the OAuth application>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Customers.WebHome]];
216 * There is a new [[method that binds coupons to LP Members>>method that binds coupons to LP Members]];
217 * There is a new [[method that returns information about the batch merging of clients, which ended with errors, in the form of a CSV file >>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.CustomerBatchLink.WebHome||anchor="04"]].
218 * **__Updated__**: In the group of methods for working with the Call Center, a new [[method that allows you to cancel the client registration that has begun>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.CallCenter.WebHome||anchor="15"]]. If the registration process has been started but has not yet been completed, the Call Center operator can cancel the registration through the customer's card using the button[[ Cancellation of registration>>doc:Main.Using.Contact_center.Typical_processes.pending_registration_cancellation.WebHome]].
219
220 == **Changes to existing API methods** ==
221
222 * In [[methods for working with clients>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Customers.WebHome]] the following changes have occurred:
223 ** A new method has been introduced that [[returns a list of attribute values by the customer's card or phone number>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Customers.WebHome||anchor="H41243E43743244043044943043544244143F43844143E43A43743D43044743543D43843943044244043843144344243E43243F43E43D43E43C43544044343A43044044244B43843B43844243543B43544443E43D43043A43B43843543D442430"]];
224 ** There is a new method that [[returns the attribute value by the customer's card or phone number>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Customers.WebHome||anchor="H41243E43743244043044943043544243743D43044743543D43843543044244043843144344243043F43E43D43E43C43544044343A43044044244B43843B43844243543B43544443E43D43043A43B43843543D442430"]];
225 ** There is a new method that [[checks the phone number verification code>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Customers.WebHome||anchor="H41F44043E43243544044F43544243A43E43443F43E43444243243544043643443543D43844F43D43E43C43544043044243543B43544443E43D430"]]**;**
226 * The response models in [[methods that return information about client statuses>>doc:Main have changed.Integration.Ways_to_use_API.API_methods.Methods_of_public_api.User.Status.WebHome||anchor="04"]];
227 * In [[methods for working with entity attributes>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome]] the following changes have occurred:
228 ** In  [[the method for attribute creating>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome||anchor="H41443E43143043243B44F435442430442440438431443442A043AA044243843F443A044144344943D43E441442438"]], the list of transmitted parameters was expanded;
229 ** In [[the method that returns all attribute values of the entity type>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome||anchor="H41243E43743244043044943043544243743D43044743543D43844F43044244043843144344243E43244144344943D43E441442438"]], the list of transmitted parameters was expanded;
230 ** In the [[method for updating the value of an entity attribute, a request model has appeared >>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome||anchor="H41E43143D43E43243B44F43544243743D43044743543D43843543044244043843144344243044144344943D43E441442438"]] , in which the JSON model with the new attribute value is passed;
231 * In the [[method for uploading a file with a list of product codes>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.GoodsGroup.The WebHome]] contained in the product group one can now use both internal and external product group identifiers.
Created 2024/01/24 05:22
Last edited 2025/09/03 04:37

News
Updates
Tag cloud
Glossary
Site