CN114942819A - Data field processing method, electronic device and computer readable storage medium - Google Patents
Data field processing method, electronic device and computer readable storage medium Download PDFInfo
- Publication number
- CN114942819A CN114942819A CN202210865467.7A CN202210865467A CN114942819A CN 114942819 A CN114942819 A CN 114942819A CN 202210865467 A CN202210865467 A CN 202210865467A CN 114942819 A CN114942819 A CN 114942819A
- Authority
- CN
- China
- Prior art keywords
- data field
- target
- component
- information
- components
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 42
- 238000000034 method Methods 0.000 claims description 50
- 238000012986 modification Methods 0.000 claims description 46
- 230000004048 modification Effects 0.000 claims description 46
- 238000012545 processing Methods 0.000 claims description 23
- 230000001360 synchronised effect Effects 0.000 claims description 16
- 238000012790 confirmation Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 6
- 230000000007 visual effect Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 15
- 230000008859 change Effects 0.000 description 10
- 238000012800 visualization Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 238000012417 linear regression Methods 0.000 description 7
- 150000001875 compounds Chemical class 0.000 description 6
- 238000010606 normalization Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000010801 machine learning Methods 0.000 description 4
- 238000013515 script Methods 0.000 description 4
- 238000004422 calculation algorithm Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000000284 resting effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a data field processing method, electronic equipment and a computer readable storage medium, and relates to the technical field of computers. The data field processing method comprises the following steps: after receiving data field configuration information input aiming at a preset port in a target assembly, configuring the data field of the preset port in the target assembly according to the data field configuration information; and then, judging whether the target data field corresponding to the data field configuration information is used by other components except the target components in the multiple components, and if the target data field is used by other components, configuring the target data field used in other components according to the data field configuration information. According to the data field processing method, the target data fields in the components are modified, and then the target data fields in other components are configured according to the use conditions of the target data fields in other components, so that the operation steps are reduced, and the use habits of users are better met.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a data field processing method, an electronic device, and a computer-readable storage medium.
Background
With the current popularity of microservices, visual modeling, and low-code development, more and more data fields are used by the interfaces between the various components. In development, management and batch update of the data fields are usually required, and currently, the management update operation is mainly realized by depending on manual operation or a related management system.
The management and the updating are carried out manually, the workload is large, and the maintenance is not easy; the conventional management system also has the problems of complicated steps, need of switching among multiple system components and high cost.
Disclosure of Invention
An object of the present invention is to provide a data field processing method, an electronic device and a computer readable storage medium, so as to overcome the above-mentioned shortcomings in the prior art.
In order to achieve the above purpose, the technical solutions adopted in the embodiments of the present application are as follows:
in a first aspect, an embodiment of the present application provides a data field processing method, where the method includes:
receiving data field configuration information input by aiming at a preset port in a target component;
configuring the data field of the preset port in the target component according to the data field configuration information;
judging whether a target data field corresponding to the data field configuration information is used by other components except the target component in the multiple components;
and if the target data field is used by the other components, configuring the target data field used in the other components according to the data field configuration information.
Optionally, the determining whether the target data field corresponding to the data field configuration information is used by another component other than the target component in all the components includes:
querying data field information of the plurality of components;
comparing the data field configuration information to data field information for the plurality of components;
and judging whether the target data field is used by other components or not according to the comparison result.
Optionally, after configuring the data field of the preset port in the target component according to the data field configuration information, the method further includes:
according to the data field configuration information, updating historical version information of the target data field corresponding to the target component in the data field version library, wherein the historical version information comprises: at least one version information of the target data field in the target component.
Optionally, the configuring, according to the data field configuration information, the target data field used in the other component includes:
presenting information of at least one of the other components using the target data field;
and if receiving synchronous modification confirmation operation aiming at the target data field and selection operation of other components, configuring the target data field of the target other component selected by the selection operation according to the data field configuration information.
Optionally, after configuring the target data field used in the other component according to the data field configuration information, the method further includes:
updating other version information of the target data field corresponding to the other component in the data field version library according to the data field configuration information, wherein the other version information includes: version information of the target data field in at least one of the other components.
Optionally, the data field configuration information is existing data field information selected for the preset port, or newly added data field information;
configuring the data field of the preset port in the target component according to the data field configuration information, including:
and setting the data field of the preset port as the target data field according to the existing data field information or the newly added data field information.
Optionally, the data field configuration information is data field modification information input for the preset port;
configuring the data field of the preset port in the target component according to the data field configuration information, including:
and modifying the data field of the preset port into the target data field information according to the data field modification information.
Optionally, if the data field modification information is: modifying information through a data field input by a data connection line associated with the preset port, wherein the data connection line is used for representing the data flow direction between the preset port and other component ports; the method further comprises:
and modifying the data fields of the other component ports into the target data fields according to the data field modification information.
In a second aspect, an embodiment of the present application further provides an electronic device, including: a processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, when the electronic device runs, the processor and the storage medium communicate through the bus, and the processor executes the program instructions to execute the steps of the data field processing method according to any one of the first aspect.
In a third aspect, an embodiment of the present application further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is executed by a processor to perform the steps of the data field processing method according to any one of the first aspect.
The beneficial effect of this application is: the embodiment of the application provides a data field processing method, which comprises the steps of receiving data field configuration information input aiming at a preset port in a target assembly, and configuring a data field of the preset port in the target assembly according to the data field configuration information; and then, judging whether the target data field corresponding to the data field configuration information is used by other components except the target components in the multiple components, and if the target data field is used by other components, configuring the target data field used in other components according to the data field configuration information. Different from the method that a user needs to actively manage a version library of data fields and then the modification of the data fields is synchronized to component examples manually or through scripts in the traditional technology, the data field processing method provided by the application is used for configuring the target data fields in other components by modifying the target data fields in the components and then by using the target data fields in other components. The operation steps are reduced, the learning cost of the version library is reduced, and the use habit of a user is better met.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a flowchart of a data field processing method according to an embodiment of the present application;
fig. 2 is a system structure diagram of a data field management system according to an embodiment of the present application;
FIG. 3 is a system block diagram of a data field management system according to another embodiment of the present application;
FIG. 4 is a schematic diagram of a front-end visual editing interface of a data field processing system according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a front-end visual editing interface of a data field processing system according to yet another embodiment of the present application;
FIG. 6 is a flowchart of a data field processing method according to another embodiment of the present application;
FIG. 7 is a schematic illustration of a visualization interface for front-end data field management according to an embodiment of the present application;
FIG. 8 is a schematic illustration of a visualization interface for front-end data field management according to yet another embodiment of the present application;
FIG. 9 is a schematic illustration of a visualization interface for front-end data field management according to yet another embodiment of the present application;
FIG. 10 is a flowchart of a data field processing method according to another embodiment of the present application;
FIG. 11 is a schematic diagram of a front-end visual editing interface of a wizard for creating custom components according to an embodiment of the present application;
FIG. 12 is a schematic diagram of a front-end visual editing interface of a data field processing system according to yet another embodiment of the present application;
FIG. 13 is a flowchart of a data field processing method according to yet another embodiment of the present application;
fig. 14 is a schematic view of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention.
In the present application, unless otherwise specifically stated or limited, "a plurality" in the description of the present invention means at least two, for example, two, three, unless otherwise specifically limited. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
With the current popularity of microservices, visual modeling, and low-code development, more and more data fields are used for interfaces between various components. At present, the management of versions of the data fields, the quick batch update of the data fields when the data fields change, and the quick reference of the existing data fields to construct new components are mainly realized by manual operation or by writing some scripts by developers, so that the management is high in workload and difficult to maintain.
Currently, a technology more advanced than manual management is to use a version management system such as an open source version control System (SVN), an open source distributed version control system (GIT), or a project object model (Maven) to manage data fields. However, these systems have several problems:
firstly, an additional warehouse needs to be established in the current data field processing mode, each modification needs to be submitted to the warehouse, and then manual synchronization is carried out on other components, so that the steps are complicated, and the workload is large; secondly, visual modeling and low-code development belong to independent systems, so that a user needs to additionally build a server and a software system, and the cost is high; in addition, it is inconvenient and costly for the user to switch between a plurality of systems.
Aiming at the existing problems, the embodiment of the application provides multiple possible implementation modes of the data field processing method so as to realize convenient and efficient processing of the data field. The following is explained by way of a number of examples in connection with the drawings. Fig. 1 is a flowchart of a data field processing method according to an embodiment of the present application, where the method may be implemented by an electronic device running the data field processing method, where the electronic device may be, for example, a terminal device or a server, and the data field processing method may be implemented by a data field processing system running on the electronic device. As shown in fig. 1, the method includes:
step 100: receiving data field configuration information input aiming at a preset port in the target component.
It should be noted that a component is a logical packaging manner, in this application, a target component may be any one component in a current program, and this application does not limit this; in addition, a specific input mode of the data field configuration information may be an input mode by a program code, and the like, and the present application is not limited thereto as long as the data field configuration information can be acquired.
In order to help users to better implement the data field processing method of the present application, the present application further provides a visualized data field processing system, which is described below. The data field processing system comprises a front end and a back end. Fig. 2 is a system structure diagram of a data field management system according to an embodiment of the present application, and referring to fig. 2, the data field management system includes a front end 101 and a back end 102, where the front end 101 is configured to display a related processing interface of a visual data field processing system, and the back end 102 is configured to process related data or process related operation information from the front end 101. The front end 101 and the back end 102 are in communication connection through a software communication mode or a hardware wiring mode, and the specific communication connection mode is not limited in the present application.
In one particular implementation, the data field processing system can be configured such that the system is more practical. Fig. 3 is a system structure diagram of a data field management system according to another embodiment of the present application, and referring to fig. 3, the data field management system includes a front end 101 and a back end 102, where the back end 102 includes a component instance management module 102a, a data field management module 102b, and a data field classification module 102 c. Among other things, the component instance management module 102a may manage the ports of the components, the data fields of the ports, and the data connections between the ports. Data field management module 102b may subscribe to or listen for changes to data fields in component instance management module 102a and, if a change occurs, will immediately synchronize the change to data field classification module 102 c. The data field classification module 102c, which may also be referred to as a version repository, may store a plurality of data fields and variations thereof.
A possible implementation of step 100 is described below in conjunction with the data field processing system of fig. 2 or fig. 3. In a possible implementation manner, fig. 4 is a schematic diagram of a front-end visual editing interface of a data field processing system, which may be shown in the front end of fig. 1, as shown in fig. 4, where the front-end visual editing interface of the data field processing system includes a flowchart editing area 202, in the flowchart editing area 202, a certain logic algorithm may be implemented by adding a connection relationship between components, and the application does not limit a specific algorithm, and in fig. 4, the application provides a logic algorithm implemented by 3 components, which specifically includes a component 1, a component 2, and a component 3, where a connection relationship exists between the component 1 and the component 2, and a connection relationship exists between the component 2 and the component 3. On the interface, a user can input data field configuration information aiming at any one component by configuring any one component, and the component is the target component. After user input, the electronic device running the method may receive data field configuration information entered for a pre-set port in the target component.
Optionally, with continued reference to fig. 4, a component repository 201 is further included on the front-end visual editing interface, and a plurality of component types are provided in the component repository 201, for example: the method comprises the steps of data processing components, component classification (two classes, multiple classes and the like can also be provided on the basis), regression components, clustering components, custom components and the like, wherein each type comprises at least one component, a user can select a proper component from a component warehouse, add the component in the component warehouse into a flow chart editing area 202 through operation modes such as selection confirmation, dragging and the like, and configure the component (for example, establishing a connection relation with other components, configuring relevant parameters of the component and the like), so that a certain business function is realized.
The above is only an example, and the data field processing method of the present application may be applied to a service scene built on a graphical interface, and the specific number of components, connection mode, and the like are not limited.
Step 110: and configuring the data field of the preset port in the target component according to the data field configuration information.
And after the data field configuration information is acquired, configuring the data field of the preset port in the target assembly. It should be noted that, depending on the type of target component, the ports owned by the target component may be different, and each component may have at least one of the following types of ports: input port, output port. The configuration information of the data field comprises the target component, the preset port of the target component and the data field to be configured, so that the configuration of the data field of the preset port in the target component can be realized according to the configuration information of the data field.
In one possible implementation, referring to fig. 4, the specific information in the data field configuration information may be obtained as follows: in fig. 4, a user may configure a data field included in any component in the flowchart editing region 202 by selecting a port of the component, where the component selected by the user is a target component, and the port of the component selected by the user is a preset port. The foregoing is merely an example, and in an actual implementation, there may be other data field configuration manners, for example, configuring the port data field by selecting a connection line in the flowchart editing area, which is not limited in this application.
Step 120: and judging whether the target data field corresponding to the data field configuration information is used by other components except the target component in the multiple components.
Since the target data field may also be used in other components (for example, some common data fields may be used in each component or in a plurality of components other than the target component), after the configuration of the data field of the preset port in the target component in the above step is completed, in order to ensure the correct operation of the process, it may be necessary to correspondingly adjust other components using the target data field, and therefore, it is first necessary to determine whether there are other components using the target data field.
Step 130: and if the target data field is used by other components, configuring the target data field used in other components according to the data field configuration information.
And if other components using the target data field exist, configuring the target data field used in the other components according to the data field configuration information. In a possible implementation manner, referring to fig. 4, after configuring a data field of a preset port in a target component according to data field configuration information, the visual editing interface of fig. 4 may prompt a user that there are other components using the target data field through a pop-up window, a highlight, a text comment, and the like.
It should be noted that, in the present application, the configuration of the target data fields of other components may be automatically configured, or the unified configuration of the target data fields in other group prices may be implemented by clicking a configuration confirmation case in the visual editing interface by a user, so as to further simplify the operation complexity of the user and implement batch processing of the data fields.
In a specific implementation manner, referring to fig. 2, after it is determined that the target data field is used by other components, a dialog box may be popped up through the front end 101 to prompt a user whether to synchronously modify the target data field of other components that refer to the same target data field, and if synchronous modification is to be performed, a confirmation operation may be performed by means of a key click, instruction input, or the like (for example, a "yes" key may be set on a popup window or a confirmation selection operation may be performed), and the target data field in other components may be modified in whole or in part. Wherein the global modification represents synchronously modifying the target data fields of all the component instances; partial modification means modification of the target data field in other components selected by the user or satisfying other preset conditions. And if the target data field does not exist in other components, the whole process is directly finished.
In another specific implementation manner, referring to fig. 3, if the target data field is used by other components (on the basis of which the target data field in other components needs to be modified synchronously), the front end 101 sends a list of instances of other components to be synchronized to the data field management module 102b of the back end 102. Data field management module 102b invokes component instance management module 102a to modify the data fields of the other component instances.
In another specific implementation, a flowchart of a machine learning application for training a linear regression model is taken as an example to illustrate a specific implementation of the above steps 100 to 130. Fig. 5 is a schematic diagram of a front-end visualization editing interface of a data field processing system according to another embodiment of the present application, which can be shown in the front end of fig. 2, as shown in fig. 5, and included in the flowchart editing area 202 is a machine learning application for training a linear regression model, including a reading database component 202a, a normalization component 202b, a linear regression component 202c, and a model library component 202 d. While the application is running, the read database component 202a will read the database and then send the read table data to the normalization component 202b over the data connection 202 e. The normalization component 202b normalizes the tabular data and sends it to the linear regression component 202c via data connection 202 f. The linear regression component 202c is trained using the normalized form data and then sends the trained model data to the model library component 202d via data connection 202 g. The model repository component 202d archives the received model data. It can be seen that the machine learning application described above includes two data fields: tabular data and model data, wherein the read database component 202a and normalization component 202b utilize tabular data, the model library component 202d utilizes model data, and the linear regression component 202c utilizes both. On this basis, for example, the target data field of the input port of the normalization component 202b is configured, and the target data field is also used in the database component 202a, so after the configuration of the normalization component 202b is completed, the target data field in the database component 202a needs to be configured.
To sum up, an embodiment of the present application provides a data field processing method, which configures a data field of a preset port in a target component according to data field configuration information after receiving the data field configuration information input for the preset port in the target component; and then, judging whether the target data field corresponding to the data field configuration information is used by other components except the target components in the multiple components, and if the target data field is used by other components, configuring the target data field used in other components according to the data field configuration information. Different from the traditional method that a user needs to actively manage a version library of a data field and then the modification of the data field is synchronized to a component instance manually or through scripts, the data field processing method provided by the application is used for modifying a target data field in a component and then configuring the target data field in other components through the use condition of the target data field in other components. The operation steps are reduced, the learning cost of the version library is reduced, and the use habit of a user is better met.
Optionally, on the basis of fig. 1, the present application further provides a possible implementation manner of a data field processing method, and fig. 6 is a flowchart of a data field processing method according to another embodiment of the present application; as shown in fig. 6, the determining whether the target data field corresponding to the data field configuration information is used by another component other than the target component in all the components includes:
step 601: data field information for a plurality of components is queried.
Step 602: the data field configuration information is compared to data field information for a plurality of components.
Step 603: and judging whether the target data field is used by other components or not according to the comparison result.
In one possible implementation, referring to fig. 4, after configuring a data field of a component port (for example, configuring a component 2), comparing a target data field configured in the component 2 with data field information of other components (e.g., component 1 and component 3) of the current flowchart, and finding whether a data field matching the target data field exists in data fields of the other components. If the data field matched with the target data field exists in other components, the target data field is used by other components; and if the data field matched with the target data field does not exist in other components, indicating that the target data field is not used by other components.
In a specific implementation manner, referring to the system structure diagram of the data field management system in fig. 3, the above steps 601 to 603 may be implemented by the following method: the data field management module 102b compares the target data field with the data field information in all other components to find out in which component instances the target data field is used.
The foregoing is merely an example, and other embodiments are possible in practical implementations, and the present application is not limited thereto.
Optionally, on the basis of fig. 1, this application further provides a possible implementation manner of a data field processing method, where after configuring, according to the data field configuration information, the data field of the preset port in the target component, the method further includes:
updating historical version information of the target data field corresponding to the target component in the data field version library according to the data field configuration information, wherein the historical version information comprises: at least one version information of the target data field in the target component.
And after the configuration of the data field is finished, updating the historical version information of the target data field corresponding to the target component in the data field version library according to the configuration information of the data field. In one possible implementation, referring to fig. 3, the component instance management module 102a may update the data field version library according to the change information of the data field, i.e., generate a new version number and history for the data field. The data field version library is positioned in the data field classification module and used for storing the related information of the data field and the history related information.
Based on the above embodiment, with continued reference to fig. 3, after updating the target data field in the other component, the data field management module 102b may update the modification of the data field of the other component instance to the data field version repository.
It should be noted that, in the foregoing embodiment, the component instance management module 102a updates the data field version library according to the change information of the data field, so as to automatically perform update for the system, thereby implementing that the system automatically records and stores the update.
In a possible implementation manner, fig. 7 is a schematic view of a visualization interface for front-end data field management provided by an embodiment of the present application; the interface can be displayed at the front end in fig. 2, as shown in fig. 7, the left side of fig. 7 is a data field list 301, and the detailed information of a selected data field can be displayed in a right data field detailed area 302 by selecting a certain data field in the data field list 301. The data field list 301 is an index area for organizing and displaying all data fields in a list or tree form; the data field detail area comprises data field specific field information and possibly operation controls (controls for viewing historical versions and other branch versions of the data field).
On the basis of fig. 7, the present application further provides a possible implementation manner of a visualization interface for front-end data field management, and fig. 8 is a schematic diagram of a visualization interface for front-end data field management provided in another embodiment of the present application, as shown in fig. 8, in a data field detail area 302, including: details of the data fields 302a, the current version number 302b, a view historical version button 302c, a view other version button 302 d. Information such as a field ID, a field name, a data type, and a default value of the data field is known through the detailed contents 302 a. The current version number 302b shows the version information of the current data field.
On this basis, by interacting with (e.g., clicking on) the view history version button 302c, the version number of the history version of the data field, the commit time, and from which component the data field originated (since the view history version is looking at the version information of the current data field in the current component, the source component here is the component of the current data field). On the basis, the detailed content of the data field in the historical version can be further checked by selecting the version (for example, clicking the version number of the historical version) and switching to the selected historical version. Furthermore, by interacting with (e.g., clicking on) the view other version button 302d, the version number of the data field as applied in the other component, the commit time, and from which component the data field originated (since it is the version information of the data field in the other component that is presented by the current detail 302a that is viewed) can be viewed. On the basis of the method, the detailed content of the selected data field in the version can be checked by selecting the version (for example, clicking the version number) and switching to the selected version.
In a specific implementation manner, fig. 9 is a schematic view of a visualization interface for front-end data field management according to still another embodiment of the present application, as shown in fig. 9, a data field list 301 includes guidance of data fields such as form data, model data, picture data, and video data, and can be selected (for example, form data is selected in fig. 9). Upon selection of a particular data field, the details of that field are presented in 302 a. The field details area 302 also shows the current version number, as well as a view historical version button 302c, and a view other version button 302 d. By clicking the view history version button 302c, the current interface displays the history version information of the data field in the history version interface 303 by performing switching display or superimposed display (since the form data is selected in fig. 9, the history version of the form data is shown); by clicking the view other version button 302d, the current interface displays other version information of the data field in the other version interface 304 by performing a toggle display or an overlay display (since the form data is selected in fig. 9, other versions of the form data are shown).
The foregoing is merely an example, and in an actual implementation, there may be other implementation manners of displaying or switching the content of the data field, the historical version, and other versions, which is not limited in this application.
Optionally, on the basis of fig. 1, the present application further provides a possible implementation manner of a data field processing method, and fig. 10 is a flowchart of a data field processing method provided in another embodiment of the present application; as shown in fig. 10, the configuring, according to the data field configuration information, the target data field used in the other component includes:
step 1001: information of at least one other component using the target data field is exposed.
Step 1002: and if receiving synchronous modification confirmation operation aiming at the target data field and selection operation of other components, configuring the target data field of the target other component selected by the selection operation according to the data field configuration information.
In a possible implementation manner, according to configuration information of a data field, information of the target data field in other components is displayed in the form of a popup window, a new interface window, a label, and the like, for example, after configuration of the target data field in a target component is completed, other components of the target data field are highlighted, or other components with the target data field are displayed in the popup window, and the like. On the information of the other displayed components, the user can select the components according to a specific display form, select other components needing to configure the target data field, and synchronously modify the target data field in the selected other components after confirmation.
If the synchronous modification confirmation operation aiming at the target data field is not accepted, other components are not modified. On this basis, the modification of the target data field at this time can also be ended by acquiring an end instruction. The ending instruction may be implemented by a user by clicking an ending button or a closing button provided on the interface, which is not limited in this application.
And if receiving synchronous modification confirmation operation aiming at the target data field and selection operation of other components, configuring the target data field of the target other component selected by the selection operation according to the data field configuration information, thereby realizing synchronous configuration of the target data field in other components.
Optionally, on the basis of fig. 1, this application further provides a possible implementation manner of a data field processing method, where after configuring, according to the data field configuration information, the target data field used in the other component, the method further includes:
updating other version information of the target data field corresponding to the other component in the data field version library according to the data field configuration information, wherein the other version information includes: version information of the target data field in at least one of the other components.
And after the target data fields in other components are configured, updating other version information of the target data fields corresponding to other components in the data field version library according to the data field configuration information. In one possible implementation, referring to FIG. 3, the data field management module 102b may update the modifications of the data fields of other component instances to the data field version repository. The data field version library is positioned in the data field classification module and used for storing the related information of the data field and the history related information.
It should be noted that, in the foregoing embodiment, the data field management module 102b may update the modification of the data field of the other component instance to the data field version library for automatic update by the system, so that the system automatically records and stores the synchronous configuration update of the other component.
For specific viewing and operation of other version information, refer to fig. 7, fig. 8, fig. 9 and corresponding embodiments, which are not described herein again.
Optionally, on the basis of fig. 1, the present application further provides a possible implementation manner of component configuration in the data field processing method, where the data field configuration information is existing data field information selected for the preset port, or newly added data field information; configuring the data field of the preset port in the target component according to the data field configuration information, including:
and setting the data field of the preset port as the target data field according to the existing data field information or the newly added data field information.
It should be noted that each component includes at least one port, and a user may select one port of the target component as a preset port by clicking or other selection operations, where in this application, the preset port may be an input port or an output port, and this application is not limited to this. In addition, the data field configuration information is the existing data field information selected for the preset port or newly added data field information; that is, in addition to the configuration of the existing data field information of the port, other data field information may be added to implement the configuration of the preset port, and the specific configuration mode is not limited in the present application. And selecting the configured existing data field in the preset port, or taking the newly added data field as the target data field.
It should be further noted that the target component in the present application may be an existing component (or a component in a component repository), or may be a customized component. The following takes a custom component as an example to describe how to configure the data fields of the component.
In a possible implementation manner, fig. 11 is a schematic diagram of a front-end visual editing interface of a wizard for creating a custom component according to an embodiment of the present application; as shown in FIG. 11, customization component wizard 401 contains a customization component 401a (illustrated by a rectangle) that can be implemented by adding input ports to customization component 401a via add input ports button 401b and adding output ports to customization component 401a via add output ports button 401c, with a corresponding data field selection button for each input port or output port added. For example, an input port 401d and two output ports 401e and 401f are respectively added in fig. 11, a data field can be selected for each port by clicking a data field selection button corresponding to each port, for example, clicking a data field selection button 401g of the output port 401f pops up a data field selection dialog box 402, the dialog box lists all existing data fields to be selected (i.e., selects existing data field information), and on this basis, a new data field can also be uploaded (i.e., uploads new data field information). After the above operations are completed, the input port and the output port of the custom component and the data field thereof are stored in the backend, and in the following flow chart, the user can refer to the custom component. It should be noted that, in a specific implementation, a blank custom component may also be directly used for building a flowchart in the flowchart editing area 202, and then the custom component is configured according to the above method.
In a specific implementation, the custom component can be represented by geometric shapes such as a rectangular box, and the input port and the output port of the custom component can be represented by geometric shapes such as a circle resting on the edge of the geometric shape of the custom component; the method comprises the steps that input ports or output ports are added to a user-defined assembly through buttons, each input/output port corresponds to a data field selection button, and a user can select one data field from all existing data fields for the port or upload a new data field through the data field selection buttons; after the operation is completed, all information of the user-defined component, including the input/output port and the corresponding data field, is sent to the component instance management module for application and storage.
In another specific implementation manner, the front-end visual editing interface of the wizard of the custom component comprises: representing the geometric shapes such as a rectangular frame of the self-defined assembly, and the number of the geometric shapes is 1; representing the geometric shapes such as circles of the input and output ports of the self-defined assembly, wherein the number of the geometric shapes is 1 or more, and the geometric shapes are controlled by a user; a button for adding or deleting an input/output port; a button for setting a data field of the input/output port.
For example, the components may also be configured according to the above manner on the basis of the existing components, and the configured components may also be saved as a new component for subsequent call.
Optionally, on the basis of fig. 1, the present application further provides a possible implementation manner of component configuration in the data field processing method, where the data field configuration information is data field modification information input for the preset port; configuring the data field of the preset port in the target component according to the data field configuration information, including:
and modifying the data field of the preset port into the target data field information according to the data field modification information.
In a possible implementation manner, in addition to adding a new data field by uploading a data field, the data field may also be modified, and according to the modification information of the data field, the data field of the preset port of the target component is modified to be the target data field information.
It should be noted that, the modification information of the data field input by the preset port may be performed by modifying the configuration on the configuration interface of the target component, modifying through a configuration command, performing a visual configuration on the target component on the flowchart interface, and the like, which is not limited in this application as long as the modification of the target data field can be achieved.
Optionally, on the basis of the foregoing embodiment, the present application further provides a possible implementation manner of the data field processing method, where if the data field modification information is: modifying information through a data field input by a data connection line associated with the preset port, wherein the data connection line is used for representing the data flow direction between the preset port and other component ports; the method further comprises:
and modifying the data fields of the other component ports into the target data fields according to the data field modification information.
In one possible implementation, the information may be modified through a data field input by a data connection associated with the predetermined port, where the data connection may characterize a data flow direction between the predetermined port and the other component ports. That is, the data field modification information may be obtained based on the data link, for example, by creating a new data link, deleting a data link, modifying components at two ends of the data link, and the like, which is not limited in the present application.
In a specific implementation manner, referring to fig. 5, a component may be dragged from the component repository 201 to the flowchart editing area 202 to create an isolated component, where the component has no connection relationship with other components in the flowchart editing area 202, and it needs to be described that the component may be a custom component without a port or a component with a preset port, which is not limited in this application. The compound operation is realized by releasing by leading out data connection lines from the ports of other components, connecting the data connection lines to the self-defined component, or connecting the data connection lines to the ports of other components which are not connected. If the compound operation is a compound operation between the self-defined component and other components, the compound operation comprises the steps of creating a port for the self-defined component and adding a data connection between the port leading out the data connection and the port just created by the self-defined component. If the compound operation does not include the custom component, the compound operation adds a data connection line between the ports of the leading-out and leading-in data connection lines of the two components. It should be noted that the data field in the port for leading in the data connection line may be completely consistent with or inconsistent with the data field in the port for leading out the data connection line, which is not limited in this application. Furthermore, if the port from which the data wire is drawn is an output port, then the incoming port (or the port created by the custom component) is an input port; if the port from which the data wire is drawn is an input port, then the incoming port (or the port created by the custom component) is an output port. It should be noted that the specific type of the data line to be led out may be selectively set by a user, or may also be determined according to a preset rule according to the specific position where the data line is led out, which is not limited in this application.
And after the data connection is established, modifying the data field of the introduced other component port into the target data field. If the data field in the port of the incoming data connection line can be completely consistent with the data field in the port of the outgoing data connection line, the data field in the port of the incoming data connection line is corresponding to the data field in the port of the outgoing data connection line, namely all the data fields in the port of the outgoing data connection line are led into the component corresponding to the port of the incoming data connection line through the data connection line; if the component corresponding to the port for leading in the data connection line is the self-defined component, all data fields in the port for leading out the data connection line can be led into the self-defined component through the data connection line.
If at least one data field in the port for leading in the data connection line can be inconsistent with at least one data field in the port for leading out the data connection line, corresponding the data fields consistent with the data fields in the port for leading out the data connection line according to the method, feeding the inconsistent data fields back to the front end in the forms of popup windows, marks or new windows and the like, presenting the inconsistent data fields to a user by the front end for selection, and determining whether the inconsistent data fields need to be led into the components corresponding to the port for leading in the data connection line. At this time, the user may complete modification of the data field in the form of newly creating the data field, matching the data field of the ingress side and the egress side (i.e., corresponding to the egress data connection port) in the component on the ingress side (i.e., corresponding to the ingress data connection port). On the basis, because the corresponding relation of the two ends of the data connecting line exists in the data connecting line, the synchronous modification of the data fields in the construction of the two ends of the data connecting line can be realized by modifying the data fields in the data connecting line.
In a specific implementation manner, fig. 12 is a schematic diagram of a front-end visual editing interface of a data field processing system according to yet another embodiment of the present application; taking fig. 12 as an example, the present application provides a visualized data field processing method. It should be noted that fig. 12 illustrates a visualization modeling for machine learning, but in a specific implementation, the flow of other methods may also be used, so that specific forms of the flowcharts may be different, but specific data field modification manners are consistent, and the specific forms of the flowcharts and the like are not limited in this application.
Referring to FIG. 12, FIG. 12 replaces the linear regression component 202c in FIG. 5 with a custom component, at this time, the custom component can be dragged from the component repository 201 to the flowchart editing area 202 to create a custom component 502 without any port, in FIG. 12, a data line 504 can be led out from the output port 503 of the component 202b and put on the custom component 502, then the system automatically creates an input port 505 for the custom component 502, and the data field of the input port 505 is directly referenced from the output port 503, i.e. the data field is consistent. Similarly, the user may extract data from the custom component to the ports of other components to complete the above operations, for example, the data in the custom component is extracted through the data connection via the output port 506 and the data connection 507 of other ports, and after the data is extracted, the data field in the model library 202d is consistent with the data field in the custom component.
In a specific implementation, the custom component can be quickly used in the flowchart editing area, and specifically, a label or an icon representing the custom component is included in the component repository;
a control for creating an operation of a blank custom component by dragging a tab or icon representing the custom component into the flowchart edit area; and (3) leading out wires from the ports of other components to the custom component, or leading out wires from the custom component to the ports of other components, so as to create a control for the custom component for the operation of leading out the port with the same data field as the port to which the wires or the wires are led out.
The modification information of the data field is acquired by processing the data connecting line, so that a user does not need to manually create a port and select the data field, the operation efficiency is improved, and the probability of misoperation is reduced.
On the basis of the above embodiments, the present application provides a possible specific implementation manner, and the data field processing method of the present application is explained from the perspective of user operation and front-end and back-end interaction. The application provides three ways to implement the processing of data fields: first, a data link can be double-clicked in the flowchart editing area 202; secondly, right clicking a certain data connection line and then selecting a modified data field in a right-click menu to carry out; third, the modification is directly made on the visualization interface (fig. 7 or fig. 8 or fig. 9) of the data field management.
If the modification of the data field is performed via the first data connection, the data fields of the ports at both ends of the data connection are modified together after the modification.
Fig. 13 is a flowchart of a data field processing method according to yet another embodiment of the present application, as shown in fig. 13, the method includes:
step 131: the user adds or modifies data fields at the front end 101.
Step 132: the front end 101 sends the modification information to the component instance management module 102a of the back end 102 for application and storage.
Step 133: the component instance management module 102a notifies the data field management module 102b of the change information of the data field by a message or a callback function. This step is premised on the data field management module 102b subscribing to the data field change message or registering a data field change callback function with the component instance management module 102a at system startup.
Step 134: the component instance management module 102a updates the data field version library according to the change information of the data field, i.e. generates a new version number and history for the data field. The implementation logic inside the data field version library is not within the scope of the present invention and therefore will not be described in detail herein.
Step 135: the data field management module 102b queries the component instance management module 102a for data field information for all component instances.
Step 136: the data field management module 102b compares the change information of the data field with the data field information of all component instances to find out in which component instances the changed data field is used. The user may subsequently want to modify these data fields synchronously, but manual modification one by one results in a heavy workload and easily results in omissions.
Step 137: based on the comparison in step 136, a determination is made as to whether additional components are using the modified data field. If yes, go to the next step 138; if not, the whole process is directly finished.
Step 138: the notification front end 101 pops up a dialog box to prompt the user whether to synchronously modify the data fields of other component instances that reference the same data fields, and if synchronous modification is desired, whether to synchronously modify the data fields of all component instances, or to synchronously modify the data fields of only a portion of the component instances.
Step 139: judging whether the user selects synchronous modification, if yes, entering the next step, step 140; if synchronous modification is not selected, the whole process is directly finished.
Step 140: the front end 101 sends a list of other component instances to be synchronized to the data field management module 102b of the back end 102.
Step 141: the data field management module 102b invokes the component instance management module 102a to modify the data fields of the other component instances.
Step 142: the data field management module 102b updates the modifications of the data fields of the other component instances to the data field version repository. This step is similar to step 134.
In summary, unlike the conventional method that requires the user to actively manage the version library of the data field and then synchronize the modification of the data field to the component instance manually or by script, the method of the present application is that the user directly modifies the component instance and then the system automatically synchronizes to the version library. Therefore, all data fields are managed in a visual mode, the use threshold is lowered, the used technology can reduce operation steps and the learning cost of a version base, and the use habit of a user is better met. Meanwhile, a graphical means of using a connecting line to refer to the data field can help a user to construct a custom assembly more conveniently, and the use efficiency is improved. In addition, the method and the device can also be used for rapidly updating all the components when the data fields are changed.
For the following description, specific implementation procedures and technical effects of the electronic device and the storage medium provided by the present application are described above, and will not be described again below.
Embodiments of the present application provide possible implementation examples of an electronic device, which can execute the data field processing method provided in the foregoing embodiments. Fig. 14 is a schematic diagram of an electronic device according to an embodiment of the present application, where the electronic device may be integrated in a terminal device or a chip of the terminal device, and the terminal may be a computing device with a data processing function.
The electronic device includes: a processor 1401, a storage medium 1402 and a bus, the storage medium storing program instructions executable by the processor, the processor and the storage medium communicating via the bus when the control device is running, the processor executing the program instructions to perform the steps of the data field processing method described above when executed. The specific implementation and technical effects are similar, and are not described herein again.
The embodiment of the present application provides a possible implementation example of a computer-readable storage medium, which is capable of executing the data field processing method provided in the foregoing embodiment, where the storage medium stores a computer program, and the computer program is executed by a processor to execute the steps of the data field processing method.
A computer program stored in a storage medium may include instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor (which may be a processor) to perform some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
In the several embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method for processing data fields, the method comprising:
receiving data field configuration information input aiming at a preset port in a target assembly;
configuring the data field of the preset port in the target assembly according to the data field configuration information;
judging whether a target data field corresponding to the data field configuration information is used by other components except the target component in the multiple components;
and if the target data field is used by the other components, configuring the target data field used in the other components according to the data field configuration information.
2. The method of claim 1, wherein the determining whether the target data field corresponding to the data field configuration information is used by the other component than the target component in all components comprises:
querying data field information of the plurality of components;
comparing the data field configuration information to data field information for the plurality of components;
and judging whether the target data field is used by other components or not according to the comparison result.
3. The method of claim 1, wherein after configuring the data field of the preset port in the target component according to the data field configuration information, the method further comprises:
updating historical version information of the target data field corresponding to the target component in a data field version library according to the data field configuration information, wherein the historical version information comprises: at least one version information of the target data field in the target component.
4. The method of claim 1, wherein the configuring the target data field used in the other component according to the data field configuration information comprises:
presenting information of at least one of the other components using the target data field;
and if receiving synchronous modification confirmation operation aiming at the target data field and selection operation of other components, configuring the target data field of the target other component selected by the selection operation according to the data field configuration information.
5. The method of claim 1, wherein after said configuring the target data field used in the other component according to the data field configuration information, the method further comprises:
updating other version information of the target data field corresponding to the other component in a data field version library according to the data field configuration information, wherein the other version information comprises: version information of the target data field in at least one of the other components.
6. The method of claim 1, wherein the data field configuration information is existing data field information or newly added data field information selected for the predetermined port;
configuring the data field of the preset port in the target component according to the data field configuration information, including:
and setting the data field of the preset port as the target data field according to the existing data field information or the newly added data field information.
7. The method of claim 1, wherein the data field configuration information is data field modification information input for the predetermined port;
configuring the data field of the preset port in the target component according to the data field configuration information, including:
and modifying the data field of the preset port into the target data field information according to the data field modification information.
8. The method of claim 7, wherein if the data field modification information is: modifying information through a data field input by a data connection line associated with the preset port, wherein the data connection line is used for representing the data flow direction between the preset port and other component ports; the method further comprises:
and modifying the data fields of the other component ports into the target data fields according to the data field modification information.
9. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing program instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is running, the processor executing the program instructions to perform the steps of the data field processing method according to any one of claims 1 to 8 when executed.
10. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the data field processing method according to one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210865467.7A CN114942819B (en) | 2022-07-22 | 2022-07-22 | Data field processing method, electronic device and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210865467.7A CN114942819B (en) | 2022-07-22 | 2022-07-22 | Data field processing method, electronic device and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114942819A true CN114942819A (en) | 2022-08-26 |
| CN114942819B CN114942819B (en) | 2022-11-11 |
Family
ID=82910729
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210865467.7A Active CN114942819B (en) | 2022-07-22 | 2022-07-22 | Data field processing method, electronic device and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114942819B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708536A (en) * | 2020-06-18 | 2020-09-25 | 深圳前海微众银行股份有限公司 | Page building method and equipment based on component configuration and readable storage medium |
| CN112104617A (en) * | 2020-08-27 | 2020-12-18 | 中国平安财产保险股份有限公司 | Authority management method, device, equipment and storage medium of microservice |
| WO2021032598A1 (en) * | 2019-08-16 | 2021-02-25 | Eigen Technologies Ltd | Training and applying structured data extraction models |
| CN112487112A (en) * | 2020-12-17 | 2021-03-12 | 江苏苏宁云计算有限公司 | Method and device for linkage configuration of components, computer equipment and storage medium |
| CN113031947A (en) * | 2021-03-05 | 2021-06-25 | 苏州帝博信息技术有限公司 | Configuration data management method and device used in interface design tool |
| CN113268226A (en) * | 2021-06-24 | 2021-08-17 | 中国平安人寿保险股份有限公司 | Page data generation method and device, storage medium and equipment |
| CN114116108A (en) * | 2021-11-30 | 2022-03-01 | 平安科技（深圳）有限公司 | Dynamic rendering method, device, equipment and storage medium |
| CN114647627A (en) * | 2020-12-17 | 2022-06-21 | 国际商业机器公司 | Ordering datasets based on data attributes |
-
2022
- 2022-07-22 CN CN202210865467.7A patent/CN114942819B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021032598A1 (en) * | 2019-08-16 | 2021-02-25 | Eigen Technologies Ltd | Training and applying structured data extraction models |
| CN111708536A (en) * | 2020-06-18 | 2020-09-25 | 深圳前海微众银行股份有限公司 | Page building method and equipment based on component configuration and readable storage medium |
| CN112104617A (en) * | 2020-08-27 | 2020-12-18 | 中国平安财产保险股份有限公司 | Authority management method, device, equipment and storage medium of microservice |
| CN112487112A (en) * | 2020-12-17 | 2021-03-12 | 江苏苏宁云计算有限公司 | Method and device for linkage configuration of components, computer equipment and storage medium |
| CN114647627A (en) * | 2020-12-17 | 2022-06-21 | 国际商业机器公司 | Ordering datasets based on data attributes |
| CN113031947A (en) * | 2021-03-05 | 2021-06-25 | 苏州帝博信息技术有限公司 | Configuration data management method and device used in interface design tool |
| CN113268226A (en) * | 2021-06-24 | 2021-08-17 | 中国平安人寿保险股份有限公司 | Page data generation method and device, storage medium and equipment |
| CN114116108A (en) * | 2021-11-30 | 2022-03-01 | 平安科技（深圳）有限公司 | Dynamic rendering method, device, equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| ZHEN ZHANG ET AL.: ""On-the-Field Test and Configuration Infrastructure for 2-D-Mesh NoCs in Shared-Memory Many-Core Architectures"", 《IEEE TRANSACTIONS ON VERY LARGE SCALE INTEGRATION SYSTEMS》 * |
| 孙逊 等: ""基于改进RBAC模型的通用用户权限组件涉及与实现"", 《软件导刊》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114942819B (en) | 2022-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10831453B2 (en) | Connectors framework | |
| CN111367513B (en) | Code complement method, device, electronic equipment and storage medium | |
| CN111666740A (en) | Flow chart generation method and device, computer equipment and storage medium | |
| US20180268515A1 (en) | Information processing method and client | |
| CN108388623B (en) | ER relationship generation method and device, computer equipment and storage medium | |
| CN115712413A (en) | Low code development method, device, equipment and storage medium | |
| WO2023138472A1 (en) | Document comment display method and apparatus, device and medium | |
| CN115729534A (en) | Method for creating and displaying low-code page, device, equipment and medium | |
| US20130231973A1 (en) | Business analysis design support device, business analysis design support method and non-transitory computer-readable medium containing business analysis design support program | |
| CN114942819B (en) | Data field processing method, electronic device and computer readable storage medium | |
| CN113377318A (en) | Display screen control method, device and system | |
| CN113010157A (en) | Code generation method and device | |
| CN113312052A (en) | Component calling method and device, electronic equipment and storage medium | |
| CN115629990B (en) | Service testing method and device, electronic equipment and storage medium | |
| WO2019242167A1 (en) | Method for managing requirements and computer device | |
| CN114281310A (en) | Page frame setting method, device, equipment, storage medium and program product | |
| CN114675921A (en) | Method and device for customizing interface, electronic equipment and storage medium | |
| US10198150B2 (en) | Cross database data selection and correlation interface | |
| CN114564662A (en) | Page guiding method and device, electronic equipment, medium and product | |
| CN114297443A (en) | Processing method, device and equipment for graph data query statement and storage medium | |
| US20160224918A1 (en) | Business influenced part extraction method and business influenced part extraction device based on business variation | |
| CN114327709A (en) | Control page generation method and device, intelligent device and storage medium | |
| CN112328149A (en) | Picture format setting method and device and electronic equipment | |
| CN112231802A (en) | Multi-window examination method and device of BIM file and computer storage medium | |
| CN112637522A (en) | Signal source switching method and device of display system, storage medium and processor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310053 No. 309 Liuhe Road, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Zhongkong Technology Co.,Ltd. Country or region after: China Address before: 309 Liuhe Road, Binjiang District, Hangzhou, Zhejiang 310000 Patentee before: ZHEJIANG SUPCON TECHNOLOGY Co.,Ltd. Country or region before: China |