WO2023109074A1 - Procédé et appareil de mise en œuvre d'une fonction de liaison, dispositif, support de stockage et programme - Google Patents

Procédé et appareil de mise en œuvre d'une fonction de liaison, dispositif, support de stockage et programme Download PDF

Info

Publication number
WO2023109074A1
WO2023109074A1 PCT/CN2022/100726 CN2022100726W WO2023109074A1 WO 2023109074 A1 WO2023109074 A1 WO 2023109074A1 CN 2022100726 W CN2022100726 W CN 2022100726W WO 2023109074 A1 WO2023109074 A1 WO 2023109074A1
Authority
WO
WIPO (PCT)
Prior art keywords
linkage
node
component
condition
component node
Prior art date
Application number
PCT/CN2022/100726
Other languages
English (en)
Chinese (zh)
Inventor
郑荣东
江旻
王大飞
陈秋雁
黎联成
Original Assignee
深圳前海微众银行股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳前海微众银行股份有限公司 filed Critical 深圳前海微众银行股份有限公司
Publication of WO2023109074A1 publication Critical patent/WO2023109074A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/33—Intelligent editors
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/36—Software reuse
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/38—Creation or generation of source code for implementing user interfaces

Definitions

  • This application relates to the technical field of cloud computing in financial technology (Fintech), and involves but is not limited to a method, device, electronic device, computer storage medium and computer program product for realizing linkage functions.
  • the present application provides a method, device, electronic equipment, computer storage medium and computer program product for realizing the linkage function, which can solve the problems of limited generalization and high cost in iterative development of Formily linkage development in the related art.
  • the embodiment of the present application provides a method for realizing the linkage function, which is applied to the low-code core class of the Formily framework, and the method includes:
  • the JSON Schema configuration sent from the user page;
  • the JSON Schema configuration is obtained by the user page from the page designer;
  • the JSON Schema configuration includes linkage configuration information for describing multiple component nodes of the user page , and the linkage configuration information of different component nodes corresponds to the same data structure specification;
  • the linkage configuration information of each component node in the plurality of component nodes is obtained; according to the data structure specification, the linkage configuration information of each component node is subjected to linkage analysis processing, and the linkage analysis is obtained.
  • the processed linkage function code is
  • the linkage function code for each component node is realized by using the linkage function code after the linkage analysis and processing.
  • the component node includes multiple pieces of linkage configuration information, and each piece of linkage configuration information in the multiple pieces of linkage configuration information includes: the final setting result of the component node and linkage conditions; the linkage conditions include condition node paths and Condition component node type;
  • the linkage function code after the linkage analysis and processing is used to perform the following steps:
  • the current linkage configuration information included in the current component node according to the condition node path and the condition component node type in the linkage condition, find out the component nodes from the remaining component nodes;
  • the current component node represents the plurality of component nodes Among the component nodes that currently need linkage analysis and processing, the remaining component nodes represent component nodes in the plurality of component nodes except the current component node;
  • the linkage condition further includes a condition node value and a condition node value type, and the judging whether the found component node satisfies the linkage condition includes:
  • condition value after the type conversion is the same as the condition node value in the linkage condition, determine that the found component node satisfies the linkage condition;
  • condition value after the type conversion is different from the condition node value in the linkage condition, it is determined that the found component node does not satisfy the linkage condition.
  • linkage function code after the linkage analysis and processing to realize the linkage function for each component node includes:
  • the linkage function code is invoked through the linkage function api to realize the linkage function for each component node.
  • the method also includes:
  • the verification function code for each component node is realized by using the verification function code after the verification analysis.
  • the component node includes multiple pieces of linkage configuration information, and each piece of linkage configuration information in the multiple pieces of linkage configuration information includes: the final setting result of the component node and linkage conditions; the linkage conditions include condition node paths and Condition component node type;
  • the verification function code after the linkage analysis and processing is used to perform the following steps:
  • the current linkage configuration information included in the current component node according to the condition node path and the condition component node type in the linkage condition, find out the component nodes from the remaining component nodes;
  • the current component node represents the plurality of component nodes Among the component nodes that currently need linkage analysis and processing, the remaining component nodes represent component nodes in the plurality of component nodes except the current component node;
  • finding the component node from other component nodes includes:
  • a component node of the same type as the conditional component node in the linkage condition is found from the partial component nodes.
  • said verifying and parsing the processed verifying function code to realize the verifying function of each component node includes:
  • the verification function for each component node is realized by executing the verification function code.
  • the method further includes:
  • the embodiment of the present application also proposes a device for realizing the linkage function, the device includes a receiving module, an obtaining module and a linkage module, wherein,
  • the receiving module is configured to receive the JSON Schema configuration sent from the user page; the JSON Schema configuration is obtained by the user page from the page designer; the JSON Schema configuration includes multiple components for describing the user page
  • the linkage configuration information of the node, and the linkage configuration information of different component nodes corresponds to the same data structure specification;
  • Obtaining a module configured to obtain the linkage configuration information of each component node in the plurality of component nodes by traversing the JSON Schema configuration; performing linkage analysis on the linkage configuration information of each component node according to the data structure specification processing to obtain the linkage function code after linkage analysis and processing;
  • the linkage module is configured to realize the linkage function of each component node by using the linkage function code after the linkage analysis and processing.
  • An embodiment of the present application provides an electronic device, the device includes a memory, a processor, and a computer program stored on the memory and operable on the processor, and the processor implements one or more of the aforementioned technologies when executing the program The method provided by the scheme to realize the linkage function.
  • An embodiment of the present application provides a computer storage medium, and the computer storage medium stores a computer program; after the computer program is executed, the method for realizing the linkage function provided by the aforementioned one or more technical solutions can be implemented.
  • the embodiment of the present application also provides a computer program product, including computer readable code, when the computer readable code is run in the electronic device, the processor in the electronic device executes to implement the aforementioned one or more The method for realizing the linkage function provided by the technical solution.
  • the embodiment of the present application proposes a method, device, electronic device, computer storage medium, and computer program product for realizing the linkage function, which are applied to the low-code core class of the Formily framework, and the method includes: receiving the JSON sent from the user page Schema configuration; the JSON Schema configuration is obtained by the user page from the page designer; the JSON Schema configuration includes linkage configuration information for describing multiple component nodes of the user page, and the linkage of different component nodes
  • the configuration information corresponds to the same data structure specification; by traversing the JSON Schema configuration, the linkage configuration information of each component node in the plurality of component nodes is obtained; the linkage configuration of each component node according to the data structure specification
  • the information is subjected to linkage analysis and processing to obtain a linkage function code after linkage analysis and processing; using the linkage function code after linkage analysis and processing to realize the linkage function of each component node.
  • each component node included in the JSON Schema configuration corresponds to the same data structure specification
  • you can Based on a generalized data structure specification these component nodes are linked and analyzed.
  • the problem of limited generalization of linked development can be solved; further, when these component nodes are linked and analyzed according to the data structure specification , by combing the rules of each protocol field in the data structure specification, the function code for realizing the linkage function can be automatically generated, so that developers do not need to hand-write code blocks related to complex linkage functions every time, and solve the cost of linkage functions in iterative development high question.
  • FIG. 1A is a schematic flow diagram of a method for realizing a linkage function in an embodiment of the present application
  • Fig. 1B is a schematic flow diagram of executing linkage function codes in the embodiment of the present application.
  • FIG. 1C is a schematic diagram of a data structure specification in the embodiment of the present application.
  • FIG. 2A is a schematic diagram of a scenario for implementing a linkage verification function according to an embodiment of the present application
  • FIG. 2B is a schematic flow diagram of performing linkage analysis processing and verification analysis processing according to an embodiment of the present application
  • FIG. 2C is another schematic flow diagram of linkage analysis processing according to the embodiment of the present application.
  • FIG. 2D is another schematic flowchart of verification and analysis processing according to the embodiment of the present application.
  • Fig. 3 is a schematic diagram of the composition and structure of the device for realizing the linkage function according to the embodiment of the present application;
  • FIG. 4 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • the term “comprising”, “comprising” or any other variation thereof is intended to cover a non-exclusive inclusion, so that a method or device comprising a series of elements not only includes the explicitly stated elements, but also include other elements not explicitly listed, or also include elements inherent in implementing the method or apparatus.
  • an element defined by the phrase “comprising a" does not exclude the presence of additional related elements (such as steps in the method or A unit in an apparatus, for example, a unit may be part of a circuit, part of a processor, part of a program or software, etc.).
  • the method for realizing the linkage function provided by the embodiment of the present application includes a series of steps, but the method for realizing the linkage function provided by the embodiment of the present application is not limited to the steps described.
  • the method for realizing the linkage function provided by the embodiment of the present application The functional device includes a series of modules, but the device for realizing the linkage function provided by the embodiment of the application is not limited to include the modules explicitly recorded, and may also include the required settings for obtaining relevant task data or processing based on task data module.
  • the embodiments of the present application can be applied to a computer system composed of servers, and can operate together with many other general-purpose or special-purpose computing system environments or configurations.
  • the server may be a distributed cloud computing technology environment including a small computer system, a large computer system, and so on.
  • program modules may include routines, programs, objects, components, logic, data structures, etc., that perform particular tasks or implement particular abstract data types.
  • the computer system/server can be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computing system storage media including storage devices.
  • Formily has three ways of using Markup Schema, JSON Schema, and JSX; the embodiment of this application can be aimed at the way of using JSON Schema.
  • the JSON Schema protocol data type used by Formily is not rich enough.
  • the JSON Schema used by Formily is a JSON string, which is generated by the page designer.
  • the value corresponding to the JSON string is mostly entered manually by the user through the input box, the obtained value is a string type.
  • Formily's schema type (type) only supports string, object, array, number, boolean, void, date and datetime. Therefore, when encountering basic types such as Boolean values (true, false), the input box of string type cannot correctly convert the string type value into a Boolean type value.
  • Formily's schema type cannot be converted correctly through string type values.
  • Formily's linkage development has limitations in generalization and high cost in iterative development.
  • the method for realizing the linkage function can be implemented by using a processor in a device for realizing the linkage function, and the above-mentioned processor can be an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a digital signal processor ( Digital Signal Processor, DSP), Digital Signal Processing Device (Digital Signal Processing Device, DSPD), Programmable Logic Device (Programmable Logic Device, PLD), Field Programmable Logic Gate Array (Field Programmable Gate Array, FPGA), CPU At least one of (Central Processing Unit, CPU), controller, microcontroller, microprocessor.
  • ASIC Application Specific Integrated Circuit
  • DSP Digital Signal Processor
  • DSPD Digital Signal Processing Device
  • PLD Programmable Logic Device
  • FPGA Field Programmable Logic Gate Array
  • CPU At least one of (Central Processing Unit, CPU), controller, microcontroller, microprocessor.
  • Fig. 1A is a schematic flowchart of a method for realizing linkage function in the embodiment of the present application. As shown in Fig. 1A, the method includes the following steps:
  • Step 100 Receive the JSON Schema configuration sent from the user page; the JSON Schema configuration is obtained by the user page from the page designer; the JSON Schema configuration includes linkage configuration information for describing multiple component nodes of the user page, and different component nodes
  • the linkage configuration information corresponds to the same data structure specification.
  • the method for realizing the linkage function can be applied to the low-code core class of the Formily framework;
  • the Formily framework includes not only the low-code core class, but also a user page and a page designer; wherein, the user page can be the World Wide Web ( The WEB interface corresponding to the World Wide Web (WEB) application can also be other human-computer interaction interfaces; the page designer is a page design platform developed by low-code, which can finally output a JSON data conforming to the JSON Schema protocol.
  • the low-code core class receives the JSON Schema configuration sent from the user page; as an example, the implementation process can be as follows, when the user page is opened, a data request for obtaining the JSON Schema configuration is sent to the page designer through the user page , when the page designer receives the data request, it returns the JSON Schema configuration to the user page, and sends the JSON Schema configuration to the low-code core class. At this time, the low-code core class receives the JSON Schema configuration sent from the user page .
  • the JSON Schema configuration can be represented by a tree data structure in JSON format, where the tree data structure is composed of multiple component nodes describing the user page; here, the component node representation is used to describe the user page
  • the node corresponding to the data information of the component.
  • the component node can be an abstract data type of view plus interactive logic, and can include hypertext markup language (hypertext markup language, html) templates, cascading style sheets (cascading style sheets, css) styles and js (javascript) Logical code snippets.
  • Step 101 By traversing the JSON Schema configuration, obtain the linkage configuration information of each component node among multiple component nodes; perform linkage analysis processing on the linkage configuration information of each component node according to the data structure specification, and obtain the linkage function after linkage analysis processing code.
  • the linkage configuration array saves the linkage configuration information from all component nodes in the JSON Schema configuration; here, the linkage configuration array is located in the cache of the low-code core class.
  • the linkage configuration information can be saved according to the format [ ⁇ "key", “data structure specification” ⁇ ]; here "key” represents the component node identity number (identity document, id).
  • key represents the component node identity number (identity document, id).
  • the linkage analysis processing is equivalent to declaring the code blocks corresponding to each protocol field in the linkage configuration information.
  • the linkage analysis processing it can be automated. Generate subsequent function codes required to realize the linkage function of each component node. It can be seen that in this process, there is no need for developers to write code blocks related to linkage functions by hand, so the problem of high cost in iterative development of linkage functions can be solved.
  • Step 102 Realize the linkage function for each component node by using the linkage function code after linkage analysis and processing.
  • a component node may include multiple pieces of linkage configuration information, wherein each piece of linkage configuration information in the multiple pieces of linkage configuration information may include the final setting result of the component node and linkage conditions; wherein, the linkage conditions may include condition node paths and Condition component node type.
  • the linkage function code after linkage analysis and processing is used to perform the following steps:
  • Step 1021 In the current linkage configuration information included in the current component node, according to the condition node path and the condition component node type in the linkage condition, find out the component node from other component nodes;
  • Step 1022 Determine whether the found component nodes meet the linkage condition
  • Step 1023 When it is determined that the found component node satisfies the linkage condition, determine that the current linkage configuration information satisfies the linkage condition, and set the final setting result in the current linkage configuration information to the result of the current component node.
  • the current component node represents a component node among the multiple component nodes that needs to be analyzed and processed currently; the rest of the component nodes represent component nodes among the multiple component nodes except the current component node.
  • finding the component node from the remaining component nodes may include: determining the part corresponding to the condition node path in the linkage condition from the remaining component nodes Component nodes; find component nodes of the same type as the conditional component nodes in the linkage condition from some component nodes.
  • the linkage condition of the current component node first, according to the condition node path in the linkage condition of the current component node, find out some component nodes under the condition node path from the remaining component nodes; Traverse each component node in some component nodes to find out the component node with the same type as the conditional component node in the linkage condition.
  • the found component node satisfies the linkage condition
  • the final setting result in the current linkage configuration information can be set to the result of the current component node
  • next linkage configuration information included in the component node check whether the found component node satisfies the linkage condition until the linkage configuration information matching the current component node is found; If the linkage configuration information matching the current component node is found, it means that the current component node does not need to trigger linkage.
  • the linkage condition may also include a condition node value and a condition node value type, and judging whether the found component node satisfies the linkage condition may include: pairing the searched component node according to the condition node value type in the linkage condition Convert the condition node value to get the condition value after type conversion; if the condition value after type conversion is the same as the condition node value in the linkage condition, it is determined that the found component node meets the linkage condition; after the type conversion If the condition value is not the same as the condition node value in the linkage condition, it is determined that the found component node does not satisfy the linkage condition.
  • the found component node if it is determined that the found component node meets the linkage condition, it means that the current linkage configuration information contained in the current component node meets the linkage condition; otherwise, if it is determined that the found component node does not meet the linkage condition, it means that the current component node includes The current linkage configuration information for does not meet the linkage conditions.
  • the linkage configuration information of each component node in the JSON Schema configuration corresponds to the same data structure specification; here, the data structure specification is a generalized protocol specification newly defined in this application; FIG. A schematic diagram of a data structure specification, as shown in Figure 1C, the data structure specification "includeAttributeValues" can be expressed in the form of ⁇ values, condition ⁇ key, values, formType, valueType ⁇ , errorMsg ⁇ ; below, the data structure Each attribute (that is, the protocol field) in the specification is described.
  • the values attribute represents the final setting result of the component node that needs to be analyzed and processed in conjunction; it should be noted that for different types of component nodes, the types of corresponding values can be different.
  • the component node is an Input component
  • values The value represents the type of linkage condition
  • the component node is a Select component
  • the values value represents the range of options
  • the condition attribute defines the conditions required for the linkage judgment of the component node, and the purpose of setting the judgment conditions in the condition attribute is to facilitate
  • the code core class performs code analysis for linkage condition judgment.
  • condition.key (the key in the condition attribute) represents the path of the condition node that needs to be observed, specifically how to observe the implementation of the linkage function code obtained by subsequent analysis.
  • condition.values (values in the condition attribute) represents the condition node value, which defines the specific value of the judgment condition.
  • condition.formType (formType in the condition attribute) represents the condition component node type, and each component node encapsulates its own linkage analysis method.
  • condition.valueType (valueType in the condition attribute) defines the data type of the condition node; here, condition.values and condition.valueType appear in pairs; errorMsg represents the error message.
  • the component node corresponding to condition.formType will first perform type conversion according to condition.valueType, and then judge the condition node value of the component node corresponding to condition.formType to determine Whether the current component node that requires linkage parsing and processing meets the linkage conditions.
  • the various attributes included in the data structure specification are sorted out through actual business, and they describe the key data information related to the linkage of component nodes.
  • Corresponding linkage parsing and processing of linkage configuration information can solve the problem that linkage development is limited in generalization.
  • the found component node in the process of judging whether the found component node satisfies the linkage condition according to the current linkage configuration information included in the current component node, it may be traversed according to the component node id of each component node in the found component node , judge one by one whether the value of the condition node after the type conversion of each component node is the same as the value of the condition node in the linkage condition of the current component node.
  • the linkage configuration information satisfies the linkage condition.
  • the final setting result in the current linkage configuration information can be set to the result of the current component node.
  • the found component node does not meet the linkage condition, that is, the current linkage configuration information does not meet the linkage condition.
  • the linkage configuration information matching the current component node is found; if the linkage configuration information matching the current component node cannot be found among the multiple linkage configuration information included in the current component node, it means that the current component node does not need to trigger linkage.
  • the linkage configuration information matching the current component node can be found from the multiple pieces of linkage configuration information included in the current component node, and the linkage configuration information can be used for subsequent implementation of the current component node. linkage.
  • using the linkage function code after linkage analysis and processing to realize the linkage function to each component node may include: registering the linkage function code after linkage analysis and processing into the linkage function api of the Formily framework; When the user page triggers linkage for each component node, the linkage function code is called through the linkage function api to realize the linkage function for each component node.
  • the corresponding linkage function code can be obtained, and the linkage function code can be registered in the Formily framework
  • the linkage function api is located in the user interface; later, when the user triggers linkage to the current component node through the user page, the corresponding linkage function code can be called according to the linkage function api, and by executing the linkage function code, you can Realize the linkage function of the current component node.
  • the embodiment of the present application proposes a method, device, electronic device, computer storage medium, and computer program product for realizing the linkage function, which are applied to the low-code core class of the Formily framework, and the method includes: receiving the JSON Schema configuration sent from the user page ;JSON Schema configuration is obtained by the user page from the page designer; JSON Schema configuration includes the linkage configuration information used to describe multiple component nodes of the user page, and the linkage configuration information of different component nodes corresponds to the same data structure specification; Traverse the JSON Schema configuration to obtain the linkage configuration information of each component node among multiple component nodes; perform linkage analysis and processing on the linkage configuration information of each component node according to the data structure specification, and obtain the linkage function code after linkage analysis and processing; use linkage Parse the processed linkage function code to realize the linkage function of each component node.
  • the above method may further include: performing verification and analysis processing on the linkage configuration information of each component node according to the data structure specification to obtain the verification function code after the verification and analysis processing;
  • the verification function code realizes the verification function of each component node.
  • the data structure specification for performing verification analysis processing is the same as the above-mentioned data structure specification for performing linkage analysis processing, and will not be repeated here.
  • the linkage configuration information of each component node is verified and analyzed according to the same data structure specification as the linkage analysis process, which can improve the accuracy of the verification result of the component node.
  • the verification function code after linkage analysis and processing is used to perform the following steps: in the current linkage configuration information included in the current component node, according to the condition node path and condition component node type in the linkage condition, Find the component nodes from the rest of the component nodes; the current component node represents the component node that needs to be analyzed and processed currently among the multiple component nodes, and the remaining component nodes represent the component nodes other than the current component node among the multiple component nodes; judge the found one Whether the component node meets the linkage condition;
  • the found component node satisfies the linkage condition, continue to judge whether the current component node passes the verification; here, passing the verification shows that the result of the current component node is consistent with the final The setting results are the same; if the verification fails, it means that the result of the current component node is different from the final setting result in the current linkage configuration information.
  • the verification function code of each component node is realized by using the verification function code after the verification analysis processing, which may include: registering the verification function code after the linkage analysis processing to the submission of the low-code core class In function; when the data recovery or submission operation is determined on the user page, the verification function of each component node is realized by executing the verification function code.
  • the above method may further include: performing type conversion on the output data of the verification function code according to the condition node data type in the linkage condition of the current component node.
  • the output data of the verification function code related to the current component node can be type-converted according to the condition node data type in the linkage condition of the current component node to obtain the verification function code final output.
  • the JSON Schema protocol data type can be enriched, and the problem that some data types cannot be correctly converted through the string type in related technologies can be solved.
  • Fig. 2A is a schematic diagram of a scenario for realizing the linkage verification function according to an embodiment of the present application. As shown in Fig. 2A, the figure includes: a user page, a low code core class (LowcodeCore) and a page designer; the specific implementation process can be as follows :
  • the user page sends a data request to the page designer to obtain the JSON Schema configuration; when the page designer receives the data request, it returns the JSON Schema configuration to the user page; after receiving the JSON Schema configuration, the user page sends the JSON Schema configuration Configuration is sent to low-code core classes.
  • the low-code core class finds out the linkage configuration information of each component node under each level of node tree by traversing the tree data structure configured by JSON Schema and saves it in the linkage configuration array; the low-code core class performs linkage configuration according to the data structure specification
  • the linkage configuration information of each component node in the configuration array is analyzed for linkage and verification, and the linkage function code and verification function code are automatically generated.
  • Fig. 2B is a schematic flow diagram of a linkage analysis process and verification analysis process according to an embodiment of the present application. As shown in Fig. 2B, the process includes the following steps:
  • Step A1 Obtain the linkage configuration array.
  • the low-code core class obtains a linkage configuration array from its own cache, and the linkage configuration array includes linkage configuration information of all component nodes in the JSON Schema configuration.
  • Step A2 Determine the work type as linkage type.
  • the work type includes two types: linkage type and verification type.
  • Step A3 Carry out linkage parsing and processing according to the data structure specification.
  • the low-code core class after determining that the current work type is a linkage type, performs linkage analysis and processing on multiple pieces of linkage configuration information in the linkage configuration array corresponding to the current component node according to the data structure specification.
  • Step A4 Find the linkage configuration information that meets the linkage conditions by traversing the linkage configuration array.
  • Step A5 Set the values in the linkage configuration information to the current component node.
  • the values value corresponds to the final setting result in the above-mentioned current linkage configuration information; after traversing the linkage configuration array to determine that all component nodes in the current linkage configuration information meet the linkage conditions, the current linkage configuration information
  • the values (final setting result) in are set to the current component node; at this time, the linkage analysis processing for the current component node is completed, and the linkage function code after the linkage analysis processing is obtained.
  • Step A2' Determine the work type as the verification type.
  • Step A3' Perform verification and parsing processing according to the data structure specification.
  • the low-code core class determines that the current work type is the verification type, it performs verification analysis processing on multiple pieces of linkage configuration information in the linkage configuration array corresponding to the current component node according to the data structure specification.
  • Step A4' find the linkage configuration information satisfying the linkage condition by traversing the linkage configuration array.
  • Step A5' Judging whether it is equal to the result of the current component node.
  • the linkage configuration information that satisfies the linkage condition, it is judged whether the values (final setting result) in the linkage configuration information is equal to the result of the current component node; if yes, it means that the verification function of the current component node is passed. , the verification is successful; otherwise, it indicates that the verification function of the current component node has failed, and at this time, the verification failure is returned.
  • FIG. 2C is another schematic flow diagram of the linkage analysis process according to the embodiment of the present application. As shown in FIG. 2C, the process includes the following steps :
  • Step B1 Obtain the linkage configuration array.
  • Step B2 Obtain the current linkage configuration information of the current component node.
  • the current piece of linkage configuration information of the current component node can be acquired from the linkage configuration array in a traversal manner.
  • the current component node represents the JSON description of one of the user interface (User Interface, UI) components in the JSON Schema tree configuration describing the current user page.
  • Step B3 Determine whether the current component node has changed.
  • Step B4 Determine some component nodes according to the conditional node path in the linkage condition.
  • some component nodes are determined according to the path of the conditional node in the linkage condition.
  • Step B5 Obtain the ComponentSchema component instance of the found component node according to the conditional component node type in the linkage condition.
  • Step B6 Pass the condition node value type and condition node value in the linkage condition to the ComponentSchema component instance of the found component node.
  • the ComponentSchema component instance after passing the condition node value type and condition node value in the linkage condition to the ComponentSchema component instance of the found component node, the ComponentSchema component instance will match the found component node according to the condition node value type in the linkage condition Perform type conversion on the condition node value of each component node in , and obtain the condition value after type conversion; judge the condition value after type conversion and the condition node value in the linkage condition, and determine whether the found component nodes satisfy the linkage condition .
  • Step B7 Judging whether the linkage condition is met. If yes, execute step B8, otherwise, execute step B4 for determining whether the next piece of linkage configuration information included in the current component node satisfies the linkage condition.
  • the found component node satisfies the linkage condition, and when it is determined that the type-converted condition value corresponding to the found component node is the same as the condition node value in the linkage condition, it is determined that the found component node satisfies The linkage condition, that is, the current linkage configuration information satisfies the linkage condition; otherwise, it is determined that the current linkage configuration information does not meet the linkage condition.
  • Step B8 Obtain the ComponentSchema component instance of the current component node, and transfer the values in the current linkage configuration information to the ComponentSchema component instance of the current component node for setting.
  • the ComponentSchema component instance of the current component node when it is determined that the current linkage configuration information satisfies the linkage condition, the ComponentSchema component instance of the current component node can be obtained, and the values in the current linkage configuration information can be transferred to the ComponentSchema component instance of the current component node for further processing.
  • the setting of the linkage result that is, setting the values (final setting result) in the current linkage configuration information to the ComponentSchema component instance of the current component node.
  • the linkage configuration array relationConfigArr including the linkage configuration information of all component nodes is taken out from the low-code core class.
  • the current component node in the linkage configuration array can represent For: '[ ⁇ "key”:"detail.identity”,”includeAttributeValues”:[ ⁇ "values":[ ⁇ "regex”:" ⁇ S”,”errorRemind”:”” ⁇ ],”condition”: [ ⁇ "key”:”detail.identityType”,”values":[ ⁇ "label”:"ID card”,”value":"0" ⁇ ],”formType”:”select”,”valueType”:” 2" ⁇ ] ⁇ ] ⁇ ]'; relationConfigArr.*.key represents the current component node id, and relationConfigArr.*.includeAttributeValues represents the linkage configuration information of the current component node.
  • the linkage configuration information relationConfig of the current component node is as follows: ( ⁇ "includeAttributeValues":[ ⁇ "values":[ ⁇ "regex”:" ⁇ S","errorRemind”:”” ⁇ ],”condition”:[ ⁇ "key”:”detail.
  • identityType "values":[ ⁇ "label”:"ID card”,”value":"0" ⁇ ]
  • formType "select”
  • Formily's data source ⁇ detail: ⁇ identity,identityType ⁇
  • condition node of relationConfig configures the condition node of relationConfig as the linkage judgment condition, use the value of condition.key as "detail.identityType" as the dependency path, and then call Formily's API onFieldValueChange with the condition.key path as detail.
  • the data of identityType monitors and registers a callback function. In the callback function, when the detail.identityType changes, get the result of detail.identityType from the formal parameter of the callback function. Then obtain the corresponding ComponentSchema component instance according to the condition.formType component type, pass the range values of the detail.identityType and condition.values judgment conditions to the ComponentSchema component instance and call validate for verification.
  • condition condition check passes, it means that the linkage condition of the current component is satisfied, otherwise it is not satisfied. Then use Array.some to traverse, verify and analyze the component nodes in the linkage configuration array. If there is a condition condition in the linkage configuration array that passes the verification of the ComponentSchema component instance, set the linkage result includeAttributeValues.*.values to the configuration relationConfig. On the component corresponding to key, the component corresponding to relationConfig.key will call Formily API setFieldState according to the current component rules to set the linkage result includeAttributeValues.*.values to the correct attribute.
  • Fig. 2D is another schematic flow diagram of verification analysis processing according to the embodiment of the present application. As shown in Fig. 2D, the flow includes the following steps:
  • Step C1 Obtain the linkage configuration array.
  • Step C2 Obtain the linkage configuration information of the component nodes that need to be parsed and processed in linkage.
  • linkage configuration information of all component nodes requiring linkage parsing and processing may be acquired from the linkage configuration array in a traversal manner.
  • Step C3 Verify according to the linkage configuration information of the current component node.
  • the current component node is a component node among all component nodes that need to be linked and parsed.
  • Step C4 Judging whether all checks are passed.
  • step C12 and step C13 in sequence If yes, execute step C12 and step C13 in sequence, otherwise, execute step C5.
  • Step C5 Obtain the ComponentSchema component instance of the found component node according to the conditional component node type in the linkage condition.
  • Step C6 Pass the condition node value type and condition node value in the linkage condition of the current component node to the ComponentSchema component instance of the found component node.
  • steps C5 to C6 are implemented in the same way as the above steps B5 to B6, and will not be repeated here.
  • Step C7 Judging whether the linkage condition is met. If yes, execute step C8, otherwise, execute step C4 to determine whether all the component nodes that require linkage analysis and processing pass the verification, if not, follow the steps below to continue the linkage verification of the next component node of the current component node ; At this point, the default current component node check is passed.
  • Step C8 Get the ComponentSchema component instance of the current component node.
  • the ComponentSchema component instance of the current component node can be obtained
  • Step C9 Transfer the values in the current linkage configuration information to the ComponentSchema component instance of the current component node for verification.
  • Step C10 Judging whether the verification is passed.
  • Step C11 Return verification failure.
  • Step C12 Perform type conversion processing on the output data.
  • the output data of the verification function code related to the current component node can be type-converted to obtain the final output result.
  • Step C13 Return verification success.
  • the linkage configuration array relationConfigArr including the linkage configuration information of all component nodes is taken out from the low-code core class.
  • the current component node in the linkage configuration array can represent For: '[ ⁇ "key”:"detail.identity”,”includeAttributeValues”:[ ⁇ "values":[ ⁇ "regex”:" ⁇ S”,”errorRemind”:”” ⁇ ],”condition”: [ ⁇ "key”:”detail.identityType”,”values":[ ⁇ "label”:"ID card”,”value":"0" ⁇ ],”formType”:”select”,”valueType”:” 2" ⁇ ] ⁇ ] ⁇ ]'.
  • relationConfigArr.*.key represents the current component node id
  • relationConfigArr.*.includeAttributeValues represents the linkage configuration information of the current component node.
  • the linkage configuration information relationConfig of the current component node is as follows: ( ⁇ "includeAttributeValues":[ ⁇ "values":[ ⁇ "regex”:" ⁇ S","errorRemind”:”” ⁇ ],”condition”:[ ⁇ "key”:"detail.
  • identityType "values":[ ⁇ "label”:"ID card”,”value":"0" ⁇ ]
  • formType "select”
  • the result data source of the submitted operation ⁇ detail: ⁇ identity,identityType ⁇
  • condition node of relationConfig is used as the linkage judgment condition
  • value of condition.key "detail.identityType” is used as the dependency path to extract the value of detail.identityType from the data source, and then obtain it according to the condition.formType component type Go to the corresponding ComponentSchema component instance, pass the range values of the detail.identityType and condition.values judgment conditions to the ComponentSchema component instance and call validate for verification. If the match is successful, it means that the linkage condition node has passed, otherwise continue to traverse the next linkage configuration. If none of the conditional nodes match successfully, it can pass the verification on behalf of the current node relationConfig.key.
  • relationConfig.key node id.
  • relationConfig.key by configuring relationConfig.key to "detail.identity" as the value path, take out the verification value from the data source, and pass the verification value and includeAttributeValues.*.values matching result range to the ComponentSchema component instance for verification. Only when the verification value conforms to the result range of includeAttributeValues.*.values can the verification pass, otherwise the node verification of relationConfig.key returns failure. Then use Array.every to traverse and analyze the verification configuration array relationConfigArr of all nodes.
  • the verification function of the verification function code is confirmed to pass, otherwise return fail. After the verification function is passed, it is necessary to perform type conversion of the output data to obtain the final data data.
  • the process of conversion such as ComponentSchema component instance, has config attribute to represent configuration information, and config.valueType represents output data type. For example, when the valueType is a number type, the output data of the current node needs to be processed as a number type. For example, 1 in a string will be updated to 1 in a number type.
  • the final verification function code is successful, output the verification result and output data such as ⁇ status: true, data: ⁇ a1, a2, a3 ⁇ .
  • Fig. 3 is a schematic diagram of the composition and structure of the device for realizing the linkage function according to the embodiment of the present application.
  • the device includes a receiving module 300, an obtaining module 301 and a linkage module 302, wherein,
  • the receiving module 300 is configured to receive the JSON Schema configuration sent from the user page; the JSON Schema configuration is obtained by the user page from the page designer; the JSON Schema configuration includes multiple The linkage configuration information of component nodes, and the linkage configuration information of different component nodes corresponds to the same data structure specification;
  • the obtaining module 301 is configured to obtain the linkage configuration information of each component node in the plurality of component nodes by traversing the JSON Schema configuration; perform linkage to the linkage configuration information of each component node according to the data structure specification Analyzing and processing to obtain the linkage function code after linkage analysis and processing;
  • the linkage module 302 is configured to use the linkage function code after the linkage analysis and processing to realize the linkage function for each component node.
  • the component node includes multiple pieces of linkage configuration information, and each piece of linkage configuration information in the multiple pieces of linkage configuration information includes: the final setting result of the component node and a linkage condition; the linkage condition includes a condition node path and condition component node types;
  • the linkage function code after the linkage analysis and processing is used to perform the following steps:
  • the current linkage configuration information included in the current component node according to the condition node path and the condition component node type in the linkage condition, find out the component nodes from the remaining component nodes;
  • the current component node represents the plurality of component nodes Among the component nodes that currently need linkage analysis and processing, the remaining component nodes represent component nodes in the plurality of component nodes except the current component node;
  • the linkage condition further includes a condition node value and a condition node value type
  • the linkage module 302 is configured to determine whether the found component node satisfies the linkage condition, including:
  • condition value after the type conversion is the same as the condition node value in the linkage condition, determine that the found component node satisfies the linkage condition;
  • condition value after the type conversion is different from the condition node value in the linkage condition, it is determined that the found component node does not satisfy the linkage condition.
  • the linkage module 302 is configured to use the linkage function code after the linkage analysis and processing to realize the linkage function for each component node, including:
  • the linkage function code is invoked through the linkage function api to realize the linkage function for each component node.
  • the device further includes a verification module, and the verification module is configured to:
  • the verification function code for each component node is realized by using the verification function code after the verification analysis.
  • the component node includes multiple pieces of linkage configuration information, and each piece of linkage configuration information in the multiple pieces of linkage configuration information includes: the final setting result of the component node and a linkage condition; the linkage condition includes a condition node path and condition component node types;
  • the verification function code after the linkage analysis and processing is used to perform the following steps:
  • the current linkage configuration information included in the current component node according to the condition node path and the condition component node type in the linkage condition, find out the component nodes from the remaining component nodes;
  • the current component node represents the plurality of component nodes Among the component nodes that currently need linkage analysis and processing, the remaining component nodes represent component nodes in the plurality of component nodes except the current component node;
  • the checking module is configured to find out component nodes from other component nodes according to the condition node path and condition component node type in the linkage condition, including:
  • a component node of the same type as the conditional component node in the linkage condition is found from the partial component nodes.
  • the verification module is configured to implement the verification function of each component node by using the verification function code after the parsing and processing of the verification, including:
  • the verification function for each component node is realized by executing the verification function code.
  • the verification module is further configured to:
  • the above-mentioned receiving module 300, obtaining module 301, linkage module 302 and verification module can all be realized by a processor located in the electronic device, and the processor can be ASIC, DSP, DSPD, PLD, FPGA, CPU, At least one of controller, microcontroller, microprocessor.
  • each functional module in this embodiment may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software function modules.
  • the integrated unit is implemented in the form of a software function module and is not sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of this embodiment is essentially or The contribution made by related technologies or all or part of the technical solution can be embodied in the form of software products, the computer software products are stored in a storage medium, and include several instructions to make a computer device (which can be a personal computer) , server, or network device, etc.) or a processor (processor) executes all or part of the steps of the method in this embodiment.
  • aforementioned storage medium comprises: various mediums that can store program codes such as U disk, mobile hard disk, read-only memory (Read Only Memory, ROM), RAM, magnetic disk or optical disk.
  • the computer program instructions corresponding to a method for realizing the linkage function in this embodiment can be stored on a storage medium such as an optical disc, a hard disk, or a USB flash drive.
  • a storage medium such as an optical disc, a hard disk, or a USB flash drive.
  • FIG. 4 shows an electronic device 400 provided by an embodiment of the present application, which may include: a memory 401 and a processor 402; wherein,
  • memory 401 configured to store computer programs and data
  • the processor 402 is configured to execute the computer program stored in the memory, so as to implement any one of the methods for realizing the linkage function in the foregoing embodiments.
  • the above-mentioned memory 401 can be a volatile memory (volatile memory), such as RAM; or a non-volatile memory (non-volatile memory), such as ROM, flash memory (flash memory), hard disk (Hard Disk Drive, HDD) or solid-state drive (Solid-State Drive, SSD); or a combination of the above-mentioned types of memory, and provide instructions and data to the processor 402.
  • volatile memory such as RAM
  • non-volatile memory such as ROM, flash memory (flash memory), hard disk (Hard Disk Drive, HDD) or solid-state drive (Solid-State Drive, SSD); or a combination of the above-mentioned types of memory, and provide instructions and data to the processor 402.
  • the aforementioned processor 402 may be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, and microprocessor. It can be understood that, for different devices implementing linkage functions, the electronic device used to implement the above processor function may also be other, which is not specifically limited in this embodiment of the present application.
  • the embodiment of the present application also provides a computer program product, the computer program product carries a program code, and the instructions included in the program code can be used to execute the load balancing method described in the above method embodiment, for details, please refer to the above method embodiment , which will not be repeated here.
  • the above-mentioned computer program product may be specifically implemented by means of hardware, software or a combination thereof.
  • the computer program product is embodied as a computer storage medium, and in another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (Software Development Kit, SDK) etc. wait.
  • a software development kit Software Development Kit, SDK
  • the functions or modules included in the device provided by the embodiments of the present application can be used to execute the methods described in the above method embodiments, and its specific implementation can refer to the descriptions of the above method embodiments. For brevity, here No longer.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application 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, optical storage, etc.) having computer-usable program code embodied therein.
  • a computer-usable storage media including but not limited to disk storage, optical storage, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Des modes de réalisation de la présente invention concernent un procédé et un appareil de mise en œuvre d'une fonction de liaison, un dispositif électronique, un support de stockage informatique et un produit programme informatique, appliqués à une classe de noyau à faible code d'une infrastructure Formily. Le procédé consiste : à recevoir une configuration de schéma JSON envoyée à partir d'une page d'utilisateur, la configuration de schéma JSON étant obtenue par la page d'utilisateur à partir d'un concepteur de page, la configuration de schéma JSON comprenant des informations de configuration de liaison destinées à décrire une pluralité de nœuds de composant de la page d'utilisateur, et les informations de configuration de liaison de différents nœuds de composant correspondant à la même spécification de structure de données ; à traverser la configuration de schéma JSON pour obtenir les informations de configuration de liaison de chacun de la pluralité de nœuds de composant ; à effectuer une analyse de liaison sur les informations de configuration de liaison de chaque nœud de composant selon la spécification de structure de données pour obtenir un code de fonction de liaison après l'analyse de liaison ; et à mettre en œuvre une fonction de liaison de chaque nœud de composant à l'aide du code de fonction de liaison après l'analyse de liaison.
PCT/CN2022/100726 2021-12-17 2022-06-23 Procédé et appareil de mise en œuvre d'une fonction de liaison, dispositif, support de stockage et programme WO2023109074A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111552350.5 2021-12-17
CN202111552350.5A CN114385148A (zh) 2021-12-17 2021-12-17 一种实现联动功能的方法、装置、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2023109074A1 true WO2023109074A1 (fr) 2023-06-22

Family

ID=81197507

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/100726 WO2023109074A1 (fr) 2021-12-17 2022-06-23 Procédé et appareil de mise en œuvre d'une fonction de liaison, dispositif, support de stockage et programme

Country Status (2)

Country Link
CN (1) CN114385148A (fr)
WO (1) WO2023109074A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117472372A (zh) * 2023-10-27 2024-01-30 北京真内控科技有限公司 一种响应式表单搭建方法及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114385148A (zh) * 2021-12-17 2022-04-22 深圳前海微众银行股份有限公司 一种实现联动功能的方法、装置、设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200097268A1 (en) * 2018-09-21 2020-03-26 Salesforce.Com, Inc. Application builder with connected components
CN112487112A (zh) * 2020-12-17 2021-03-12 江苏苏宁云计算有限公司 一种组件联动配置的方法、装置、计算机设备及存储介质
CN113094561A (zh) * 2021-05-08 2021-07-09 中国工商银行股份有限公司 网页生成方法、网页生成装置、电子设备以及存储介质
CN114385148A (zh) * 2021-12-17 2022-04-22 深圳前海微众银行股份有限公司 一种实现联动功能的方法、装置、设备和存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200097268A1 (en) * 2018-09-21 2020-03-26 Salesforce.Com, Inc. Application builder with connected components
CN112487112A (zh) * 2020-12-17 2021-03-12 江苏苏宁云计算有限公司 一种组件联动配置的方法、装置、计算机设备及存储介质
CN113094561A (zh) * 2021-05-08 2021-07-09 中国工商银行股份有限公司 网页生成方法、网页生成装置、电子设备以及存储介质
CN114385148A (zh) * 2021-12-17 2022-04-22 深圳前海微众银行股份有限公司 一种实现联动功能的方法、装置、设备和存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117472372A (zh) * 2023-10-27 2024-01-30 北京真内控科技有限公司 一种响应式表单搭建方法及系统
CN117472372B (zh) * 2023-10-27 2024-04-09 北京真内控科技有限公司 一种响应式表单搭建方法及系统

Also Published As

Publication number Publication date
CN114385148A (zh) 2022-04-22

Similar Documents

Publication Publication Date Title
Gao et al. Checking smart contracts with structural code embedding
US10540270B1 (en) Representation-based automated software testing
US10177996B2 (en) System and method for validating documentation of representational state transfer (REST) services
US9483387B1 (en) Tree comparison functionality for services
US10901961B2 (en) Systems and methods for generating schemas that represent multiple data sources
WO2023109074A1 (fr) Procédé et appareil de mise en œuvre d'une fonction de liaison, dispositif, support de stockage et programme
US10452407B2 (en) Adapter configuration
KR101755365B1 (ko) 레코드 포맷 정보의 관리
US10824636B2 (en) Mechanisms for querying disparate data storage systems
Martin-Lopez et al. Specification and automated analysis of inter-parameter dependencies in web APIs
US10642863B2 (en) Management of structured, non-structured, and semi-structured data in a multi-tenant environment
US20170364386A1 (en) Event-Driven Multi-Tenant Computer-Management Platform
Felício et al. Rapitest: Continuous black-box testing of restful web apis
US20230040635A1 (en) Graph-based impact analysis of misconfigured or compromised cloud resources
WO2024000955A1 (fr) Procédé et appareil de mise à jour à chaud de page, dispositif et support d'enregistrement
CN117493158A (zh) 测试方法及其装置、电子设备、存储介质
CN113703739B (zh) 基于omiga引擎的跨语言融合计算方法、系统及终端
CN116088846A (zh) 一种持续集成代码格式的处理方法、相关装置及设备
CN117632710A (zh) 测试代码的生成方法、装置、设备及存储介质
US10719424B1 (en) Compositional string analysis
US20230072988A1 (en) System and a method for automatic generation of smart contracts across blockchain platforms
CN116346609A (zh) 基于go语言实现路由配置和参数绑定的方法
WO2021022702A1 (fr) Procédé et appareil d'insertion de journal, appareil informatique et support de stockage
WO2022111209A1 (fr) Procédé et appareil d'acquisition de données, dispositif d'acquisition de données et support de stockage lisible
Halfond Identifying inter-component control flow in web applications

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22905840

Country of ref document: EP

Kind code of ref document: A1