MANAGEMENT OF USER FIELDS IN BITRIX24 - COMPULSORY, EDITING RESTRICTION

automation with bitrix24

Bitrix24 CRM provides a set of easy-to-use interfaces for adding/editing various entity fields, whether it be invoices, leads, or deals. The introduction of the updated CRM card has led to a significant improvement in the perception of information by the end user, and the ability to create custom field types opens up a lot of new possibilities for customizing the interface to the client.

During the works, for our clients, while configuring the CRM system Bitrix24 often enough there is a task to protect previously entered data in certain fields of the entity.

For example, at one stage of the business process for our Spanish client who is engaged in the rental of real estate, information about the amount and order of payment from the client is entered into the deal fields. This information is used at later stages of the business process when billing occurs. It is necessary to ensure the protection and consistency of this information from change by managers who have access to the deal.

Unfortunately, despite all the features of the Bitrix24 interface, it is impossible to do this with standard means.

FIELD PROTECTION FROM CHANGES

Having analyzed the problem, we were able to find a solution. There are methods in Bitrix24 REST API that allow you to protect fields of different entities from editing. Portal administrator rights are required to block fields.

There are also some restrictions on these methods in terms of field types. 

FIELD BLOCKING AUTOMATION

Field blocking can be used in automating company processes, for example from business processes or in robots. To do this, an activation is added to the blocks of business processes, which allows you to prohibit editing for the desired fields in the entity.

An alternative way to use this feature in business processes is to block fields for editing by events of changing the status of an invoice/lead/deal using web hooks.

HOW CAN THIS BE USED?

The ability to use field filling protection allows you to solve a number of typical customer problems:

deal information protection

entered at a certain stage of the deal (for example: personal customer data, information about payments, trigger fields used for automation in business processes, etc.).

FINANCIAL ACCOUNT INFORMATION protection

from being changed by a manager or other person authorized to see the account data

in-lead information protection

intended for subsequent analysis in reports or uploads.

SUMMARY

Our experience with integration and automation in Bitrix24 shows that using a system of locking fields for recording, leads to increased stability of standard processes, as well as increases reliability by eliminating errors due to human factor.