CN115129304A - Zero-code-platform-based visual business service arrangement method and device - Google Patents
Zero-code-platform-based visual business service arrangement method and device Download PDFInfo
- Publication number
- CN115129304A CN115129304A CN202210556581.1A CN202210556581A CN115129304A CN 115129304 A CN115129304 A CN 115129304A CN 202210556581 A CN202210556581 A CN 202210556581A CN 115129304 A CN115129304 A CN 115129304A
- Authority
- CN
- China
- Prior art keywords
- service
- engine
- business
- component
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 78
- 230000000007 visual effect Effects 0.000 title claims abstract description 45
- 238000012360 testing method Methods 0.000 claims abstract description 26
- 238000004519 manufacturing process Methods 0.000 claims abstract description 17
- 230000002688 persistence Effects 0.000 claims abstract description 13
- 238000004088 simulation Methods 0.000 claims abstract description 7
- 238000009877 rendering Methods 0.000 claims description 31
- 230000007246 mechanism Effects 0.000 claims description 27
- 230000006870 function Effects 0.000 claims description 23
- 230000008569 process Effects 0.000 claims description 19
- 238000012545 processing Methods 0.000 claims description 18
- 238000012544 monitoring process Methods 0.000 claims description 17
- 238000004458 analytical method Methods 0.000 claims description 14
- 238000012800 visualization Methods 0.000 claims description 13
- 230000001360 synchronised effect Effects 0.000 claims description 8
- 230000002159 abnormal effect Effects 0.000 claims description 6
- 238000011144 upstream manufacturing Methods 0.000 claims description 4
- 230000005540 biological transmission Effects 0.000 claims description 3
- 230000008676 import Effects 0.000 claims description 3
- 238000011161 development Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 8
- 230000014509 gene expression Effects 0.000 description 8
- 241000208340 Araliaceae Species 0.000 description 5
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 description 5
- 235000003140 Panax quinquefolius Nutrition 0.000 description 5
- 230000008901 benefit Effects 0.000 description 5
- 235000008434 ginseng Nutrition 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 230000008520 organization Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 239000012634 fragment Substances 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 238000010521 absorption reaction Methods 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008571 general function Effects 0.000 description 1
- 230000008570 general process Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000013049 sediment Substances 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
- G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/151—Transformation
- G06F40/154—Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/38—Concurrent instruction execution, e.g. pipeline or look ahead
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a visual business service arranging method based on a zero code platform, which comprises the following steps: configuring a visual interface dragging engine, configuring a service arranging engine, configuring a parameter analyzing engine, configuring a test environment, performing service arranging, adding data for testing while arranging, configuring a production environment, configuring an execution engine, constructing a service control layer, constructing a modeling layer and constructing a persistence layer, wherein when a user performs visual service arranging, a platform API receives configuration data collected by a front end, the configuration data is converted into an xml model through the service arranging engine, acquiring xml model data from a cache during simulation execution, and the service arranging engine analyzes and executes the xml model data. The method is applied to a zero-code platform, and drag configuration is directly carried out in the platform to realize the visual business service arrangement.
Description
Technical Field
The invention relates to the technical field of development of informatization application software, in particular to a visual business service arrangement method and device based on a zero-code platform.
Background
With the process of enterprise digital transformation accelerating, the application of the zero-code platform is more and more extensive and is gradually accepted and accepted by enterprise-level clients. Zero code is just as the name implies that applications and functions can be built to meet the requirements of customers without writing codes, but the fact is harsh, real customer requirements are always more complicated than those imagined by us, and traditional informationized application software zero code products need to provide various expansion capabilities, such as allowing developers to write codes of complicated business logic and interface the codes into a platform. The specific development steps are as follows: the requirement analyst and the client confirm the requirements, form a requirement document and submit the requirement document to development; a development manager understands the requirements and splits a part which can be directly configured by a zero code platform and a part which needs to be written with code extension; a developer writes a Restful API interface for the extension; issuing and deploying a Restful API interface; registering an interface method in a test platform, and selecting the interface method and configuring the input and output parameters at a calling place; after the verification passes in the test environment, the test result is issued to the production environment; when the customer requirement is changed, the previous steps are repeated. This, while satisfactory, has two problems: 1. the requirements of customers can change at any time, and the codes need to be modified as soon as the requirements change; 2. front-line business personnel cannot directly adjust in the platform. At this time, business service arrangement is required, for example: warehouse logistics warehouse-out first-in first-out updates the inventory, in a warehouse logistics system, the warehousing of commodities has time sequence, and the warehouse-in first-in warehouse-out is required to be followed when the commodities are taken out of the warehouse, as shown in fig. 1, in an information application software zero-code product system without business service arrangement, after a function is built, an API interface method for processing warehouse-out logic needs to be compiled and a certain method in the system is butted, and the work can be completed only by developers. If the business server scheduling tool is used, the method can be easily realized through visual dragging, as shown in FIG. 2; for another example, as shown in fig. 3, after the staff leaves the job, a series of operations, including modifying the state of the corresponding user in the hr system, deleting the account in the enterprise WeChat, disabling the mailbox, and sending the notification, may be easily implemented by using business service arrangement, provided that there are abundant business components. The arrangement of service business is that a series of single business components are combined in a flow mode, and finally the purpose of business is achieved. Referring to the flow, various leave-asking approval flows and contract approval flows in the OA system, the CRM system and the like are generally thought. In fact, a workflow in a broad sense is an abstraction, generalization, or description of a workflow and its business rules between its various operational steps. It is simply understood that, in order to achieve a certain business goal, a workflow is a series of abstracted steps and a cooperative relationship among the steps. Namely the above-mentioned orchestration process of business services. The general architecture of the service orchestration engine is shown in fig. 4, and there are three common modes for the current service orchestration: specification, coordinating internal and external service interaction through an executable flow, and controlling the overall target, the related operation and the service calling sequence through the flow. This model must have a flow control service to receive requests, organize calls between services, and ultimately complete business logic. Although the execution condition of the service can be clearly known at a certain moment, when the service is complex and the services are many, a large amount of coupling exists in the control service, so that the maintenance is difficult; choreography, the interaction of individual partial resources is controlled by a sequence of interactions of messages, the resources involved in the interaction being peer-to-peer, without centralized control. The message-driven mode, or subscription-publish mode, can be considered, and different services are connected in series through a message mechanism, and this mode is mostly asynchronous. The benefit is low coupling, but also some problems, such as: the business process is embodied in a subscription mode, and the processing of each business is difficult to monitor directly, so that the debugging is difficult, the subscription is a common concept in message middleware, a producer and a consumer exist in the message middleware, the consumer subscribes a certain type of message channel, and when the producer sends a message to the message channel, the consumer receives the message and processes the message. The processing in the service flow by using the subscription mode refers to: the process comprises two nodes, namely a node A and a node B, wherein the node A sends a message (equivalent to a producer) after being finished, and the message processing logic receives the message, processes the message and then transfers the message to the node B (equivalent to a consumer); because there is no predefined flow, it is difficult to ensure the correctness of the flow in advance, and basically depends on analyzing data afterwards to judge, etc.; API gateway, which is a simple interface aggregation/splitting way: the request of the service component firstly reaches the gateway, and the gateway calls each micro service and finally aggregates/splits the result to be fed back; the API gateway is actually an adaptation gateway, for example, for a Web end, several tens of requests can be initiated simultaneously by one page, and for a mobile end, preferably several requests can be initiated by one page; with an API gateway, the following microservices may be identical. But only for a few logically simple scenarios. Referring to the most relevant patent 201811084640.X, an atomic service is designed to call an API, parameters required by the API are solved, in order to meet business service requirements, a plurality of atomic services are organized into a flow, and the atomic service arrangement and API automated execution are realized with the help of the support of the existing workflow engine, so that the purpose of rapidly arranging business and rapidly executing business is achieved.
The invention patent 201811084640.X 'A parameter-driven-based automatic business arrangement method and device' discloses calling an API by designing an atomic service, solving parameters required by the API, organizing a plurality of atomic services into a flow in order to meet business service requirements, and realizing arrangement and API automatic execution of the atomic service by means of the support of the existing workflow engine (namely an executable flow), namely combining the organization (arrangement) and an API gateway, thereby achieving the purpose of quickly arranging business and quickly executing business. However, the defects and problems of the organization mode are not solved, and business service organization by using a visual dragging mode is not involved.
Disclosure of Invention
Aiming at the defects and the improvement requirements of the prior art, the invention provides a business service arrangement tool based on visualization, which comprises a visualization interface dragging engine, a service arrangement engine and a parameter analysis engine,
the specific technical scheme of the invention is as follows:
a visual business service arrangement method based on a zero code platform is applied to the zero code platform, drag configuration is directly carried out in the platform, and visual business service arrangement is realized, and the method comprises the following steps:
configuring a visual interface dragging engine, wherein the visual interface dragging engine is used for meeting the business combination and arrangement operation of an interface layer;
configuring a service arranging engine, wherein the service arranging engine is used for logically recombining and storing business services arranged by a user;
configuring a parameter analysis engine, wherein the parameter analysis engine is used for analyzing parameters and linking up upstream and downstream services;
configuring a test environment, wherein the test environment is used for performing service arrangement by a user directly in the test environment according to the understanding of business requirements, and adding data for testing while arranging;
configuring a production environment, wherein the production environment is used for releasing the business service which is tested normally to the production environment by a user;
configuring an execution engine, wherein the execution engine is used for carrying out various scheduling when a user triggers a certain scheduled service and finally returning a result to the user;
constructing a service control layer, wherein the arrangement of one service is composed of one or more business service components;
a model-type layer is constructed,
a business service component is disassembled into 1 or more atomic services;
each atomic service can be abstracted into a common model;
each atomic service provides a REST API interface or an event monitoring mechanism;
building a persistence layer, wherein each atomic service updates data to a subscribed persistence component according to a persistence adapter;
when a user carries out visual business service arrangement, the platform API receives configuration data collected by the front end, the configuration data are converted into an xml model through the service arrangement engine, xml model data are obtained from a cache during simulation execution, and the service arrangement engine analyzes and executes the xml model data.
Further, the visualization drag engine comprises a page renderer, the page renderer is used for asynchronous loading when the business service component is rendered, and the steps when the page is rendered are as follows:
the front end calculates the size of a display screen and transmits the size as a parameter to the rear end;
searching all components of the current page at the back end, and counting the rendering sequence and size of the components;
comparing the screen size with the component size to determine whether the component is split or not;
and if the data is split, returning the split data to the front end, and carrying out asynchronous loading on the front end according to the split data.
Further, the specific method for determining whether the component is split is as follows:
comparing the screen width height pixel value with the component set width height pixel value,
and if the screen width and height pixel values are N times of the width and height pixel values set by the components, loading N components on the screen according to the statistical rendering sequence of the components, wherein N is a natural number.
Furthermore, each service component defines its own entry and exit, and dynamically organizes parameters according to different execution stages in the request context of a service arrangement, and the parameter adapter automatically adapts according to name, type, and the like, or adapts according to manual binding in a setting interface.
Furthermore, the atomic service can assemble various service components with different functions through one atomic service or a plurality of atomic services, and service and component decoupling can be realized through an event monitoring mechanism, so that flexible assembly can be realized.
Further, the specific method for completely decoupling the services and the components by the event monitoring mechanism is as follows: and by utilizing the message middleware, each component has a producer and a consumer, and the consumer receives and processes the message and determines whether to send the message out according to the configuration after the message is processed. If a message is sent, other components that have a snoop for the message type will receive the message for processing.
Further, the air conditioner is provided with a fan,
the calling of the business service component is synchronous or asynchronous, is determined by a user in a mode set by the user, and provides a retry mechanism to ensure the final consistency of data; when the complete service call is started, a unique ID is generated and is always stored in a call context;
the atomic service can be executed in two modes, namely a REST API mode or an event monitoring mode, wherein the REST API mode or the event monitoring mode selects one mode, if the REST API mode or the event monitoring mode is adopted, the ID can be placed in a request head and transmitted to the next layer, and if the REST API mode or the event monitoring mode is adopted, the ID can be transmitted as a part of a message body;
the final calling results (input and output, atomic service time consumption, service component time consumption, abnormal logs and the like in the process) are displayed in the interface, and all calling information related to the ID can be inquired according to the ID.
Further, the specific method that the ID will always be stored in the calling context is: the global unique ID can be designed as an attribute field in a message transmission entity, the value is assigned after the ID is generated at the most source head, then the message is circulated all the time, the information is stored in the memory in the circulating process, and if the message middleware has an abnormal condition, the data can be persisted, which is the data stored in the hard disk.
Further, a compensation mechanism is also included: assuming that the user has already programmed a complex service, for each calling component operation, a corresponding compensation (i.e. undo) operation is registered, and the operation itself and its compensation operation are completed in one transaction, and when the subsequent operation fails, all the undo operations registered previously need to be completed in reverse order.
Further, the compensation mechanism is divided into two types:
independent settings on specific service components;
the global control calls compensation, all called services are recorded in a list, and if the operation needing retrying or rollback occurs, the operation is obtained from the list to carry out corresponding operation; in the compensation mode, the operation requiring a service capable of providing compensation must support idempotent (otherwise, data errors occur when performed multiple times)
Compared with the prior art, the method of the invention has the following advantages:
the invention provides a visual business service arrangement tool, which comprises a visual interface dragging engine, a service arrangement engine and a parameter analysis engine, wherein the method is characterized in that the method is used for converting the original logic compiling of developers to meet the business service requirements into a mode of directly dragging and configuring in a platform, so that business operators of enterprises which are skilled in mastering the business but do not understand the programming technology can realize business functions easily, the original business service requirements which can be realized through a long period of requirement submission, requirement investigation, development, testing and online are converted into a mode of simply dragging and configuring in an interface, the development efficiency is greatly improved, and the continuously changed business requirements of enterprise users are quickly responded;
furthermore, in the process of carrying out dragging configuration in an interface, if a plurality of elements in a page affect the loading speed of the whole page, because a browser needs to consume a CPU/GPU (central processing unit/graphic processing unit) for rendering the page, each visual component needs to render a large number of information elements which can be understood as countless html elements, which can cause no small influence on the page performance, the invention loads the components on a canvas asynchronously instead of loading dozens of hundreds of components at one time, so as to solve the problems of reducing the page volume and enabling a user to see page elements earlier, specifically, the web development of a software system compiled by the method is a front-end and back-end separation framework, the problem of jitter does not exist in the frame of a new front end, namely a browser is used at the front end of the invention, the user sees the interface, the back end, i.e. the back end program, handles the business logic. The rendering of the asynchronous components mainly solves the problem of page rendering performance, and particularly can calculate which components need to be rendered according to the size of a screen so as to improve the page rendering performance;
meanwhile, the advantages of organization and chord are combined, a business service arrangement engine is developed, when the atomic service is used for calling the API in a synchronous or asynchronous mode, the decision is made according to the requirements of users, the high coupling degree in the control service is avoided, and the flow correctness is ensured in advance.
Drawings
FIG. 1 is a schematic diagram of warehouse logistics warehouse-out FIFO update stock quantity in a conventional method;
FIG. 2 is a schematic diagram of the method of the present invention for visually dragging the warehouse to exit the warehouse with FIFO update of the inventory.
FIG. 3 is a schematic diagram of operations of the method of the present invention for visualizing a number of columns to be processed after a dragger leaves an office;
FIG. 4 is a schematic diagram of the general architecture of the service orchestration engine according to the method of the present invention;
FIG. 5 is a schematic diagram of a visual drag engine of the method of the present invention;
FIG. 6 is a schematic view of a specific flowchart during page rendering according to the method of the present invention;
FIG. 7 is a schematic view of the overall service orchestration process according to the method of the present invention;
FIG. 8 is a schematic diagram of the independent setup compensation mechanism on a particular service component of the method of the present invention;
FIG. 9 is a schematic diagram of a mechanism for managing and performing manual retry compensation in a log list of failed calls according to the method of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In addition, the technical features mentioned in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
A visual business service arrangement method based on a zero code platform is applied to the zero code platform, drag configuration is directly carried out in the platform, and visual business service arrangement is realized, and the method comprises the following steps:
configuring a visual interface dragging engine, wherein the visual interface dragging engine is used for meeting the service combination and arrangement operation of an interface layer;
the user can directly add, delete and modify the nodes and configure the attribute setting and parameters of each service node in a Web interface by using a dragging mode. The information is obtained, and the effect can be immediately checked through on-line simulation operation after configuration is finished;
the architecture diagram of the visual dragging engine is shown in fig. 5, wherein a dragger is a core module of the visual dragging engine, and can be realized by using native js, which is developed by using the grammar of the most basic js language, and a third-party library is also used, so that the method is flexible, but the development cost is high; the third-party library is a frame for accumulating sediments for many years in an open source community, is convenient to use, but may be limited in function;
draggable is used in this embodiment. The following are code fragments of the core implementation:
the step of generating corresponding control attributes and dynamically rendering the control attributes to an interface when the selected form control changes in the code label means that model data stored in a database is displayed on a page in a code logic mode.
In general, the loading speed of the whole page is affected when the number of elements in one page is large, because the browser needs to consume the CPU/GPU for rendering the page. For a visualization page, each visualization component needs to render a large number of information elements, which can be understood as numerous html elements. This has little effect on page performance, so in the present invention, rather than loading tens of hundreds of components at once, components are loaded onto the canvas asynchronously.
The page renderer provides a mechanism for ensuring that the components are loaded asynchronously, which can reduce the page size on one hand and allow the user to see page elements earlier on the other hand.
The principle of asynchronous loading is as follows: when 100 components exist in the platform and 10 components are dragged on a page, the page rendering only requests js files of the 10 components, and then the rendering is performed, so that the performance is greatly improved. In addition, according to the judgment of the first screen loading, only 2 to 3 js may be requested when the page is opened, and the page rendering speed is further increased.
Specifically, the visual interface drag engine in this embodiment is divided into two large parts: the connection and control between nodes between drag and service,
dragging:
1. dragable component of open source is used in the drag part of the invention;
2. dragable is an vue dragging plug-in realized based on sortable.js, can support a PC end and a mobile end, and can drag and select text and drag among different lists of other elements;
3. by import drawable from 'vuedragable'; can refer to the drag-change component
4. Placing a dragable code block at the place of use
<draggable class＝"widget-form-list widget-form-list-drag"
v-model＝"data.layoutDetail"style＝"min-height:600px；"
v-bind＝"{group:'people',ghostClass:'ghost',swapThreshold: 0.5}"@add＝"handleWidgetAdd"
5. Adding handleWidgetAdd (evt) of elements in a panel in a handleWidgetAdd function (evt) { const newIndex ═ evt.newindex;
this.selectWidget＝this.data.layoutDetail[newIndex]；
this.addServiceNode()；}；
connection and control between nodes between services:
1. the connection of the nodes between services uses an open source component antv/g 6;
2. g6 is a graph visualization engine that provides the basic capability for graph visualization for drawing, layout, analysis, interaction, animation, etc. of graphs;
3. as mentioned above, g6 provides a basic capability, and the visualization of the service orchestration of the present invention needs to be expanded on this basis, with three key points:
the service node performs the branch processing of the connecting line under the condition judgment,
providing a drag block of the group, into which a plurality of service nodes may be added to implement the loop logic,
the auxiliary lines of the service nodes are aligned when the service nodes are connected;
and (3) branch processing of the connecting wire:
1. the anchor point of the node in the mouse point, remembering the starting point of the line,
2. when the mouse is dragged by the canvas, the position of the mouse on the canvas is obtained, a connecting line is rendered,
3. judging the distance between the mouse and the target node, if the distance is very close, directly adsorbing the connecting line to the node,
4. in the release point of the mouse, whether the connecting line is absorbed to the node or not is judged, the connecting line is removed without absorption,
5. connecting points in the points, displaying the set nodes, setting conditions, and changing the rendering attribute of the connecting lines if the conditions are set so as to render the connecting lines into dotted lines;
and (3) circulating logic:
1. the group of nodes in the mouse point, remembering the node data,
2. when a node group in a mouse point is dragged by the canvas, the position of the mouse on the canvas is obtained, a virtual wire frame is rendered on the canvas,
3. in the mouse release point, the position of the mouse on the canvas is obtained, the node group is rendered,
4. repeating the above steps to drag the service node into the node group;
alignment of auxiliary lines:
1. when a node group in a mouse point is dragged by canvas, the position of the mouse on the canvas is obtained, a virtual wire frame is rendered on the canvas,
2. finding out the nearest node of the top line, the bottom line, the middle line, the left side line, the middle vertical line and the right side line of all the nodes on the canvas and the dragging node,
3. and rendering auxiliary lines between the found nodes and the dragged nodes and between wire frames of the canvas, and 4, obtaining the position of the mouse on the canvas from the mouse release points, rendering the nodes and removing the auxiliary lines displayed on the canvas.
Specifically, the visualization drag engine comprises a page renderer, the page renderer is used for asynchronous loading when a business service assembly page is rendered, and the page rendering steps are as follows:
the front end calculates the size of a display screen and transmits the size as a parameter to the rear end; the front end in this embodiment may be understood as a browser;
searching all components of the current page at the back end, and counting the rendering sequence and size of the components;
comparing the screen size with the component size to determine whether the component is split or not;
and if the data is split, returning the split data to the front end, and carrying out asynchronous loading on the front end according to the split data. The split data specifically includes: if the number of all components of the current page is 100, the number of the components which can be displayed on the head screen and are split according to the comparison of the pixel sizes may be 2, or may be 4 or other numbers; the continuous loading scrolls all pages down to load all 100 components.
The program of the invention is a framework with separated front and back ends, the front end is rendered by a browser, a user sees an interface, the back end processes business logic, and the back end is the back end program.
The specific method for determining whether the component is split is as follows:
comparing the screen width height pixel value with the component set width height pixel value,
and if the screen width and height pixel values are N times of the width and height pixel values set by the components, loading N components on the screen according to the statistical rendering sequence of the components, wherein N is a natural number. For example, the screen has a width of 1000px (pixels) and a height of 800px, the first component has a width of 1000px and a height of 400px, the second component has a width of 1000px and a height of 400px, and the screen can load the two components at the same time; if the first component is 1000px wide and 800px high, the screen loads only this one component; if all the components of the current page have 100 components, the rendering sequence and the size of the components are counted by the back end, the configuration information of the 100 components is returned to the front end at one time, and asynchronous loading is carried out according to the split data as required, so that the asynchronous loading is one of the advantages of the invention, and if synchronous loading is carried out, the user experience is poor, and the performance is poor.
The specific flow chart is shown in fig. 6. Two cases are distinguished:
1. when the pixels of all the components are smaller than the pixels of the screen, all the components can be displayed on the first screen, so that the configuration information of all the components is directly returned to the front end, and all the components are traversed to perform asynchronous rendering;
2. when all the components are added to be larger than the screen, judging how many components can be loaded on the first screen according to calculation, grouping and returning the configuration information of each group of components which can be loaded on the screen to the front end, and performing asynchronous rendering on each group of components; for example, a total of 100 components, the first screen can display 10, and then the return is divided into multiple groups.
The following code fragments are core code of the asynchronous dynamic rendering part:
configuring a service arranging engine, wherein the service arranging engine is used for logically recombining and storing business services arranged by a user;
the arrangement of business services is that a series of single business components are combined in a flow manner, and finally the purpose of business is achieved.
The general processes include various leave-asking approval flows and contract approval flows in OA systems, CRM systems and the like, and in fact, the workflow in a broad sense is abstract, summary and description of business rules among the workflow and various operation steps of the workflow. It is simply understood that, in order to achieve a certain business goal, a series of steps abstracted and disassembled and the cooperative relationship among the steps are workflows. Namely the above-mentioned arrangement flow of business services.
The service arranging engine is similar to a grammar parser of a programming language, and judgment rules, circulation rules and the like set in the interface are analyzed through configuration by the service arranging engine and converted into instructions which can be executed by a machine.
The general architecture of the service orchestration engine is shown in FIG. 4:
the steps of service orchestration in this embodiment are as follows:
constructing a service control layer, wherein the arrangement of one service is composed of one or more business service components;
a model-type layer is constructed,
a business service component is disassembled into 1 or more atomic services;
each atomic service can be abstracted into a common model; for example, deduction is an atomic service, transfer requires a service component for transfer, but the transfer process includes two atomic services, one is that a target account needs to increase the amount of money, and the other is that a source account needs to subtract the amount of money, so that the atomic service of deduction is completed;
each atomic service provides a REST API interface or an event monitoring mechanism;
building a persistence layer, wherein each atomic service updates data to a subscribed persistence component according to a persistence adapter;
when a user carries out visual business service arrangement, a platform API receives configuration data collected by a front end, the configuration data is converted into an xml model through a service arrangement engine, when simulation execution is carried out, namely in a configuration stage (namely, a stage of not formally releasing an online state), the model operation can be carried out by using test data to judge the correctness of a program, xml model data is obtained from a cache, and the service arrangement engine analyzes and executes the xml model data. Parsing is to obtain the xml configuration stored in the database, convert it into logic that the program can recognize, and then the program can execute the logic of the layout.
The overall process of service orchestration is shown in fig. 7:
after setting and storing dragging nodes and attributes in a visual arrangement interface, the configuration data of the whole business arrangement model can form an xml model to be stored in a database, and the following model segments are shown as follows:
after the user performs visual service arrangement, the platform API receives configuration data collected by the front end and converts the configuration data into an xml model through the service arrangement engine. During simulation execution, obtaining xml model data from the cache, analyzing and executing the xml model data by a service arranging engine, for example, setting of UEls attribute is used for controlling condition judgment of service, and branching; the UFor attribute is used to control the processing of the looping content.
The calling of the service component is divided into synchronous and asynchronous, and the decision is handed over to the user to be a better implementation mode, can be carried out in a setting mode, and provides a retry mechanism to ensure the final consistency of data. The retry mechanism refers to a mechanism for re-executing to guarantee the correctness of a service when the execution of a service fails for some reason (network, database problem, etc.). There are many ways to implement the retry mechanism, and the message queue is used in this embodiment. For example, when a deduction is initiated, a deduction initiator sends the task of deduction to a message queue, a receipt represents that normal processing is completed after the message queue is processed, and if no receipt exists, the identification processing fails, and the receipt is continuously arranged in the queue to wait for processing. This ensures final consistency. As shown in fig. 8.
The asynchronous loading of the business service component during page rendering and whether the calling of the business service component is synchronous or asynchronous are consistent in logic, and only different scenes are used. In the rendering of the page: the synchronous means that rendering operation is started after all contents on the page are acquired, and the asynchronous means that rendering can be performed on a part of the contents, for example, the first screen of a pan-bao first page comes out quickly, and the next dish starts to be loaded when the page is scrolled downwards and also belongs to an asynchronous range; synchronization in the retry mechanism refers to: if the retry of the two service calls is sequential, the first call is first, and the second call is then performed after the first call is finished, and the asynchronous calls are two calls which can be performed simultaneously.
Each service component does not exist independently, and has own access and exit, for example, a service logic is that four digits in the middle of a telephone number are represented by an asterisk, two service components are used, one component is used for inquiring the telephone number, and the other component is used for processing the asterisk:
component to obtain phone number:
ginseng introduction: name of user
Ginseng production: inquiring user's telephone number return according to user's name
Asterisk processing component:
ginseng introduction: telephone number retrieved from last component
Ginseng production: processed telephone number with star
Each service component defines its own import and export parameters, and dynamically organizes parameters according to different execution stages in a service orchestration request context, and parameter adapters automatically adapt according to names, types, and the like, or adapt according to manual binding in a setting interface. Specifically, the parameter value is obtained by being specified at runtime, but not a fixed value assigned in advance, for example, deduction is an atomic service, one service component is used for transferring money, the transfer service component comprises two atomic services, one is that a target account needs to be subjected to money increment, the other is that a source account needs to be subjected to money decrement, it is known which account should be transferred to when the account is run, how much money is transferred, and the account and the transferred money are parameters and are dynamically taken out at the time of the run.
The atomic service only does one thing, various service components with different functions can be assembled through one atomic service or a plurality of atomic services, and service components and components can be completely decoupled through an event monitoring mechanism, so that flexible assembly can be realized. For example, a service component is used for transferring money, but the service component comprises two atomic services, namely, the target account is subjected to amount increase, and the source account is subjected to amount deduction.
Another service component is now used for deduction, which may contain a atomic service, i.e. the second service in the above example, to deduct the amount of money in an account. Thus, the atomic service can be reused, and the role of the atomic service is to deduct the money of a certain account by a designated amount, so long as the business needs to deduct the account amount.
The specific method for completely decoupling services and components by using the event monitoring mechanism is as follows: and by utilizing the message middleware, each component has a producer and a consumer, and the consumer receives and processes the message and determines whether to send the message out according to the configuration after the message is processed. If a message is sent, other components that have snooped the message type will receive the message for processing.
With the increase of services and components, the call chain becomes more and more complex, and when the whole process of arranging one service is finished, the call chain forms a complex network, which causes great trouble to the problem of troubleshooting. We use full link tracing to solve this problem, and at the beginning of a complete service call, a unique ID is generated and stored in the call context. The global unique ID can be designed as an attribute field in a message transmission entity, the ID is generated at the most source and then assigned, and then the message is circulated all the time, the information is stored in a memory in the process of circulation, and if the message middleware has an abnormal condition, the data can be persisted, which means that the data is stored in a hard disk.
In the above, atomic service may be executed in two ways, namely, a REST API and an event monitoring way, where the two ways are performed by selecting one of them according to a situation, where the REST API is that a caller directly accesses a callee, and is usually a targeted function interface, for example, when the function of the callee is only used by the caller. Event snooping is commonly used in general function modules. If it is REST API, ID will be put in the request header and passed to the next layer, if it is event monitoring, ID will be passed as part of the message body, for example: since many different atomic services, which may also be deployed in a distributed manner, may be involved in a complete call of a service orchestration, in order to be able to track all call cases, a globally unique ID is generated at the beginning of the call, and this globally unique ID is stored as an attribute of the message body and is therefore taken along during the call.
The REST API is an active calling mode, in essence, a caller and a callee are in a coupled relationship, but can also be decoupled, for example, by using a proxy mode. How does the proxy mode decouple? The proxy mode is that a middle layer is added between a caller and a callee. The caller interacts with the middle layer, and the callee also interacts with the middle layer. Therefore, the caller and the callee do not need to interact directly, and decoupling is realized. Specifically, the customer borrows money, the person who pays money is borrowed from the flower of the person who pays money, the person who pays money may also be called money from a bank to the customer, the customer is the caller, the bank is the callee, and the flower of the person who pays money is the intermediate layer.
The final calling results (in-process participation, out-participation, atomic service time consumption, service component time consumption, abnormal logs and the like) are displayed in the interface in a tree form, and all calling information related to the ID can be inquired according to the ID. This is the final presentation of a log, since in multi-service calls, a complete log is needed for debugging or troubleshooting errors.
Assuming that a user has already arranged a complex service, the calling between service components is synchronous and asynchronous, and when a problem occurs in a certain link, the final consistency of data needs to be ensured. One way that is commonly used is a compensation mechanism:
the core idea of the compensation mode is as follows: for each operation, a compensation (undo) operation corresponding to the operation is registered, and generally, the operation itself and the compensation operation are completed in one transaction, and when the subsequent operation fails, all the undo operations registered before are required to be completed in reverse order. A transaction is a strict series of logical operations in a program, and all operations must be completed successfully, otherwise all changes made in each operation are undone. Can be understood in popular terms as: it is how many things are handled as one thing, either all successful or all failed. Such as: buying goods by the e-commerce involves placing an order and then deducting inventory, which is two operations, order generation and stock deduction, and if the order generation is successful and the stock deduction is lost, the order is rolled back.
The compensation mechanism of the present invention is divided into two types:
1. independent settings on a particular service component, as shown in FIG. 8;
2. and (4) global control call compensation, recording all called services into a list, and if an operation needing to be retried or rolled back occurs, acquiring the operation from the list to perform corresponding operation.
In the compensation mode, the operation requiring a service capable of providing compensation must support idempotent, otherwise data errors occur when performed multiple times. Idempotent, is a mathematical and computer concept, which is commonly found in abstract algebra. An idempotent operation in programming is characterized by the same effect of any number of executions as one. An idempotent function, or idempotent method, refers to a function that can be repeatedly performed using the same parameters and achieve the same result. For example, an interface is used for deducting credit cards, the interface needs to be called to deduct a certain amount of money under a certain service scene, and then the interface is called for many times and only deducts a certain amount of money, which is in line with idempotent.
Normally, all compensation is triggered automatically, but some special scenarios still require manual intervention, and manual retry is performed in the log list of call failure, as shown in fig. 8:
configuring a parameter analysis engine, wherein the parameter analysis engine is used for analyzing parameters and linking up upstream and downstream services;
parameter analysis is an important environment in service arrangement, and plays a role in connecting each service node in series, the output of one node is the input of another node, and data combination of a plurality of service nodes and the like all need to depend on a parameter analysis engine.
Specifically, in the business service orchestration, there are two types of parameters, ingress and egress ingress: setting using dynamic expressions
Ginseng production: mostly fixed json format
Therefore, the parameter analysis engine mainly analyzes the input parameters. The participating resolution is divided into two large parts
Parameter expression parsing
Custom function parsing
Analyzing the parameter expression:
1. the parsing function in the parametric parsing engine receives a parametric expression, such as the expression: { f _745b066857} + { f _ e2b90aea19} represents the addition of two fields;
2. code identifying two fields according to braces in expression
3. Identifying the operation symbol in the expression +
4. Obtaining field values from data sources based on identified fields
5. Operating on two values according to an operator
6. Returning the result after operation;
analyzing the custom function:
1. an abstract base class Function is arranged in a parameter analysis engine, and an abstract method Parse is arranged in the abstract base class Function
2. All Function classes inherit from the Function abstract base class and realize the abstract method Parse
3. For example, a function for calculating the length of a string is defined as follows:
4. for example, the parameter expression LENGTH ({ f _745b066857}) is used to obtain the LENGTH of a field, identify the previous LENGTH function by a small bracket, then identify the field in a large bracket, and obtain a value from the data source according to the field, and take the value as the reference of the LENGTH function, and finally the code is executed to the Parse method of the third step above.
Configuring a test environment, wherein the test environment is used for performing service arrangement by a user directly in the test environment according to the understanding of business requirements, and adding data for testing while arranging;
configuring a production environment, wherein the production environment is used for releasing the business service which is tested normally to the production environment by a user;
and configuring an execution engine, wherein the execution engine is used for carrying out various scheduling when a user triggers a certain scheduled service and finally returning the result to the user.
According to the visual business service arranging method based on the zero code platform, if the business requirement of a client is changed, the flow steps required to be realized are as follows:
the personnel of the customer service department or the configuration personnel of the platform directly carry out service arrangement in the test environment according to the self understanding of the service requirement;
data can be added for testing while arranging;
and releasing the test result to a production environment after the test is normal.
According to the same inventive concept, the embodiment of the application provides a visual business service arranging device based on a zero code platform, which comprises:
the visual interface dragging engine is used for meeting the business combination and arrangement operation of an interface layer;
the service arranging engine is used for logically recombining and storing the service arranged by the user;
the parameter analysis engine is used for analyzing parameters and linking up upstream and downstream services;
the testing environment module is used for performing service arrangement directly in a testing environment according to the understanding of business requirements by a user, and adding data for testing while arranging;
the production environment module is used for releasing the business service which is tested normally to a production environment by a user;
the execution engine is used for carrying out various scheduling and finally returning a result to the user when the user triggers a certain scheduled service;
the service control layer is used for arranging one service and consists of one or more business service components;
a layer of a model of the device,
a business service component is disassembled into 1 or more atomic services;
each atomic service can be abstracted into a common model;
each atomic service provides a REST API interface or an event monitoring mechanism;
building a persistence layer, wherein each atomic service updates data to a subscribed persistence component according to a persistence adapter;
when a user carries out visual business service arrangement, the platform API receives configuration data collected by the front end, the configuration data are converted into an xml model through the service arrangement engine, xml model data are obtained from a cache during simulation execution, and the service arrangement engine analyzes and executes the xml model data.
In one embodiment, the visualization drag engine comprises a page renderer, the page renderer is used for asynchronous loading when the business service component page is rendered, and the steps when the page is rendered are as follows:
the front end calculates the size of a display screen and transmits the size as a parameter to the rear end;
searching all components of the current page at the back end, and counting the rendering sequence and size of the components;
comparing the screen size with the component size to determine whether the component is split or not;
and if the data is split, returning the split data to the front end, and carrying out asynchronous loading on the front end according to the split data.
According to the visual business service arrangement method and device based on the zero code platform, the following two business services are arranged:
1. warehouse logistics warehouse-out first-in first-out updating inventory
In the warehouse logistics system, the warehousing of the commodities has a time sequence, and the commodities need to be exported after being warehoused first when being exported, as shown in fig. 1;
in a system without business service arrangement, after the function is built, an API interface method for processing warehouse-out logic needs to be written and connected with a certain method in the system. This work can only be done by the developer.
The business server orchestration tool of the present invention can be used to easily visualize the drag, as shown in FIG. 2.
2. After the staff leave, some series of operations need to be processed, such as:
modifying the status of the corresponding user in the hr system
Deleting account number in enterprise WeChat
Disabled mailboxes
Sending notifications
The orchestration of business services using the present invention can be easily accomplished if there are rich business components, as shown in FIG. 3.
Claims (10)
1. A visual business service arrangement method based on a zero code platform is characterized in that the method is applied to the zero code platform, drag configuration is directly carried out in the platform, and visual business service arrangement is realized, and the method comprises the following steps:
configuring a visual interface dragging engine, wherein the visual interface dragging engine is used for meeting the business combination and arrangement operation of an interface layer;
configuring a service arranging engine, wherein the service arranging engine is used for logically recombining and storing business services arranged by a user;
configuring a parameter analysis engine, wherein the parameter analysis engine is used for analyzing parameters and linking up upstream and downstream services;
configuring a test environment, wherein the test environment is used for performing service arrangement by a user directly in the test environment according to the understanding of business requirements, and adding data for testing while arranging;
configuring a production environment, wherein the production environment is used for releasing the business service which is tested normally to the production environment by a user;
configuring an execution engine, wherein the execution engine is used for carrying out various scheduling when a user triggers a certain scheduled business service and finally returning a result to the user;
constructing a service control layer, wherein the arrangement of one service is composed of one or more business service components;
a model-type layer is constructed,
a business service component is disassembled into 1 or more atomic services;
each atomic service can be abstracted into a common model;
each atomic service provides a REST API interface or an event monitoring mechanism;
building a persistence layer, wherein each atomic service updates data to a subscribed persistence component according to a persistence adapter;
when a user carries out visual business service arrangement, the platform API receives configuration data collected by the front end, the configuration data are converted into an xml model through the service arrangement engine, xml model data are obtained from a cache during simulation execution, and the service arrangement engine analyzes and executes the xml model data.
2. The zero-code platform based visualization business service orchestration method according to claim 1, wherein the visualization drag engine comprises a page renderer, the page renderer is used for asynchronous loading of business service components during page rendering, and the steps during page rendering are as follows:
the front end calculates the size of a display screen and transmits the size as a parameter to the rear end;
searching all components of the current page at the back end, and counting the rendering sequence and size of the components;
comparing the screen size with the component size to determine whether the component is split or not;
and if the data is split, returning the split data to the front end, and carrying out asynchronous loading on the front end according to the split data.
3. The visual business service orchestration method based on zero-code platform according to claim 2, wherein the specific method for deciding whether the component is split is as follows:
comparing the screen width height pixel value with the component set width height pixel value,
and if the screen width and height pixel value is N times of the width and height pixel value set by the component, loading N components on the screen according to the statistical rendering sequence of the components, wherein N is a natural number.
4. The zero-code platform based visualization business service orchestration method according to claim 1, wherein each service component defines its own import and export parameters, and dynamically organizes parameters according to different execution stages in a request context of a service orchestration, and the parameter adapters automatically adapt according to name, type, etc., or manually adapt according to manual binding in a setting interface.
5. The visual business service orchestration method based on zero-code platform according to claim 1, wherein the atomic service only does one thing, and business components with different functions can be assembled through one atomic service or multiple atomic services, and service and component can be completely decoupled through an event monitoring mechanism, so that flexible assembly is possible.
6. The visual business service orchestration method based on zero-code platform according to claim 5, wherein the specific method for completely decoupling services and components by the event monitoring mechanism is as follows: and by utilizing the message middleware, each component has a producer and a consumer, and the consumer receives and processes the message and determines whether to send the message out according to the configuration after the message is processed. If a message is sent, other components that have a snoop for the message type will receive the message for processing.
7. The visual business service orchestration method based on zero-code platforms according to claim 1,
the calling of the business service component is synchronous or asynchronous, is determined by a user in a mode set by the user, and provides a retry mechanism to ensure the final consistency of data;
when the complete service call is started, a unique ID is generated and is always stored in a call context;
the atomic service can be executed in two modes, namely an REST API mode or an event monitoring mode, if the REST API mode is adopted, the ID can be placed in a request head and transmitted to the next layer, and if the REST API mode is adopted, the ID can be transmitted as a part of a message body;
the final calling results (in-process participation, out-process participation, atomic service time consumption, service component time consumption, abnormal logs and the like) are displayed in the interface, and all calling information related to the ID can be inquired according to the ID.
8. The visual business service orchestration method based on zero-code platform according to claim 7, wherein the specific method that the ID will always be stored in the calling context is: the global unique ID can be designed as an attribute field in a message transmission entity, the ID is generated at the most source and then assigned, and then the message is circulated all the time, the information is stored in a memory in the process of circulation, and if the message middleware has an abnormal condition, the data can be persisted, which means that the data is stored in a hard disk.
9. The visual business service orchestration method based on zero-code platforms according to claim 1, further comprising a compensation mechanism: assuming that the user has already programmed a complex service, for each calling component operation, a corresponding compensation (i.e. undo) operation is registered, and the operation itself and its compensation operation are completed in one transaction, and when the subsequent operation fails, all the undo operations registered previously need to be completed in reverse order.
10. The visual business service orchestration method based on zero-code platform according to claim 9, wherein the compensation mechanism is divided into two types:
independent settings on a particular service component;
the global control calls for compensation, all called services are recorded in a list, and if the operation needing retrying or rollback occurs, the operation is obtained from the list to carry out corresponding operation; in the compensation mode, the operation requiring a service capable of providing compensation must support idempotent (otherwise data errors occur when performed multiple times).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210556581.1A CN115129304B (en) | 2022-05-20 | 2022-05-20 | Visual business service arrangement method and device based on zero code platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210556581.1A CN115129304B (en) | 2022-05-20 | 2022-05-20 | Visual business service arrangement method and device based on zero code platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115129304A true CN115129304A (en) | 2022-09-30 |
| CN115129304B CN115129304B (en) | 2024-05-14 |
Family
ID=83376875
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210556581.1A Active CN115129304B (en) | 2022-05-20 | 2022-05-20 | Visual business service arrangement method and device based on zero code platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115129304B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112346729A (en) * | 2019-10-28 | 2021-02-09 | 杭州衣科信息技术有限公司 | iOS platform interface engine processing method based on asynchronous disaster tolerance service technology |
| CN115826923A (en) * | 2022-11-03 | 2023-03-21 | 广州市企微信息科技有限公司 | PaaS platform low-code development operation and maintenance method and system |
| CN116610305A (en) * | 2023-07-19 | 2023-08-18 | 湖南云畅网络科技有限公司 | Expression arrangement method, system and storage medium for clamping groove adsorption type |
| CN116795378A (en) * | 2023-08-18 | 2023-09-22 | 宁波数益工联科技有限公司 | Method and device for arranging and executing process based on code dynamic compiling |
| CN117314127A (en) * | 2023-11-29 | 2023-12-29 | 武汉爱科软件技术股份有限公司 | Production planning and scheduling method of hybrid genetic tabu search algorithm |
| CN117806611A (en) * | 2024-02-29 | 2024-04-02 | 鱼快创领智能科技(南京)有限公司 | Method for creating new service interface based on visual automatic arrangement of interface discovery |
| CN117827191A (en) * | 2024-01-10 | 2024-04-05 | 广东赛意信息科技有限公司 | Execution method, device, equipment and storage medium based on visual modeling |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012100750A1 (en) * | 2011-01-30 | 2012-08-02 | International Business Machines Corporation | Business mashup |
| CN113608730A (en) * | 2021-07-31 | 2021-11-05 | 苏州暴暴龙物联网信息科技有限公司 | Low-code platform building method applied to digital twin collaboration field |
| CN113885858A (en) * | 2021-09-30 | 2022-01-04 | 广东电网有限责任公司 | Visual arranging method and related device for micro-service |
| CN113971037A (en) * | 2021-10-28 | 2022-01-25 | 北京锐安科技有限公司 | Application processing method and device, electronic equipment and storage medium |
| WO2022056735A1 (en) * | 2020-09-16 | 2022-03-24 | 深圳晶泰科技有限公司 | Cloud high-performance scientific calculation workflow design control system and graphical user interface |
| CN114416064A (en) * | 2021-12-16 | 2022-04-29 | 江苏康众汽配有限公司 | Distributed service arranging system and method based on BPMN2.0 |
-
2022
- 2022-05-20 CN CN202210556581.1A patent/CN115129304B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012100750A1 (en) * | 2011-01-30 | 2012-08-02 | International Business Machines Corporation | Business mashup |
| WO2022056735A1 (en) * | 2020-09-16 | 2022-03-24 | 深圳晶泰科技有限公司 | Cloud high-performance scientific calculation workflow design control system and graphical user interface |
| CN113608730A (en) * | 2021-07-31 | 2021-11-05 | 苏州暴暴龙物联网信息科技有限公司 | Low-code platform building method applied to digital twin collaboration field |
| CN113885858A (en) * | 2021-09-30 | 2022-01-04 | 广东电网有限责任公司 | Visual arranging method and related device for micro-service |
| CN113971037A (en) * | 2021-10-28 | 2022-01-25 | 北京锐安科技有限公司 | Application processing method and device, electronic equipment and storage medium |
| CN114416064A (en) * | 2021-12-16 | 2022-04-29 | 江苏康众汽配有限公司 | Distributed service arranging system and method based on BPMN2.0 |
Non-Patent Citations (2)
| Title |
|---|
| 文建全;李井锐;邹驰华;: "无代码平台技术及其在HIS系统中的应用", 电脑与信息技术, no. 05, 15 October 2020 (2020-10-15) * |
| 狄程;杨中国;韩燕波;刘晨;: "面向流数据的实时处理及服务化系统", 重庆大学学报, no. 07, 31 December 2020 (2020-12-31) * |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112346729A (en) * | 2019-10-28 | 2021-02-09 | 杭州衣科信息技术有限公司 | iOS platform interface engine processing method based on asynchronous disaster tolerance service technology |
| CN112346729B (en) * | 2019-10-28 | 2024-01-26 | 杭州衣科信息技术股份有限公司 | iOS platform interface engine processing method based on asynchronous disaster recovery service technology |
| CN115826923A (en) * | 2022-11-03 | 2023-03-21 | 广州市企微信息科技有限公司 | PaaS platform low-code development operation and maintenance method and system |
| CN116610305A (en) * | 2023-07-19 | 2023-08-18 | 湖南云畅网络科技有限公司 | Expression arrangement method, system and storage medium for clamping groove adsorption type |
| CN116610305B (en) * | 2023-07-19 | 2023-09-19 | 湖南云畅网络科技有限公司 | Expression arrangement method, system and storage medium for clamping groove adsorption type |
| CN116795378A (en) * | 2023-08-18 | 2023-09-22 | 宁波数益工联科技有限公司 | Method and device for arranging and executing process based on code dynamic compiling |
| CN116795378B (en) * | 2023-08-18 | 2023-11-21 | 宁波数益工联科技有限公司 | Method and device for arranging and executing process based on code dynamic compiling |
| CN117314127A (en) * | 2023-11-29 | 2023-12-29 | 武汉爱科软件技术股份有限公司 | Production planning and scheduling method of hybrid genetic tabu search algorithm |
| CN117314127B (en) * | 2023-11-29 | 2024-03-12 | 武汉爱科软件技术股份有限公司 | Production planning and scheduling method of hybrid genetic tabu search algorithm |
| CN117827191A (en) * | 2024-01-10 | 2024-04-05 | 广东赛意信息科技有限公司 | Execution method, device, equipment and storage medium based on visual modeling |
| CN117806611A (en) * | 2024-02-29 | 2024-04-02 | 鱼快创领智能科技(南京)有限公司 | Method for creating new service interface based on visual automatic arrangement of interface discovery |
| CN117806611B (en) * | 2024-02-29 | 2024-05-14 | 鱼快创领智能科技(南京)有限公司 | Method for creating new service interface based on visual automatic arrangement of interface discovery |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115129304B (en) | 2024-05-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115129304A (en) | Zero-code-platform-based visual business service arrangement method and device | |
| US11487529B2 (en) | User interface that integrates plural client portals in plural user interface portions through sharing of one or more log records | |
| US9070104B2 (en) | Cross-context task management | |
| US10845962B2 (en) | Specifying user interface elements | |
| US8302096B2 (en) | Methods and systems to perform individual tasks as a composite task | |
| Wohed et al. | Patterns-based evaluation of open source BPM systems: The cases of jBPM, OpenWFE, and Enhydra Shark | |
| US7925977B2 (en) | Architecture solution map builder | |
| EP2369502A2 (en) | SQL generation | |
| US9311144B1 (en) | Processing virtual transactions of a workflow in atomic manner in a workflow management computer system | |
| CN111784108B (en) | Modeling method and device of main data management platform | |
| CN111258567A (en) | Service code development processing method and device | |
| US20130152039A1 (en) | Project specific software delivery planning | |
| US11609932B2 (en) | Web services having live data updates | |
| JP2002041744A (en) | Method and system for workflow processing | |
| US10713016B1 (en) | Method of implementing rules on visual language using visual blocks | |
| CN114936152A (en) | Application testing method and device | |
| Xu et al. | A petri net-based method for data validation of web services composition | |
| Privitera | Creation of a web platform for event-flow visualization | |
| Team | Service Development and Operation | |
| Reis | Distributed and Scalable Architecture for SAF-T Analysis and Processing | |
| Nuraminah | Implementation of Data Access Object Pattern in Bookkeeping System Development | |
| Zhang | Migrating a monolithic system to Event-Driven Microservices: A case study in Philips | |
| CN115879434A (en) | Template generation method, device, equipment and storage medium for information disclosure report | |
| CN112685015A (en) | Low-code quick digital development system for new retail | |
| CN113205421A (en) | Accounting method and device for financial products |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |