CN112800030B - Method and device for managing component data of flow and computer readable storage medium - Google Patents
Method and device for managing component data of flow and computer readable storage medium Download PDFInfo
- Publication number
- CN112800030B CN112800030B CN202110180629.9A CN202110180629A CN112800030B CN 112800030 B CN112800030 B CN 112800030B CN 202110180629 A CN202110180629 A CN 202110180629A CN 112800030 B CN112800030 B CN 112800030B
- Authority
- CN
- China
- Prior art keywords
- flow
- component
- data
- component data
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 99
- 238000013523 data management Methods 0.000 claims abstract description 17
- 230000008569 process Effects 0.000 claims description 49
- 238000009877 rendering Methods 0.000 claims description 9
- 230000001419 dependent effect Effects 0.000 claims description 6
- 238000007726 management method Methods 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 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
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 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
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)
- User Interface Of Digital Computer (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method and a device for managing component data of a flow and a computer readable storage medium, wherein the method comprises the following steps: receiving subscription information of a display type component of a first flow, wherein the subscription information is used for subscribing component data provided by a target input type component of a target flow; in each flow instance of each flow starting operation, receiving release information of component data provided by an input component of each flow; in a first flow instance of the first flow starting operation, receiving a data request sent by a display component of the first flow, and calling a matching rule based on the data request and subscription information to determine corresponding release information; component data of the target input type component is acquired based on the release information and provided to the presentation type component of the first flow. By using the method, unified management of page component data is realized, and the problem of confusion of data management 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 flow 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 on-line design, deployment, release and operation of the business flow, can greatly improve the landing efficiency of various business scenes on the system platform, and avoids heavy background code development in the traditional mode.
Many management systems in the market at present integrate a flow customization function, but are mainly applied to 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 business flow landings, the scheme provides a flow customization scheme supporting complex business scenes, and by means of the scheme, quick landing deployment of operation flows of most business scenes on a system platform can be solved.
At present, more and more management systems realize a flow customization function, but are mainly used for solving the problem of rapid flow landing in specific scenes, are mainly applied to approval scenes, and can only process simple business data relations; when there is a complex data association relationship between the nodes before and after the business process, the component data processing capability becomes very fragile.
Disclosure of Invention
In order to solve the problems in the prior art, a method, an apparatus and a computer readable storage medium for managing component data of a process are provided, and the problems can be solved by using the method, the apparatus and the computer readable storage medium.
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 flow, wherein the subscription information is used for subscribing component data provided by a target input type component of a target flow; in each flow instance of the starting operation of each flow, receiving release information of component data provided by an input component of each flow; in a first flow instance of the first flow starting operation, receiving a data request sent by the display component of the first flow, and calling a matching rule based on the data request and the subscription information to determine the corresponding release information; component data of a target input type component is obtained based on the release information and provided to the presentation type component of the first flow.
In some possible embodiments, the method further includes a page assembling step of each flow, specifically including: a first-level configuration step, namely constructing a plurality of components with different layout structures and display forms by taking node elements as units to form a component library; and a secondary configuration step, namely determining required components according to the operation requirements of each flow by taking the components of the component library as basic units and adjusting the layout structure relationship among the components, and finally constructing a flow 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 carrying out online dragging on the components in the component library.
In some possible embodiments, the component library has an extension component developed by a third party integrated therein.
In some possible implementations, the matching rules include one or more sub-matching rules of: a homology rule for indicating that, in the first flow instance of the first flow, the exposed component matches component data of the same flow instance of the same flow; inheritance rules for indicating that in the first flow instance of the first flow, the exposed component matches component data of a parent flow instance of the first flow instance; and a custom rule for indicating that in the first flow instance of the first flow, the exposed component matches component data of a custom flow instance, wherein the custom flow instance is determined based on an input dependent instruction.
In some possible embodiments, the method further comprises: integrating a plurality of sub-matching rules, and setting priority for each sub-matching rule; and determining the publication information provided by the target input-type component of the target flow based on the subscription information and the matching rule, further comprising: each sub-matching rule is adapted one by one according to the priority from high to low, and when matching is realized according to any one sub-matching rule, 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, acquiring the component data of the target input type component based on the release information further includes: querying a database based on the published information to obtain component data of the target input type component; and in the operation stage of each flow instance of each flow, receiving the release information of the component data provided by the flow components of each flow, 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 flow, the method further includes: and providing the component data of the target input type component to the presentation type component of the first flow, so that the presentation type component can perform page rendering in a browser based on the component data of the target input type component.
In a second aspect, there is provided a component data management apparatus of a flow, including: the subscription module is used for receiving subscription information of the display type component of the first flow, and the subscription information is used for subscribing component data provided by the target input type component of the target flow; the issuing module is used for receiving issuing information of the component data provided by the input type component of each flow in each flow example of the starting operation of each flow; the matching module is used for receiving a data request sent by the display component of the first flow in a first flow instance of the first flow starting operation, and calling a matching rule based on the data request and the subscription information so as to determine the corresponding release information; and the data providing module is used for 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.
In some possible embodiments, the apparatus further includes a page assembly module of each flow, specifically including: the first-level configuration unit is used for constructing a plurality of components with different layout structures and display forms by taking the node elements as units to form a component library; the secondary configuration unit is used for determining required components according to the operation requirements of each flow by taking the components of the component library as basic units and adjusting the layout structure relationship among the components, and finally constructing a flow page containing one or more components.
In some possible embodiments, the apparatus is further for: in the secondary configuration step, a flow page containing one or more components is constructed by carrying out online dragging on the components in the component library.
In some possible embodiments, the component library has an extension component developed by a third party integrated therein.
In some possible implementations, the matching rules include one or more sub-matching rules of: a homology rule for indicating that, in the first flow instance of the first flow, the exposed component matches component data of the same flow instance of the same flow; inheritance rules for indicating that in the first flow instance of the first flow, the exposed component matches component data of a parent flow instance of the first flow instance; and a custom rule for indicating that in the first flow instance of the first flow, the exposed component matches component data of a custom flow instance, wherein the custom flow instance is determined based on an input dependent instruction.
In some possible embodiments, the matching module is further configured to: integrating a plurality of sub-matching rules, and setting priority for each sub-matching rule; and each sub-matching rule is adapted one by one according to the priority from high to low, and when matching is realized according to any one sub-matching rule, 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 published information to obtain component data of the target input type component; and in the operation stage of each flow instance of each flow, receiving the release information of the component data provided by the flow components of each flow, and storing the component data into the database.
In some possible embodiments, the apparatus is further for: after receiving the data request sent by the exhibition component of the first flow, providing the component data of the target input component to the exhibition component of the first flow, so that the exhibition component can execute page rendering in a browser based on the component data of the target input component.
In a third aspect, a component data management apparatus of a flow 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, the instructions being executable by the at least one processor to enable 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 as in the first aspect.
The above-mentioned at least one technical scheme that this application embodiment adopted can reach following beneficial effect: in the embodiment, the unified management of the page component data can be realized by adopting the component data management scheme of the publish-subscribe mechanism, so that the problem of confusion of data management in a complex service scene is avoided.
It should be understood that the foregoing description is only an overview of the technical solutions of the present invention, so that the technical means of the present invention may be more clearly understood and implemented in accordance with the content of the specification. The following specific embodiments of the present invention are described in order to make the above and other objects, features and advantages of the present invention more comprehensible.
Drawings
The advantages and benefits described herein, as well as other advantages and benefits, will become 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 designate like parts throughout the figures. In the drawings:
FIG. 1 is a flow chart of a component data management method according to an embodiment of the invention;
FIG. 2 is an assembly diagram of a process page according to an embodiment of the invention;
FIG. 3 is a schematic diagram of a matching rule according to an embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating a configuration of a device for managing component data according to a flow of an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a component data management apparatus according to a flow of 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 should be understood that terms such as "comprises" or "comprising" are intended to indicate the presence of features, numbers, steps, acts, components, portions or combinations thereof disclosed in the present specification, and are not intended to exclude the possibility of the presence of one or more other features, numbers, steps, acts, components, portions or combinations thereof.
Unless otherwise indicated, "/" means or, e.g., A/B may represent A or B; "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone.
The terms "first," "second," and the like 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 defining "a first", "a second", etc. may explicitly or implicitly include one or more such feature. In the description of the embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.
All codes in this application are exemplary and those skilled in the art will recognize variations depending on the programming language used, specific requirements and personal habits, etc. without departing from the spirit of the application.
FIG. 1 is a flow diagram of a component data management method according to an embodiment of the present application, in which, from a device perspective, an executing subject may be one or more electronic devices; from the program perspective, the execution subject may be a program mounted on these electronic devices, accordingly.
As shown in fig. 1, the method provided in this embodiment may include the following steps:
s101, receiving subscription information of a display type component of a first flow.
Specifically, at a process assembly stage of the first process, the control center receives subscription information of a presentation type component of the first process, where the subscription information is used to subscribe to component data provided by a target input type component of the target process. The subscription information may include: a first flow ID, a presentation type component ID, a target flow ID, and a target input type component ID.
The input type component is a component capable of receiving input information of a user side and storing the input information in a warehouse. The presentation component refers to a component that can refer to data stored by a specific input-type component for rendering presentation at the browser side.
It will be appreciated 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 particularly limited in this application.
In one example, in the page configuration stage 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, in each flow example of starting operation of each flow, receiving release information of component data provided by an input component of each flow.
Specifically, the release information includes: a flow ID, a component ID, and a flow instance ID. Generally, a process platform issues a wide variety of processes, and each process may initiate numerous process instances. For example, for the process of submitting the leave application, multiple process examples such as "Zhang Sanfu leave application", "Lisi Fu application" and the like can be started.
In one example, during the process running phase, when any one of the process instances R2 of the process P2 generates data of the input component C2, a piece of release information pro (P2, C2, R2) is submitted to the control center, and the control center likewise stores the release information locally. In the actual execution process, if the process P2 starts N process instances, the control center will acquire and store N pieces of adv release information.
S103, in a first flow instance of the first flow starting operation, receiving a data request sent by a display component of the first flow, and calling a matching rule based on the data request and subscription information to determine corresponding release information.
Specifically, the data request may include: a first flow ID, a presentation component ID, and a first flow instance ID.
In one example, when the process P1 runs at a process instance R1, and data of the presentation component C1 needs to be loaded, a data request is sent to the control center, where the data request may include a request (P1, C1, R1). The control center determines subscription information sub (P1, C1, P2, C2) corresponding to the component C1 of the flow P1 based on the data request (P1, C1, R1), and finds the required release information pro (P2, C2, ri) based on the subscription information sub (P1, C1, P2, C2) invoking the matching rule.
S104, 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 one example, after obtaining the release information pro (P2, C2, ri), the release information pro (P2, C2, ri) is returned to the component C1 of the flow P1, and the component C1 accurately finds the component data of the corresponding target input type component based on the release information pro (P2, C2, ri), so as to finally complete the page rendering of the component C1.
The embodiment provides a standardized management scheme for the component data based on a publish-subscribe mechanism, and unified storage and fetching management of page component data can be realized based on the management scheme, so that the problem of confusion of data management in a complex service scene is avoided.
The "first" in the first flow is not defined in any particular sense, and is only a specific flow among a plurality of flows.
Generally, a process platform issues a wide variety of processes, and each process may initiate numerous instances. Thus, for an input-type component, the data referenced by the input-type component may come from the same instance of the same flow, may come from different instances of the same flow, may come from a certain instance of a different flow, and in the process assembly stage, only the static relationship of the input-type component of the exposed component referenced from the certain flow may be specified, but the dynamic relationship of the input-type component of which flow instance is referenced from cannot be specified.
In one possible embodiment, to solve the above problem of failing to specify the dynamic relationship of the input-type component from which flow instance is referenced, the matching rule may include one or more sub-matching rules of: (1) Homology rules for indicating, in a first flow instance of a first flow, that a presentation component matches component data of the same flow instance of the same flow. (2) Inheritance rules for indicating that in a first flow instance of a first flow, a exposed component matches component data of a parent flow instance of the first flow instance. Specifically, a node of a process a calls up another process B, a called parent process, B called child process, due to the need of work. For example, if the target flow is determined to be a parent flow of the first flow in advance, when the first flow starts to run the first flow instance, the parent flow instance of the first flow instance is dynamically determined, and whether one piece of release information corresponding to the parent flow instance of the first flow instance exists in a plurality of pieces of release information of the target input type component of the target flow is judged based on inheritance rules, if so, matching is completed. (3) And the custom rule is used for indicating that the exposed component is matched with the component data of the custom flow instance in the first flow instance of the first flow, wherein the custom flow instance is determined based on the input dependent instruction. For example, in a specific scenario, options for specific flow instances, such as "Zhang Sanhu application", "Lifour hu application", etc., may be provided on the flow page of the first flow, and after the user selects any one specific flow instance on the flow page of the first flow, the user may match the exposed component of the first flow to the component data of the selected custom flow instance.
In one possible embodiment, the method further comprises: integrating a plurality of sub-matching rules, and setting 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, …, rule N refer to sub-matching rules, and 103 may further include: each sub-matching rule (rule in a circle) is adapted one by one according to the priority from high to low, and when any one sub-matching rule is matched, corresponding release information is searched according to any one sub-matching rule; if all sub-match rules do not achieve a match, the data request is discarded.
In one possible embodiment, the method shown in fig. 1 further includes an assembling step of each flow, specifically including: and a primary configuration step, wherein a plurality of components with different layout structures and display forms are constructed by taking the component elements as units to form a component library. And a secondary configuration step, wherein components of the component library are taken as basic units, required components are screened according to the operation requirements of each flow, the layout structure relationship among the components is adjusted, and finally, a flow page containing one or more components is constructed.
In this embodiment, as shown in fig. 2, the components in the component library are mainly divided into custom components and extension components. The custom component mainly comprises a plurality of node elements, wherein the node elements represent a minimum display unit on a flow 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 a name, a height, a width, a color, a relative position and the like. The self-defining component is mainly formed by self-constructing in an on-line dragging node element mode. When the custom component is assembled, all configuration parameters are stored in the database in the form of a serialized string. When the subsequent component is accessed, the page renderer completes rendering and displaying of the component in the page by analyzing the configuration parameters. Based on the created component library, in the second stage configuration step, the final page effect can be assembled on line according to the requirements of the business process.
In one possible embodiment, the method further comprises: in the two-stage configuration step, a flow page containing one or more components is constructed by online dragging of the components in the component library. Thereby facilitating the use of the process page to be structured in accordance with the desired layout format.
In the second-level configuration step of the first flow, the first flow is configured based on the presentation type components contained in the component library, and subscription information of the presentation type components of the first flow is generated, wherein the subscription information is used for indicating component data of target input type components of the target flow to be referenced by the presentation type components of the first flow.
In one possible implementation, as shown in fig. 2, in addition to custom components, the component library may have integrated therein extension components developed by third parties. At present, the expansion component can be dynamically integrated into a component library of a system as long as the development of interface logic such as component data storage, component data reading, component layout structure switching and the like is realized according to the system standardization specification.
In one possible embodiment, the component data of the target input-type component is acquired based on the release information, further comprising: querying a database based on the published information to obtain component data of the target input type component; and in the operation stage of each flow instance of each flow, receiving the release information of the component data provided by the flow components of each flow, and storing the component data into a database.
In one possible embodiment, after receiving the data request sent by the presentation component of the first flow, the method further includes: the component data of the target input-type component is provided to the presentation-type component of the first flow 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 terms "some possible implementations", "some embodiments", "examples", "specific examples", or "some examples" etc. 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, schematic representations of the above terms are not necessarily directed 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, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present invention, the meaning of "plurality" means at least two, for example, two, three, etc., unless specifically defined 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 further 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 respect to the method flow diagrams of the embodiments of the present application, certain operations are described as distinct steps performed in a certain order. Such a flowchart is illustrative and not limiting. Some steps described herein may be grouped together and performed in a single operation, may be partitioned into multiple sub-steps, and may be performed in an order different than that shown herein. The various steps illustrated in the flowcharts may be implemented in any manner by any circuit structure and/or tangible mechanism (e.g., by software running on a computer device, hardware (e.g., processor or chip implemented logic functions), etc., and/or any combination thereof).
Based on the same technical concept, the embodiment of the invention also provides a component data management device of a flow, which is used for executing the component data management method provided by any one of the embodiments. Fig. 4 is a schematic structural diagram of a device for managing component data 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 presentation component of a first process, where the subscription information is used to subscribe to component data provided by a target input 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 an input 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 presentation component of the first process, and invoke a matching rule based on the data request and the subscription information, so as to determine the corresponding published information;
the data providing module 404 is configured to obtain component data of a target input component based on the release information, and provide the component data to the presentation component of the first flow.
In some possible embodiments, the apparatus further includes a page assembly module of each flow, specifically including: the first-level configuration unit is used for constructing a plurality of components with different layout structures and display forms by taking the node elements as units to form a component library; the secondary configuration unit is used for determining required components according to the operation requirements of each flow by taking the components of the component library as basic units and adjusting the layout structure relationship among the components, and finally constructing a flow page containing one or more components.
In some possible embodiments, the apparatus is further for: in the secondary configuration step, a flow page containing one or more components is constructed by carrying out online dragging on the components in the component library.
In some possible embodiments, the component library has an extension component developed by a third party integrated therein.
In some possible implementations, the matching rules include one or more sub-matching rules of: a homology rule for indicating that, in the first flow instance of the first flow, the exposed component matches component data of the same flow instance of the same flow; inheritance rules for indicating that in the first flow instance of the first flow, the exposed component matches component data of a parent flow instance of the first flow instance; and a custom rule for indicating that in the first flow instance of the first flow, the exposed component matches component data of a custom flow instance, wherein the custom flow instance is determined based on an input dependent instruction.
In some possible embodiments, the matching module is further configured to: integrating a plurality of sub-matching rules, and setting priority for each sub-matching rule; and each sub-matching rule is adapted one by one according to the priority from high to low, and when matching is realized according to any one sub-matching rule, 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 published information to obtain component data of the target input type component; and in the operation stage of each flow instance of each flow, receiving the release information of the component data provided by the flow components of each flow, and storing the component data into the database.
In some possible embodiments, the apparatus is further for: after receiving the data request sent by the exhibition component of the first flow, providing the component data of the target input component to the exhibition component of the first flow, so that the exhibition component can execute page rendering in a browser based on the component data of the target input component.
It should be noted that, the component data management device of the flow in the embodiment of the present application may implement each process of the embodiment of the component data management method of the foregoing flow, and achieve the same effect and function, which is not described herein again.
Fig. 5 is a component data management apparatus for executing the component data management method of the flow shown in fig. 1 according to an embodiment of the present application, the apparatus 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 enable the at least one processor to perform the methods of the above embodiments.
According to some embodiments of the present application, there is provided a non-transitory computer storage medium having stored thereon computer-executable instructions configured to, when executed by a processor, perform: the method of the above embodiment.
All embodiments in the application are described in a progressive manner, and identical and similar parts of all embodiments are mutually referred, so that each embodiment mainly describes differences from other embodiments. In particular, for apparatus, devices and computer readable storage medium embodiments, the description thereof is simplified as it is substantially similar to the method embodiments, as relevant points may be found in part in the description of the method embodiments.
The apparatus, the device, and the computer readable storage medium provided in the embodiments of the present application are in one-to-one correspondence with the methods, so that the apparatus, the device, and the computer readable storage medium also have similar beneficial technical effects as the corresponding methods, and since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the apparatus, the device, and the computer readable storage medium are not repeated herein.
It will be appreciated by those skilled in the art that 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
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 storage media for a computer 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, which can be used to store information that can be accessed by a computing device. Furthermore, although the operations of the methods of the present invention are depicted in the drawings in a particular order, this is not required to either imply that the operations must be performed in that particular order or that all of the illustrated operations be performed to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.
While the spirit and principles of the present 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 does it imply that features of the various aspects are not useful in combination, nor are they useful in any combination, such as for convenience of description. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (16)
1. A method for managing component data of a process, comprising:
receiving subscription information of a display type component of a first flow, wherein the subscription information is used for subscribing component data provided by a target input type component of a target flow;
in each flow instance of starting operation of each flow, receiving release information of component data provided by an input component of each flow;
in a first flow instance of the first flow starting operation, receiving a data request sent by the display component of the first flow; determining the subscription information corresponding to the exposed component of the first flow based on the data request; based on the subscription information, invoking a matching rule to determine the corresponding release information;
Wherein the matching rules include one or more sub-matching rules of:
a homology rule for indicating that, in the first flow instance of the first flow, the exposed component matches component data of the same flow instance of the same flow; inheritance rules for indicating that in the first flow instance of the first flow, the exposed component matches component data of a parent flow instance of the first flow instance; a custom rule for indicating that in the first flow instance of the first flow, the exposed component matches component data of a custom flow instance, wherein the custom flow instance is determined based on an input dependent instruction;
and 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.
2. The method according to claim 1, further comprising a page assembly step of the respective flow, in particular comprising:
a first-level configuration step, namely constructing a plurality of components with different layout structures and display forms by taking node elements as units to form a component library;
And a secondary configuration step, namely determining required components according to the operation requirements of each flow by taking the components of the component library as basic units and adjusting the layout structure relationship among the components, and finally constructing a flow page containing one or more components.
3. The method according to claim 2, wherein the method further comprises:
in the secondary configuration step, a flow page containing one or more components is constructed by carrying out online dragging on the components in the component library.
4. The method of claim 2, wherein the library of components has integrated therein an extension component developed by a third party.
5. The method according to claim 1, wherein the method further comprises: integrating a plurality of sub-matching rules, and setting priority for each sub-matching rule; the method comprises the steps of,
determining the publication information provided by the target input-type component of the target flow based on the subscription information and the matching rule, further comprising:
each sub-matching rule is adapted one by one according to the priority from high to low, and when matching is realized according to any one sub-matching rule, 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.
6. The method of claim 1, wherein obtaining component data of a target input type component based on the release information, further comprises:
querying a database based on the published information to obtain component data of the target input type component;
and in the operation stage of each flow instance of each flow, receiving the release information of the component data provided by the flow components of each flow, and storing the component data into the database.
7. The method of claim 1, further comprising, after receiving the data request sent by the presentation component of the first flow:
and providing the component data of the target input type component to the presentation type component of the first flow, so that the presentation type component can perform page rendering in a browser based on the component data of the target input type component.
8. A component data management apparatus of a flow, comprising:
the subscription module is used for receiving subscription information of the display type component of the first flow, and the subscription information is used for subscribing component data provided by the target input type component of the target flow;
the issuing module is used for receiving issuing information of the component data provided by the input type component of each flow in each flow example of the starting operation of each flow;
The matching module is used for receiving a data request sent by the display component of the first flow in a first flow instance of the first flow starting operation; determining the subscription information corresponding to the exposed component of the first flow based on the data request; based on the subscription information, invoking a matching rule to determine the corresponding release information;
wherein the matching rules include one or more sub-matching rules of:
a homology rule for indicating that, in the first flow instance of the first flow, the exposed component matches component data of the same flow instance of the same flow; inheritance rules for indicating that in the first flow instance of the first flow, the exposed component matches component data of a parent flow instance of the first flow instance; a custom rule for indicating that in the first flow instance of the first flow, the exposed component matches component data of a custom flow instance, wherein the custom flow instance is determined based on an input dependent instruction;
and the data providing module is used for 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.
9. The device according to claim 8, further comprising a page assembly module of the respective flow, specifically comprising:
the first-level configuration unit is used for constructing a plurality of components with different layout structures and display forms by taking the node elements as units to form a component library;
the secondary configuration unit is used for determining required components according to the operation requirements of each flow by taking the components of the component library as basic units and adjusting the layout structure relationship among the components, and finally constructing a flow page containing one or more components.
10. The apparatus of claim 9, wherein the apparatus is further configured to:
in the secondary configuration step, a flow page containing one or more components is constructed by carrying out online dragging on the components in the component library.
11. The apparatus of claim 9, wherein the library of components has integrated therein an extension component developed by a third party.
12. The apparatus of claim 8, wherein the matching module is further configured to:
integrating a plurality of sub-matching rules, and setting priority for each sub-matching rule; and each sub-matching rule is adapted one by one according to the priority from high to low, and when matching is realized according to any one sub-matching rule, 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.
13. The apparatus of claim 8, wherein the data providing module is further configured to:
querying a database based on the published information to obtain component data of the target input type component;
and in the operation stage of each flow instance of each flow, receiving the release information of the component data provided by the flow components of each flow, and storing the component data into the database.
14. The apparatus of claim 8, wherein the apparatus is further configured to:
after receiving the data request sent by the exhibition component of the first flow, providing the component data of the target input component to the exhibition component of the first flow, so that the exhibition component can execute page rendering in a browser based on the component data of the target input component.
15. A component data management apparatus of a flow, 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, the instructions being executable by the at least one processor to enable the at least one processor to perform: the method of any one of claims 1-7.
16. 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 any of claims 1-7.
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 CN112800030A (en) | 2021-05-14 |
| CN112800030B true 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) |
Families Citing this family (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 (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
| 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 |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8356011B2 (en) * | 2005-07-26 | 2013-01-15 | Microsoft Corporation | Organizing presence information into collections of publications |
| GB0623914D0 (en) * | 2006-11-30 | 2007-01-10 | Ibm | 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 |
| US8229736B2 (en) * | 2008-04-16 | 2012-07-24 | International Business Machines Corporation | Transforming a natural language request for modifying a set of subscriptions for a publish/subscribe topic string |
| US10002202B2 (en) * | 2010-05-28 | 2018-06-19 | Microsoft Technology Licensing, Llc | Realtime websites with publication and subscription |
| US9285800B2 (en) * | 2011-11-11 | 2016-03-15 | Rockwell Automation Technologies, Inc | Systems and methods for asynchronous searching and filtering of data |
| US11308264B2 (en) * | 2015-07-07 | 2022-04-19 | International Business Machines Corporation | Managing document annotations in a publish/subscribe system |
| CN110555028A (en) * | 2019-08-22 | 2019-12-10 | 上海数禾信息科技有限公司 | data display method and device |
-
2021
- 2021-02-08 CN CN202110180629.9A patent/CN112800030B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
| CN111752540A (en) * | 2020-06-28 | 2020-10-09 | 北京百度网讯科技有限公司 | Tree component generation method, device, equipment and computer storage medium |
Non-Patent Citations (3)
| Title |
|---|
| 发布_订阅中间件中的可配置流程控制机制研究;曹旻;《信息科技》;全文 * |
| 基于"发布-订阅"模型的异构信息资源获取技术;姜振华等;《信息技术与信息化》;20150720;全文 * |
| 组件化数据监显软件设计与实现;王毅;赵俊翔;封慧英;薛凯;;计算机测量与控制;20171125(11);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112800030A (en) | 2021-05-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5154002B2 (en) | Method, system, and apparatus for providing access to a workbook model via remote function calls | |
| US7721205B2 (en) | Integration of composite objects in host applications | |
| US9262850B2 (en) | Descriptive framework for data visualization | |
| CN105511873B (en) | User interface control display method and device | |
| JP2016224923A (en) | Method and system for automated generation of user form interface | |
| US10120886B2 (en) | Database integration of originally decoupled components | |
| CN107622080B (en) | Data processing method and equipment | |
| CN113495797B (en) | Message queue and consumer dynamic creation method and system | |
| EP3812917A1 (en) | Data structure reading method and apparatus, data structure updating method and apparatus, and electronic device | |
| CA3142770A1 (en) | Component linkage configuration method, device, computer equipment and storage medium | |
| CN112800030B (en) | Method and device for managing component data of flow and computer readable storage medium | |
| CN115841236A (en) | Business modeling method, device and medium for realizing quick response | |
| US20130127863A1 (en) | Determining an optimal sequence of status transitions for business objects | |
| CN108241620B (en) | Query script generation method and device | |
| US9230022B1 (en) | Customizable result sets for application program interfaces | |
| CN108241624B (en) | Query script generation method and device | |
| CN116167882A (en) | Conditional expression dynamic configuration method, accounting condition calculation method and accounting condition calculation device | |
| CN113485686B (en) | Information system program generation method and device, electronic equipment and storage medium | |
| CN115617338A (en) | Method and device for quickly generating service page and readable storage medium | |
| CN111651160B (en) | Plug-in construction and webpage design method and device | |
| CN115016769A (en) | Scaffold building method based on field drive design and application development method | |
| CN115328458A (en) | Business application development method and device | |
| CN110874322A (en) | Test method and test server for application program | |
| CN115687704A (en) | Information display method and device, electronic equipment and computer readable storage medium | |
| CN114691112A (en) | Data processing method and device and data processing server |
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 |