2.7.0 (10.11.2024)— added the ability to create tasks in amoCRM
— improved English language support
- other minor edits
2.6.2 (25.10.2024)— products from amo are now synchronized by ID and price. When changing the price of a product in the store, a new product will be created in amo.
— the obsolete settings "Price type for products in the order created from the deal" and "Price type for new products in the cart" have been removed. For more stable operation, the products updated from AMO in the cart will be assigned a custom price flag
— added support for custom amo field "birthday"
- removed some methods that were marked as deprecated for a long time
2.6.1 (04.10.2024)— added transfer of balances by warehouses for goods
- additional security checks added
— PHP 7.4 and 8.0 support discontinued. Minimum supported version is 8.1
— added additional checks when replacing placeholders
2.6.0 (20.09.2024)— в профиль интерации заказо добавлено новое поле «Состав заказа (со ссылками на товары)»
— добавлена возможноть выгружать только корзины авторизованных пользователей (с ФИО покупателя)
— добавлены дополнительные проверки безопасности
— улучшен перевод на английский язык
2.5.4 (26.08.2024)— исправлены мелкие ошибки и неточности
— повышена стабильность работы модуля
2.5.3 (26.07.2024)— mapping of fields of statistics systems for transactions has been restored
— fixed an inaccuracy due to which the order domain could be incorrectly determined under certain server settings
2.5.2 (12.06.2024)— added reverse synchronization of custom fields for deals, contacts and companies with order properties
— settings for order and cart integration profiles have been regrouped
- fixed the error "Argument 'EDIT_FORM_LABEL' is null or empty" that sometimes occurred during installation
- fixed a bug due to which not all fields were transferred to AMO
2.5.0 (07.06.2024)— added reverse synchronization of custom fields for deals, contacts and companies with order properties
— settings for order and cart integration profiles have been regrouped
- fixed the error "Argument 'EDIT_FORM_LABEL' is null or empty" that sometimes occurred during installation
1.1.2 (25.02.2021)— added the ability to transfer products as entities when creating and updating an order
— passing the location name instead of the code in the order property of the "Location" type
— fixes for sites in single-byte encodings (windows-1251, etc.)
- found errors have been fixed
1.2.1 (26.03.2021)— added support for tag fields of statistics systems in AMO (tracking_data)
— added the ability to edit the list of available statistics system tags from the admin panel
— the list of statistical system tags available by default has been expanded
— added the ability to use placeholders for your own values in the field mapping
- reworked adding integration profiles
— the integration profile settings interface has been redesigned, settings are grouped by actions
— when creating an order, the ability to add visitor_uid to the transaction has been added. This allows you to track the visitor in auto funnels. https://www.amocrm.ru/developers/content/digital_pipeline/site_visit
- fixed a bug due to which sometimes duplicate products in a deal could occur when updating an order
- other found errors have been fixed
- updated SDK for communication with amoCRM
1.2.3 (02.04.2021)— added search for duplicates.
— improved compatibility with older versions of the Main Module
— fields added to mapping: cost without delivery, delivery cost, currency, name of payment system, name of delivery service
— added default values for the deal in the new integration profile: name, budget, order contents and user comment
— the “List of Responsible” field in the profile has been made optional. If it is not filled in, the responsible person from the amo is set by default
- bugs fixed
1.3.5 (07.04.2021)— added synchronization of the store catalog with amoSRM products
- added full export of the entire catalog to amoSRM
— added groups of custom fields in the integration profile
- added agent restart button
- fixed removal of tags from text fields
- fixed errors and inaccuracies when synchronizing by status
- other bugs fixed
- refactoring
1.3.7 (15.04.2021)— added correct transfer of order properties of the "List" and "File" types
— added an additional field "Delivery city". It only shows the city, without the country or region.
- added default statistics labels when creating an integration profile
— the “amoCRM related entities” setting in the integration profile has been made optional. If it is not filled in, a warning will be displayed
— the “Sites” and “Types of Payers” settings are made optional. If they are not selected, then the profile applies to all sites or all payer types, respectively
- fixed unloading of product property names
- fixed transmission of statistics labels
- fixed duplication of transactions when updating an order
- fixed synchronization of deal and order statuses
1.3.8 (16.04.2021)— mapping of catalog product fields is now applied to products from the cart
— statistics tags are now added only when creating a new order and are no longer updated
— added system events beforeFindEventProfiles and afterFindEventProfiles allowing you to customize the search for suitable integration profiles when processing an event
— a new field has been added to the mapping of order fields: link to order
— found errors in exporting products from the catalog have been fixed
— names of product fields in mapping have been restored
- refactoring
1.4.1 (26.04.2021)— added bulk unloading of orders
— properties of elements such as string, number, list and directory have been added to product mapping
— added synchronization of statuses when massively changing transaction statuses in Amo
- optimized processing of online store and AMO events
— fixed synchronization of order properties of the “multilist” type with a custom AMO field of the same type
- fixed an error in mapping product fields if there is more than one catalog
- fixed a bug due to which goods without trade offers were not transferred
— synchronization between order and transaction statuses has been fixed.
1.4.3 (06.05.2021)— added a filter of orders by status. Now in Amo you can create a deal when a store order reaches a certain status
— added a form for viewing integration profile orders
- added support for describing property values (DESCRIPTION field) for amo products
— fixed the possibility of disabling products and visitor_uid for a transaction
— work has been optimized with a large number of properties added to the product name from the sales offer
- fixed a bug when passing values of multiple properties to amo products
— other minor improvements and corrections
1.4.4 (19.05.2021)— added ajax uploading of all orders and products, without agents
- added re-processing of all successful/error events via ajax, without agents
— added default values for product mapping
- refactoring
1.4.8 (15.07.2021)— the limit of 50 custom fields for an entity has been removed
— bulk export and filter have been added to the profile order viewing page
- added product update in Amo when updating price in the store
— added the ability to disable section updates when updating a product
- fixed price processing if there are extraneous characters
- fixed the work of bread crumbs in the admin panel
- minor bugs fixed
1.5.1 (17.08.2021)— added support for customers and purchases. The buyer is tied to the site user, the purchase is tied to the order
- added additional order field “buyer name”, which contains the name of the Bitrix user who placed the order
- added auto-cleaning of the event table
— the number of retries for processing erroneous events is limited to three
— the interface for working with the list of orders has been restored for a new installation
- other found errors have been fixed
1.5.2 (27.08.2021)— added custom order fields: “order source”, “shipment ID”, “shipment document number”, “shipment document date”
— flags “paid”, “shipped”, “canceled”, “problem with order”, “external order” have been added to status mapping
— added beforeAddComplex and afterAddComplex events, allowing you to modify data when adding a deal in the duplicate search mode
— added beforeSaveAmoEntity and afterSaveAmoEntity events, allowing you to modify data when adding/updating an entity if the duplicate search mode is disabled
- fixed change in transaction budget when attaching goods to it
— other minor errors and shortcomings found were fixed
1.5.3 (16.01.2022)- added transfer of discount coupon and applied discounts
— when creating a new integration profile, deal and contact creation, as well as order creation/update processing are enabled by default
— fixed a bug due to which numerical labels of statistics systems were not transmitted
— fixed a bug due to which orders were not exported if products were disabled in Amo
— fixed a bug due to which manual event processing might not work
— updated SDK for communication with AmoCRM
1.5.4 (18.01.2022)— the ability to add your own fields for transfer to AMO. More details in the documentation https://rover-it.me/knowledge/course/course3/lesson129/
1.5.5 (21.02.2022)— added the ability to delete an order when deleting the corresponding transaction
— fixed event counters in operation/new/frozen/erroneous
— the sdk version for communication with amoCRM has been increased to 0.7.2
1.5.9 (11.05.2022)— added the ability to search when adding fields in mapping, as well as in the order filter and list of responsible persons
— the fields in the mapping have been regrouped: the groups “Order”, “Delivery”, “Payment” have been added. Removed - "Additional order fields" and "Order fields"
— many new fields for delivery and payment have been added to the mapping
— added support for the "Address" field of amoSRM
- expanded error messages
- updated default values when creating a new profile
— in the integration profile settings, the “Order Filter” section has been moved to the “General Parameters” tab
- improved work in windows-1251 encoding
- found errors have been fixed
- refactoring
1.5.11 (12.07.2022)— fixed a bug when processing custom fields
- fixed order cutoff
- fixed errors that sometimes occurred during installation
1.6.0 (08.09.2022)— Added synchronization by flags and statuses of the first shipment
- fixed synchronization by order flags
- refactoring
1.6.7 (03.10.2022)— added management of access rights to the module
- fixed errors that sometimes occurred during installation and uninstallation
— errors in synchronization of shipping flags have been fixed
- other bugs fixed
- refactoring
1.7.3 (24.10.2022)— added synchronization of goods amoSRM -> store
- refactoring
— correction of minor errors and inaccuracies
1.7.4 (08.11.2022)— new events have been added for the creation of amo entities from the site side (see documentation https://rover-it.me/knowledge/course/course3/chapter096/)
— added support for custom fields of the “File” type (you can attach files that already exist in amoCRM by uuid)
— when passing the fields “Picture for announcement”, “Detailed picture” and properties of the “file” type, a link to the file is now transmitted
— when passing to a custom field of the “link” type, the first link from the passed value is now taken as the value
- updated version of sdk communication with amocrm to 0.12.3
- found errors have been fixed
1.7.5 (09.11.2022)— added the ability to transfer fields and properties of trade offers to products
— in the fields and properties of elements, values from the elements are now transmitted (and not from offers, if the product was an offer). In this way, you can, for example, configure the transfer of images to a product from the offer, and descriptions from the main element.
1.7.7 (06.12.2022)— added the ability to edit and delete connections in the list
— access rights have been expanded: added reading and editing only integration profiles and connections
- found errors have been fixed
1.7.8 (27.12.2022)— for better compatibility, added the ability to disable additional js scripts
- refactoring
1.7.13 (22.02.2023)— found compatibility errors with php 8 and php 8.1 have been fixed
- other found errors have been fixed
- refactoring
1.7.14 (03.03.2023)— found compatibility errors with php 8 and php 8.1 have been fixed
1.8.1 (22.05.2023)— added support for custom order fields (mainly used in SRM)
— the structure of the left menu has been expanded
— minor changes in the structure of the integration profile settings
- updated dependencies
— specifying one site when creating an integration profile has been made mandatory. Old profiles will still work, but when updating them you will also need to specify at least one site.
— the “Control duplicates” checkbox has been removed from the integration profile settings, because this feature has been disabled by amoSRM for third-party integrations
— fixed a bug where the deal status was not updated when updating an order if updating the deal fields was turned off.
- other found errors have been fixed
1.8.4 (09.06.2023)TECHNICAL UPDATE necessary to continue development of the module. READ THE DESCRIPTION.
After this update, integration profiles will remain associated with only one site:
If the profile on the "General Settings" tab in the "Order Filter" section was linked to only one site, then nothing will happen to it.
If you were linked to several sites, then duplicate profiles will be created for each of these sites
If there was no binding to sites at all, then duplicate profiles will be created for EVERY core site.
Therefore, before installing this update, in order to avoid the appearance of a large number of duplicates, it is RECOMMENDED to leave the integration profiles with bindings only to the necessary sites.
1.8.5 (13.06.2023)Integration profiles were divided into order integration profiles and product integration profiles (more details in the documentation on the website https://rover-it.me/):
— Settings for synchronization, export and mapping of product fields have been moved to product integration profiles.
— Previous integration profiles are now only responsible for orders.
— After the update, product integration profiles will be automatically created based on existing integration profiles; no additional actions are required.
1.8.9 (28.06.2023)— fixed a bug due to which, when exporting orders in bulk, transactions were created with the same name (and other field values could be duplicated
— other found errors and inaccuracies have been corrected
- refactoring
1.8.10 (30.06.2023)- fixed compatibility error in Bitrix core version 23.300.100 and higher
- other found errors have been fixed
- updated dependencies
1.8.13 (05.07.2023)- fixed a bug when creating an order integration profile
- fixed error when saving integration profiles
- installation errors fixed
2.0.2 (25.08.2023)— Added integration with abandoned carts
— Added a list of integration profile baskets with the possibility of full or partial export to amoSRM
— Redesigned order profile settings
— The ability to download all orders has been moved from the integration profile settings to the list of orders (a checkbox “for all” has been added)
— Added weight transfer for ordering
— Removed some methods that had long been marked as obsolete
- Fixed found errors
— Improved module stability
2.1.2 (29.08.2023)— Added synchronization of goods from a transaction with a forgotten cart
— Fixed a bug that could cause the export of forgotten carts to get stuck in a loop
— Fixed a bug due to which the correct transaction status might not be set when exporting orders
— Fixed other found errors and inaccuracies
— Improved English language support
2.1.5 (07.09.2023)— Added calculation of discounts when updating the basket from Amo
— when adding a product with a discount (through an order or cart), a new product will be created in the AMO catalog, rather than updating the existing one
— The Highload block "AmoSale: Carts" has been removed, because KGO functionality was moved to the Highload block "AmoSale: Communications"
— Improved English language support
— Installation errors fixed
— Fixed other found errors
2.2.1 (15.09.2023)— Added control of duplicates from the module side (requires connection to a paid filtering API from amoCRM)
— Added transfer of different types of prices for goods
— Added the ability to specify the type of price from which products from AMO will be added to the order/cart
— Improved English language support
— Fixed a bug if a value from a multiple property was passed to a product group
— Fixed a bug due to which products might not be uploaded to Amo when creating/updating a product in the site catalog
- Fixed an error that sometimes occurred during installation
2.2.5 (25.09.2023)— added the "Update responsible user of the duplicate" setting
— added assignment of a person responsible for a transaction from a found duplicate contact/company
— added transfer of the name of the main section for products
— fixed a bug due to which, when updating duplicates, custom fields that were not in the original were overwritten
— fixed an error that occurred when searching for duplicate deals with an active filter by status
- found errors and inaccuracies have been corrected
2.2.7 (13.10.2023)— Fixed compatibility error in main module version 23.600.0 and higher
— Fixed an error that occurred if the creator of the duplicate was no longer in the amoSRM account
— Fixed a bug due to which the person responsible from the duplicate might not be forwarded
- fixed an error that sometimes occurred during installation
— improved English language support
- minor errors and inaccuracies corrected
2.2.9 (07.11.2023)— the appearance of the placeholder insertion window has been redesigned
— improved support for sites in single-byte encodings
— a bug in searching for duplicates has been fixed, due to which, when updating an entity on the site, the person responsible for related entities in AMO could change
- fixed an error that sometimes occurred during installation
2.2.11 (22.11.2023)— new system settings have been added to the administrative part of the module
— improved English language support
- fixed an error searching for duplicates that occurred if the user who updated the duplicate is no longer in Amo
— fixed a bug in searching for duplicates that occurred if the person responsible for the duplicate was no longer in AMO
- fixed a bug when the found double in Amo had double fields
- fixed a bug that appeared when searching for duplicates
— other found errors and inaccuracies have been corrected
2.2.14 (12.03.2024)— fixed the list of possible values for a custom field of the “list” type
— fixed transaction status update not always working correctly depending on the order flag
— fixed a bug where transaction statuses were not synchronized with order statuses if products were disabled in the Amo account
- other found errors have been fixed
2.3.1 (12.04.2024)— added the ability to cancel overwriting of selected fields in AMO when updating an order in the store
— the “Do not create notes if they already exist” setting has been moved to the mapping page, to the same place where the ability to update fields is now configured
— fixed a bug due to which integration profiles might not be deleted
— processing of changes to goods in a transaction is temporarily disabled, because Errors were found in this place that could cancel the order on the site
- refactoring
2.3.4 (19.04.2024)— a filter by site domain has been added to the order integration profile
— reverse synchronization of goods has been restored. Now it only works if the transfer of goods from an order to a transaction is enabled, in order to avoid overwriting the order contents
— improved English language support
- Fixed alternate switching of responsible persons if several of them are specified in the integration profile.
- Fixed the sometimes occurring error "Class "Illuminate\Support\Collection" not found"
— other found errors and inaccuracies have been corrected
- refactoring
2.3.7 (24.04.2024)— added the ability to transfer regular and custom fields of the user who created the order
— settings for statistics system labels are placed on a separate tab
— improved English language support
- added additional check for the existence of the owner, creator and updater when saving the entity
- other minor improvements
- minor inaccuracies corrected
2.4.0 (03.05.2024)- added a new free method for finding duplicates “Solution /ufee/amoapi”. You can select a method in the module settings on the “Additional settings” -> “Double search method” tab. The method is enabled by default for new installations. For older ones, if necessary, you need to switch manually. No further action is required. Searching for duplicates based on filtering API also still works
— compatibility with module event handlers written before version 2.3.1 has been restored
- updated communication libraries with amoSRM
2.4.1 (12.05.2024)- minor fixes
2.4.5 (24.05.2024)— translation into English has been significantly expanded
— fixed an error that occurred when searching for duplicates through API filtering
- Fixed occasional errors during installation
- refactoring
- other improvements and fixes