Accelerating Enterprise Digital Marketing: How to Use YonBuilder to Build Lead Management Applications
How to develop lead management application with YonBuilder low code?
Lead management refers to the process of collecting, screening, scoring, assigning, following up and nurturing potential customers' information through various channels in order to convert them into customers.
Realizing good lead management through digital and intelligent means can help companies improve marketing effects, optimize the allocation of sales resources, enhance customer relationship maintenance, and improve sales performance and income. It is an important link for companies to achieve sustainable development.
This article uses the YonBuilder application construction service of the Yonyou Developer Center to build a basic lead management form, and the functions realized are as follows:
- User submits investment information
- Leads are uniformly submitted to the lead record form
- Transfer to the corresponding communication form according to user needs
- The follow-up personnel record the details of each communication after the communication
- Write back the thread record table in real time after the communication record is updated
- entity configuration
Splitting the lead flow requirements shows that we need to configure two types of forms: lead record form and communication record form in different directions, so configure the entity first.
- thread record entity
The entity corresponding to the thread record form should contain the following information, and the fields can be configured according to business requirements. It should be noted that the business flow interface must be checked:
You can see that some fields in the entity are set as radio types, and this part of the type needs to refer to the enumeration. In addition to the system's own enumeration, you can also add a custom enumeration in the enumeration management under object modeling.
The two enumeration types referenced here are configured as follows, and the enumeration values and names can be modified according to requirements:
- Communication record entities in different directions
Since the enumeration of user needs is divided into two directions: mobile development and application construction, it is necessary to create communication record forms in two different directions, and corresponding communication record entities in two directions are required. The following is the mobile development communication record entity configuration as an example. First create a communication record main entity, and create a communication detail sub-entity based on the main entity to record communication information.
The main entity configuration information is as follows:
The subentity configuration information is as follows:
- page configuration
Firstly, corresponding pages are generated according to the entities created in the first part. Those that contain sub-entities need to be created as one main and multiple sub-pages, and those that only have the main entity, select a single-card page. After that, configure the page according to the required functions.
- When submitting investment reservation information through the mobile terminal form, users only need to submit three types of information: name, contact information, and requirements. Other fields need to be hidden from users, and the retention time should default to the current date when the user submits information, so the configuration is as follows:
Hide retention time and lead status fields:
Modify table style:
The retention time defaults to the current date:
- In the lead communication record table, because you do not want uncontrollable modification of the data, the editing is set to invisible, that is, only new documents are allowed.
- In the classified communication record table, the lead status is updated according to the status in the latest communication record in the sub-table. At the same time, the communication frequency field needs to count the data in the sub-table, and the fields in the main table are set to be non-modifiable.
Get the number of child tables:
Update thread status:
The main table field is set as unmodifiable, and all fields can be operated in the same way.
- Business flow configuration
After completing the configuration of the basic page, in order to realize the flow of information in the thread record table and the communication record table, you need to configure the business flow. The configuration path is as follows:
- First drag the documents and branches to be configured onto the canvas, and connect them according to the data flow process.
- The configuration branch enables documents to flow to different communication record tables according to different user needs.
The final branch realizes the effect:
- Taking the application construction communication record form as an example, complete the push configuration according to the requirement of automatic push when saving.
- Configure the rules for writing back communication information
- achieve effect
The configuration of all the requirements expected to be realized in this article has been completed above, and then the function is verified by simple data.
First, add new data to the lead recording table on the mobile terminal.
Secondly, on the PC preview page, you can see that the submitted data has been added, and there is no editing option.
Next, after refreshing the mobile development communication record table, you can see that the new data has been synchronously added to the corresponding category communication table.
In the communication form, all the main form fields are grayed out, which means they cannot be modified. However, through the above configuration, after editing the communication details, the thread status and communication times in the communication record table can still be updated.
Finally, go back to the lead record table and refresh the page, the lead status has been updated according to the communication record details.
