CN116521162A - Low-code-based visual CRM system, page building method and storage medium - Google Patents

Abstract

The invention discloses a visual CRM system based on low codes, which comprises a design state designer and an operation state renderer, wherein the design state designer comprises a material pile, a visual form design module, a visual flow design module and a form expansion module; the material stack comprises a control library unit and an associated form unit; the control library unit is used for providing a standardized assembly for graphics, and the association form unit is used for associating and synchronizing data of other forms in the current form; the running state renderer is used for rendering the basic information of the form according to the schema data newly added by the design state designer, and dynamically rendering the controls of different types by matching the control types, so that the rendering of the visual interface is realized. The invention realizes the visualization of all operations, namely, the visualization is obtained, and when in secondary development, a user can expand the form capacity based on the provided method, realize the data multiplexing through the associated forms, and the forms are not isolated any more.

Description

Low-code-based visual CRM system, page building method and storage medium

Technical Field

The invention relates to the technical field of computers, in particular to a low-code-based visual CRM system, a page building method and a storage medium.

Background

The low-code development platform is a development platform capable of quickly generating an application program without coding (zero codes) or through a small amount of codes, and a method for developing the application program through visualization enables developers with different experience levels to conveniently construct web pages and mobile application programs through a graphical visual interface and using a drag component and model-driven logic.

Customer relationship management system (CRM system) is an information system that uses software, hardware and network technology to build a customer information collection, management, analysis and utilization for an enterprise. The management of the client data is taken as a core, various interaction behaviors of enterprises and clients in the marketing and sales processes and various states of related activities are recorded, various data models are provided, and support is provided for later analysis and decision.

Low code CRM systems on the market typically have different implementations depending on different usage scenarios or different technology stacks, but their system core functions and capabilities are generally similar, and the final implementations and experiences tend to be similar or identical from a technical point of view.

The current low code CRM platforms typically have the following problems:

(1) The functions are bloated, the system construction is complex and complicated, and the service form can not be quickly built;

(2) The system interface is not open enough, the customization degree is high, and the secondary development cost is high;

(3) The scene support is single, the application scene of the CRM system is difficult to expand, and repeated development can consume a great deal of manpower and time cost;

based on this, it is desirable to construct a CRM system that is more convenient to develop and use.

Disclosure of Invention

In order to solve the technical problems, the first aspect of the invention discloses a low-code-based visual CRM system, which comprises a design state designer and an operation state renderer, wherein the design state designer comprises a material pile, a visual form design module, a visual flow design module and a form expansion module;

the material stack comprises a control library unit and an associated form unit; the control library unit is used for providing a standardized assembly for graphics, and the association form unit is used for associating and synchronizing data of other forms in the current form;

the visual form design module is used for providing a visual interface for a user to draw a page to be displayed in a dragging mode from the control library;

the visual flow design module is used for creating a flow, acquiring flow data from the visual form design module through a pre-packaged data transmission interface, and realizing flow operation corresponding to a standardized component in the visual interface according to the flow data;

the form expansion module is used for expanding the custom function of the design state designer;

the running state renderer is used for rendering the basic information of the form according to the schema data newly added by the design state designer, and dynamically rendering the controls of different types by matching the control types, so that the rendering of the visual interface is realized.

Further, the visual form design module further comprises an editing unit and a basic information configuration unit;

the editing unit is used for providing a visual interface, a basic information function of configuration fields and a formula editing function;

the basic information configuration unit is used for configuring basic information of the form in the visual interface.

Further, the running state renderer comprises a creation module, a detail module and a list module;

the creation module is used for dynamically rendering the visual interface, changing the content of the visual interface according to form data, outputting a result according to a calculation formula and changing the visual interface;

the detail module is used for displaying corresponding pages to different users according to the user permission;

the list module is used for providing a dynamic rendering list query page function, a dynamic adjustment display list function, a query condition grouping and saving function and a data screening function according to the basic control, the enhancement control and the service control.

Further, the steps when the running state renderer performs rendering include:

analyzing the newly added schema data of the design state designer;

matching different controls according to the control types;

and dynamically rendering the page according to the page type, if the page is the creation module, carrying out mounting calculation formulas and events, giving the form linkage and calculation capability functions, otherwise, further matching whether to dynamically render the flow form of the detail module.

Further, the visual flow design module comprises a node configuration module, a template storage module and a permission configuration module;

the node configuration module is used for customizing flow nodes in the flow;

the template storage module is used for storing a plurality of versions of processes and carrying out switching multiplexing of the processes;

the authority configuration module is used for providing flow approval actions and configuring field editing authorities of the flow nodes.

Further, the form expansion module comprises a business association unit, a form verification unit, a printing unit and a data pushing unit;

the business association unit is used for realizing the function of synchronizing the data of one form after the data of the other form is newly added or modified;

the form verification unit is used for configuring form data rules and carrying out rule verification on the form data when a user submits the form;

the printing unit is used for printing the form data according to the self-defined printing template;

the data pushing unit is used for providing a data pushing function.

Further, the custom functions include expanding custom controls, inserting custom content in the page, querying custom columns in a table of the page, column width dragging tones, and displaying or hiding the screen options and columns in the table.

The second aspect of the invention discloses a page building method of a CRM system, which is applied to the low-code-based visual CRM system according to the first aspect of the invention, and comprises the following steps:

performing visual interface configuration in the visual form design module, and creating a flow in the visual flow design module;

the visual flow design module obtains flow data from the visual form design module through a pre-packaged data transmission interface, and flow operation corresponding to a standardized component in the visual interface is realized according to the flow data;

and the running state renderer dynamically renders the visual interface and the flow.

A third aspect of the invention discloses a computer storage medium storing computer instructions which, when invoked, are adapted to perform part or all of the steps of the page building method disclosed in the second aspect of the invention.

Compared with the prior art, the embodiment of the invention has the following beneficial effects:

in the embodiment of the invention, the interface functions are clearly divided through the visual form design module and the visual flow design module, and all operations are visualized, so that the method is obtained. Advanced controls such as organizations, personnel, addresses and the like are added on the basis of the basic controls, and a user can quickly build a personalized form.

When the form is developed for the second time, the form capacity is enhanced based on the provided method through the form expansion module, the custom control can be expanded, and the custom content can be inserted into the page. The self-defined columns can be inserted into the table of the query page, the manual drag adjustment of the column width is supported, the display and the hiding of the screen options and the columns in the table can be controlled, and more self-defined functions can be added to the whole page on the basis of design.

By introducing the associated form units in the CRM system, mutual reference among the forms is realized, the use boundary of the forms is expanded, and the data among the forms are not isolated any more.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a low code based visualization CRM system according to an embodiment of the present invention;

FIG. 2 is a schematic flow chart of a page building method of a CRM system according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a computer storage medium according to an embodiment of the present invention;

FIG. 4 is a flowchart illustrating steps performed by a run-state renderer to render, according to an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The terms first, second and the like in the description and in the claims and in the above-described figures are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, apparatus, article, or article that comprises a list of steps or elements is not limited to only those listed but may optionally include other steps or elements not listed or inherent to such process, method, article, or article.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the invention. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.

In the embodiment of the invention, the interface functions are clearly divided through the visual form design module and the visual flow design module, and all operations are visualized, so that the method is obtained. Advanced controls such as organizations, personnel, addresses and the like are added on the basis of the basic controls, and a user can quickly build a personalized form. When the form is developed for the second time, the form capacity is enhanced based on the provided method through the form expansion module, the custom control can be expanded, and the custom content can be inserted into the page. The self-defined columns can be inserted into the table of the query page, the manual drag adjustment of the column width is supported, the display and the hiding of the screen options and the columns in the table can be controlled, and more self-defined functions can be added to the whole page on the basis of design. By introducing the associated form units in the CRM system, mutual reference among forms is realized, the use boundary of the forms is expanded, and data among the forms are not isolated and are respectively described in detail below.

Example 1

Referring to fig. 1, fig. 1 is a schematic structural diagram of a low-code-based visual CRM system according to an embodiment of the present invention. As shown in fig. 1, the low-code-based visualization CRM system may include a designer 101 and a running renderer 102, where the designer 101 includes a material stack, a visualization form design module, a visualization flow design module, and a form expansion module;

the material stack comprises a control library unit and an associated form unit; the control library unit is used for providing a standardized assembly for graphics, and the association form unit is used for associating and synchronizing data of other forms in the current form; further, the standardized component comprises a basic component and an enhancement control, wherein the basic component is a meta-component and can not be nested, the basic value filling capability of the form is supported, the enhancement control is a compound component, and the compound component can be nested, is usually compounded by a common component, a multi-layout component and a component supporting special capability, and supports the input of complex types of values. The association form element may provide a material component across applications, invoking data for other applications. I.e., after setting up the cross-application, the table data of other applications can be selected when selecting the data source. And meanwhile, the data of the current application can be called by other applications.

The basic components include single-line input frame, multiple-line input frame, digital input frame, single-selection frame, multiple-selection frame, date interval, explanatory text, telephone, etc

The enhancement controls include pictures, amounts, attachments, members, departments, addresses, forms, serial numbers, scores, and the like.

Accordingly, the layout components described above, particularly for beautifying forms, implementing the drawn form gauge Fan Buju, include, but are not limited to: grid layout, tab pages, side containers, basic layout, etc.

The visual form design module is used for providing a visual interface for a user to draw a page to be displayed in a dragging mode from the control library;

the visual flow design module is used for creating a flow, acquiring flow data from the visual form design module through a pre-packaged data transmission interface, and realizing flow operation corresponding to a standardized component in the visual interface according to the flow data;

the form expansion module is used for expanding the self-defining function of the design state designer;

the running state renderer 102 is used for rendering the basic information of the form according to the newly added schema data of the design state designer, and dynamically rendering the controls of different types according to the matched control types, so that the rendering of the visual interface is realized. The advanced screening of the query list dynamically sets matched query conditions according to column data in the list, all columns of the list are dynamically rendered according to data returned by a list interface, secondary development is supported to insert custom columns, data driving is achieved, and flexible page rendering is achieved. Run-state renderer event adoption

The system does not need repeated compiling of codes by a user, realizes a low code effect, can realize interaction only by dragging and configuration information simply configured on a visual interface in the whole process after the development of related components is completed, supports a component library rich in graphics, and rapidly configures various form interfaces in a dragging mode based on data of the system. The program development and design threshold is reduced, the code is not required to be modified, and the communication cost of service requirements and technical development is reduced. Multiple types of data are supported, and form data can be associated with each other. The forms can be associated with other existing forms through the function of the associated forms, so that the problem of data multiplexing among different forms is solved, the problem of data island is solved, and the corresponding field configuration and editing can be carried out on a visual interface, so that the system is flexible to change, and the generation of new BUG is reduced.

Further, the visual form design module further comprises an editing unit and a basic information configuration unit;

the editing unit is used for providing a visual interface, a basic information function of configuration fields and a formula editing function; the prefabricated form uses prefabricated config configuration, and single control in the control library binds different config configurations, and the config configuration is mounted to the vnode.

As can be appreciated, in one example, the formula edit function can be implemented to maintain a formula visualization field mapping table, weakening the visual edit boundary; deconstructing form operable field data, and tiling data retrieval; the editing area realizes semantic highlighting of operators and keywords; the code rules are separated from the display rules, the fields are divided regularly, and the unicode transcoding reconstruction rules are spliced, so that the effect of converting a specific operator by xss is realized; finally, json is exported through a back-end interface: form-render (rendering engine sdk) +DSL (json tree) =page, the calculation formula configuration can be performed on the numeric or monetary type fields added in the page, the calculation logic is dynamically bound during rendering, and when the dependent term input changes, the result is dynamically calculated according to the calculation formula.

The basic information configuration unit is used for configuring basic information of the form in the visual interface.

Further, the running state renderer comprises a creation module, a detail module and a list module;

the creation module is used for dynamically rendering the visual interface, changing the content of the visual interface according to the form data and providing output results according to the calculation formula and changing the visual interface;

the detail module is used for displaying corresponding pages to different users according to the user permission;

the list module is used for providing a dynamic rendering list query page function, a dynamic adjustment display list function, a query condition grouping and saving function and a data screening function according to the basic control, the enhancement control and the service control.

Further, as shown in fig. 4, fig. 4 discloses a flowchart of a step of rendering by the running state renderer, and the steps of rendering by the running state renderer include:

analyzing the newly added schema data of the design state designer;

matching different controls according to the control types;

dynamically rendering the page, and if the page is a creation module, carrying out mounting of a calculation formula and an event, giving the form linkage and calculation capability functions, otherwise, further matching whether to dynamically render the flow form of the detail module.

Further, the visual flow design module comprises a node configuration module, a template storage module and a permission configuration module;

the node configuration module is used for customizing flow nodes in the flow; specifically, process nodes such as an approval person, a copying person, a conditional branch and the like can be defined, different conditions can be set for the process trend, different processes are triggered according to different data in the use process, and flexible process setting is realized.

The template storage module is used for storing a plurality of versions of processes and carrying out switching multiplexing on the processes;

the authority configuration module is used for providing flow approval actions and configuring field editing authorities of flow nodes.

Further, the form expansion module comprises a business association unit, a form verification unit, a printing unit and a data pushing unit;

the business association unit is used for realizing the function of synchronizing the data of one form after the data of the other form is newly added or modified;

the form verification unit is used for configuring form data rules and carrying out rule verification on the form data when a user submits the form;

the printing unit is used for printing the form data according to the self-defined printing template;

the data pushing unit is used for providing a pushing function of data.

Further, the custom functions include expanding custom controls, inserting custom content in the page, querying custom columns in a table of the page, column width dragging tones, and displaying or hiding the screen options and columns in the table.

The embodiment of the application has the following advantages:

1. advanced screening: through the customized form fields and conditions, various wanted data can be flexibly, freely and accurately screened out

2. Formula editing: by using the custom form field as a variable, the mathematical function formula and the date function formula can freely build an automatic calculation result for different controls.

Available reference scenarios: according to the input quantity and unit price, automatically calculating the amount, the calculation formula can be set as: number is unit price.

3. And (3) rapidly building enterprise application in batches, and increasing power assisting business: the UI framework provided by the low-code platform comprises a basic component, an additional component, an associated control, a visual chart and the like, and can help build a functional prototype through simply dragging the spliced component so as to realize service growth.

4. Data intercommunication: association forms: the data of other forms are associated in the current form, and the data of the other forms are synchronous with the organization structure of other applications such as nails and the custom form data.

Cross-application data interactions: as the name implies, the cross-application data can be called for other applications, namely, after the cross-application data is set, the table data of other applications can be selected when the data source is selected, and meanwhile, the data of the current application can be called by other applications.

5. A kit: the suite can be circularly applied in different forms, and convenient, safe and intelligent operation experience is brought to users. Form data in the suite is initialized, user input is reduced, and data security is enhanced; according to the context in the form, linking with a service system in real time to acquire accurate data information; and checking the suite data at the time of submission.

6. The workflow: the process setting can be understood as approval, and each form can be set in the process, namely, approval setting.

Each flow can be further configured with a flow node, each task stage through which data needs to pass in the circulation process, and a specific responsible person can be added in the flow node; setting various operations such as approval, withdrawal and the like; the node's operation and visibility rights, e.g., editable, visible, etc., may also be configured.

Example two

Referring to fig. 2, fig. 2 is a schematic flow chart of a page building method of a CRM system according to an embodiment of the present invention. As shown in fig. 2, the page building method of the CRM system may include the following operations:

201, performing visual interface configuration in a visual form design module, and creating a flow in a visual flow design module;

202, the visual flow design module obtains flow data from the visual form design module through a pre-packaged data transmission interface, and realizes flow operation corresponding to a standardized component in the visual interface according to the flow data;

203 the run-state renderer dynamically renders the visual interface and flow.

For a specific description of the page building method of the CRM system, reference may be made to the specific description of the low-code-based visual CRM system, which is not described in detail herein.

Example III

Referring to fig. 3, fig. 3 is a schematic structural diagram of a computer storage medium according to an embodiment of the invention. As shown in fig. 3, an embodiment of the present invention discloses a computer storage medium 401, where the computer storage medium 401 stores computer instructions for executing steps in the page building method of the CRM system disclosed in the first embodiment of the present invention when the computer instructions are called.

The apparatus embodiments described above are merely illustrative, in which the modules illustrated as separate components may or may not be physically separate, and the components shown as modules may or may not be physical, i.e., may be located in one place, or may be distributed over multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

From the above detailed description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course by means of hardware. Based on such understanding, the foregoing technical solutions may be embodied in essence or in a portion contributing to the prior art in the form of a software product that may be stored in a computer readable storage medium including Read-only memory (ROM), random access memory (RandomAccessMemory, RAM), programmable Read-only memory (PROM), erasable programmable Read-only memory (ErasableProgrammableReadOnlyMemory, EPROM), one-time programmable Read-only memory (One-OnlyMemory, OTPROM), electrically erasable programmable Read-only memory (CD-ROM) or other optical disk memory, magnetic disk memory, tape memory, or any other medium that can be used for carrying or storing data that is readable by a computer.

Finally, it should be noted that: the embodiment of the invention discloses a low-code-based visual CRM system, a page building method and a storage medium, which are disclosed by the embodiment of the invention only as a preferred embodiment of the invention, and are only used for illustrating the technical scheme of the invention, but not limiting the technical scheme; although the invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that; the technical scheme recorded in the various embodiments can be modified or part of technical features in the technical scheme can be replaced equivalently; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.

Claims (9)

1. The visual CRM system based on the low codes is characterized by comprising a design state designer and an operation state renderer, wherein the design state designer comprises a material pile, a visual form design module, a visual flow design module and a form expansion module;

the material stack comprises a control library unit and an associated form unit; the control library unit is used for providing a standardized assembly for graphics, and the association form unit is used for associating and synchronizing data of other forms in the current form;

the visual form design module is used for providing a visual interface for a user to draw a page to be displayed in a dragging mode from the control library;

the visual flow design module is used for creating a flow, acquiring flow data from the visual form design module through a pre-packaged data transmission interface, and realizing flow operation corresponding to a standardized component in the visual interface according to the flow data;

the form expansion module is used for expanding the custom function of the design state designer;

the running state renderer is used for rendering the basic information of the form according to the schema data newly added by the design state designer, and dynamically rendering the controls of different types by matching the control types, so that the rendering of the visual interface is realized.

2. The low code based visualization CRM system of claim 1, wherein the visualization form design module further comprises an editing unit and a base information configuration unit;

the editing unit is used for providing a visual interface, a basic information function of configuration fields and a formula editing function;

the basic information configuration unit is used for configuring basic information of the form in the visual interface.

3. The low code based visualization CRM system of claim 1, wherein the run-state renderer comprises a creation module, a detail module, and a list module;

the creation module is used for dynamically rendering the visual interface, changing the content of the visual interface according to form data, outputting a result according to a calculation formula and changing the visual interface;

the detail module is used for displaying corresponding pages to different users according to the user permission;

the list module is used for providing a dynamic rendering list query page function, a dynamic adjustment display list function, a query condition grouping and saving function and a data screening function according to the basic control, the enhancement control and the service control.

4. The low code based visualization CRM system of claim 3, wherein the step when rendered by the run-state renderer comprises:

analyzing the newly added schema data of the design state designer;

matching different controls according to the control types;

and dynamically rendering the page according to the page type, if the page is the creation module, carrying out mounting calculation formulas and events, giving the form linkage and calculation capability functions, otherwise, further matching whether to dynamically render the flow form of the detail module.

5. The low code based visualization CRM system of claim 1, wherein the visualization process design module comprises a node configuration module, a template storage module, and a rights configuration module;

the node configuration module is used for customizing flow nodes in the flow;

the template storage module is used for storing a plurality of versions of processes and carrying out switching multiplexing of the processes;

the authority configuration module is used for providing flow approval actions and configuring field editing authorities of the flow nodes.

6. The low code based visualization CRM system of claim 1, wherein the form expansion module comprises a business association unit, a form verification unit, a printing unit, and a data pushing unit;

the business association unit is used for realizing the function of synchronizing the data of one form after the data of the other form is newly added or modified;

the form verification unit is used for configuring form data rules and carrying out rule verification on the form data when a user submits the form;

the printing unit is used for printing the form data according to the self-defined printing template;

the data pushing unit is used for providing a data pushing function.

7. The low code based visualization CRM system of claim 1, wherein the custom functions comprise expanding custom controls, inserting custom content in pages, querying custom columns in a table of pages, column wide drag-and-drop, and displaying or hiding the screen options and columns in the table.

8. A method for building a page of a CRM system, applied to the low-code based visual CRM system according to any one of claims 1 to 7, characterized in that it comprises:

performing visual interface configuration in the visual form design module, and creating a flow in the visual flow design module;

the visual flow design module obtains flow data from the visual form design module through a pre-packaged data transmission interface, and flow operation corresponding to a standardized component in the visual interface is realized according to the flow data;

and the running state renderer dynamically renders the visual interface and the flow.

9. A computer readable storage medium storing a computer program, which when executed by a processor implements the page building method of the CRM system of claim 8.