What this solution does
The 'CRM Field Change History' module by 5 UGLOV addresses gaps in the standard CRM card chronology. The default history shows only that an object was modified, without details for most fields, especially custom UF_* fields. The 'History' tab also does not always provide complete information. This makes it difficult to answer questions such as who changed the deal amount, when a lead source was updated, or what the value of a contract field was before yesterday's edit.
Administrators select specific fields for monitoring. Once activated, every change to a selected field is recorded in the card, capturing the user who made the edit, the date and time, as well as the previous and new values.
Module capabilities:
Tracking changes for any fields in Deals, Leads, Contacts, and Companies, including custom UF_* fields that are not displayed in the standard chronology.
Recording changes in two standard locations: the chronology and the 'History' tab. Employees view data in familiar sections without needing to learn new tools.
Precise configuration. Fields are selected individually for each entity type. For Deals, settings apply separately to each sales pipeline. Only changes to explicitly included fields appear in the card.
The module displays readable names instead of internal codes in the CRM field history. Statuses, sources, data types, and links to infoblock elements are shown as text rather than numeric identifiers.
Two chronicle formats are available: a detailed format where each field change is recorded as a separate entry showing the transition from the old value to the new one, or a summary format where all changes made during a single save operation are combined into one message.
Only fields that have actually changed are recorded in the log. Re-saving a card without modifications does not create new entries.
The settings include convenient field search by name or code. A table of all tracked fields is provided, allowing monitoring to be disabled for any field with a single click.
The system notifies users about new module versions: a bell icon appears in the settings, and portal administrators receive a corresponding message. The portal server requests the latest version number once daily. Version checking can be disabled in the settings.
Environment requirements:
— Bitrix24 on-premise version with the CRM module installed.
— PHP version 8.2 or higher.
— Database: MySQL or PostgreSQL; the module is compatible with both systems.
If “5 Corners. Field Change History in CRM” is required, General iT can help with installation, configuration and a technical check after integration.