CN112800030A - Process component data management method and device and computer readable storage medium - Google Patents
Process component data management method and device and computer readable storage medium Download PDFInfo
- Publication number
- CN112800030A CN112800030A CN202110180629.9A CN202110180629A CN112800030A CN 112800030 A CN112800030 A CN 112800030A CN 202110180629 A CN202110180629 A CN 202110180629A CN 112800030 A CN112800030 A CN 112800030A
- Authority
- CN
- China
- Prior art keywords
- component
- data
- component data
- components
- instance
- 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
- 238000000034 method Methods 0.000 title claims abstract description 315
- 230000008569 process Effects 0.000 title claims abstract description 266
- 238000013523 data management Methods 0.000 title claims abstract description 18
- 238000009877 rendering Methods 0.000 claims description 8
- 230000000712 assembly Effects 0.000 claims description 6
- 238000000429 assembly Methods 0.000 claims description 6
- 230000001419 dependent effect Effects 0.000 claims description 6
- 238000007726 management method Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 230000008901 benefit Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012905 input function Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention provides a method and a device for managing component data of a process and a computer readable storage medium, wherein the method comprises the following steps: receiving subscription information of the display type component of the first process, wherein the subscription information is used for subscribing component data provided by a target input type component of a target process; receiving issuing information of component data provided by an input type component of each process in each process instance of starting operation of each process; in a first process example of starting operation of a first process, receiving a data request sent by a display type component of the first process, and calling a matching rule based on the data request and subscription information to determine corresponding release information; and acquiring the component data of the target input type component based on the release information, and providing the component data to the display type component of the first flow. By using the method, the unified management of the page component data is realized, and the problem of data management confusion in a complex service scene is avoided.
Description
Technical Field
The invention belongs to the field of data processing, and particularly relates to a method and a device for managing component data of a process and a computer-readable storage medium.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
The flow customization platform can realize the on-line design, deployment, release and operation of the business flow, greatly improve the landing efficiency of various business scenes on the system platform and avoid the heavy background code development in the traditional mode.
Many management systems in the market integrate a flow customization function at present, but are mainly applied to examination and approval business scenes and only support simple input form page layout. In order to improve the application range of the flow customization platform and support more service flows to land, the scheme provides a flow customization scheme supporting complex service scenes, and the scheme can be used for solving the problem of rapid landing deployment of operation flows of most service scenes on the system platform.
At present, more and more management systems realize a flow customization function, but are mainly used for solving the problem of quick flow landing in a specific scene, are mainly applied to examination and approval scenes and only can process simple business data relation; when complex data association relationship exists between nodes before and after the business process, the data processing capacity of the components becomes very weak.
Disclosure of Invention
In view of the above problems in the prior art, a method, an apparatus, and a computer-readable storage medium for managing component data of a process are provided.
The present invention provides the following.
In a first aspect, a method for managing component data of a process is provided, including: receiving subscription information of a display type component of a first process, wherein the subscription information is used for subscribing component data provided by a target input type component of a target process; in each process instance of starting operation of each process, receiving release information of component data provided by an input type component of each process; in a first process instance of starting operation of the first process, receiving a data request sent by the exhibition type component of the first process, and calling a matching rule based on the data request and the subscription information to determine the corresponding release information; and acquiring component data of a target input type component based on the release information, and providing the component data for the display type component of the first flow.
In some possible embodiments, the method further includes a page assembly step of each of the processes, specifically including: a first-level configuration step, which is to construct a plurality of assemblies with different layout structures and display forms by taking the node elements as units to form an assembly library; and a second-stage configuration step, namely determining required components according to the operation requirements of each process by taking the components of the component library as basic units, adjusting the layout structure relationship among the components, and finally constructing a process page containing one or more components.
In some possible embodiments, the method further comprises: in the secondary configuration step, a flow page containing one or more components is constructed by performing online dragging and pulling on the components in the component library.
In some possible embodiments, the component library is integrated with extension components developed by a third party.
In some possible embodiments, the matching rule comprises one or more sub-matching rules of: a source rule indicating that in the first process instance of the first process, the exhibited component matches to component data of the same process instance of the same process; an inheritance rule indicating that in the first process instance of the first process, the exposed component matches to component data of a parent process instance of the first process instance; a custom rule indicating that in the first process instance of the first process, the exposed component matches to component data of a custom process instance, wherein the custom process instance is determined based on an input dependent instruction.
In some possible embodiments, the method further comprises: integrating a plurality of the sub-matching rules and setting a priority for each sub-matching rule; and determining the publication information provided by a target input-type component of a target process based on the subscription information and matching rules, further comprising: each sub-matching rule is adapted one by one from high to low according to the priority, and if any sub-matching rule is matched, the corresponding release information is searched according to any sub-matching rule; and if all the sub-matching rules do not realize matching, discarding the data request.
In some possible embodiments, obtaining component data of the target input-type component based on the release information further includes: querying a database based on the release information to obtain component data for the target input-type component; and receiving the issuing information of the component data provided by the process components of each process at each process instance operation stage of each process, and storing the component data into the database.
In some possible embodiments, after receiving the data request sent by the presentation component of the first process, the method further includes: providing the component data of the target input type component to the presentation type component of the first process, so that the presentation type component can execute page rendering in a browser based on the component data of the target input type component.
In a second aspect, there is provided a device for managing component data of a process, including: the subscription module is used for receiving subscription information of the display type assembly of the first process, and the subscription information is used for subscribing assembly data provided by a target input type assembly of a target process; the release module is used for receiving release information of component data provided by the input type components of each process in each process instance of each process starting operation; the matching module is used for receiving a data request sent by the exhibition component of the first flow in a first flow instance in which the first flow starts to run, and calling a matching rule based on the data request and the subscription information to determine the corresponding release information; and the data providing module is used for acquiring component data of the target input type component based on the release information and providing the component data to the display type component of the first flow.
In some possible embodiments, the apparatus further includes a page assembly module of each of the processes, specifically including: the first-level configuration unit is used for constructing a plurality of assemblies with different layout structures and display forms by taking the node elements as units to form an assembly library; and the secondary configuration unit is used for determining required components according to the operation requirements of each process by taking the components of the component library as basic units, adjusting the layout structure relationship among the components and finally constructing a process page containing one or more components.
In some possible embodiments, the apparatus is further configured to: in the secondary configuration step, a flow page containing one or more components is constructed by performing online dragging and pulling on the components in the component library.
In some possible embodiments, the component library is integrated with extension components developed by a third party.
In some possible embodiments, the matching rule comprises one or more sub-matching rules of: a source rule indicating that in the first process instance of the first process, the exhibited component matches to component data of the same process instance of the same process; an inheritance rule indicating that in the first process instance of the first process, the exposed component matches to component data of a parent process instance of the first process instance; a custom rule indicating that in the first process instance of the first process, the exposed component matches to component data of a custom process instance, wherein the custom process instance is determined based on an input dependent instruction.
In some possible embodiments, the matching module is further configured to: integrating a plurality of the sub-matching rules and setting a priority for each sub-matching rule; and each sub-matching rule is adapted one by one from high to low according to the priority, and if any one sub-matching rule is matched, the corresponding release information is searched according to any one sub-matching rule; and if all the sub-matching rules do not realize matching, discarding the data request.
In some possible embodiments, the data providing module is further configured to: querying a database based on the release information to obtain component data for the target input-type component; and receiving the issuing information of the component data provided by the process components of each process at each process instance operation stage of each process, and storing the component data into the database.
In some possible embodiments, the apparatus is further configured to: after receiving the data request sent by the presentation component of the first process, providing the component data of the target input component to the presentation component of the first process, so that the presentation component performs page rendering in a browser based on the component data of the target input component.
In a third aspect, an apparatus for managing component data of a process is provided, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform: the method of the first aspect.
In a fourth aspect, there is provided a computer readable storage medium storing a program which, when executed by a multi-core processor, causes the multi-core processor to perform the method of the first aspect.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: in this embodiment, by using the component data management scheme of the publish-subscribe mechanism, unified management of page component data can be achieved, and the problem of data management confusion in a complex service scenario is avoided.
It should be understood that the above description is only an overview of the technical solutions of the present invention, so as to clearly understand the technical means of the present invention, and thus can be implemented according to the content of the description. In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.
Drawings
The advantages and benefits described herein, as well as other advantages and benefits, will be apparent to those of ordinary skill in the art upon reading the following detailed description of the exemplary embodiments. The drawings are only for purposes of illustrating exemplary embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like elements throughout. In the drawings:
FIG. 1 is a flow chart illustrating a method for managing component data according to an embodiment of the present invention;
FIG. 2 is an assembly diagram of a flow page according to an embodiment of the invention;
FIG. 3 is a diagram illustrating matching rules according to an embodiment of the present invention;
FIG. 4 is a block diagram of a component data management apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a device for managing component data according to an embodiment of the present invention.
In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In the description of the embodiments of the present application, it is to be understood that terms such as "including" or "having" are intended to indicate the presence of the features, numbers, steps, actions, components, parts, or combinations thereof disclosed in the specification, and are not intended to preclude the presence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.
Unless otherwise stated, "/" indicates an OR meaning, e.g., A/B may indicate A or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone.
The terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first," "second," etc. may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present application, "a plurality" means two or more unless otherwise specified.
All code in this application is exemplary and variations will occur to those skilled in the art based upon the programming language used, the specific needs and personal habits without departing from the spirit of the application.
Fig. 1 is a flowchart illustrating a component data management method according to a flowchart of an embodiment of the present application, in which an execution subject may be one or more electronic devices from a device perspective; from the program perspective, the execution main body may accordingly be a program loaded on these electronic devices.
As shown in fig. 1, the method provided by this embodiment may include the following steps:
s101, receiving subscription information of the display type component of the first process.
Specifically, in the process assembly stage of the first process, the control center receives subscription information of the display type component of the first process, where the subscription information is used for subscribing component data provided by the target input type component of the target process. The subscription information may include: a first process ID, an exposed component ID, a target process ID, and a target input component ID.
The input type component is a component which can receive input information of a user side and store the input information in a storage. A presentation component refers to a component that can reference data stored by a particular input component to render a presentation at the browser end.
It is to be understood that the input-type component may also include a presentation function, and the presentation-type component may also include an input function, which is not specifically limited by the present application.
In one example, in the page configuration phase of the process, when the component C1 in the process P1 needs to refer to the component data of the component C2 in the process P2, a piece of subscription information sub (P1, C1, P2, C2) is submitted to the control center through the configuration center, and the control center stores the subscription information locally.
S102, receiving the publishing information of the component data provided by the input type component of each process in each process instance of the starting operation of each process.
Specifically, the issuing information includes: a process ID, a component ID, and a process instance ID. Generally, a process platform issues various processes, and each process may also start numerous process instances. For example, for the process of submitting a leave application, a plurality of process instances such as "three-filing leave application", "four-filing leave application", and the like can be started.
In one example, during the process run phase, when any one of the process instances R2 of the process P2 produces data for the input-type component C2, a piece of publishing information prov (P2, C2, R2) is submitted to the control center, which is also stored locally. In the actual implementation process, if the process P2 starts N process instances, the control center may acquire and store N pieces of prov release information.
S103, in a first process example of starting operation of the first process, receiving a data request sent by the display type component of the first process, and calling a matching rule based on the data request and the subscription information to determine corresponding release information.
Specifically, the data request may include: a first process ID, a presentation component ID, and a first process instance ID.
In one example, when a process instance R1 of the process P1 requires data of the exposed component C1 to be loaded during operation, a data request, which may include a request (P1, C1, R1), is sent to the control center. The control center determines subscription information sub (P1, C1, P2, C2) corresponding to the component C1 of the process P1 based on the data request (P1, C1, R1), and the control center calls a matching rule to find required release information prov (P2, C2, Ri) based on the subscription information sub (P1, C1, P2, C2).
And S104, acquiring the component data of the target input type component based on the release information, and providing the component data for the display type component of the first flow.
In one example, after obtaining the publishing information prov (P2, C2, Ri), the publishing information prov (P2, C2, Ri) is returned to the component C1 of the process P1, and the component C1 accurately finds the component data of the corresponding target input-type component based on the publishing information prov (P2, C2, Ri), and finally completes the page rendering of the component C1.
The embodiment provides a component data standardization management scheme based on a publish-subscribe mechanism, which can realize the unified storage and retrieval management of page component data and avoid the problem of data management confusion in a complex service scene.
It should be noted that "first" in the first flow does not have any special meaning, and only a specific flow among a plurality of flows is described.
Generally, a process platform issues various processes, and each process may start numerous instances. Therefore, for an input-type component, the referenced data may be from the same instance of the same process, may be from different instances of the same process, or may be from a certain instance of different processes, and in the process assembly stage, only the static relationship of the input-type component referenced from a certain process by the presentation-type component may be specified, but the dynamic relationship of the input-type component referenced from which process instance cannot be specified.
In one possible embodiment, to solve the problem of the dynamic relationship of the input-type component that cannot specify which process instance is referenced from, the matching rule may include one or more sub-matching rules of the following: (1) and the homologous rule is used for indicating that in the first process example of the first process, the display type component is matched with the component data of the same process example of the same process. (2) An inheritance rule indicating that in a first process instance of a first process, an exposed component matches component data of a parent process instance of the first process instance. Specifically, one node of one process a calls another process B due to the need of work, where a calls the parent process and B calls the child process. For example, if the target process is determined to be the parent process of the first process in advance, when the first process starts to run the first process instance, the parent process instance of the first process instance is dynamically determined, whether one piece of release information corresponding to the parent process instance of the first process instance exists in a plurality of pieces of release information of the target input type component of the target process is judged based on the inheritance rule, and if yes, matching is completed. (3) And the custom rule is used for indicating that in the first flow example of the first flow, the display type component is matched with the component data of the custom flow example, wherein the custom flow example is determined based on the input dependent instruction. For example, in a specific scenario, selectable items such as "three-file submission application" and "lee-file submission application" for specific process instances may be provided on a process page of the first process, and after a user checks any one specific process instance on the process page of the first process, the user may match the display-type component of the first process to the component data of the selected custom process instance.
In one possible embodiment, the method further comprises: integrating a plurality of sub-matching rules and setting a priority for each sub-matching rule; and, referring to fig. 3, a schematic diagram of an exemplary matching rule is shown, where rule 1, rule 2, …, and rule N refer to sub-matching rules, and the method 103 may further include: each sub-matching rule (rule in circle) is adapted one by one according to the priority from high to low, and if any sub-matching rule is matched, the corresponding release information is searched according to any sub-matching rule; and if all the sub-matching rules do not realize matching, discarding the data request.
In a possible implementation, the method shown in fig. 1 further includes an assembly step of each process, specifically including: and a first-level configuration step, wherein a plurality of assemblies with different layout structures and display forms are constructed by taking the assembly elements as units to form an assembly library. And a second-stage configuration step, wherein the components of the component library are used as basic units, required components are screened according to the operation requirements of each process, the layout structure relationship among the components is adjusted, and finally a process page containing one or more components is constructed.
In the present embodiment, as shown in fig. 2, the components in the component library are mainly divided into the custom component and the extension component. The custom component is mainly composed of a plurality of node elements, the node elements represent a minimum display unit on the process page, such as an input box, a text box, a drop-down box and the like, and each node element is associated with a plurality of style attributes, such as name, height, width, color, relative position and the like. The user-defined component is mainly formed by automatically building in a mode of dragging the node elements on line. When the custom component is assembled, all configuration parameters are stored in the database in the form of serialized strings. And when the subsequent component is accessed, the page renderer analyzes the configuration parameters to finish rendering and displaying of the component in the page. Based on the created component library, the final page effect can be assembled on line according to the requirements of the business process in the second-stage configuration step.
In one possible embodiment, the method further comprises: in the secondary configuration step, the components in the component library are dragged and dragged on line, so that a flow page containing one or more components is constructed. Thereby facilitating construction of the flow page in a desired layout format.
In the second-level configuration step of the first process, the first process is formed based on the display type components contained in the component library, and subscription information of the display type components of the first process is generated, wherein the subscription information is used for indicating that the display type components of the first process need to refer to component data of target input type components of the target process.
In one possible embodiment, as shown in FIG. 2, in addition to custom components, third party developed extension components may be integrated into the component library. At present, the extension component can be dynamically integrated into a component library of a system only by realizing interface logic development such as component data storage, component data reading, component layout structure switching and the like according to a system standardization specification.
In one possible embodiment, obtaining component data for the target input-type component based on the release information further comprises: querying a database based on the release information to obtain component data for the target input-type component; and receiving the issuing information of the component data provided by the process components of each process at each process instance operation stage of each process, and storing the component data into a database.
In a possible implementation, after receiving the data request sent by the presentation component of the first process, the method further includes: the component data of the target input-type component is provided to the presentation-type component of the first process for the presentation-type component to perform page rendering in the browser based on the component data of the target input-type component.
In the description of the present specification, reference to the description of the terms "some possible implementations," "some embodiments," "examples," "specific examples," or "some examples," or the like, means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
With regard to the method flow diagrams of embodiments of the present application, certain operations are described as different steps performed in a certain order. Such flow diagrams are illustrative and not restrictive. Certain steps described herein may be grouped together and performed in a single operation, may be divided into multiple sub-steps, and may be performed in an order different than that shown herein. The various steps shown in the flowcharts may be implemented in any way by any circuit structure and/or tangible mechanism (e.g., by software running on a computer device, hardware (e.g., logical functions implemented by a processor or chip), etc., and/or any combination thereof).
Based on the same technical concept, an embodiment of the present invention further provides a process component data management apparatus, configured to execute the component data management method provided in any of the embodiments. Fig. 4 is a schematic structural diagram of an element data management apparatus according to an embodiment of the present invention.
As shown in fig. 4, the apparatus 400 includes:
a subscription module 401, configured to receive subscription information of a display-type component of a first process, where the subscription information is used to subscribe to component data provided by a target input-type component of a target process;
a publishing module 402, configured to receive, in each process instance in which the respective process starts to run, publishing information of component data provided by the input-type component of the respective process;
a matching module 403, configured to receive, in a first process instance in which the first process starts to run, a data request sent by the exhibition component of the first process, and invoke a matching rule based on the data request and the subscription information to determine corresponding publishing information;
a data providing module 404, configured to obtain component data of a target input-type component based on the publishing information, and provide the component data to the display-type component of the first process.
In some possible embodiments, the apparatus further includes a page assembly module of each of the processes, specifically including: the first-level configuration unit is used for constructing a plurality of assemblies with different layout structures and display forms by taking the node elements as units to form an assembly library; and the secondary configuration unit is used for determining required components according to the operation requirements of each process by taking the components of the component library as basic units, adjusting the layout structure relationship among the components and finally constructing a process page containing one or more components.
In some possible embodiments, the apparatus is further configured to: in the secondary configuration step, a flow page containing one or more components is constructed by performing online dragging and pulling on the components in the component library.
In some possible embodiments, the component library is integrated with extension components developed by a third party.
In some possible embodiments, the matching rule comprises one or more sub-matching rules of: a source rule indicating that in the first process instance of the first process, the exhibited component matches to component data of the same process instance of the same process; an inheritance rule indicating that in the first process instance of the first process, the exposed component matches to component data of a parent process instance of the first process instance; a custom rule indicating that in the first process instance of the first process, the exposed component matches to component data of a custom process instance, wherein the custom process instance is determined based on an input dependent instruction.
In some possible embodiments, the matching module is further configured to: integrating a plurality of the sub-matching rules and setting a priority for each sub-matching rule; and each sub-matching rule is adapted one by one from high to low according to the priority, and if any one sub-matching rule is matched, the corresponding release information is searched according to any one sub-matching rule; and if all the sub-matching rules do not realize matching, discarding the data request.
In some possible embodiments, the data providing module is further configured to: querying a database based on the release information to obtain component data for the target input-type component; and receiving the issuing information of the component data provided by the process components of each process at each process instance operation stage of each process, and storing the component data into the database.
In some possible embodiments, the apparatus is further configured to: after receiving the data request sent by the presentation component of the first process, providing the component data of the target input component to the presentation component of the first process, so that the presentation component performs page rendering in a browser based on the component data of the target input component.
It should be noted that the component data management apparatus of the process in the embodiment of the present application can implement each process of the embodiment of the component data management method of the foregoing process, and achieve the same effect and function, which is not described herein again.
Fig. 5 is a component data management apparatus of a process according to an embodiment of the present application, configured to execute the component data management method of the process shown in fig. 1, where the apparatus includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the above embodiments.
According to some embodiments of the present application, there is provided a non-transitory computer storage medium of a component data management method of a process, having stored thereon computer-executable instructions configured to, when executed by a processor, perform: the method of the above embodiment.
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus, device, and computer-readable storage medium embodiments, the description is simplified because they are substantially similar to the method embodiments, and reference may be made to some descriptions of the method embodiments for their relevance.
The apparatus, the device, and the computer-readable storage medium provided in the embodiment of the present application correspond to the method one to one, and therefore, the apparatus, the device, and the computer-readable storage medium also have advantageous technical effects similar to those of the corresponding method.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. Moreover, while the operations of the method of the invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
While the spirit and principles of the invention have been described with reference to several particular embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (18)
1. A method for managing component data of a process, comprising:
receiving subscription information of a display type component of a first process, wherein the subscription information is used for subscribing component data provided by a target input type component of a target process;
in each process instance of starting operation of each process, receiving release information of component data provided by an input type component of each process;
in a first process instance of starting operation of the first process, receiving a data request sent by the exhibition type component of the first process, and calling a matching rule based on the data request and the subscription information to determine the corresponding release information;
and acquiring the component data of the target input type component based on the release information, and providing the component data for the display type component of the first process.
2. The method according to claim 1, wherein the method further comprises a page assembly step of each process, specifically comprising:
a first-level configuration step, which is to construct a plurality of assemblies with different layout structures and display forms by taking the node elements as units to form an assembly library;
and a second-stage configuration step, namely determining required components according to the operation requirements of each process by taking the components of the component library as basic units, adjusting the layout structure relationship among the components, and finally constructing a process page containing one or more components.
3. The method of claim 2, further comprising:
in the secondary configuration step, a flow page containing one or more components is constructed by performing online dragging and pulling on the components in the component library.
4. The method of claim 2, wherein the component library is integrated with extension components developed by third parties.
5. The method of claim 1, wherein the matching rules include one or more sub-matching rules selected from the group consisting of:
a source rule indicating that in the first process instance of the first process, the exhibited component matches to component data of the same process instance of the same process;
an inheritance rule indicating that in the first process instance of the first process, the exposed component matches to component data of a parent process instance of the first process instance;
a custom rule indicating that in the first process instance of the first process, the exposed component matches to component data of a custom process instance, wherein the custom process instance is determined based on an input dependent instruction.
6. The method of claim 5, further comprising: integrating a plurality of the sub-matching rules and setting a priority for each sub-matching rule; and the number of the first and second groups,
determining the publication information provided by a target input-type component of a target process based on the subscription information and matching rules, further comprising:
each sub-matching rule is adapted one by one from high to low according to the priority, and if any sub-matching rule is matched, the corresponding release information is searched according to any sub-matching rule; and if all the sub-matching rules do not realize matching, discarding the data request.
7. The method of claim 5, wherein obtaining component data for a target input-type component based on the release information further comprises:
querying a database based on the release information to obtain component data for the target input-type component;
and receiving the issuing information of the component data provided by the process components of each process at each process instance operation stage of each process, and storing the component data into the database.
8. The method of claim 1, wherein after receiving the data request sent by the presentation component of the first process, further comprising:
providing the component data of the target input type component to the presentation type component of the first process, so that the presentation type component can execute page rendering in a browser based on the component data of the target input type component.
9. A component data management apparatus of a process, comprising:
the subscription module is used for receiving subscription information of the display type assembly of the first process, and the subscription information is used for subscribing assembly data provided by a target input type assembly of a target process;
the release module is used for receiving release information of component data provided by the input type components of each process in each process instance of each process starting operation;
the matching module is used for receiving a data request sent by the exhibition component of the first flow in a first flow instance in which the first flow starts to run, and calling a matching rule based on the data request and the subscription information to determine the corresponding release information;
and the data providing module is used for acquiring component data of the target input type component based on the release information and providing the component data to the display type component of the first flow.
10. The apparatus according to claim 9, wherein the apparatus further includes a page assembly module for each process, specifically including:
the first-level configuration unit is used for constructing a plurality of assemblies with different layout structures and display forms by taking the node elements as units to form an assembly library;
and the secondary configuration unit is used for determining required components according to the operation requirements of each process by taking the components of the component library as basic units, adjusting the layout structure relationship among the components and finally constructing a process page containing one or more components.
11. The apparatus of claim 10, wherein the apparatus is further configured to:
in the secondary configuration step, a flow page containing one or more components is constructed by performing online dragging and pulling on the components in the component library.
12. The apparatus of claim 10, wherein the component library is integrated with extension components developed by third parties.
13. The apparatus of claim 9, wherein the matching rules comprise one or more sub-matching rules selected from the group consisting of:
a source rule indicating that in the first process instance of the first process, the exhibited component matches to component data of the same process instance of the same process;
an inheritance rule indicating that in the first process instance of the first process, the exposed component matches to component data of a parent process instance of the first process instance;
a custom rule indicating that in the first process instance of the first process, the exposed component matches to component data of a custom process instance, wherein the custom process instance is determined based on an input dependent instruction.
14. The apparatus of claim 13, wherein the matching module is further configured to:
integrating a plurality of the sub-matching rules and setting a priority for each sub-matching rule; and each sub-matching rule is adapted one by one from high to low according to the priority, and if any one sub-matching rule is matched, the corresponding release information is searched according to any one sub-matching rule; and if all the sub-matching rules do not realize matching, discarding the data request.
15. The apparatus of claim 13, wherein the data providing module is further configured to:
querying a database based on the release information to obtain component data for the target input-type component;
and receiving the issuing information of the component data provided by the process components of each process at each process instance operation stage of each process, and storing the component data into the database.
16. The apparatus of claim 9, wherein the apparatus is further configured to:
after receiving the data request sent by the presentation component of the first process, providing the component data of the target input component to the presentation component of the first process, so that the presentation component performs page rendering in a browser based on the component data of the target input component.
17. A component data management apparatus of a process, comprising:
at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform: the method of any one of claims 1-8.
18. A computer-readable storage medium storing a program that, when executed by a multi-core processor, causes the multi-core processor to perform the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110180629.9A CN112800030B (en) | 2021-02-08 | 2021-02-08 | Method and device for managing component data of flow and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110180629.9A CN112800030B (en) | 2021-02-08 | 2021-02-08 | Method and device for managing component data of flow and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112800030A true CN112800030A (en) | 2021-05-14 |
| CN112800030B CN112800030B (en) | 2024-03-29 |
Family
ID=75814984
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110180629.9A Active CN112800030B (en) | 2021-02-08 | 2021-02-08 | Method and device for managing component data of flow and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112800030B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113568683A (en) * | 2021-08-05 | 2021-10-29 | 京东科技控股股份有限公司 | Method and device for dynamically expanding asset data stream processing service assembly |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070027702A1 (en) * | 2005-07-26 | 2007-02-01 | Microsoft Corporation | Organizing presence information into collections of publications |
| US20080133541A1 (en) * | 2006-11-30 | 2008-06-05 | International Business Machines Corporation | Flexible Topic Identification in a Publish/Subscribe System |
| US20090248612A1 (en) * | 2008-03-31 | 2009-10-01 | Morris Robert P | Methods, Systems, And Computer Program Products For Providing Prior Values Of A Tuple Element In A Publish/Subscribe System |
| US20090265161A1 (en) * | 2008-04-16 | 2009-10-22 | Fletcher Benjamin J | Transforming a natural language request for modifying a set of subscriptions for a publish/subscribe topic string |
| US20110296050A1 (en) * | 2010-05-28 | 2011-12-01 | Microsoft Corporation | Realtime websites with publication and subscription |
| US20130124613A1 (en) * | 2011-11-11 | 2013-05-16 | Rockwell Automation Technologies, Inc. | Systems and Methods for Asynchronous Searching and Filtering of Data |
| CN103404087A (en) * | 2011-02-24 | 2013-11-20 | 国际商业机器公司 | Peer-to-peer collaboration of publishers in a publish-subscription environment |
| CN104933118A (en) * | 2015-06-05 | 2015-09-23 | 东南大学 | Process definition meta model in theme-based issuing/subscription system and building method of process definition meta model |
| CN105577533A (en) * | 2016-03-18 | 2016-05-11 | 微梦创科网络科技（中国）有限公司 | Distributed message delivery system and method |
| US20170011021A1 (en) * | 2015-07-07 | 2017-01-12 | International Business Machines Corporation | Managing document annotations in a publish/subscribe system |
| CN109614100A (en) * | 2018-10-26 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Page display method, device, server, front end and storage medium |
| CN109862063A (en) * | 2018-11-12 | 2019-06-07 | 平安科技（深圳）有限公司 | Distribution subscription matching process, device and storage medium based on MQTT |
| CN110555028A (en) * | 2019-08-22 | 2019-12-10 | 上海数禾信息科技有限公司 | data display method and device |
| US10761813B1 (en) * | 2018-10-01 | 2020-09-01 | Splunk Inc. | Assisted visual programming for iterative publish-subscribe message processing system |
| CN111752540A (en) * | 2020-06-28 | 2020-10-09 | 北京百度网讯科技有限公司 | Tree component generation method, device, equipment and computer storage medium |
-
2021
- 2021-02-08 CN CN202110180629.9A patent/CN112800030B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070027702A1 (en) * | 2005-07-26 | 2007-02-01 | Microsoft Corporation | Organizing presence information into collections of publications |
| US20080133541A1 (en) * | 2006-11-30 | 2008-06-05 | International Business Machines Corporation | Flexible Topic Identification in a Publish/Subscribe System |
| US20090248612A1 (en) * | 2008-03-31 | 2009-10-01 | Morris Robert P | Methods, Systems, And Computer Program Products For Providing Prior Values Of A Tuple Element In A Publish/Subscribe System |
| US20090265161A1 (en) * | 2008-04-16 | 2009-10-22 | Fletcher Benjamin J | Transforming a natural language request for modifying a set of subscriptions for a publish/subscribe topic string |
| US20110296050A1 (en) * | 2010-05-28 | 2011-12-01 | Microsoft Corporation | Realtime websites with publication and subscription |
| CN103404087A (en) * | 2011-02-24 | 2013-11-20 | 国际商业机器公司 | Peer-to-peer collaboration of publishers in a publish-subscription environment |
| US20130124613A1 (en) * | 2011-11-11 | 2013-05-16 | Rockwell Automation Technologies, Inc. | Systems and Methods for Asynchronous Searching and Filtering of Data |
| CN104933118A (en) * | 2015-06-05 | 2015-09-23 | 东南大学 | Process definition meta model in theme-based issuing/subscription system and building method of process definition meta model |
| US20170011021A1 (en) * | 2015-07-07 | 2017-01-12 | International Business Machines Corporation | Managing document annotations in a publish/subscribe system |
| CN105577533A (en) * | 2016-03-18 | 2016-05-11 | 微梦创科网络科技（中国）有限公司 | Distributed message delivery system and method |
| US10761813B1 (en) * | 2018-10-01 | 2020-09-01 | Splunk Inc. | Assisted visual programming for iterative publish-subscribe message processing system |
| CN109614100A (en) * | 2018-10-26 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Page display method, device, server, front end and storage medium |
| CN109862063A (en) * | 2018-11-12 | 2019-06-07 | 平安科技（深圳）有限公司 | Distribution subscription matching process, device and storage medium based on MQTT |
| CN110555028A (en) * | 2019-08-22 | 2019-12-10 | 上海数禾信息科技有限公司 | data display method and device |
| CN111752540A (en) * | 2020-06-28 | 2020-10-09 | 北京百度网讯科技有限公司 | Tree component generation method, device, equipment and computer storage medium |
Non-Patent Citations (4)
| Title |
|---|
| W13707470416: "VUE响应式数据原理 订阅-发布模式解析", Retrieved from the Internet <URL:https://blog.csdn.net/w13707470416/article/details/88995187> * |
| 姜振华等: "基于"发布-订阅"模型的异构信息资源获取技术", 《信息技术与信息化》, 20 July 2015 (2015-07-20) * |
| 曹旻: "发布_订阅中间件中的可配置流程控制机制研究", 《信息科技》 * |
| 王毅;赵俊翔;封慧英;薛凯;: "组件化数据监显软件设计与实现", 计算机测量与控制, no. 11, 25 November 2017 (2017-11-25) * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113568683A (en) * | 2021-08-05 | 2021-10-29 | 京东科技控股股份有限公司 | Method and device for dynamically expanding asset data stream processing service assembly |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112800030B (en) | 2024-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112036736B (en) | Workflow creation method and device | |
| US7721205B2 (en) | Integration of composite objects in host applications | |
| US9336184B2 (en) | Representation of an interactive document as a graph of entities | |
| US9208212B2 (en) | Field extensibility in a multi-tenant environment with columnar database support | |
| US9262850B2 (en) | Descriptive framework for data visualization | |
| CN106557486A (en) | A kind of storage method and device of data | |
| US9195456B2 (en) | Managing a catalog of scripts | |
| CN110674227A (en) | Method, system, medium and terminal for generating data visualization chart and page | |
| CN107622080B (en) | Data processing method and equipment | |
| US11449764B2 (en) | AI-synthesized application for presenting activity-specific UI of activity-specific content | |
| US11354581B2 (en) | AI-driven human-computer interface for presenting activity-specific views of activity-specific content for multiple activities | |
| CN111966334A (en) | Service processing method, device and equipment | |
| CN115617338A (en) | Method and device for quickly generating service page and readable storage medium | |
| CN113495797A (en) | Message queue and consumer dynamic creation method and system | |
| CN111784108A (en) | Modeling method and device for main data management platform | |
| US20200004388A1 (en) | Framework and store for user-level customizable activity-based applications for handling and managing data from various sources | |
| US20170300461A1 (en) | Representation of an Interactive Document as a Graph of Entities | |
| CN107209763B (en) | Rules for specifying and applying data | |
| CN112800030A (en) | Process component data management method and device and computer readable storage medium | |
| CN108241624B (en) | Query script generation method and device | |
| CN116167882A (en) | Conditional expression dynamic configuration method, accounting condition calculation method and accounting condition calculation device | |
| CN116069310A (en) | Visual business logic code-free development method, equipment and medium | |
| US9230022B1 (en) | Customizable result sets for application program interfaces | |
| CN116127154A (en) | Knowledge tag recommendation method and device, electronic equipment and storage medium | |
| CN112559603B (en) | Feature extraction method, device, equipment and computer-readable storage medium |
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 |