3.5.3 (06.12.2024)— the transfer of the name and ID of the web form result has been added to the mapping
— found errors and inaccuracies have been corrected
3.5.2 (13.11.2024)- fixed a bug that could prevent a task from being created
- fixed bug with new installation
3.5.1 (29.10.2024)- fixed a bug that could prevent a task from being created
3.5.0 (24.10.2024)— added support for the "Birthday" field in amoCRM
- when creating a task with an empty description, a placeholder has been added to it to avoid errors
— fixed display of domain filter in profile list
— the module settings interface has been slightly redesigned
3.4.6 (04.10.2024)— added domain filter
- removed some obsolete methods
— minimum php version increased to 8.1
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
3.4.5 (10.09.2024)— исправлена ошибка в определении путей к файлам, которыя могли возникать при определённых настройках сервера.
— добавлены события onAfterUpdateContacts, onAfterUpdateLeads, onAfterUpdateCompanies
— исправлены найденные незначительные ошибки и повышена стабильность работы модуля
1.0.1 (16.02.2017)Added compatibility with version 15.5.4 and older
1.0.2 (17.02.2017)Added English language support
1.0.3 (20.02.2017)Minor bugs fixed.
1.1.0 (21.02.2017)Added the ability to set the name of the deal
Added the ability to set a transaction budget
Added processing of hidden fields in web forms
1.2.0 (23.02.2017)Added the ability to transfer values from forms and mail events to budget and custom transaction fields. Simple types of custom fields are supported: text, number, text area, short address, link, date.
For all types of drop-down lists and flags, manual setting of values is available.
1.2.1 (27.02.2017)Improved number recognition when adding a field to a transaction budget
When adding several fields to a budget, their values are summed.
1.2.2 (27.02.2017)Added the ability to clear values from html tags
1.2.3 (10.03.2017)The list of displayed errors has been expanded and clarified
Optimized the number of requests sent
1.2.4 (12.03.2017)Fixed an error in calculating the transaction budget from several fields
1.2.5 (12.03.2017)Added the ability to create a deal without creating a contact
1.3.0 (13.03.2017)Added the ability to create tasks
1.3.1 (16.03.2017)Fixed an error that occurred when upgrading from version 1.2.4 to version 1.2.5 during a new installation
Fixed other minor bugs
1.3.2 (20.03.2017)PHP 5.4 compatibility fix
1.3.3 (14.04.2017)Minor fixes
1.4.0 (21.04.2017)Added duplicate control
In contacts:
- adding a note to a new contact stating that there are duplicates
- updating the main contact without creating a duplicate
- use the main contact without updating
In notes: if an entity has an identical note, then a new one is not created
1.4.1 (24.04.2017)When searching for duplicates, spaces at the beginning and end of the compared fields are now not taken into account
1.4.2 (26.04.2017)Duplicate search errors have been fixed
Added search for duplicates if there are more than 500 contacts
1.5.0 (11.05.2017)Ability to add deals and contacts to "Unsorted"
When duplicate control is enabled, links to them will be added to contacts in “Unsorted” regardless of settings.
It is not possible to create tasks when adding them to "Unsorted".
1.5.1 (12.05.2017)Added checking for the presence of the CURL library on the server
1.5.2 (15.05.2017)minor improvements
1.5.3 (16.05.2017)Fixed an error that occurred during a new installation
1.5.4 (16.05.2017)minor improvements
1.5.5 (17.05.2017)Fixed a bug where it was impossible to add a new rule
1.5.6 (18.05.2017)Fixed a bug due to which in some cases the “Add to Unsorted” checkbox in the settings could be unchecked
Improved stability when checking duplicates
1.5.7 (22.05.2017)When the "Add to Unsorted" option is enabled, non-participating controls (deal status and tasks) become inactive
Fixed a bug due to which, when installing the solution, the installation of the necessary modules was not checked
Other minor improvements
1.5.8 (23.05.2017)When the "Add to Unsorted" option is enabled, the selection of actions with duplicates becomes inactive
Other minor improvements
1.5.9 (25.05.2017)When transferring to "Uncollected", the identifier of the person responsible is removed from the notes
1.6.0 (29.05.2017)Added support for utm tags
1.6.1 (01.06.2017)Fixed transfer of Cyrillic domains when adding to "Undisassembled"
Other minor improvements
1.6.2 (02.06.2017)Expanded checking of required modules and extensions
Added the ability to log requests
1.6.3 (02.06.2017)Added the ability to select a funnel for a deal
1.6.4 (04.06.2017)Fixed a bug where sometimes not all selected parameters were transferred
1.6.5 (04.06.2017)Added the ability to group notes
When adding multiple values to a contact name, they are now separated by a space instead of a comma
1.6.6 (04.06.2017)Fixed a bug with installing a module with the demo period already expired
1.6.7 (06.06.2017)Added writability check for required files and folders
1.6.8 (06.06.2017)Added check for domain validity
Other minor improvements
1.6.9 (08.06.2017)Added support for sites in encodings other than utf-8
1.6.10 (13.06.2017)File structure optimization
Error correction
1.6.11 (16.06.2017)Fixing bugs in duplicate processing
Other bug fixes
1.6.12 (16.06.2017)Added support for custom field "Smart Address" for transaction and contact
1.7.0 (20.06.2017)Added notification letter about amoCrm unavailability
1.7.1 (21.06.2017)Processing of events by the module is queued last so that all changes can be captured.
1.7.2 (21.06.2017)Fixed an error that occurred when checking the time of sending the last letter to the administrator.
1.7.3 (26.06.2017)Fixed a compatibility issue with older versions of Bitrix when creating email templates
1.7.4 (04.07.2017)Fixed a bug due to which utm tags were not always pulled up
1.7.5 (08.07.2017)Added the ability to transfer the domain of the current site
Added the ability to set the name of the deal in “Unsorted”
1.7.6 (09.07.2017)Added a component for importing the results of previously filled out web forms and past mail events
Added the ability to transfer files as URLs leading to their location on the site where the event occurred.
1.7.7 (10.07.2017)Fixed the order of events
1.7.8 (14.07.2017)Added pre-integration events with mail events and web forms. In events, you can change the contents of fields before sending, as well as cancel sending to AMO. More details in the documentation.
The field for sending advertising tags utm_* has been expanded, now you can also send tags like roistat_* through it
Added the ability to search for advertising tags in cookies
1.7.9 (14.07.2017)Improved event called before integration starts
1.7.10 (15.07.2017)Fixed an error that sometimes occurred when deleting a solution.
1.8.0 (25.07.2017)Added the ability to search for duplicates among transactions. The same actions are available with duplicate transactions as with duplicate contacts:
- adding a note to the new deal stating that there are duplicates
- updating the main transaction without creating a duplicate
- use of the main transaction without updating
Among other things, this functionality makes it possible to carry out a transaction by status depending on the events that occurred on the site;
Minor bugfixes.
1.8.1 (02.08.2017)Fixed an error that occurred in the demo version when sending a notification to the administrator
1.8.2 (15.08.2017)Selecting a funnel and status is now done in one line
Added support for openstat advertising tags
1.8.3 (08.09.2017)Added the ability to substitute “unparsed” field values into the deal name. Values are inserted through placeholders of the form #field_name#
A separate setting has been added - whether to update the name of the duplicate deal or not.
1.9.0 (19.09.2017)New view for integration rules in the admin panel: Services -> Integration with amoCrm
Refactoring
Error correction
1.9.1 (19.09.2017)Error correction
1.9.2 (19.09.2017)Fixing bugs in finding duplicates
Fixes other minor bugs
Refactoring
1.9.3 (20.09.2017)When creating "Unbroken" the creation of a transaction is made mandatory
1.9.4 (25.09.2017)Added the ability to filter advertising campaign tags
1.9.5 (26.09.2017)Fixed errors in transferring custom selectboxes
1.9.6 (27.09.2017)Fixed an error that sometimes occurred when searching for contact deals
1.9.7 (27.09.2017)Fixed a bug in displaying settings
1.9.8 (27.09.2017)Fixed a bug in transferring custom fields
1.10.0 (28.09.2017)Added the ability to import results of past mail events and previously filled out web forms from the administrative part (Services -> Integration with amoCrm)
Other improvements and enhancements
1.10.1 (29.09.2017)Elements renamed results for integration rules
1.10.2 (04.10.2017)Added the ability to insert placeholders into the tags and text of the created task
Added tooltip for placeholders
Added the ability to select the site on which the integration rule will be triggered (if there are 2 or more sites)
1.11.0 (11.10.2017)Added the ability to defer the integration process to agents. Useful for increasing website performance.
Added logging of all events
Support for the rover:amocrm.import component has been discontinued; instead, you can use the new administrative interface Services -> Integration with amoCrm
Minor bugs fixed
1.11.1 (11.10.2017)Minor bugs fixed
1.11.2 (12.10.2017)Fixed errors in localization files for rover:amocrm.preset.elements
Removed old unnecessary language files
Fixed a bug in displaying results
1.11.3 (17.10.2017)Added new fields for transfer to AMO:
- Name of the site
- site IP address
- the page on which the event occurred
Added advertising tag from
Fixed a bug related to the disappearance of the first field in a connected web form
Minor bugs fixed
1.11.4 (31.10.2017)- guaranteed integration (events that were sent with an error will be resent)
- ability to configure the number of events processed by the agent in one pass
- fixed a bug when substituting values from placeholders
- other bugs fixed
1.12.0 (31.10.2017)Added the ability to create companies. The same actions are available with companies as with contacts.
Required php version downgraded to 5.3
1.12.1 (01.11.2017)Fixed a bug with the disappearance of sections for setting up contacts, companies, and tasks
1.12.2 (28.11.2017)Error correction
1.12.3 (30.11.2017)Bug fixes, refactorings
1.12.4 (01.12.2017)Bugs fixed
1.12.5 (08.12.2017)- added a button for immediate processing of events that are awaiting processing by the agent
- added output of log file size
- added a limit on the maximum size of log files
1.12.6 (12.12.2017)Fixed error messages when installing/uninstalling
1.12.7 (16.02.2018)Fixed a bug due to which integration rules were sometimes not displayed in the "Services" section
Added the ability to skip integration of duplicate events on one hit. Can be useful when connecting web forms through a mail event and in some other cases.
1.12.8 (19.02.2018)Fixed compatibility with PHP 5.3 for the agent
1.12.10 (04.04.2018)new:
- advertising campaign tags are now always searched for in cookies
- added the ability to set the necessary RC labels manually.
- added RK label for clientId Google Analytics (_ga)
- the agent no longer reprocesses messages with errors
fixes:
- fixed the activity of the “funnel” field for a deal when “unsorted” is enabled
- fixed an error that sometimes occurred when updating a deal
- fixed transaction update logging error
- fixed the error "The value of an argument 'tab' is outside the allowable range of values" in the list of integration rules when there is no connection with amosrm.
1.12.11 (06.04.2018)Refactoring and minor bug fixes
1.13.0 (09.04.2018)Added the ability to transfer each advertising campaign label to a separate field
Refactoring
1.13.1 (22.04.2018)Fixed an error that sometimes occurred when mass exporting elements to AMOSRM
1.13.2 (21.05.2018)Adding a user ID (visitor_uid) to the deal and additional entity fields
Final transfer of the list and settings of integration rules from the module settings to a separate section.
1.13.3 (27.05.2018)Added the ability to enable/disable the creation of “unsorted”, deal, contact, company and task from the general list of integration rules
Fixed a pagination error in the list of integration rules
Other minor improvements
1.13.5 (30.05.2018)Fixed search for duplicate transactions in the fields "Name", "Budget", "Status"
Added the ability to search for duplicates by matching any of the selected fields
The "All advertising campaign tags" field has been moved to the "Advertising campaign tags" section
1.13.7 (05.06.2018)Added the ability to separately re-process events that previously had an error when sending them
Increased productivity
1.13.8 (21.06.2018)— Improved error handling in components
— Minimum php version raised to 5.6
— The minimum version of the "Administrative Part Designer" has been raised to 1.8.3
1.14.0 (03.07.2018)— the list of advertising campaign tags available by default has been expanded, and their brief description has been added
— added search for analytics and advertising campaign tags in the query string and session
— added the ability to save analytics and advertising campaign tags in a session
— added a filter for the _ga (Google Analytics Client Id) label, removing the api version from the label: GA1.2.1054613344.1468150257 => 1054613344.1468150257
- redesigned internal event system
- some bugs fixed
1.14.1 (03.07.2018)Visibility of fields marked as "Only from API" has been restored
2.0.0 (13.07.2018)— data exchange has been switched to version 2 of the amoCRM api
- extended error messages
- refactoring and minor bug fixes
2.0.7 (20.07.2018)— to avoid blocking by amoCRM, an artificial delay between requests of 0.3 seconds has been introduced
- reduced memory consumption when searching for duplicates
— multilingual support and English translation have been restored
- added additional dependency checking when events are triggered
- fixed display of funnel statuses
— other errors and inaccuracies have been fixed
2.0.8 (25.07.2018)— improved performance of saving advertising campaign labels when navigating between pages
- some errors and inaccuracies have been fixed
2.0.11 (28.08.2018)— added automatic clearing of entries about old events in the log;
— errors in working with custom task types have been fixed;
— errors in searching for duplicate transactions from a contact have been fixed;
— displaying a warning about disabled integration in components;
— minor changes in the settings interface;
— minor changes in the integration rules interface: placeholders are now indicated to the right of the field, etc.
— the minimum required version of the “Administrative Part Designer” has been raised to 1.8.12;
- refactoring.
2.0.14 (13.09.2018)- fixed a bug due to which the transaction price was sometimes not transmitted
— added type and encoding check for RK and analytics labels
- detected warnings have been fixed
- interface slightly improved
2.0.18 (05.11.2018)- added standard advertising campaign label utm_referrer
— the integration rules interface has been improved
— the ability to change data sent to amoCRM through events has been restored
— comments removed from js code
- fixed a bug due to which transactions were sometimes not sent
— API response is accelerated by 50%
— other minor improvements and refactorings
2.0.19 (27.12.2018)— fixed a bug with pulling up additional labels of advertising companies
2.0.20 (07.01.2019)Improved multilingual support
2.0.21 (29.01.2019)— fixed a bug due to which the created integration events could sometimes not go to AMO;
— fixed an error that occurs if the creation of an entity (deal, contact, etc.) is prohibited in the pre-integration event.
2.1.0 (09.02.2019)— Added the ability to set a deadline for a task;
— for ease of use, in the integration rule settings, the sections responsible for setting fields have been moved to internal tabs;
— faster response via API;
— the minimum required version of the “Administrative Part Designer” has been increased to 1.8.15.
2.1.3 (23.03.2019)— added the ability to automatically reprocess events with errors on the agent
— a column with the responsible manager and the ability to change it have been added to the list of integration rules
— in the integration rule settings, the fields are marked “only from api”
- fixed activation/deactivation of integration rules in the list
- minor bug fixes
2.1.9 (22.07.2019)— added support for mail events added by the \Bitrix\Main\Mail\Event::send($data) method; cores d7. Method support \Bitrix\Main\Mail\Event::sendImmediate($data); not yet, since suitable events are not raised there;
— new events have been added. For a full description of the events, see here https://github.com/pavelshulaev/amocrm/blob/master/events.md;
— increased reliability of connection with the amoCrm server;
- found errors have been fixed
2.1.10 (19.08.2019)- found errors have been fixed
2.1.11 (31.12.2019)- fixed a bug due to which events in amoCRM were sometimes duplicated
— integration on agents now works only if the agents are transferred to cron
— the minimum PHP version has been increased to 7.0
— the system of internal events has been changed (more details in the description of the solution on GitHub https://github.com/pavelshulaev/amocrm/blob/master/events.md)
- class \Rover\AmoCRM\Entity\Result is deprecated
— refactoring and correction of minor errors and inaccuracies
BE SURE to create a backup copy of the site before updating. If you have been using legacy module events, plan to migrate to the new ones in the near future.
2.1.12 (01.01.2020)— management of advertising campaign and analytics tags has moved from the integration rule settings to a separate tab in the module settings, because By and large, these settings are the same for the entire site
— refactoring and correction of minor errors and inaccuracies
2.2.0 (07.01.2020)— added the ability to synchronize transaction statuses in amoCRM with order statuses in the online store. Available only if the "Online Store" module is installed. More details in the documentation https://github.com/pavelshulaev/amocrm/blob/master/status-sync.md.
— agent settings are placed on a separate tab;
— correction of minor errors and inaccuracies, refactoring.
2.2.6 (16.01.2020)— added additional fields “telephone”, “zip code”, “location”, “delivery address”, “cost without delivery”, “payment system name”, “delivery service name”, “delivery cost”, “order comment” in mail events "New order" (SALE_NEW_ORDER), "Change of order status" (SALE_STATUS_CHANGED_), "Order paid" (SALE_ORDER_PAID), "New order for subscription renewal" (SALE_NEW_ORDER_RECURRING), "Order delivery allowed" (SALE_ORDER_DELIVERY), "Order cancellation " (SALE_ORDER_CANCEL), "Subscription cancelled" (SALE_RECURRING_CANCEL). These fields can be used both for integration with amoCRM and in letters generated based on events;
— fixed a bug with saving advertising campaign labels in the integration rules settings;
- Fixed processing of placeholders in tags;
— improved handling of d7 events;
— the work of the agent has been restored; it converts stuck events into erroneous ones after three hours;
— Fixed a bug due to which tabs in the settings disappeared when there was no connection.
2.2.7 (19.01.2020)— adding placeholders in integration rules has become more convenient. Now you can add them with one click in a pop-up window;
— a bug has been fixed when instead of a missing placeholder value its code was transmitted, now an empty value is transmitted;
— the filter for duplicate events on one hit has been restored;
— the translation of the English version has been improved;
— refactoring and minor bug fixes.
2.2.8 (24.01.2020)— added the ability to select the “unassembled” funnel;
— transfer of the website page on which the “unsorted” was created;
— in the additional field “Page Address” the full address is now transmitted, with http/https and domain;
— minor bug fixes and refactorings
2.2.9 (29.01.2020)— added check of the rights of the responsible user; if some rights are missing, a message is displayed about this;
— added the ability to view and change the owner in the list of integration rules
2.2.10 (20.02.2020)— correction of found errors
2.2.12 (11.03.2020)— fixed a bug due to which when synchronizing order statuses in the direction amo -> store, mail events did not fire and the order change date did not change
— added the ability to edit the names of integration rules
— new events now receive the second argument as the Rover\AmoCRM\Helper\TransportProvider object, which contains all significant objects
- Fixed errors that occurred when installing the solution, due to which event handlers and additional functions could not be registered. order fields;
— the required version of the "Administrative Part Designer" has been upgraded to 1.9.1
— refactoring and correction of other minor errors and inaccuracies
2.3.0 (16.03.2020)— added the ability to add several integration rules for each mail event and web form result;
— the ability to link a task to a deal, contact or company has been restored;
— the date of creation of the result has been added to the list of results of integration rules;
- fixed bread crumbs;
— other fixes and refactorings.
2.3.1 (22.03.2020)— added the ability to synchronize the order cancellation flag with transaction statuses
— added the onBeforeWebhook event, which fires before the webhook is called. More details in the documentation https://github.com/pavelshulaev/amocrm/blob/master/events/onbeforewebhook.md
- minor bugs and inaccuracies fixed
- refactoring
2.3.2 (22.04.2020)- added the ability to copy integration rules
— other minor improvements and improvements
2.4.0 (25.04.2020)BEFORE INSTALLING THIS UPDATE, BE SURE TO MAKE A BACKUP COPY!!!
— added the ability to transfer products from an order to amoCRM products
— added reverse synchronization of the number of goods in transactions with the number of goods in an online store order
— added new events for working with products: beforeCatalogProductGetList, afterCatalogProductGetList, beforeCatalogProductAdd, afterCatalogProductAdd. For more details, see the description of the events: https://github.com/pavelshulaev/amocrm/blob/master/events.md
— now the only element passed to these events is \Rover\AmoCRM\Controller\Transport: onBeforePushData, onAfterPushData, beforePushUnsortedData, onPushUnsortedData, onAfterPushUnsortedData, onBeforePushStandardData, onAfterPushStandardData
— support for legacy events has been discontinued
— support for the Rover\AmoCRM\Model\Result object has been discontinued
— the minimum PHP version has been increased to 7.1
- minimal version of ch. module increased to 16.5.9
— minor bug fixes and refactorings.
2.4.5 (15.06.2020)— added transmission of fields to amoSrm lists by value
— added the default rk label Yandex ClientId (_ym_uid)
- fixed errors when creating “unassembled” with included goods
— bugs with the impossibility of creating “unassembled” have been fixed
- fixed errors in version integrity checking
- fixed installation and uninstallation errors
— other minor inaccuracies corrected
2.5.0 (02.07.2020)— “Unsorted” is now created when setting the deal status to “Unsorted”
— the ability to create an “unassembled” integration rule from the first tab has been removed
— the title of the “unparsed” in Amo now contains its name, not a link
— additional fields are now added to the order even if the integration rule is disabled (the integration itself must be enabled). They can be used in email templates.
- found errors have been fixed
2.6.0 (31.07.2020)BEFORE INSTALLING THIS UPDATE, BE SURE TO MAKE A BACKUP COPY!!!
ATTENTION! This update changes the authorization scheme in amoCRM. After installing the update, in order to continue using the solution, you will need to follow the steps to establish a connection with amo, described in the "Installation" tab.
— Transition to outh2 authorization (see the "Installation" tab)
— Fixed a bug when creating “unassembled”
2.6.2 (28.08.2020)— added the ability to specify multiple responsible persons for an integration rule. Responsible persons are assigned in turn each time the rule is triggered;
— the interface for synchronizing the store with Amo has been redesigned, a separate setting has been added for status synchronization;
— added/removed goods in a store order upon delivery/removal of them in a linked AMO transaction;
— the “transfer goods” setting, which is responsible for transferring goods to AMO as entities and their further synchronization, has been moved from the integration rules settings to the module settings;
— to guarantee the construction of addresses for authorization links and webhooks, a check for the existence of a default site with a filled in domain name has been added;
— a bug has been fixed when goods disappeared from orders when the transfer of goods to AMO was enabled;
- other errors and inaccuracies have been fixed
2.6.8 (16.10.2020)— new additional fields have been added to mail events associated with the order: cost without delivery (number), delivery cost (number), currency code, currency name. Now the cost of goods and delivery can be transmitted both in formatted form with a currency code, and as a number
— added the ability to specify codes for the types of mail events associated with the order, to which additional fields will be added. Mail events must contain the fields ORDER_ID or ORDER_REAL_ID, in which the order ID must be transmitted
— added a check that the account under which the connection to amoSRM occurs is administrative
— added synchronization of statuses when transferring from “unsorted”
— due to the gradual transition to API version 4, the afterCatalogsGetStatus event has been removed
— fixed the status check error that occurred after updating from versions lower than 2.6
— fixed the error of the expired demo period after installation
- other various fixes
2.6.15 (08.12.2020)— added events for searching and creating a product in amoCRM based on a cart item
— when searching for an existing product in amoCRM, a price check has been added
— added the ability to manually set a site for notifications
— added the ability to set a custom site domain for notifications
— the "Parameter Lists" module is no longer required
- fixed bug after installation
— fixed a bug due to which integration rules were not created
— files that were mistakenly not included in the previous version have been uploaded
- other minor fixes and refactorings
2.7.1 (15.01.2021)— agents have been redesigned: the efficiency and stability of event processing has been increased
— integration rules have been renamed to integration profiles
— added label roistat_visit
- found errors have been fixed
- refactoring
2.7.2 (26.01.2021)— connection settings are placed on a separate page
- updated SDK for communication with amoCRM
— new events have been added (see https://github.com/pavelshulaev/amocrm/blob/master/events.md)
— improved compatibility with sites in single-byte encodings, for example windows-1251
— found errors have been corrected, incl. in demo version
— due to the update of the amocrm api, when editing goods in a transaction, synchronization with the order remained only in composition and quantity.
- minimum php version increased to 7.2.5
2.7.3 (20.02.2021)BEFORE INSTALLING THIS UPDATE, BE SURE TO MAKE A BACKUP COPY!!!
— settings for synchronizing statuses and products in orders have been moved from the module settings to the “order” tab of the corresponding integration profiles
— html tags are now always cut out from the text, because they are not supported in amoCRM. Line breaks are preserved
— you no longer need to specify fields to identify orders in Amo, transactions are now automatically linked to orders
— for the transfer of goods to the AmoSRM online store, the restriction on the minimum length of the order number of 3 characters has been removed
— the “Number of events processed in one pass” setting has been removed from the visual part
— the minimum version of the "Administrative Part Designer" has been increased to 1.9.7
- search for duplicates restored
- found errors have been fixed
2.8.2 (08.03.2021)— added the ability to connect to multiple amoCRM accounts
— the "Administrative part designer" module is no longer required
— notification and logging settings have been moved to the "Advanced settings" tab
— agent settings have been moved to the "Basic Settings" tab
- fix installation errors
— other bug fixes and refactorings
2.8.3 (24.03.2021)— added support for tag fields of statistics systems in AMO (tracking_data)
— added default labels: _ym_counter, openstat_service, openstat_campaign, openstat_ad, openstat_source, gclientid, fbclid
— webhook is now created automatically when connecting/reconnecting
— error notification email is enabled by default for new installations
— correction of errors and inaccuracies
- updated SDK for communication with amoCRM
2.8.6 (01.06.2021)- added agent restart button
— the limit on 50 custom fields for an entity has been removed
— fixed a bug due to which the responsible persons in the list were not switched
— correction of other minor inaccuracies
- refactoring
2.8.8 (06.07.2021)— processing of instant mail events has been restored (CEvent::SendImmediate)
- fixed errors in event processing when the number of custom fields is more than 50
- fixed bread crumbs in the administrative part
— bugs in processing statistics labels have been fixed
— other found errors and inaccuracies have been corrected
- refactoring
2.8.16 (19.08.2021)— the list of events has been transferred from the table to the hl block
— the number of retries to process erroneous events is limited to 3
— fixed an error that occurred when calling a non-existent mail event
- fixed attachment of order products to the transaction
- fixed price processing if there are extraneous characters
- Fixed re-sending integration profile results
— fixed selection of transaction stages in the integration profile for accounts with one funnel
- fixed automatic webhook forwarding
— version exclusion from the _ga label has been restored
- fixed installation error with expired demo period
- fixed errors in processing instant mail events (CEvent::SendImmediate)
- other found errors have been fixed
- refactoring
2.8.20 (06.10.2021)— added the ability not to change the status of a found duplicate transaction in the “Update and use the very first of the found duplicates” mode
— added the ability to search for duplicate transactions by linking to a contact. This allows you to avoid creating a new deal if the contact already has one
— integration profiles have been transferred from options to the hl block, the restriction on the number of profiles has been removed
— mass transfer from undisassembled has been restored
— fixed a bug due to which numerical labels of statistics systems were not transmitted
— fixed a bug due to which the integration profile was not saved if there was only one funnel in Amo
- other found errors have been fixed
- refactoring
FOR DEVELOPERS:
For developers: in custom event handlers, replace the Rover\AmoCRM\Profile object with Rover\AmoCRM\Directory\Entity\Profile
3.0.0 (30.11.2021)BEFORE INSTALLING THIS UPDATE, BE SURE TO MAKE A BACKUP COPY!!!
ATTENTION!!! This update DOES NOT have event compatibility with previous versions! If you wrote your own event handlers, CAREFULLY read the “FOR DEVELOPERS” section before installation.
— added control of duplicates by AMO. Additional configuration of the source is required https://www.amocrm.ru/developers/content/crm_platform/duplication-control
— processing of duplicates by the module has been accelerated. Now the number of entities does not affect the processing speed.
— in the search for duplicates on the module’s side, the “Linked contacts” field has been renamed to “Linked contact deals”, the “Limit the search area to existing contact deals” checkbox has been removed, because its functionality now duplicates this field
— the mapping field "All tags of statistical systems" has been removed
— the “deal name/unparsed” field has been moved to the deal field mapping
— the “task text” field has been moved to the mapping of task fields
— added the value “in an hour” for the task deadline
— added the ability to set tags separately for a deal, contact, company
- Notes are now always grouped. The corresponding setting has been removed. Links to duplicates come as a separate note.
— updated placeholders
— notifications about configuration errors have been added to the integration profile settings
— links to linked entities have been added in the results: deals, contacts and companies
— other visual changes to the integration profile settings
FOR DEVELOPERS
— transition to version 4 of the amoCRM API. More details about the sdk used here https://github.com/amocrm/amocrm-api-php
— the version of the API connection with amoSRM has been updated to 0.6.1, all libraries on which there are dependencies have also been updated.
- removed obsolete classes \Rover\AmoCRM\Profile, Rover\AmoCRM\Model\Preset and \Rover\AmoCRM\IntegrationRule, use \Rover\AmoCRM\Directory\Entity\Profile instead
- removed obsolete classes \Rover\AmoCRM\Event and \Rover\AmoCRM\Model\StatusTable, use \Rover\AmoCRM\Directory\Entity\Event instead
- removed the obsolete class \Rover\AmoCRM\Config\Options, use \Rover\AmoCRM\Options instead
— the \RoverAmoCRMEvents class has been renamed to \RoverAmoCRM, the old class is retained for now for compatibility
- removed events onBeforePushData, onAfterPushData, onBeforePushUnsortedData, onPushUnsortedData, onAfterPushUnsortedData, onBeforePushStandardData, onAfterPushStandardData. New ones have been added instead. See the module course https://rover-it.me/knowledge/course/course1/chapter0124/
— new events beforeCheckDuplicates and afterCheckDuplicates have been added, allowing you to cancel or modify the search for duplicates from the module. For more details, see the section on module course events.
3.0.2 (17.12.2021)- added the ability to delete connections. You can only delete connections that are not associated with any integration profile
— added automatic setting of default statistics labels for a transaction when creating a new integration profile
- added default label referrer
- improved search for creating duplicate events on the same hit
- improved compatibility with older kernel versions
— classes and fields that became unnecessary since version 3.0 have been removed
- expanded error messages
- fixed a bug when processing instant mail events
— other found errors and inaccuracies have been corrected
- refactoring
3.0.3 (12.01.2022)- error correction
3.1.0 (23.01.2022)— added integration with creating and updating information block elements
- refactoring
— SDK integration with amoCRM api has been updated to version 0.7.0
— fixed event counters in operation/new/frozen/erroneous
- other minor fixes and improvements
3.1.2 (14.03.2022)— the work of the setting "Remove information about the api version from the _ga label" has been fixed
— to avoid confusion, the “Control duplicates from AMO” setting is made unavailable if deal creation is disabled
— deletion of tags when passing fields to a note has been restored
— added a delay during mass processing of events to avoid blocking by amoSRM
- fixed bug with event processing freezing
— other improvements and minor fixes
3.1.6 (19.04.2022)— filling of fields like AMOCRM_ for mail events related to the order has been restored
- improved work in windows-1251 encoding
- fixed errors when updating order status based on transaction status
- other minor bugs fixed
3.1.7 (21.04.2022)— added support for the "Address" type field
- refactoring
3.1.8 (13.05.2022)— added search for duplicate transactions on linked orders
— added search to the selection of the responsible person, mapping, selection of a mail event, web form, information block when adding an integration profile
- when creating a new profile, deals and contacts are now enabled by default
- refactoring
3.1.9 (30.05.2022)- fixed errors when searching for duplicates
- fixed behavior when contacts might not be created when a deal is disabled
- other found errors have been fixed
3.1.10 (28.07.2022)- fixed an error that sometimes occurred when processing unparsed items through agents
— fixed a bug due to which transactions could sometimes not be created
— other found errors and inaccuracies were corrected
3.1.11 (11.08.2022)- found errors and inaccuracies have been corrected
3.1.12 (22.09.2022)- minor bugs and inaccuracies fixed
- refactoring
3.1.13 (28.10.2022)— the list of available infoblock property types for integration has been expanded
3.1.14 (27.12.2022)— when passing to a custom field of the “link” type, the first link from the passed value is now taken as the value
— for better compatibility, added the ability to disable additional js scripts
- updated version of sdk communication with amocrm to 0.12.3
- refactoring
- found errors have been fixed
3.1.16 (21.02.2023)— found compatibility errors with php 8 and php 8.1 have been fixed
— other found errors and inaccuracies have been corrected
3.1.18 (22.05.2023)— added transfer of multiple checkboxes from web forms
- updated dependencies
— the ability to search for duplicates on the part of AmoSRM has been removed, because they disabled this feature for external integrations
— to search for duplicates on the site side, in order to avoid errors, a filtering API connection check has been added in AMO. To connect, you need to contact technical support for your amoSRM account. The service is paid.
3.2.1 (27.06.2023)— added differentiation of access rights to the module
— updated design of the list of integration profiles and the list of results
— expanded functionality of the left menu in the admin panel
- minor edits
3.2.2 (30.06.2023)- fixed compatibility error in Bitrix core version 23.300.100 and higher
- other found errors have been fixed
- updated dependencies
3.2.5 (29.08.2023)- fixed links to integration profiles from the left menu
— a bug has been fixed that sometimes prevented the ability to control duplicates after paying for API filtering.
— added the number of elements on the page in the results
- minor visual improvements and interface fixes
- bug fixes
3.3.0 (07.09.2023)— Added mass export of elements from the list of results
— Added manual mass processing of new and erroneous events from the module settings
— Minor interface adjustments
- Fixed found errors
3.3.5 (27.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
— the duplicate search settings tab has been redesigned
- fixed compatibility issue with old kernel version
— fixed an error that occurred when searching for duplicate deals with an active filter by status
— fixed a bug due to which, when updating duplicates, custom fields that were not in the original were overwritten
- other found errors have been fixed
3.3.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 other minor errors and inaccuracies
3.3.8 (29.10.2023)— for information block elements, a link to the element on the site has been added, and for detailed images and previews, links to a file on the site are now transmitted
— the appearance of the placeholder insertion window has been redesigned
— added the ability to transfer language and site ID
- fixed automatic site detection
— 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
3.3.9 (17.11.2023)— fixed a bug when the found double in Amo had double fields
- 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 due to which entities could not always bind to each other
— other found errors and inaccuracies have been corrected
3.3.10 (11.12.2023)— new system settings have been added to the administrative part of the module
— fixed a bug due to which events might not be sent to amoSRM if the site was not explicitly specified in the integration profile
— fixed a bug due to which the site language might not be transmitted
3.3.12 (01.04.2024)— added transfer of properties of the type “Binding to an information block element” when integrating information blocks. The name of the bound element is passed as the value
— added events that allow you to customize the creation of a deal, contact and company (onBeforeBuildContact, onAfterBuildContact, onBeforeBuildLead, onAfterBuildLead, onBeforeBuildCompany, onAfterBuildCompany). For more details see https://rover-it.me/knowledge/course/course1/chapter0124/
— fixed a bug due to which transaction statuses might not be synchronized with order statuses
3.3.13 (04.05.2024)— sequential switching of responsible persons has been optimized if several are specified in the integration profile.
- redesigned module settings interface
- updated communication libraries with amoSRM
- Fixed the sometimes occurring error "Class "Illuminate\Support\Collection" not found"
— other found errors and inaccuracies have been corrected
3.4.0 (12.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
— some methods and constants that were considered obsolete for a long time have been removed
3.4.4 (22.05.2024)— fixed an error that occurred when searching for duplicates using API filtering
- installation errors fixed
- other minor improvements and fixes
- bug fixed when updating