CN114995879A

CN114995879A - Information processing method and system based on low-coding platform

Info

Publication number: CN114995879A
Application number: CN202210742254.5A
Authority: CN
Inventors: 张晓芳; 陈科; 赵富鑫; 丁杰; 潘文凯; 龙芳
Original assignee: Smartdot Technologies Co ltd
Current assignee: Smartdot Technologies Co ltd
Priority date: 2022-06-28
Filing date: 2022-06-28
Publication date: 2022-09-02
Anticipated expiration: 2042-06-28
Also published as: CN114995879B

Abstract

The invention relates to the field of workflow processing, and particularly discloses an information processing method and system based on a low-code platform.

Description

Information processing method and system based on low-coding platform

Technical Field

The invention relates to the field of information processing, in particular to an information processing method and system based on a low-coding platform.

Background

The low-code platform is widely applied at present, and particularly under the condition that various micro applications are wide, various minimally invasive enterprises call various service applications in a self-defined mode through the existing component mode and the like so as to realize the combination of various applications in various processes.

In the prior office system, based on an approval process configuration system in a low-code platform, the approval of various different businesses of an enterprise is generally integrated into a unified platform window, and according to the actual self-defined approval process of the business, the characteristics of conditional branches, node parallelism, signing, unfixed processes and the like are supported, the approval path is flexibly adjusted and changed, and the dynamic configuration is realized and is changed as required. However, how to coordinate the low-coded structured components in the front end and the back end with the application of the back end server to improve the security of information access and the convenience of process operation becomes a focus of attention.

Disclosure of Invention

In order to solve one of the above problems, the present invention provides an information processing method and system based on a low-coding platform.

The method comprises the steps that a Spring framework is adopted by the low-coding platform, the Spring framework is set to be a layered framework and used for a user to select components independently, the simple components are configured to form application objects, and the application objects are combined in an XML or Java mode to realize application functions; arranging a plurality of components in a plurality of application servers;

the low-coding platform is set to be separated into a front end and a back end, wherein the back end only needs to be responsible for providing a callable API service to the front end according to an agreed data format; the front end and the back end interact through HTTP requests, after the front end obtains data, page assembly and rendering are carried out on the components, and results are returned to the browser; the component or the component set is stored with identification information, and the identification information is mapped with user role information;

when a user calls the component or the component set through the API interface, authenticating the role information and the identification information of the user, and after the user passes the authentication, allowing the API interface to call the corresponding component and generate a corresponding application object; the authentication is realized in a service layer based on Spring Security.

Optionally, the layered structure includes an interface adaptation layer, where the interface adaptation layer encapsulates an interface that needs to interact with the outside, and format conversion of different structures is completed through interface adaptation.

The interface package comprises an REST interface, a Soap interface and an Rpc interface.

The hierarchical structure includes a persistence/interface layer shield layer configured to shield technical differences of the application program from the infrastructure operation.

And a common service layer is arranged in the hierarchical structure and used for providing common capacity needed by the process platform, the common capacity is realized in an interface mode, and common transaction control in the platform is executed based on Spring transactions.

Optionally, assembling and rendering a page of the component, and returning a result to the browser, specifically including: different component identifications are displayed in a front-end page, different component functions are correspondingly realized by the different component identifications, a user selects and arranges target components in the front-end page of the low-code platform through the component identifications in an operation page, the component identifications and the arrangement operation correspond to a transaction processing workflow, a back end calls the corresponding component identifications according to the generated transaction flow, and target component information is obtained from a background server to generate a corresponding transaction flow chart.

Optionally, the low-code platform is a work service flow platform, and the front end and the back end are separated for constructing the UI, and the needed page is customized according to needs.

Optionally, the setting of the rights to the character information is to list all the rights in a tree structure.

Optionally, the authentication of the role is implemented by a java web token + spring security framework.

The system provides an information processing system based on a low-code platform, and the system comprises the low-code platform and is used for executing the method.

According to the scheme, the role is used as a safety mechanism of the access component through the layered framework based on the front-end separation and the spring framework, the code control amount is reduced, and the relationship between the role and the application component can be completely distinguished through traversing the layered inheritance attribute of the authority node according to the authority setting of the tree structure. Therefore, when the front end and the back end are called, the user only needs to obtain the authority role corresponding table, namely, the corresponding component is marked, and when the authority role is verified, the user only needs to verify the attribution of the authority information of different components according to the subordinate hierarchical relation of the authority, so that the quick verification calling and the safety control verification on the low-code platform are realized.

Drawings

The features and advantages of the present invention will be more clearly understood by reference to the accompanying drawings, which are schematic and are not to be construed as limiting the invention in any way.

FIG. 1 is a schematic flow chart of the application of the method of the present invention.

Detailed Description

These and other features and characteristics of the present invention, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will be better understood upon consideration of the following description and the accompanying drawings, which form a part of this specification. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. It will be understood that the figures are not drawn to scale. Various block diagrams are used in the present invention to illustrate various variations of embodiments according to the present 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 some, not all, embodiments of the present invention. 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 "/" herein means "or", for example, A/B may mean A or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone.

It should be noted that, for the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first", "second", and the like are used to distinguish the same items or similar items with basically the same functions or actions, and those skilled in the art can understand that the terms "first", "second", and the like do not limit the quantity and execution order. For example, the first information and the second information are for distinguishing different information, not for describing a specific order of information.

It should be noted that, in the embodiments of the present invention, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present relevant concepts in a concrete fashion.

Example 1

As shown in fig. 1, the present invention provides an information processing method based on a low-code platform, where the low-code platform uses a Spring framework, and is based on a layered framework, the layered framework allows a user to select components autonomously, and sets multiple components in multiple application servers, and configures simple components into application objects based on the Spring framework, and the application objects are combined in an XML or Java manner to implement application functions; the platform is set to be in a front-end and back-end separated architecture, and the back end only needs to be responsible for providing callable API services to the front end according to an agreed data format. The front end and the back end interact through HTTP requests, and after the front end obtains data, assembly and rendering of a page are carried out, and finally the page is returned to the browser. Separation of front and rear ends: the front end code base and the back end code base are separated, the front end codes have pseudo back ends which can be used for Mock testing, and the method for simplifying the testing environment by constructing the virtual testing object can support independent development and testing of the front ends. And the back-end code also stores detailed test cases except for function realization so as to ensure the usability of the API and reduce the integration risk.

Optionally, the front end may adopt a mainstream MVVM framework, and adopt Vue as a front end development framework. The rear end is based on Spring, various capabilities are realized by the idea of layering and service, and independent application packaging is carried out based on Spring Boot and Spring Cloud; the system decouples the front end and the back end, and then both sides can only concentrate on the service logic which needs to be realized, thereby improving the flexibility and the stability of the application, and reducing the work and the influence on the system caused by that all codes need to be adjusted and changed when any modification is carried out.

The system based on the low code can be specifically a workflow platform in an application approval service, the low code system supports UI construction using a front-end and back-end separation technology, a required page can be customized according to needs, and the API service interface provides rich process capability interfaces for a front-end system to directly use. Optionally, the first component set is obtained from the low-code platform based on the target component information, and a plurality of target components are selected from the low-code platform based on the component list information in the target component information; and acquiring a first component set based on the plurality of target components and component layout information in the target component information. Different component identifications are displayed in a front-end page of the low-code platform, different component functions are correspondingly realized by the different component identifications, and a user can select and arrange target components in the front-end page of the low-code platform through dragging the component identifications in the page, so that a background server of the low-code platform reads a dragging operation instruction of the user, and component list information and component arrangement information in the target component information can be generated.

The overall approval work business process platform is developed in a layering and serving mode: the technical framework of the platform development is Spring/Spring boot and Spring cloud.

The platform is provided with a persistence/interface layer shielding layer for shielding the technical difference of the application program on the operation of the infrastructure, and the upper layer application code basically does not need to be adjusted when the infrastructure such as data is replaced. The database persistence realizes the use of different levels based on Spring Data/JPA/JDBC, and the platform uses the difference of Spring Cache shielding caching technology

The common service layer in the layering of the platform is used for providing the common capacity needed by the process platform, the overall capacity is abstractly provided in an interface mode, when the use of the upper-layer capacity is ensured, and when concrete implementation (such as the replacement of personnel information sources) is needed to be replaced, such as the change of personnel position and position in the workflow of an enterprise, the code adjustment is not needed for other dependent services, and the overall transaction control is performed based on Spring transactions. The authority control system realizes a field service layer by means of Spring Security, namely the core of the platform, the platform defines various service capabilities of a flow in an external interface mode, and interaction between the platform and other services ensures loose coupling between the platform and other services through interfaces.

In the layered service in the platform, an interface adaptation layer is provided for interface encapsulation when interaction with the outside is needed, and format conversion request packaging of different structures is completed through interface adaptation. For front-back separation and interaction between systems, the method and the system provide differentiated interface setting, and the platform provides an REST interface; for the traditional WebServicce, the method is provided in a form of a Soap interface; the method comprises the steps of providing REST and Rpc modes for micro-service calling, providing a directly used Java Api expression layer for providing support of a user interface for embedded extension, providing support for interface customization by a platform in a mode of completing a page, an interface component, a service function library and the like, packaging the interface component based on a Jquery framework for a traditional browser, and packaging the interface component based on an Vue framework for a modern browser.

The authority control system is realized by depending on Spring Security, front-end maintenance Role information is provided mainly through Role Api types in Role setting, a Role list is obtained through find Role ust, check Role name is used for judging whether a Role name is repeated, a delete Role name is used for deleting a Role, an update Role, change members is used for setting Role user information, a create Role is used for building a Role, a get Role select list is used for obtaining an existing Role user, increasing, deleting, changing and checking operations of user operation roles are provided, users contained in the roles are used for setting Role information of the users in Role division, a fixed Role and other user roles are preset in the system, the fixed Role can not be deleted and changed, and only user Role attributes contained in the fixed Role can be set.

And the authority sets two interfaces, namely a function API interface and a role permission API interface. The function API class provides generation of a front-end permission tree, a query tree node method can be provided by adopting a menu display class in a platform for an approval workflow to return to the permission tree, a role permission API class provides a function get functions for role permission allocation to obtain an existing permission tree of a current role, and an update role permission updates the permission tree of the current role.

The system authentication of the role can also be realized through a java web token + spring security framework. Through the generation and the calling of the menu tree type-based permission, the inheritance creation of the role permission information configuration is realized, and the setting inheritance and the covering of the permission are facilitated.

Optionally, the tree authority is set to give different authorities to 4 role personnel for example, so as to perform different menu renderings. The function module is divided into personnel management, role management and authority management through a role authentication module class diagram, and after a role is created. A person may be set to a role, which represents that the user has the configured permissions for that role, and all permissions of the role are granted to the role through the permission management, so that the person has certain permissions. When the authority is set in the authority management, all the authorities can be listed in a tree structure, and an administrator can select the authorities. User setting is mainly provided for a corresponding interface of a front end through a User API class, User authentication is provided for a front end User through an authentication API class, an RSA encryption algorithm is provided through an RSA service class to prevent plain text transmission of a User password, a User detail service interface is provided through a Spring security architecture to realize a method for verifying whether a User is legal by a User name and inquiring User information through a User API.

Acquiring the authority set through a Role permission API, calling a User details class inheriting Spring security to generate a jwtuis object, storing User information and authority information, calling a jwttokenuil class generator token method to synthesize token information, and returning the token information to the front end.

Meanwhile, in order to prevent the illegal program from calling the middleware on the application server, the middleware must first confirm the validity of the identity of the application program, and an application program identifier pid (programid) is set in the application program, and the identifier can be replaced by a GuID generated by Delphi, and the GuID is 128-bit binary data which occupies 16 bytes. Further, in the role-based security mechanism, the security mechanism is hierarchically divided into a component hierarchy, a component interface hierarchy, and a component interface method hierarchy. When the security is controlled by a program, it is preferable that the security control is performed only at the component interface method level. As long as the security of the interface method hierarchy is controlled, it is ensured that all functions provided by the application server are not called by illegal programs.

When setting up a component, each method of the interface adds a check on the validity of the application, i.e. each method must carry a PID parameter. If the PID submitted by the application program is matched with the PID carried by the component, the application program is legal; otherwise, the application program is an illegal program, and the calling is terminated. When a client wants to make a call to a component on an application server, it must first check against the PID on the application server. If the authentication is successful, the corresponding function provided by the component can be called, otherwise, the operation is quitted.

When a user needs to use a certain function in the client interface, the client firstly judges the authority of the user. If the function has the authority to use the function, the corresponding component is called, and if not, the corresponding component is exited. Role-based security can be configured through component services management tools to set roles as aliases for a set of users; a plurality of roles are established in advance, and then one or more user groups are added into each role. Different roles are then assigned to the component objects. Thus, when a user accesses a component object, the component will check the role assigned to it, and if the user belongs to a role assigned to it, the user can access the component, otherwise the user has no access rights to the component. The security mechanism can be hierarchically divided into a component hierarchy, a component interface hierarchy, and a component interface method hierarchy. The strictness of security control is gradually increased according to the refinement of the hierarchy.

Optionally, when a user passes the security checks at the component level, the component includes three interfaces A, B, C; wherein the role assigned to interface A, B includes the user and the role assigned to interface C does not include the user, then the user has access only to interface A, B and not to interface C; if two methods M and N are included in the a interface, where the user is included in the role assigned to the M method and not in the role assigned to the N method, then the user can only access method M and not method N.

The role is used hierarchically as a safety mechanism of the access component, code control amount is reduced, and the relationship between the role and the application component can be completely distinguished by traversing hierarchical inheritance attributes of the authority nodes according to the authority setting of the tree structure. Therefore, when the front end and the back end are called, the user only needs to obtain the authority role corresponding table, namely, the corresponding component is marked, and when the authority role is verified, the user only needs to verify the attribution of the authority information of different components according to the subordinate hierarchical relation of the authority, so that the quick verification calling and the safety control verification on the low-code platform are realized.

Those skilled in the art will appreciate that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can include the processes of the embodiments of the methods described above when executed. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid State Drive (SSD), or the like; the storage medium may also comprise a combination of memories of the kind described above.

As used in this application, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being: a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of example, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

It should be noted that the above-mentioned embodiments are only for illustrating the technical solutions of the present invention and not for limiting, and although the present invention has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, which should be covered by the claims of the present invention.

Claims

1. An information processing method based on a low coding platform is characterized in that: the low-coding platform adopts a Spring framework, the Spring framework is set to be a layered framework, under the Spring framework, the components are selected autonomously, and a plurality of components are arranged in a plurality of application servers;

the low-coding platform is set to be separated from a front end and a back end, wherein the back end is used for providing a callable API service to the front end according to an agreed data format; the front end and the back end interact through HTTP requests, after the front end obtains data, assembly and rendering of a page are carried out on the assembly, and a result is returned to the browser; configuring simple components to form application objects, and combining the application objects in an XML or Java mode to realize application functions; the component or the component set is stored with identification information, and the identification information is mapped with user role information;

when the user calls the component or the component set through the API interface, the role information and the identification information of the user are authenticated, and after the user passes the authentication, the API interface is allowed to call the corresponding component and generate a corresponding application object; the authentication is realized in a service layer based on Spring Security.

2. The method of claim 1, wherein: the layered structure comprises an interface adaptation layer, the interface adaptation layer encapsulates an interface when the interface adaptation layer needs to interact with the outside, and format conversion of different structures is completed through interface adaptation.

3. The method of claim 2, wherein: the interface package comprises an REST interface, a Soap interface and an Rpc interface.

4. The method of claim 3, wherein: the hierarchical structure comprises a persistence/interface layer shielding layer for shielding the technical difference of the application object on the infrastructure operation.

5. The method of claim 4, wherein: and a common service layer is arranged in the hierarchical structure and used for providing common capacity required to be used by the platform, the common capacity is in an interface mode, and common transaction control in the platform is executed based on Spring transactions.

6. The method of claim 5, wherein: the assembly and rendering of the page to the component and the return of the result to the browser specifically include: different component identifications are displayed in a front-end page, different component functions are correspondingly realized by the different component identifications, a user selects and arranges target components in the front-end page of the low-code platform through the component identifications in an operation page, the component identifications and the arrangement operation correspond to a transaction processing workflow, a back end calls the corresponding component identifications according to the generated transaction flow, and target component information is obtained from a background server to generate a corresponding transaction flow chart.

7. The method of claim 6, wherein: the low-coding platform is a work business process platform, the front end and the back end are separated and used for constructing the UI, and the needed page is customized according to the requirement.

8. The method of claim 7, wherein: the rights settings for the role information are such that all rights are listed in a tree structure.

9. The method of claim 8, wherein: the authentication of the role is realized through a java web token + spring security framework.

10. An information handling system based on a low code platform, the system comprising a low code platform for performing the method of any of claims 1-9.