Version 2022.2

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 2022.2 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 2022.2 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 2022.2

12

13

{{showhide showmessage="Show content" hidemessage="Hide content"}}

(% 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:

* grocery stores,

* specialty stores,

* boutiques,

* pharmacies,

* supermarkets,

* hypermarkets,

* cafes, etc.

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 2022.2 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 client'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]].

)))

(((

== 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 clients. Now a template for entering the number set in the System is displayed and the possibility to select a template, if several are provided.

)))

)))

|(% 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.

)))

)))

)))

= **CRM** =

== 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]].

= **Marketing** =

== 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>>https://docs.loymax.net/xwiki/bin/view/Main/Using/MMP/Marketing/Offers/Action_catalog/Minimum_price_setting/]] 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>>https://docs.loymax.net/xwiki/bin/view/Main/Using/MMP/Marketing/Offers/Filters/Other/Merchants/]] 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 offeras that will be available to several Partners at once within the framework of [[coalition Loyalty Program>>https://docs.loymax.net/xwiki/bin/view/Main/General_information/Loymax_Loyalty/Loyalty_Programs/]].

134

135

For example, such counters can be used when [[creating offers with a common product catalog>>https://docs.loymax.net/xwiki/bin/view/Main/Using/MMP/Marketing/Offers/General_information/Offers_life_cycle/4.Creating_offers_general_catalog/]].

)))

= **Admin Panel** =

== New in the **Users** section ==

141

142

|(% style="border-color:white" %)(((

143

=== Filtering by **user status** ===

144

145

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:

* all users,

* only active,

* only deleted ones.

)))

== New in the section **Card issue** ==

153

154

|(% style="border-color:white" %)(((

155

=== 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 ===

156

157

Prior to version 2022.2 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 client 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.

158

159

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 2022.2, it is possible to generate only CVC codes when creating a card issue.

160

161

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 2022.2.

)))

== __Updated__: New section **Additional attributes for entities** ==

167

168

|(% style="border-color:white; width:25%" %)(((

169

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:

170

171

* [[Offers>>path:/xwiki/bin/view/Main/Using/MMP/Marketing/Offers/General_information/Offers_life_cycle/Creating_offers/#H41443E43143043243B43543D43843543044244043843144344243E43243443B44F43043A446438439]],

172

* [[Product groups>>path:/xwiki/bin/view/Main/Using/MMP/Marketing/Goods_groups/Goods_group_creating/]],

173

* [[Marketing campaign>>path:/xwiki/bin/view/Main/Using/MMP/Marketing/Marketing_campaigns/Creating_a_marketing_campaign_and_actions_with_it/#H41443E43143043243B43543D43843543044244043843144344243E43243443B44F43C43044043A43544243843D43343E43244B44543A43043C43F43043D438439]],

174

* [[Target audience>>path:/xwiki/bin/view/Main/Using/MMP/CRM/Target_groups/Creating_and_editing_of_target_groups/#H41443E43143043243B43543D43843543044244043843144344243E43243443B44F44643543B43543244B44543044343443844243E440438439]],

175

* [[Mailings>>path:/xwiki/bin/view/Main/Using/MMP/Communications/Mailings/Mailing_creating/]].

176

177

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/]].

)))

= **Settings** =

== **__Updated:__ **New in the **Configurations section** ==

183

184

[[Configuration parameters>>doc:Main.Installation_and_configuration.System_configuration.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:Main.Installation_and_configuration.System_configuration.Internal_settings.WebHome]].

185

186

=== New in the section **Regular tasks** ===

187

188

=== Regular task to clean up calculations of Target audiences ===

189

190

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]].

191

192

= **__Updated:__** **Changes in API methods** =

193

194

* 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.WebHome]] contained in the product group one can now use both internal and external product group identifiers.

195

* __Updated:__ [[Method>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.CouponEmission.WebHome||anchor="H41F43544043543243E43443844244143E43743443043D43D44B43543A44343F43E43D44B43244143E44144243E44F43D4384352241243E44743544043543443843D43043244B4344304474432243843243E43743244043044943043544243D43E43C43544043043A44343F43E43D43E432"]] appeared, which allows you to transfer the created coupons to the "In the queue for issuance" state, as well as return a list of coupon numbers whose states have changed.

196

* __Updated:__ 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:

197

** In [[method for creating attribute>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome||anchor="H41443E43143043243B44F435442430442440438431443442A043AA044243843F443A044144344943D43E441442438"]], the request model has changed for the selected entity type. Now the name of the attribute, its description and status are also passed in the request;

198

** In [[a 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 expanded;

199

** 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;

200

** There is a new method that [[archives the entity attribute>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Attributes.WebHome||anchor="H410440445438432438440443435442A0430442440438431443442A044144344943D43E441442438"]];

201

** There is a new 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"]];

202

** There is a new 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"]].

203

* __Updated:__ There is a new group of [[methods for working with Customer attributes via an OAuth application>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.Customers.WebHome]].

204

* __Updated:__ There is a new [[method that binds coupons to LP Members>>doc:Main.Integration.Ways_to_use_API.System_Api_Methods.Methods_of_system_api.CouponOperation.WebHome||anchor="02"]].

Navigation

Wiki source code of Version 2022.2