CN114063982A - Method for automatically constructing functional components based on multi-scenario application - Google Patents
Method for automatically constructing functional components based on multi-scenario application Download PDFInfo
- Publication number
- CN114063982A CN114063982A CN202111327979.XA CN202111327979A CN114063982A CN 114063982 A CN114063982 A CN 114063982A CN 202111327979 A CN202111327979 A CN 202111327979A CN 114063982 A CN114063982 A CN 114063982A
- Authority
- CN
- China
- Prior art keywords
- component
- application
- scene
- functional components
- functional
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- 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/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
本发明公开了一种基于多场景应用的自动构建功能组件的方法，包括以下步骤：S1：功能模块标准化、组件化：对接入的应用场景提供的服务进行清单化；S2：注册新增组件：复用场景组件库中已存在的功能组件，新增缺失的功能组件；S3：配置文件：确定应用需求，根据应用需求对接入的应用场景定义其专属配置文件；S4：调度机制生效，进行逻辑处理：定义完成配置文件后，通过解析制度和调度机制配合完成该应用场景的专属配置文件的解析，调用对应的功能组件完成应用处理。本发明能有效降低开发成本，通过功能组件配置化管理，通过一系列组件的定制、加载、运行就可快速实现业务需求，通过复用在用的功能组件可有效降低新项目生产运行事故风险。
The invention discloses a method for automatically constructing functional components based on multi-scenario applications, comprising the following steps: S1: standardization and componentization of functional modules: listing the services provided by the connected application scenarios; S2: registering new components : Reuse the existing functional components in the scene component library, and add the missing functional components; S3: Configuration file: Determine the application requirements, and define its own configuration file for the connected application scene according to the application requirements; S4: The scheduling mechanism takes effect, Perform logical processing: After the configuration file is defined, the analysis system and the scheduling mechanism are used to complete the analysis of the exclusive configuration file of the application scenario, and the corresponding functional components are called to complete the application processing. The invention can effectively reduce the development cost. Through the configuration management of functional components, business requirements can be quickly realized through the customization, loading and operation of a series of components, and the production and operation accident risk of new projects can be effectively reduced by reusing the functional components in use.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method for automatically constructing a functional component based on multi-scenario application.
Background
The customer requirements accepted by the banking industry are consistent in main body, but each customer can additionally provide a featured requirement under the condition that the basic requirements are met, so that the demand development is carried out on each type of customer requirements in a bank, a large amount of repeated development is needed, and a large amount of human resources are consumed. For example: when a bank accepts a batch issuance commission initiated by each group client, a client A requires to issue an issuance completion short message notification, a client B requires to examine and verify before the bank accepts a task, a client C requires to provide issuance data statistics, and a client D requires to issue an approval and needs to double recheck and other various characteristic requirements.
The invention patent application document with the application number of CN201911341274.6 discloses a quick implementation method for building application scenes in a componentization manner, which includes the following steps: step A, scene analysis is carried out; b, performing scene componentization; step C, carrying out scene configuration; step D, analyzing the configuration information; step E, constructing application; and F, deploying the application. The rapid implementation method for building the application scene in a componentization manner improves the building efficiency of the application scene and reduces the repeated development delivery time. But the method is mainly applied to the field of game application scene development.
The invention patent application document with the application number of CN201910987691.1 provides a label configuration method, a label configuration device and a computer storage medium, and solves the technical problems that similar labels cannot be reused and the workload is large when labels are newly added and updated. In the embodiment of the invention, component information is acquired, a label atomic component is constructed according to the component information, and the label atomic component is added into an atomic component set; acquiring label information, and selecting a label atom component from the atom component set according to the label information; tags are constructed based on the selected tag atom components. The embodiment of the invention modularizes the label, constructs the label based on the label atom component, enables the complex label to be formed by splicing a plurality of label atom components, and the similar label can be reused as long as the constructed label atom components are the same, thereby avoiding repeated development. When the label is newly added or updated, only the label atomic component needs to be newly added or updated, and the label constructed by the label atomic component can be updated, so that the workload is greatly reduced, and the difficulty in updating or newly adding the label on line is reduced. However, the invention aims at the problem of label management, and cannot solve the industrial problems that the customer requirements accepted by the banking industry are consistent in main body, but each customer can additionally provide a featured requirement under the condition that the basic requirement is met, so that the demand development is carried out on each type of customer requirement in a bank, a large amount of repeated development is needed, and a large amount of human resources are consumed.
Disclosure of Invention
The invention aims to provide a method for automatically constructing a functional component based on multi-scenario application, and aims to solve the problems that in the prior art, a bank needs to be developed according to the requirements of each type of customers, a large amount of repeated development is needed, and a large amount of human resources are consumed.
In order to achieve the above object, the present invention provides a method for automatically constructing a functional component based on multi-scenario application, which comprises the following steps:
s1: functional module standardization and componentization: listing the services provided by the accessed application scenes;
s2: registering the newly added component: reusing the existing functional components in the scene component library, and newly adding missing functional components;
s3: configuration files: determining application requirements, and defining an exclusive configuration file of an accessed application scene according to the application requirements;
s4: the scheduling mechanism takes effect, and logic processing is carried out: after the configuration file is defined, the analysis of the exclusive configuration file of the application scene is completed through the cooperation of an analysis system and a scheduling mechanism, and the corresponding functional component is called to complete application processing.
Furthermore, the configuration file is used for recording the logic flow that the application scenario needs to be executed successively from the service providing.
Further, the S1 includes the following steps before accessing the application scenario:
s00: accessing a new application scene, and determining functional components which need to be provided by the application scene;
s01: fuzzy search is carried out in the scene component library record list according to the names and the functions of the functional components, and whether the required functional components exist in the scene component library record list is judged;
s02: subscribing the required functional components existing in the scene component library record table, newly adding the required functional components not existing in the scene component library record table, and removing the dependency relationship among the components;
s03: and adding the newly added functional components in the S02 to the scene component library record table.
Further, the adding of the newly added functional component to the scene component library record table in S03 further includes: and sequentially recording the names of the newly added functional components, the function summaries, the input parameters and the output parameters, defining the output values and the abnormal output values of the newly added components after the successfully executed components, and defining the names of the subsequent flow components corresponding to the abnormal output values of each definition.
Furthermore, the scene component library record table is used for recording the developed functional component information, defining the input and output parameters of the functional component and an exception handling process.
Further, the S4 specifically includes the following sub-steps:
s41: initializing a business scene control table;
s42: starting an analysis mechanism and reading a flow configuration file;
s43: reading the name of the previous flow component, the name of the current flow component and the name of the next flow component by using an analysis mechanism;
s44: updating a business scene control table, and updating the three component names read by the analysis mechanism into the business scene control table;
s45: the platform executes a scheduling mechanism and executes the functional components of the current flow;
s46: updating the service scene control table, and writing the execution result of the functional component in the S45 into the service scene control table;
s47: querying a scene component library, judging whether the execution result of the component is successful, if so, jumping to S48, and if not, jumping to S49;
s48: judging whether the next process is finished, if so, finishing the service, otherwise, repeating the step S43 and executing the functional component of the next process;
s49: and executing an abnormal flow according to the definition of the scene component library record table, and ending the application service.
Further, in S47, the scene component library record table is queried by obtaining the output parameter and the functional component name of the functional component.
Furthermore, the service scene control table records the component information executed by the current logic flow of the scene.
The beneficial effect of this application:
(1) development cost is effectively reduced, and business requirements can be quickly realized through configuration management of functional components and customization, loading and operation of a series of components;
(2) the risk of production and operation accidents of new projects can be effectively reduced by multiplexing the functional components in use;
(3) all projects with common requirements can be upgraded iteratively through upgrading of a single functional component, and labor development cost is greatly reduced;
(4) through newly-increased functional component development standardization, unification, it is strong to realize platform subassembly source code readability, is convenient for upgrade, transformation, debugging processing, effectively reduces all customized project later stage operation and maintenance costs.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the structures of the drawings without creative efforts.
FIG. 1 is a general flow chart of the present invention;
FIG. 2 is a flow chart of preparation before access of a new application scenario of the present invention;
FIG. 3 is a flow chart of the logic processing of the present invention;
the implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that all the directional indicators (such as up, down, left, right, front, and rear … …) in the embodiment of the present invention are only used to explain the relative position relationship between the components, the movement situation, etc. in a specific posture (as shown in the drawing), and if the specific posture is changed, the directional indicator is changed accordingly.
In addition, the technical solutions in the embodiments may be combined with each other, but it must be based on the realization of those skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should be considered to be absent and not within the protection scope of the present invention.
The method aims at the condition that the customer requirements accepted by the banking industry are consistent in main body, but each customer additionally puts forward a distinctive requirement under the condition that the basic requirements are met, so that the demand development is carried out on each type of customer requirements in a bank, a large amount of repeated development is caused, and a large amount of human resources are consumed. For example: when a bank accepts a batch issuance commission initiated by each group client, a client A requires to issue an issuance completion short message notification, a client B requires to examine and verify before the bank accepts a task, a client C requires to provide issuance data statistics, and a client D requires to issue an approval and needs to double recheck and other various characteristic requirements.
In order to solve the technical problems, a method for automatically constructing a functional component based on multi-scenario application is particularly provided.
For ease of understanding, the following specific examples are set forth:
in this embodiment, as shown in fig. 1, the present invention provides a method for automatically building a functional component based on a multi-scenario application, which includes the following steps:
s1: functional module standardization and componentization: listing the services provided by the accessed application scenes;
s2: registering the newly added component: reusing the existing functional components in the scene component library, and newly adding missing functional components;
s3: configuration files: determining application requirements, and defining an exclusive configuration file of an accessed application scene according to the application requirements;
s4: the scheduling mechanism takes effect, and logic processing is carried out: after the configuration file is defined, the analysis of the exclusive configuration file of the application scene is completed through the cooperation of an analysis system and a scheduling mechanism, and the corresponding functional component is called to complete application processing.
In this embodiment, the configuration file is used to record a logic flow that the application scenario needs to be executed successively from the time of providing the service.
In this embodiment, the S1 includes the following steps before accessing the application scenario:
s00: accessing a new application scene, and determining functional components which need to be provided by the application scene;
s01: fuzzy search is carried out in the scene component library record list according to the names and the functions of the functional components, and whether the required functional components exist in the scene component library record list is judged;
s02: subscribing the required functional components existing in the scene component library record table, newly adding the required functional components not existing in the scene component library record table, and removing the dependency relationship among the components;
s03: and adding the newly added functional components in the S02 to the scene component library record table.
In this embodiment, the adding of the newly added functional component to the scene component library record table in S03 further includes: and sequentially recording the names of the newly added functional components, the function summaries, the input parameters and the output parameters, defining the output values and the abnormal output values of the newly added components after the successfully executed components, and defining the names of the subsequent flow components corresponding to the abnormal output values of each definition.
In this embodiment, the scene component library record table is used to record the developed functional component information, and define the input/output parameters and the exception handling procedures of the functional component.
In this embodiment, the S4 specifically includes the following sub-steps:
s41: initializing a business scene control table;
s42: starting an analysis mechanism and reading a flow configuration file;
s43: reading the name of the previous flow component, the name of the current flow component and the name of the next flow component by using an analysis mechanism;
s44: updating a business scene control table, and updating the three component names read by the analysis mechanism into the business scene control table;
s45: the platform executes a scheduling mechanism and executes the functional components of the current flow;
s46: updating the service scene control table, and writing the execution result of the functional component in the S45 into the service scene control table;
s47: querying a scene component library, judging whether the execution result of the component is successful, if so, jumping to S48, and if not, jumping to S49;
s48: judging whether the next process is finished, if so, finishing the service, otherwise, repeating the step S43 and executing the functional component of the next process;
s49: and executing an abnormal flow according to the definition of the scene component library record table, and ending the application service.
In this embodiment, in S47, the scene component library record table is queried by acquiring the output parameter and the functional component name of the functional component.
In this embodiment, the service scenario control table records component information executed by the current logic flow of the scenario.
Specifically, the method provides a strategy for rapidly realizing multiple application scenes with common requirements, avoids repeated development of common functional components, and improves universality and reusability of codes.
The method carries out listing on the service provided by the accessed application scene, reuses the existing functional components in the scene component library, and simultaneously adds the missing functional components; after the application requirement is determined, namely the externally provided service is definite, defining an exclusive configuration file for the accessed application scene, wherein the configuration file records a logic flow which needs to be executed successively from the service providing of the application scene, and which functional component is executed first and which component is executed subsequently; after the configuration file is defined, the analysis mechanism and the scheduling mechanism of the method cooperate to finish the explanation of the configuration file of the application scene and call the corresponding functional component to finish the whole application processing.
As shown in fig. 2, in the preparation stage of accessing a new application scenario, it is necessary to ensure that all functional components required by the application scenario are included in the scenario component library record table 1, and then customize the configuration file of the application scenario according to the actual application requirements.
Firstly, the application requirements are determined, and the function list required to be provided by the application scene is determined. Fuzzy search is carried out on the sorted functional components in a scene component library according to component names or functions, and matched functional components are subscribed; for the missing functional components, performing new addition processing, performing functional modularization and componentization of new addition following units, standardizing input and output, and removing the dependency relationship among the components; after the development and encapsulation of the newly added functional component are completed, the newly added functional component is added to the scene component library record table 1, the newly added component name, the function summary, the input parameters and the output parameters are sequentially recorded, the output value (default output 0) and the abnormal output value of the successfully executed newly added component are defined, and the name of the subsequent process component corresponding to each defined abnormal output value is defined. After determining that all functional components required by the application scene are in the scene component library record table 1, defining a configuration file of the application scene according to format requirements defined by the method, and recording a first functional component name, a second component name and a third component name in the configuration file according to the sequence of the logic processing flow.
After the preparation work of accessing a new application scene is finished, the device can provide services to the outside, and the configuration file for explaining the application scene and the corresponding functional components are called to finish the whole application processing by matching the analysis mechanism and the scheduling mechanism of the method.
As shown in fig. 3, when the present apparatus starts to provide service for a new application scenario, a service scenario control table 2 is initialized, a parsing mechanism is started to read the names of the first two functional components (the first component name and the second component name) and write the names into the current component column and the next component column in the service scenario control table 2, respectively; starting a scheduling mechanism to execute the functional components in the current component column in the service scene control table 2, obtaining an output parameter i of the component after the execution is finished, querying a scene component library record table 1 according to the output parameter i and the functional component names, and judging whether the execution result of the component is a result or an abnormal result: if the abnormal process is abnormal, executing the abnormal process according to the definition of the scene component library record table 1, and ending the application service; if the component is executed successfully, the scheduling mechanism of the device executes the component of the next component column in the business scenario control table 2. And after the first round of functional components is executed, reading a second round of functional component list of the configuration file of the application scene by an analysis mechanism of the device, updating the service scene control table 2, and calling the components of the second round.
The beneficial effect of this application:
(1) development cost is effectively reduced, and business requirements can be quickly realized through configuration management of functional components and customization, loading and operation of a series of components;
(2) the risk of production and operation accidents of new projects can be effectively reduced by multiplexing the functional components in use;
(3) all projects with common requirements can be upgraded iteratively through upgrading of a single functional component, and labor development cost is greatly reduced;
(4) through newly-increased functional component development standardization, unification, it is strong to realize platform subassembly source code readability, is convenient for upgrade, transformation, debugging processing, effectively reduces all customized project later stage operation and maintenance costs.
The foregoing is illustrative of the preferred embodiments of this invention, and it is to be understood that the invention is not limited to the precise form disclosed herein and that various other combinations, modifications, and environments may be resorted to, falling within the scope of the concept as disclosed herein, either as described above or as apparent to those skilled in the relevant art. And that modifications and variations may be effected by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (8)
1. A method for automatically constructing functional components based on multi-scenario application is characterized by comprising the following steps:
s1: functional module standardization and componentization: listing the services provided by the accessed application scenes;
s2: registering the newly added component: reusing the existing functional components in the scene component library, and newly adding missing functional components;
s3: configuration files: determining application requirements, and defining an exclusive configuration file of an accessed application scene according to the application requirements;
s4: the scheduling mechanism takes effect, and logic processing is carried out: after the configuration file is defined, the analysis of the exclusive configuration file of the application scene is completed through the cooperation of an analysis system and a scheduling mechanism, and the corresponding functional component is called to complete application processing.
2. The method for automatically building functional components based on multi-scenario application according to claim 1, wherein the configuration file is used to record the logic flow that the application scenario needs to be executed sequentially from the service provisioning.
3. The method for automatically building functional components based on multi-scenario application as claimed in claim 1, wherein said S1 comprises the following steps before accessing application scenario:
s00: accessing a new application scene, and determining functional components which need to be provided by the application scene;
s01: fuzzy search is carried out in the scene component library record list according to the names and the functions of the functional components, and whether the required functional components exist in the scene component library record list is judged;
s02: subscribing the required functional components existing in the scene component library record table, newly adding the required functional components not existing in the scene component library record table, and removing the dependency relationship among the components;
s03: and adding the newly added functional components in the S02 to the scene component library record table.
4. The method for automatically building functional components based on multi-scenario application as claimed in claim 3, wherein the adding of the newly added functional components to the scenario component library record table in S03 further comprises: and sequentially recording the names of the newly added functional components, the function summaries, the input parameters and the output parameters, defining the output values and the abnormal output values of the newly added components after the successfully executed components, and defining the names of the subsequent flow components corresponding to the abnormal output values of each definition.
5. The method according to claim 3, wherein the scene component library record table is used for recording the developed functional component information, defining the functional component input/output parameters and exception handling procedures.
6. The method for automatically building a functional component based on multi-scenario application as claimed in claim 1, wherein the S4 specifically comprises the following sub-steps:
s41: initializing a business scene control table;
s42: starting an analysis mechanism and reading a flow configuration file;
s43: reading the name of the previous flow component, the name of the current flow component and the name of the next flow component by using an analysis mechanism;
s44: updating a business scene control table, and updating the three component names read by the analysis mechanism into the business scene control table;
s45: the platform executes a scheduling mechanism and executes the functional components of the current flow;
s46: updating the service scene control table, and writing the execution result of the functional component in the S45 into the service scene control table;
s47: querying a scene component library, judging whether the execution result of the component is successful, if so, jumping to S48, and if not, jumping to S49;
s48: judging whether the next process is finished, if so, finishing the service, otherwise, repeating the step S43 and executing the functional component of the next process;
s49: and executing an abnormal flow according to the definition of the scene component library record table, and ending the application service.
7. The method as claimed in claim 6, wherein the S47 is configured to query the scene component library record table by obtaining the output parameter and the function component name of the function component.
8. The method for automatically building functional components based on multi-scenario application as claimed in claim 6, wherein the business scenario control table records component information executed by the current logic flow of the scenario.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111327979.XA CN114063982A (en) | 2021-11-10 | 2021-11-10 | Method for automatically constructing functional components based on multi-scenario application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111327979.XA CN114063982A (en) | 2021-11-10 | 2021-11-10 | Method for automatically constructing functional components based on multi-scenario application |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114063982A true CN114063982A (en) | 2022-02-18 |
Family
ID=80274805
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111327979.XA Pending CN114063982A (en) | 2021-11-10 | 2021-11-10 | Method for automatically constructing functional components based on multi-scenario application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114063982A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114625935A (en) * | 2022-02-28 | 2022-06-14 | 深圳市世强元件网络有限公司 | Scene search method and system |
| CN114926290A (en) * | 2022-03-21 | 2022-08-19 | 中国人寿保险股份有限公司 | Contract issuing flow configuration method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030004746A1 (en) * | 2001-04-24 | 2003-01-02 | Ali Kheirolomoom | Scenario based creation and device agnostic deployment of discrete and networked business services using process-centric assembly and visual configuration of web service components |
| CN1920779A (en) * | 2005-08-25 | 2007-02-28 | 中兴通讯股份有限公司 | Configuration document based program flow control method |
| CN110851114A (en) * | 2019-10-24 | 2020-02-28 | 山东中创软件工程股份有限公司 | Business system development method and device, electronic equipment and storage medium |
| CN111506359A (en) * | 2020-03-26 | 2020-08-07 | 平安普惠企业管理有限公司 | Visual service configuration method, device, equipment and storage medium |
| CN112540837A (en) * | 2020-12-18 | 2021-03-23 | 贝壳技术有限公司 | Service processing component calling method, system, electronic equipment and storage medium |
-
2021
- 2021-11-10 CN CN202111327979.XA patent/CN114063982A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030004746A1 (en) * | 2001-04-24 | 2003-01-02 | Ali Kheirolomoom | Scenario based creation and device agnostic deployment of discrete and networked business services using process-centric assembly and visual configuration of web service components |
| CN1920779A (en) * | 2005-08-25 | 2007-02-28 | 中兴通讯股份有限公司 | Configuration document based program flow control method |
| CN110851114A (en) * | 2019-10-24 | 2020-02-28 | 山东中创软件工程股份有限公司 | Business system development method and device, electronic equipment and storage medium |
| CN111506359A (en) * | 2020-03-26 | 2020-08-07 | 平安普惠企业管理有限公司 | Visual service configuration method, device, equipment and storage medium |
| CN112540837A (en) * | 2020-12-18 | 2021-03-23 | 贝壳技术有限公司 | Service processing component calling method, system, electronic equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114625935A (en) * | 2022-02-28 | 2022-06-14 | 深圳市世强元件网络有限公司 | Scene search method and system |
| CN114625935B (en) * | 2022-02-28 | 2024-10-01 | 深圳市世强元件网络有限公司 | Method and system for scene search |
| CN114926290A (en) * | 2022-03-21 | 2022-08-19 | 中国人寿保险股份有限公司 | Contract issuing flow configuration method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108958714B (en) | Business component type development method and device, computer equipment and storage medium | |
| US8010844B2 (en) | File mutation method and system using file section information and mutation rules | |
| US8589884B2 (en) | Method and system for identifying regression test cases for a software | |
| CA3131079A1 (en) | Test case generation method and device, computer equipment and storage medium | |
| US6243835B1 (en) | Test specification generation system and storage medium storing a test specification generation program | |
| US5594892A (en) | Method for automated software application testing | |
| CN112699055B (en) | Software automatic test method and system with lower maintenance cost | |
| CN114371762B (en) | Method, device and storage medium for printing custom labels | |
| CN114063982A (en) | Method for automatically constructing functional components based on multi-scenario application | |
| CN113296902B (en) | Task scheduling method, device, apparatus and system, and computer-readable storage medium | |
| CN116795378B (en) | Method and device for arranging and executing process based on code dynamic compiling | |
| CN111784108A (en) | Modeling method and device for main data management platform | |
| CN116755669A (en) | Low code development method and tool based on DSL language operation model | |
| CN116226078A (en) | Data migration method, device, equipment and storage medium | |
| CN114090521A (en) | Image uploading method and device | |
| CN115525534A (en) | Test case generation method and platform based on swagger interface test | |
| CN112766829A (en) | Service processing method, device and equipment | |
| CN112631763A (en) | Program changing method and device of host program | |
| CN109697216B (en) | Clearing transaction information processing method, device and system | |
| CN117234466B (en) | Enterprise management software development method, system, equipment and storage medium | |
| CN111679812A (en) | Business processing method, apparatus, device, and computer-readable storage medium | |
| CN116301758B (en) | Rule editing method, device, equipment and medium based on event time points | |
| CN119440615B (en) | Multi-level object version management method and system for service system | |
| CN116643751A (en) | Information processing method, apparatus, device and computer readable storage medium | |
| KR20250104304A (en) | Asset administration shell-based application software information management and distribution method |
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 |