CN116579593A - Service processing method, device, electronic equipment and computer readable storage medium - Google Patents
Service processing method, device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN116579593A CN116579593A CN202210107310.8A CN202210107310A CN116579593A CN 116579593 A CN116579593 A CN 116579593A CN 202210107310 A CN202210107310 A CN 202210107310A CN 116579593 A CN116579593 A CN 116579593A
- Authority
- CN
- China
- Prior art keywords
- service
- business
- processing
- service processing
- flow
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 41
- 238000012545 processing Methods 0.000 claims abstract description 608
- 238000000034 method Methods 0.000 claims abstract description 212
- 230000008569 process Effects 0.000 claims description 192
- 238000004590 computer program Methods 0.000 claims description 19
- 230000006870 function Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 11
- 238000011161 development Methods 0.000 description 9
- 230000003993 interaction Effects 0.000 description 6
- 238000007726 management method Methods 0.000 description 6
- 238000005111 flow chemistry technique Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/177—Editing, e.g. inserting or deleting of tables; using ruled lines
- G06F40/18—Editing, e.g. inserting or deleting of tables; using ruled lines of spreadsheets
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Data Mining & Analysis (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the application provides a service processing method, a device, electronic equipment and a computer readable storage medium, and relates to the technical field of computers. The method comprises the following steps: the service processing request which is sent by the service system and comprises the service flow record list identification and the service data to be processed is received, the corresponding service flow record list and the service processing flow file are determined based on the service flow record list identification, the service data to be processed can be processed through the service processing flow file, the service processing data generated by each service processing node is recorded in the service flow record list, then the service data processing result is generated according to the service processing data recorded in the service flow record list and is sent to the service system, the service processing flow and the service system are decoupled deeply, the service processing data can be read, modified or input directly from the corresponding service flow record list, and the service processing efficiency is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a service processing method, a device, an electronic apparatus, and a computer readable storage medium.
Background
With the rapid development of computer technology, paperless office work increasingly replaces traditional office modes, and people begin to become accustomed to more designing and managing business processes or workflows by computers, for example, using computers to automatically transfer documents, information or tasks according to some predefined rule.
The existing flow system for managing the business flow is generally a subsystem of the business system, and has higher coupling degree with the business system. When a service person needs to check, modify or examine the service data, the service form of the service system is generally obtained for the service person to perform corresponding processing, and when the service person finishes processing the service data in the service form, the service person also needs to interact with the service system, and the history form in the service system is updated based on the processed service form.
When a plurality of business processing nodes are needed to process data in a business form in a business process, after the business form is updated according to the processing operation of the business personnel of each business processing node, interaction with a business system is needed, and a history form in the business system is updated according to the processed business form, so that a large number of repeated operations are generated, the efficiency is lower when the business is processed, and the actual requirement is difficult to meet.
Disclosure of Invention
The embodiment of the application aims to solve the problem of low service processing efficiency.
In a first aspect, a service processing method is provided, where the method includes:
receiving a service processing request sent by a service system, wherein the service processing request comprises a service flow record table identifier and service data to be processed;
determining a corresponding business process record table and a business process flow file based on the business process record table identification, wherein the business process flow file comprises at least one business process node;
processing the service data to be processed based on the service processing flow file, and recording the service processing data generated by each service processing node in a service flow record table;
based on the business processing data recorded in the business process record table, generating a business data processing result corresponding to the business processing request, and sending the business data processing result to the business system.
In an alternative embodiment of the first aspect, the business process record table is generated by:
creating a business item based on the received business item creation request;
determining a business form rule corresponding to a business project;
acquiring flow configuration information;
And generating a business process record table based on the business form rule and the process configuration information.
In an optional embodiment of the first aspect, the service item creation request includes a service item identifier, at least one service attribute corresponding to the service item identifier, and attribute configuration information corresponding to each service attribute;
determining a service form rule corresponding to the service item comprises the following steps:
receiving a selection operation aiming at least one service attribute, and determining at least one target service attribute from the at least one service attribute based on the selection operation; taking at least one target service attribute and attribute configuration information corresponding to each target service attribute as a service form rule corresponding to a service item;
the business process record list comprises at least one target business attribute;
in an alternative embodiment of the first aspect, the service data to be processed comprises at least one target service attribute and a corresponding attribute value;
after determining the corresponding business process record table based on the business process record table identification, the method further comprises the following steps:
and taking an attribute value corresponding to at least one target service attribute in the data to be processed as initial service processing data, and storing the initial service processing data in an attribute value field of the corresponding target service attribute in a service flow record table.
In an optional embodiment of the first aspect, obtaining the flow configuration information includes:
receiving a business process configuration operation aiming at a business project through a business process configuration interface;
determining flow configuration information based on the business flow configuration operation;
the method further comprises the steps of:
and generating a business processing flow file corresponding to the business project based on the flow configuration information.
In an alternative embodiment of the first aspect, the business process configuration interface comprises a process drawing interface, the business process configuration operation comprises a process drawing operation, the process drawing operation comprises a business processing node selection operation, a business processing logic configuration operation for the selected business processing node, and a node authority configuration operation.
In an alternative embodiment of the first aspect, the flow configuration information includes: at least one service processing node, node authority information of each service processing node and service processing logic sequence among each service processing node.
In an optional embodiment of the first aspect, processing service data to be processed based on a service processing flow file, and recording service processing data generated by each service processing node in a service flow record table, including:
Processing the corresponding target service data by each service processing node, and storing the processed service processing data in a service flow record table;
aiming at a first service processing node in the service processing logic sequence, the target service data corresponding to the first service processing node is the service data to be processed;
for each service processing node except the first service processing node, the target service data corresponding to the service processing node is the service processing data generated by the last service processing node in the service processing logic sequence.
In an optional embodiment of the first aspect, when any service processing node in the service processing logic sequence has at least two corresponding next service processing nodes, the flow configuration information further includes execution conditions corresponding to the at least two next service processing nodes, the target service processing node is determined according to service processing data corresponding to the service processing node and the execution conditions corresponding to the at least two next service processing nodes, the service processing data corresponding to the service processing node is processed by the target processing node, and the service processing data obtained after the processing is stored in the service flow record table.
In a second aspect, there is provided a service processing apparatus, the apparatus comprising:
the receiving module is used for receiving a service processing request sent by the service system, wherein the service processing request comprises a service flow record table identifier and service data to be processed;
the determining module is used for determining a corresponding business process record table and a business processing flow file based on the business process record table identification, wherein the business processing flow file comprises at least one business processing node;
the processing module is used for processing the business data to be processed based on the business processing flow file and recording the business processing data generated by each business processing node in the business flow record table;
the result sending module is used for generating a service data processing result corresponding to the service processing request based on the service processing data recorded in the service flow record table and sending the service data processing result to the service system.
In an optional embodiment of the second aspect, the recording table generating module is further configured to:
creating a business item based on the received business item creation request;
determining a business form rule corresponding to a business project;
acquiring flow configuration information;
and generating a business process record table based on the business form rule and the process configuration information.
In an optional embodiment of the second aspect, the service item creation request includes a service item identifier, at least one service attribute corresponding to the service item identifier, and attribute configuration information corresponding to each service attribute;
the record table generation module is specifically used for, when determining the business form rule corresponding to the business item:
receiving a selection operation aiming at least one service attribute, and determining at least one target service attribute from the at least one service attribute based on the selection operation; taking at least one target service attribute and attribute configuration information corresponding to each target service attribute as a service form rule corresponding to a service item;
the business process record list comprises at least one target business attribute;
in an alternative embodiment of the second aspect, the service data to be processed comprises at least one target service attribute and a corresponding attribute value;
the system also comprises an initial service processing data recording module which is specifically used for:
and taking an attribute value corresponding to at least one target service attribute in the data to be processed as initial service processing data, and storing the initial service processing data in an attribute value field of the corresponding target service attribute in a service flow record table.
In an optional embodiment of the second aspect, the record table generating module is specifically configured to, when acquiring the flow configuration information:
Receiving a business process configuration operation aiming at a business project through a business process configuration interface;
determining flow configuration information based on the business flow configuration operation;
the system further comprises a flow file generation module, which is specifically used for:
and generating a business processing flow file corresponding to the business project based on the flow configuration information.
In an alternative embodiment of the second aspect, the business process configuration interface comprises a process drawing interface, the business process configuration operation comprises a process drawing operation, the process drawing operation comprises a business processing node selection operation, a business processing logic configuration operation for the selected business processing node, and a node authority configuration operation.
In an alternative embodiment of the second aspect, the flow configuration information includes: at least one service processing node, node authority information of each service processing node and service processing logic sequence among each service processing node.
In an optional embodiment of the second aspect, when the processing module processes the service data to be processed based on the service processing flow file, and records the service processing data generated by each service processing node in the service flow record table, the processing module is specifically configured to:
processing the corresponding target service data by each service processing node, and storing the processed service processing data in a service flow record table;
Aiming at a first service processing node in the service processing logic sequence, the target service data corresponding to the first service processing node is the service data to be processed;
for each service processing node except the first service processing node, the target service data corresponding to the service processing node is the service processing data generated by the last service processing node in the service processing logic sequence.
In an optional embodiment of the second aspect, the method further comprises a condition detection module, specifically configured to:
when any service processing node in the service processing logic sequence has at least two corresponding next service processing nodes, the flow configuration information also comprises execution conditions corresponding to the at least two next service processing nodes respectively, a target service processing node is determined according to the service processing data corresponding to the service processing nodes and the execution conditions corresponding to the at least two next service processing nodes respectively, the service processing data corresponding to the service processing nodes are processed through the target processing node, and the service processing data obtained after the processing is stored in a service flow record table.
In a third aspect, an electronic device is provided, the electronic device comprising:
The system comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the service processing method of any embodiment when executing the program.
In a fourth aspect, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the service processing method of any of the above embodiments.
In a fifth aspect, a computer program product or computer program is provided, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The computer instructions are read from a computer-readable storage medium by a processor of a computer device, which executes the computer instructions, such that the computer device, when executed, implements the method provided in the embodiments of the first aspect.
According to the business processing method, the business processing request which is sent by the business system and comprises the business flow record table identification and the business data to be processed is received, and the corresponding business flow record table and the business processing flow file are determined based on the business flow record table identification, wherein the business flow processing file can comprise at least one business processing node. The service processing flow is deeply decoupled from the service system by processing the service data to be processed through the service processing flow file, recording the service processing data generated by each service processing node in the service flow record table, generating a service data processing result according to the service processing data recorded in the service flow record table, and transmitting the service data processing result to the service system, wherein in the service processing flow, the service data with requirements of checking, modifying, approving and the like can be directly read, modified or recorded from the corresponding service flow record table, and the service processing efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that are required to be used in the description of the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic flow chart of a service processing method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a business process record of a business processing method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a business process record of a business processing method according to an embodiment of the present application;
fig. 4 is a schematic diagram of processing service data to be processed in a service processing method according to an embodiment of the present application;
fig. 5 is a schematic diagram of determining a target service processing node by using an execution condition in a service processing method according to an embodiment of the present application;
fig. 6 is a schematic flow chart of a service processing method according to an embodiment of the present application;
fig. 7 is a schematic diagram of a system architecture of a flow system in a service processing method according to an embodiment of the present application;
fig. 8 is a schematic diagram of creating and configuring a service processing flow in a service processing method according to an embodiment of the present application;
fig. 9 is a schematic diagram of a service processing flow in a service processing method according to an embodiment of the present application;
Fig. 10 is a schematic structural diagram of a service processing device according to an embodiment of the present application;
fig. 11 is a schematic structural diagram of an electronic device for service processing according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described below with reference to the drawings in the present application. It should be understood that the embodiments described below with reference to the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application, and the technical solutions of the embodiments of the present application are not limited.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless expressly stated otherwise, as understood by those skilled in the art. It will be further understood that the terms "comprises" and "comprising," when used in this specification, specify the presence of stated features, information, data, steps, operations, elements, and/or components, but do not preclude the presence or addition of other features, information, data, steps, operations, elements, components, and/or groups thereof, all of which may be included in the present specification. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. The term "and/or" as used herein indicates that at least one of the items defined by the term, e.g., "a and/or B" may be implemented as "a", or as "B", or as "a and B".
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
The workflow, i.e. the process of automatically executing and managing the business process flow by a computer, enables the process of transferring documents, information or tasks between a plurality of participants to be automatically performed according to some predefined rule, thereby realizing some expected business objective or causing the realization of the objective.
At present, a process system for realizing workflow generally establishes association with a process instance through a service system, has higher coupling degree with a process center, and generally embeds a document page of the service system into a process center display interface of the process system when service personnel need to check and modify and approve a service document. If the business personnel need to control the operation authority of the business document on the approval node (or the business processing node), the operation authority corresponding to the corresponding business document in the business system needs to be modified, and if the business document information corresponding to each approval node (or the business processing node) needs to be recorded in the approval (or processing) process, a corresponding history table needs to be established for recording, so that the process efficiency of the business document approval (or processing) is lower, and the actual requirements are difficult to meet.
The application provides a service processing method, a device, electronic equipment and a readable storage medium, and aims to solve the technical problems in the prior art.
The technical solutions of the embodiments of the present application and technical effects produced by the technical solutions of the present application are described below by describing several exemplary embodiments. It should be noted that the following embodiments may be referred to, or combined with each other, and the description will not be repeated for the same terms, similar features, similar implementation steps, and the like in different embodiments.
The embodiment of the application provides a service processing method, which is applied to a server, as shown in fig. 1, and comprises the following steps:
step S101, a service processing request sent by a service system is received, wherein the service processing request comprises a service flow record table identifier and service data to be processed.
The service system may be any external system that needs to perform flow design and management, and may receive a service processing request sent by the service system, where the service processing request may include a service flow record table identifier and service data to be processed. Specifically, the service processing method provided by the application can be implemented as a flow system, and the service system can interact with the flow system through a predefined interface.
In the embodiment of the application, the service processing request can be triggered by a user through a client associated with the service system, the data to be processed is input through a user interface of the client, the service processing request type is selected, the service flow record table identifier corresponding to the service processing request type can be determined through the service processing request type selected by the user, and the determined service flow record table identifier can be used as the service flow record table identifier in the service processing request.
Specifically, a matching relationship between a service request type and a service flow record table identifier may be preconfigured in the service system, for example, the service request type may include a leave document, a financial expenditure document, and a reimbursement document, the service flow record table identifier may include a leave document record table identifier, a financial expenditure flow record table identifier, and a reimbursement flow record table identifier, and the preconfigured matching relationship may be: the leave-out bill is matched with the leave-out flow record table identifier, the financial expense bill is matched with the financial expense flow record table identifier, the reimbursement bill is matched with the reimbursement flow record table identifier, the corresponding business flow record table identifier can be determined according to the business processing request type selected by the user, the business flow record table identifier in the business system has a corresponding relation with the business flow record table identifiers of all business flow record tables in the flow system, and the corresponding business flow record table can be determined according to the business flow record table identifier in the business processing request.
Step S102, determining a corresponding business process record table and a business process flow file based on the business process record table identification, wherein the business process flow file comprises at least one business process node;
each business process record table may have a corresponding business process record table identifier, including but not limited to a name, a number, etc., and the corresponding business process record table may be determined according to the business process record table identifier in the business process request. And a business process record list can correspond to a business process flow file, and the business process flow file corresponding to the business process request can be further determined through the determined business process record list.
The business process flow file may characterize a business process flow, and in particular may include at least one business process node, each of which may characterize a business process step in the business process flow. When there are multiple service processing nodes, there is an execution order between the service processing nodes, and each service processing node may have a corresponding service processor and a service processing authority of the service processor for the service processing node.
The service flow record table can be used for recording service processing data generated by each service processing node in the process of processing the service data to be processed, namely recording the change process of the service data after passing through each service processing node.
In the embodiment of the application, the business process record table can be generated by the following ways:
(1) Based on the received business item creation request, a business item is created.
The service item creation request may include a service item identifier, at least one service attribute corresponding to the service item identifier, and attribute configuration information corresponding to each service attribute.
Specifically, when the service processing method provided by the application is implemented as a flow system, the flow system can provide a service item creation interface for the user, and the user can configure the service item identifier, at least one service attribute corresponding to the service item identifier and attribute configuration information corresponding to each service attribute through the service item creation interface. The business project can be understood as a business theme needing to create a corresponding task processing flow, and a user can visually configure some basic information (namely, business project identification, business attribute, attribute configuration information and the like) of the business project through a business project creation interface. The service item identifier may be a service item name, the service attribute may be an attribute associated with the service item, and the attribute configuration information may refer to a condition that a parameter value of each service attribute should satisfy, for example, a data range, a text length, and the like.
In some embodiments, the flow system may first obtain, from the service system, each first service item identifier in the service system (where the prefix of "first" is only used to distinguish between service items in two systems), and service attribute, attribute configuration information corresponding to each first service item identifier. When a user configures a service item, the service item identifier can be configured first, then the flow system determines a matched first service item identifier according to the service item identifier, and service attribute and attribute configuration information corresponding to the matched first service item identifier are used as service attribute and attribute configuration information corresponding to the service item identifier, so that the user does not need to configure the service item identifier in the flow system again.
As an example, when the service item identifier is an employee leave approval process, the service attribute corresponding to the service item identifier may include a leave request, a leave request time, a leave request type, a leave request reason, and the like. Taking the service attribute of the applicant as an example, the attribute configuration information of the service attribute can be: the text length is 1-10 bytes, and the data type is character type.
In some embodiments, a service item may be further subdivided into a plurality of service points, and a corresponding service attribute and attribute configuration information may be further configured for each service point. For example, for a business item identified as an employee leave examination and approval process, the business item may be further subdivided into a plurality of business points, for example, a business point may be set in the business item for each department of the company, that is, the business point corresponding to the a department, the business point corresponding to the B department, and so on may be further included under the business item. The service attribute and the attribute configuration information corresponding to each service point may be all identical, or different service attributes and attribute configuration information may be respectively configured, which is not limited by the present application.
(2) And determining a business form rule corresponding to the business item.
Wherein, determining the business form rule corresponding to the business item may include: at least one target business attribute is determined from at least one business attribute corresponding to a business project, and then attribute configuration information corresponding to each target business attribute is further determined, so that the at least one target business attribute and the attribute configuration information corresponding to each target business attribute can be used as business form rules corresponding to the business project.
(3) And acquiring flow configuration information. In the embodiment of the application, the business process configuration operation for the business project can be received through the preset business process configuration interface, and then the process configuration information is determined based on the business process configuration operation, and the process configuration information can be used for representing the business processing process corresponding to the business project. Specifically, a method of acquiring the flow configuration information will be described in detail later.
(4) Based on the business form rule and the flow configuration information, a business flow record table is generated, wherein the business flow record table comprises at least one target business attribute. The service data to be processed in the service processing request is associated with the target service attribute, and specifically, the service data to be processed may include an attribute value corresponding to at least one target service attribute.
The business form rule may include at least one target business attribute and attribute configuration information of the target business attribute, and the flow configuration information may include node base attributes of business processing nodes in a business processing flow corresponding to the business item, for example, the node base attributes may include approval node names, approval types, approvers, approval opinions, approval times, and the like, and the business flow record table may be generated based on the business form rule and the flow configuration information. Specifically, the target service attribute and the node attribute may be used as attribute value fields in a service flow record table.
For example, when the target business attribute includes a dummy, a dummy requesting time and a dummy requesting type, and the node base attribute in the flow configuration information may include an approval node name, an approval person, an approval time and an approval opinion, the target business attribute and the node base attribute may be used as attribute value fields in a business flow record table, and a schematic diagram of the formed business flow record table may be shown in fig. 2. At this time, the business flow record table is not filled with business data yet.
When the target service attribute includes a dummy, a dummy time and a dummy type, the service data to be processed in the service processing request may include at least one target service attribute and a corresponding attribute value, for example, the service data to be processed may be "dummy: king; leave-on time: for 2 days; leave-on type: false matters.
In the embodiment of the application, the service item creation request may include a service item identifier, at least one service attribute corresponding to the service item identifier, and an attribute configuration value corresponding to each service attribute.
The determining the business form rule corresponding to the business item may include the following steps: a selection operation for at least one business attribute is received, and at least one target business attribute is determined from the at least one business attribute based on the selection operation.
When the service processing method provided by the application is implemented as a flow system, a plurality of service attribute options can be provided for a user in a service item configuration interface of the flow system, at least one target service attribute is determined from at least one service attribute according to the selection operation of the user, and the target service attribute and the corresponding attribute configuration information can be used as a form rule corresponding to the service item.
It is understood that the business process record table generated based on the business form rules and the process configuration information includes at least one target business attribute.
The business processing method provided by the application can adapt to various in-use and complex business scenes, and can establish corresponding form rules based on at least one target attribute and corresponding attribute configuration information only by selecting at least one target business attribute from a plurality of business attributes, so as to quickly generate a business flow record list.
In some embodiments, when a service item includes a plurality of service points, different target service attributes may be set for each service point, and the target service attribute corresponding to each service point and the attribute configuration information corresponding to the target service attribute are used as the form rule corresponding to the service point.
In the embodiment of the application, the service data to be processed can comprise at least one target service attribute and a corresponding attribute value. After determining the corresponding business process record table based on the business process record table identification, the method further comprises the following steps: and taking an attribute value corresponding to at least one target service attribute in the data to be processed as initial service processing data, and storing the initial service processing data in an attribute value field of the corresponding target service attribute in a service flow record table.
In one example, when the attribute value field in the business process record table includes a dummy please, a dummy requesting time and a dummy requesting type, the business data to be processed is "dummy requesting: king; leave-on time: for 2 days; leave-on type: in case of false, the service data to be processed can be used as initial service processing data and stored in the attribute value field of the corresponding target service attribute in the service flow record table, and the schematic diagram of the service flow record table is shown in fig. 3.
Step S103 may process the service data to be processed based on the service processing flow file, and record the service processing data generated by each service processing node in the service flow record table.
The service processing flow file includes at least one service processing node, and processing the data to be processed based on the service processing flow file may refer to processing the data to be processed based on at least one service processing node in the service processing flow file.
Specifically, the service processing flow file may represent a service processing flow, and the service processing node may represent a service processing step in the service processing flow, and based on the service processor corresponding to the service processing node and the service processing authority of the service processor for the service processing node, it may be determined what kind of processing is performed on the service data to be processed by which person in the service processing step. In an actual application scenario, when processing service data to be processed based on a service processing node, the service data to be processed may be actually sent to a client of the service processor according to a service processor corresponding to the service processing node and service processing rights of the service processor, so that the service processor may process the service data to be processed in its own service processing rights through the client, and after the processing is completed, the service data obtained after the processing is sent to a server of the flow system through the client.
In the embodiment of the present application, processing service data to be processed based on a service processing flow file, and recording service processing data generated by each service processing node in a service flow record table, may include the following steps:
and processing the corresponding target service data through each service processing node, and storing the processed service processing data in a service flow record table.
Wherein, for the first service processing node in the service processing logic sequence, the target service data corresponding to the first service processing node is the service data to be processed (i.e. the initial service processing data in the service flow record table); for each service processing node except the first service processing node, the target service data corresponding to the service processing node is the service processing data generated by the last service processing node in the service processing logic sequence. Here, the service processing data generated by the last service processing node may refer to service processing data obtained after the last service processing node completes processing and recorded in the service flow record table.
In an example, in a process of processing service data to be processed based on a service processing flow file, a process of changing the service processing data may be as shown in fig. 4, and it is assumed that one service processing flow file includes a service processing node a, a service processing node B, a service processing node C, and a service processing node D.
Aiming at the service processing node A, the corresponding target service data is the service data to be processed, when the service processing node A processes the service data to be processed, the service processing data A is obtained, and the service processing data A is recorded in a service flow record table.
Aiming at the service processing node B, the corresponding target service data is service processing data A, after the service processing data A is processed by the service processing node B, service processing data B is obtained, and the service processing data B is recorded in a service flow record table.
For the service processing node C, the corresponding target service data is service processing data B, and when the service processing node C processes the service processing data B, the service processing data C is obtained and recorded in the service flow record table.
For the service processing node D, the corresponding target service data is service processing data C, and after the service processing data C is processed by the service processing node D, the service processing data D is obtained and recorded in the service flow record table.
In some embodiments, when a certain service processing node in the service processing logic sequence has at least two next service processing nodes, each next service processing node may have a corresponding execution condition, and the next service processing node corresponding to the execution condition satisfied by the service processing data obtained after processing by the current service processing node may be used as a target service processing node, and the service processing data of the current service processing node is processed by the target service processing node, and the service processing data obtained after processing is stored in the service flow record table.
Step S104, based on the business processing data recorded in the business process record list, generating a business data processing result corresponding to the business processing request, and sending the business data processing result to the business system.
In the embodiment of the application, the latest business processing data recorded in the business process record table can be converted into the corresponding JSON file by using a JSON (lightweight data exchange format) format, and the JSON file is used as a business data processing result to be sent to a business system.
According to the business processing method, the business processing request which is sent by the business system and comprises the business flow record table identification and the business data to be processed is received, and the corresponding business flow record table and the business processing flow file are determined based on the business flow record table identification, wherein the business flow processing file can comprise at least one business processing node. The service processing flow is deeply decoupled from the service system by processing the service data to be processed through the service processing flow file, recording the service processing data generated by each service processing node in the service flow record table, generating a service data processing result according to the service processing data recorded in the service flow record table, and transmitting the service data processing result to the service system, wherein in the service processing flow, the service data with requirements of checking, modifying, approving and the like can be directly read, modified or recorded from the corresponding service flow record table, and the service processing efficiency is improved.
The embodiment of the application provides a possible implementation manner, and the business processing flow file corresponding to the business item can be generated based on flow configuration information, wherein the flow configuration information can comprise: at least one service processing node, node authority information of each service processing node and service processing logic sequence among each service processing node.
The process configuration information acquisition may include the following steps: receiving a business process configuration operation aiming at a business project through a business process configuration interface; flow configuration information is determined based on the business flow configuration operation.
In the embodiment of the present application, the business process configuration interface may include a process drawing interface, the business process configuration operation may include a process drawing operation, and the process drawing operation includes a business processing node selection operation, a business processing logic configuration operation for the selected business processing node, and a node authority configuration operation.
Receiving a business process configuration operation for the business project through a business process configuration interface; determining flow configuration information based on the business flow configuration operation may include the steps of:
receiving a flow drawing operation for the service item through a flow drawing interface, wherein the flow drawing operation comprises a service processing node selection operation and a service processing logic configuration operation for the selected service processing nodes;
The method comprises the steps of determining at least one service processing node and a service processing logic sequence among the service processing nodes based on flow drawing operation, wherein the service processing logic sequence can comprise an execution sequence among the at least one service processing node, and can also comprise an execution condition corresponding to each next service processing node respectively when one service processing node (assumed to be the current service processing node) corresponds to at least two next service processing nodes, so that in practical application, the target service processing node is determined from the at least two next service processing nodes as the next service processing node to be executed by detecting the execution condition met by the service processing data of the current service processing node.
Specifically, when the service processing method provided by the application is implemented as a flow system, the service flow configuration interface can be implemented by a flow designer in the flow system, and the selection of the service processing nodes and the configuration of service processing logic between the service processing nodes can be completed by visually drawing a flow chart containing at least one service processing node. After the drawing of the flow chart is completed through the flow designer, the engine is required to deploy the flow chart to generate a business flow processing file. The business process file can be in an XML format, so that the process system can determine the execution sequence among the business process nodes based on the business process text, sequentially send business data which are responsible for processing by the business process nodes to the clients of business processors of the business process nodes according to the execution sequence, and receive the business process data returned by the clients of the business processors.
Specifically, the flow designer can be realized based on bpmn.js (a flow chart modeler), a visual business flow configuration interface can be formed, the interface can comprise a menu bar and a drawing area, and various node icons required for drawing the flow chart can be arranged in the menu bar; business personnel may draw a flow chart on the designer, including but not limited to: at least one service processing node is selected from the menu bar, and drawing of the flow chart is completed in a dragging, connecting line and other modes.
In the embodiment of the application, the business process configuration operation further comprises node authority configuration operation aiming at each business processing node, the process configuration information comprises node authority information of each business processing node, and the node authority information comprises business processing persons corresponding to the business processing nodes and business processing authorities of the business processing persons aiming at the business processing nodes;
wherein, the service processing authority of the service processor can comprise at least one of the following:
and checking, modifying or approving the service processing data to be processed or the service processing data in the service flow record list.
In the embodiment of the application, the service processing authority of each service processing node can be set according to the requirement for the service processing personnel of the service processing node, one service processing node can be formed by a plurality of service processing personnel, and each service processing personnel can have different service processing authorities.
Meanwhile, the configuration of the service processing authority can be more refined, for example, aiming at the authority of viewing the service processing data in the service flow record table, the service processor can be further limited to see the attribute values of which attribute fields in the service flow record table, the range of the service processor viewing the historical service processing data can be limited, for example, the service processor of each service processing node can only see the service processing data of the last service processing node, and the configuration can be flexibly performed, so that the application is not limited.
The embodiment of the application provides a possible implementation manner, and for each service processing node except for the last service processing node in the service processing logic sequence, at least one next service processing node exists;
when any service processing node in the service processing logic sequence has at least two corresponding next service processing nodes, determining a target service processing node according to service processing data corresponding to the service processing node and execution conditions corresponding to the at least two next service processing nodes respectively, processing the service processing data corresponding to the service processing node through the target processing node, and storing the processed service processing data in a service flow record table.
The determining a target service processing node according to the service processing data corresponding to the service processing node and the execution conditions respectively corresponding to at least two next service processing nodes may refer to determining which next service processing node execution condition the current service processing data meets according to the current service processing data of the current service processing node, taking the next service processing node corresponding to the met execution condition as the target service processing node, and processing the current service processing data corresponding to the current service processing node through the target processing node.
In one example, assume that the approval process of the leave application for a employee is shown in fig. 5, where there are two next service processing nodes, service processing node C and service processing node E, respectively, in service processing node B. The execution condition corresponding to the service processing node C is greater than or equal to 2 days, and the execution condition corresponding to the service processing node E is less than 2 days, so that the target service processing node after the service processing node B can be determined according to the leave-out days in the service data B of the service processing node B, specifically, when the leave-out days in the service data B are greater than or equal to 2 days, the target service processing node is the service processing node C, and when the leave-out days in the service data B are less than 2 days, the target service processing node is the service processing node E, and the service processing data B is processed through the target processing node.
In one example, as shown in fig. 6, the service processing method provided by the present application includes the following steps:
step S601, receiving a service item creation request, wherein the service item creation request comprises a service item identifier, at least one service attribute corresponding to the service item identifier and attribute configuration information corresponding to each service attribute;
step S602, creating a business item based on the business item creation request;
step S603, receiving a selection operation for at least one service attribute, and determining at least one target service attribute from the at least one service attribute based on the selection operation; taking at least one target service attribute and attribute configuration information corresponding to each target service attribute as a service form rule corresponding to a service item;
step S604, obtaining flow configuration information;
step S605, generating a business processing flow file corresponding to the business project based on the flow configuration information;
step S606, based on the business form rule and the flow configuration information, generating a business flow record table, wherein the business flow record table comprises at least one target business attribute;
step S607, receiving a service processing request sent by a service system, where the service processing request includes a service flow record table identifier and service data to be processed; the service data to be processed comprises at least one target service attribute and a corresponding attribute value;
Step S608, determining a corresponding business process record table and a business process flow file based on the business process record table identifier, wherein the business process flow file includes at least one business process node;
step S609, processing the corresponding target service data through each service processing node, and storing the processed service processing data in a service flow record table;
the target service data corresponding to the first service processing node in the service processing logic sequence is the service data to be processed; for each service processing node except the first service processing node, the target service data corresponding to the service processing node is the service processing data corresponding to the last service processing node in the service processing logic sequence;
specifically, for each service processing node except the last service processing node in the service processing logic sequence, there is at least one next service processing node; when at least two next service processing nodes exist, the flow configuration information further includes execution conditions corresponding to the at least two next service processing nodes, and the processing of the corresponding target service data by each service processing node includes:
For any service processing node, responding to the existence of at least two next service processing nodes, determining a target service processing node according to service processing data corresponding to the service processing node and execution conditions respectively corresponding to the at least two next service processing nodes, and processing the service processing data corresponding to the service processing node through the target processing node;
step S610, based on the business processing data recorded in the business process record table, generating a business data processing result corresponding to the business processing request, and sending the business data processing result to the business system.
In order to more clearly explain the service processing method of the present application, the service processing will be further described with reference to specific examples.
The application provides a service processing method by which the deep decoupling of a service system and a flow system can be realized. The business system can be used for configuring and executing the business processing flow, and storing business processing data generated by each business processing node in the business processing flow in a corresponding business flow record table, and the business system can be in butt joint with the flow system through a pre-agreed interface, so that business processing requests containing business flow record table identifiers and business data to be processed are sent to the flow system, business data processing results returned by the flow system and aiming at the business processing requests are received, so that business developers on the side of the business system can concentrate on self business development without the professional knowledge of too many workflow engines, and more time is strived for business development while the business processing efficiency is improved.
In practical application, the service processing method provided by the embodiment of the present application may be implemented as a flow system, as shown in fig. 7, and may interact with an external system (i.e. a service system) through a pre-agreed interface.
Specifically, the pre-agreed interface may be a RESTful (representational state transfer) interface, and may be an interface conforming to the REST (Representational State Transfer ) principle. In REST principle, anything that may be referred to can be regarded as a resource, and the resource can be an entity or an abstract concept. While the RESTful interface may implement any resource, access to the resource may be made by using the same interface.
The external system in fig. 1 may be any business system that needs to perform flow design and management, and may be connected to the flow system through a RESTful interface.
The functions implemented by the flow system on the right side can be mainly divided into three parts: flow configuration, flow functions, and data storage. Wherein:
(1) The flow configuration may specifically include a service point configuration function, a form rule configuration function, a flow modeling function, a rights configuration function, an event subscription function, and the like.
Specifically, the service point configuration function may refer to that service personnel may perform addition and deletion of service points and configuration and maintenance of service point related information through a flow system; the service points may refer to a specific process scenario (such as a leave note, a reimbursement note, etc.), where the service points in the process system are set according to the service points in the service system, and the service attributes of the service points in the process system may be all or part of the service attributes of the corresponding service points in the service system, where an association relationship exists between the two service attributes; the service point related information may be basic data such as project numbers of service points, service point names, service point types, service attributes corresponding to the service points, and the like.
The form rule configuration function may refer to that a service person may configure key service attributes and types for a service point through a flow system, where the key service attributes may be service attributes that need to be focused selected from multiple service attributes of the service point. The type of service attribute may refer to attribute configuration information such as data range, text length, etc.
The process modeling function may refer to that a business person may configure a business process flow (e.g., a business approval flow) for a business point through a process system. Specifically, the drawing of the flow chart can be performed through a model designer in the flow system, so that the visual configuration of the business processing flow is realized. The model designer comprises a menu bar and a drawing area, wherein the menu bar is provided with various node icons required by drawing a flow chart; business personnel can draw a flow chart on a model designer, and can consider a drawn flow chart as a flow model, and the process of the flow chart drawn by the business personnel is a flow modeling process. Specifically, a service person may draw a flowchart for a service point through a model designer, one flowchart may include a plurality of service processing nodes, each service processing node may be configured, for example, a service processor of each service processing node is set, or an execution condition of each service processing node is set, and the execution condition may be an expression about a value of a key service attribute.
The rights configuration function may be flexible in referring to the processing rights of the service processor controlling each service point, for example, the service processor controlling each service node may view, modify or edit which of the key service attributes.
The event subscription function refers to process processing information of a service point in the service system, where the process processing information may include various events of each service processing node in a service processing process, for example, after a certain designated service processing node processes (or a certain approval node approves passing in an approval process), a corresponding notification message is sent to the service system.
(2) A process function may refer to a process system providing a respective user interface (i.e., a workbench) to a respective business person using the process system, where the business person may operate the respective function of the use system by performing the operation in the respective user interface. In particular, the interaction options of the user interface may include, but are not limited to: the interactive options of 'my application', 'my agent', 'my done', 'event management', 'flow monitoring', etc. can be set according to the actual application requirements, and the user interfaces of business personnel having different operation authorities in the flow system can display different interactive options, which is not a limitation of the present application. If the 'event management' interaction option is clicked, the processing of the business process can be performed, and if the 'process monitoring' interaction option is clicked, the historical processing details of the business process can be checked.
(3) The data storage function refers to the ability to store data in the flow system through different types of databases.
The flow system has low use threshold and flexible various configuration functions, can provide stable, efficient and powerful flow service, and meets the actual application requirements.
In one example, the service processing method provided by the application may include the following steps:
the first step, the process system can receive a service item creation request of the service system, create a corresponding service item, select an item manager, and enter the process system by the item manager to perform process configuration for the service item. In this example, a business item may be a generic concept of a business point, and one business item may correspond to a plurality of business points.
In the process of flow configuration, as shown in fig. 8, after a service item is created, an item initialization configuration may be performed, for example, a message queue may be allocated, then a project manager may create a service point under the service item, one service item may correspond to one service point or may correspond to a plurality of service points, and a project manager may set a service name, a type, a service attribute, and other relevant basic configuration of each service point. The project manager may further configure a form rule of each service point, that is, determine a key service attribute from a plurality of service attributes of the service point, and set attribute configuration information of the key service attribute, for example, a data range, a text length, and the like, to complete rule configuration related to the service form attribute, where the determined key service attribute is used to determine which service attributes are included in the service processing flow record table, and a condition that a value of each key service attribute should meet. After the regular configuration of the forms, project management personnel can visually draw a flow chart through a model designer, one flow chart can be regarded as a flow model, and the design of the flow model is completed. In the process of designing the flow model, project management personnel can configure for each service processing node (i.e. flow approval node) of the flow model, including but not limited to setting service processing personnel of each service processing node, and setting flow processing authority of each service processing personnel. After the process model design is completed, the process model can be deployed, and a business process record table (i.e. a business entity table in the figure) can be generated according to rule configuration (i.e. form rule). After the process model is deployed, a business process flow file is generated and stored in a database.
And secondly, the service system sends the service data to be processed to the flow system for processing in a Restful interface mode. The service data to be processed may include service point numbers, service flow record table identifiers, applicant identifiers, and service data to be processed. The service data to be processed may be associated with a form rule of the service point, for example, if the service point is a leave list, the service data to be processed may include four fields including a leave request, a leave request start time, a leave request end time, a leave request reason, and values of the respective fields.
And thirdly, determining a target service point based on the service point number, processing the service data to be processed according to the service processing flow file corresponding to the target service point, inserting an initial service data in a service flow record table, and continuously recording in a subsequent service processing flow.
And fourthly, processing the latest recorded business data in the business process record list sequentially through each business processing node in the business process according to the business process flow file, wherein the processing operation comprises but is not limited to operations such as checking, approving, modifying or annotating. After a service processor of a service processing node finishes processing service data, the service data processed by the service processing node is inserted into a service flow record table, so that the processing process and the processing result in the whole service processing flow are recorded.
And fifthly, ending the business processing flow, and returning the latest business data to the business system by the flow system, wherein the business system can synchronize the data according to the returned business data.
As shown in fig. 9, the following describes a business processing method provided by the present application by taking a leave-on ticket as an example:
firstly, a business system submits a business document to be processed to a flow system for approval. The service bill to be processed is assumed to be a leave bill, and the service bill contains information such as leave requesting person, leave requesting type (sick, annual leave, leave), leave requesting days, leave requesting start and stop time and the like. When the business system submits the to-be-processed leave bill to the flow system, the flow system determines a business processing flow file (such as an XML format file for describing a flow chart drawn in advance by business personnel) corresponding to the leave bill, generates a business flow instance based on the business processing flow file, and drives the circulation of the business flow according to each business processing node in the business flow instance under the pushing of a flow engine to display and manage the business flow.
In this example, the leave document may include the following information: please dummy, king; leave-on type, leave-on; leave for 3 days. When the business system submits the leave bill to the flow system, a flow engine of the flow system generates a business flow instance according to a business processing flow file corresponding to the leave bill and starts the business flow instance, wherein the execution sequence of each business processing node (also called as an approval node) in the business flow instance corresponds to a flow chart drawn in advance by business personnel. And determining a business flow record list corresponding to the leave list, and inserting an initial bill information into the business flow record list according to the leave list.
As shown in fig. 9, the service processing of the first service processing node in the service flow example is an artificial development manager, and initial bill information recorded in the service flow record table is displayed in the client of the development manager for the development manager to examine and approve the initial bill information. If the processing authority of the service processor set by the service processing node includes modifying the bill information, the development manager can modify the bill information, for example, change the leave-in days in the bill information into 2 days, and record the approved bill information in the service flow record table. After the development manager examines and approves, the next service processing node changes, as shown in fig. 3, since the leave-on days are changed to 2 days after the development manager examines and approves, the service processing of the next service processing node is the company leader, and the latest recorded bill information in the service flow record table is displayed in the client side of the company leader for the company leader to examine and approve. And after the company leads the approval, recording the approved bill information in a business flow record list and taking the bill information as the latest recorded bill information. And similarly, displaying the latest recorded bill information in the business process record list in the client of the personnel manager, allowing the personnel manager to examine and approve, taking the examined and approved bill information as the latest recorded bill information in the business process record list after examination and approval, generating a subscription message based on the latest recorded bill information in the business process record list, and sending the subscription message to the business system.
In the above process, each time the service processor of the service processing node examines and approves the bill information, a piece of data is inserted into the service flow record table, the change of the bill information in the examination and approval process and the examination and approval result are recorded, and after the last service processor examines and approves, the service flow record table is stored in the database.
In the whole approval process, the information of the approval document is directly read and recorded from the business process record table of the process system, interaction with the business system is not needed, and the business processing efficiency is greatly improved.
An embodiment of the present application provides a service processing apparatus, as shown in fig. 10, the testing apparatus 100 may include: a receiving module 1001, a determining module 1002, a processing module 1003, and a result transmitting module 1004, wherein,
the receiving module 1001 is configured to receive a service processing request sent by a service system, where the service processing request includes a service flow record table identifier and service data to be processed;
a determining module 1002, configured to determine a corresponding service flow record table and a service processing flow file based on the service flow record table identifier, where the service processing flow file includes at least one service processing node;
The processing module 1003 is configured to process the service data to be processed based on the service processing flow file, and record service processing data generated by each service processing node in a service flow record table;
the result sending module 1004 is configured to generate a service data processing result corresponding to the service processing request based on the service processing data recorded in the service flow record table, and send the service data processing result to the service system.
The service processing device receives a service processing request including a service flow record table identifier and service data to be processed, which is sent by a service system, and determines a corresponding service flow record table and a service processing flow file based on the service flow record table identifier, wherein the service flow processing file may include at least one service processing node. The service processing flow is deeply decoupled from the service system by processing the service data to be processed through the service processing flow file, recording the service processing data generated by each service processing node in the service flow record table, generating a service data processing result according to the service processing data recorded in the service flow record table, and transmitting the service data processing result to the service system, wherein in the service processing flow, the service data with requirements of checking, modifying, approving and the like can be directly read, modified or recorded from the corresponding service flow record table, and the service processing efficiency is improved.
In the embodiment of the application, the method further comprises a record table generation module, which is specifically used for:
creating a business item based on the received business item creation request;
determining a business form rule corresponding to a business project;
acquiring flow configuration information;
and generating a business process record table based on the business form rule and the process configuration information.
In the embodiment of the application, the service item creation request comprises a service item identifier, at least one service attribute corresponding to the service item identifier and attribute configuration information corresponding to each service attribute;
the record table generation module is specifically used for, when determining the business form rule corresponding to the business item:
receiving a selection operation aiming at least one service attribute, and determining at least one target service attribute from the at least one service attribute based on the selection operation; taking at least one target service attribute and attribute configuration information corresponding to each target service attribute as a service form rule corresponding to a service item;
the business process record list comprises at least one target business attribute;
in the embodiment of the application, the service data to be processed comprises at least one target service attribute and a corresponding attribute value;
The system also comprises an initial service processing data recording module which is specifically used for:
and taking an attribute value corresponding to at least one target service attribute in the data to be processed as initial service processing data, and storing the initial service processing data in an attribute value field of the corresponding target service attribute in a service flow record table.
In the embodiment of the present application, when the record table generating module acquires the flow configuration information, the record table generating module is specifically configured to:
receiving a business process configuration operation aiming at a business project through a business process configuration interface;
determining flow configuration information based on the business flow configuration operation;
the system further comprises a flow file generation module, which is specifically used for:
and generating a business processing flow file corresponding to the business project based on the flow configuration information.
In the embodiment of the application, the business process configuration interface comprises a process drawing interface, the business process configuration operation comprises a process drawing operation, the process drawing operation comprises a business processing node selection operation, a business processing logic configuration operation aiming at the selected business processing node and a node authority configuration operation.
In the embodiment of the application, the flow configuration information comprises: at least one service processing node, node authority information of each service processing node and service processing logic sequence among each service processing node.
In the embodiment of the present application, when processing the service data to be processed based on the service processing flow file, and recording the service processing data generated by each service processing node in the service flow record table, the processing module 1003 is specifically configured to:
processing the corresponding target service data by each service processing node, and storing the processed service processing data in a service flow record table;
aiming at a first service processing node in the service processing logic sequence, the target service data corresponding to the first service processing node is the service data to be processed;
for each service processing node except the first service processing node, the target service data corresponding to the service processing node is the service processing data generated by the last service processing node in the service processing logic sequence.
In the embodiment of the application, the system further comprises a condition detection module, which is specifically used for:
when any service processing node in the service processing logic sequence has at least two corresponding next service processing nodes, the flow configuration information also comprises execution conditions corresponding to the at least two next service processing nodes respectively, a target service processing node is determined according to the service processing data corresponding to the service processing nodes and the execution conditions corresponding to the at least two next service processing nodes respectively, the service processing data corresponding to the service processing nodes are processed through the target processing node, and the service processing data obtained after the processing is stored in a service flow record table.
The device of the embodiment of the present application may perform the method provided by the embodiment of the present application, and its implementation principle is similar, and actions performed by each module in the device of the embodiment of the present application correspond to steps in the method of the embodiment of the present application, and detailed functional descriptions of each module of the device may be referred to the descriptions in the corresponding methods shown in the foregoing, which are not repeated herein.
The embodiment of the application provides an electronic device (computer device/system), which comprises a memory, a processor and a computer program stored on the memory, wherein the processor executes the computer program to realize the steps of a service processing method, and compared with the related technology, the method can realize the following steps: the business data with the requirements of checking, modifying, approving and the like can be directly read, modified or input from the corresponding business process record list, so that the business processing efficiency is improved.
In an alternative embodiment, an electronic device is provided, as shown in fig. 11, the electronic device 11000 shown in fig. 11 includes: a processor 11001 and a memory 11003. In which a processor 11001 is coupled to a memory 11003, such as via a bus 11002. Optionally, the electronic device 11000 may also include a transceiver 11004, where the transceiver 11004 may be used for data interaction between the electronic device and other electronic devices, such as transmission of data and/or reception of data, etc. It should be noted that, in practical applications, the transceiver 11004 is not limited to one, and the structure of the electronic device 11000 is not limited to the embodiment of the present application.
The processor 11001 may be a CPU (Central Processing Unit ), general purpose processor, DSP (Digital Signal Processor, data signal processor), ASIC (Application Specific Integrated Circuit ), FPGA (Field Programmable Gate Array, field programmable gate array) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules and circuits described in connection with this disclosure. The processor 11001 may also be a combination of computing functions, e.g., including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.
Bus 11002 may include a path to transfer information between the aforementioned components. Bus 11002 may be a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus or EISA (Extended Industry Standard Architecture ) bus, or the like. The bus 11002 may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 11, but not only one bus or one type of bus.
The Memory 11003 may be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory ) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory ), a CD-ROM (Compact Disc Read Only Memory, compact disc Read Only Memory) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store a computer program and that can be Read by a computer, without limitation.
The memory 11003 is used for storing a computer program for executing an embodiment of the present application, and is controlled to be executed by the processor 11001. The processor 11001 is configured to execute a computer program stored in the memory 11003 to implement the steps shown in the foregoing method embodiments.
Among them, electronic devices include, but are not limited to: mobile terminals such as mobile phones, notebook computers, PADs, and stationary terminals such as digital TVs, desktop computers, and the like.
Embodiments of the present application provide a computer readable storage medium having a computer program stored thereon, which when executed by a processor, implements the steps of the foregoing method embodiments and corresponding content.
The embodiment of the application also provides a computer program product, which comprises a computer program, wherein the computer program can realize the steps and corresponding contents of the embodiment of the method when being executed by a processor.
The terms "first," "second," "third," "fourth," "1," "2," and the like in the description and in the claims and in the above figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate, such that the embodiments of the application described herein may be implemented in other sequences than those illustrated or otherwise described.
It should be understood that, although various operation steps are indicated by arrows in the flowcharts of the embodiments of the present application, the order in which these steps are implemented is not limited to the order indicated by the arrows. In some implementations of embodiments of the application, the implementation steps in the flowcharts may be performed in other orders as desired, unless explicitly stated herein. Furthermore, some or all of the steps in the flowcharts may include multiple sub-steps or multiple stages based on the actual implementation scenario. Some or all of these sub-steps or phases may be performed at the same time, or each of these sub-steps or phases may be performed at different times, respectively. In the case of different execution time, the execution sequence of the sub-steps or stages can be flexibly configured according to the requirement, which is not limited by the embodiment of the present application.
The foregoing is merely an optional implementation manner of some of the implementation scenarios of the present application, and it should be noted that, for those skilled in the art, other similar implementation manners based on the technical ideas of the present application are adopted without departing from the technical ideas of the scheme of the present application, and the implementation manner is also within the protection scope of the embodiments of the present application.
Claims (12)
1. A method for processing a service, comprising:
receiving a service processing request sent by a service system, wherein the service processing request comprises a service flow record table identifier and service data to be processed;
determining a corresponding business process record table and a business process flow file based on the business process record table identifier, wherein the business process flow file comprises at least one business process node;
processing the service data to be processed based on the service processing flow file, and recording service processing data generated by each service processing node in the service flow record table;
and generating a service data processing result corresponding to the service processing request based on the service processing data recorded in the service flow record table, and sending the service data processing result to the service system.
2. The business processing method of claim 1, wherein the business process record table is generated by:
creating a business item based on the received business item creation request;
determining a business form rule corresponding to the business item;
acquiring flow configuration information;
and generating a business process record table based on the business form rule and the process configuration information.
3. The service processing method according to claim 2, wherein the service item creation request includes a service item identifier, at least one service attribute corresponding to the service item identifier, and attribute configuration information corresponding to each service attribute;
the determining the service form rule corresponding to the service item comprises the following steps:
receiving a selection operation for the at least one service attribute, and determining at least one target service attribute from the at least one service attribute based on the selection operation; taking the at least one target service attribute and attribute configuration information corresponding to each target service attribute as a service form rule corresponding to the service item;
the business process record table includes the at least one target business attribute.
4. A service processing method according to claim 3, wherein the service data to be processed comprises the at least one target service attribute and a corresponding attribute value;
after the corresponding business process record table is determined based on the business process record table identification, the method further comprises the following steps:
and taking an attribute value corresponding to the at least one target service attribute in the data to be processed as initial service processing data, and storing the initial service processing data in an attribute value field of the corresponding target service attribute in the service flow record table.
5. The service processing method according to claim 2, wherein the obtaining flow configuration information includes:
receiving a business process configuration operation aiming at the business project through a business process configuration interface;
determining the flow configuration information based on the business flow configuration operation;
the method further comprises the steps of:
and generating the business processing flow file corresponding to the business item based on the flow configuration information.
6. The business processing method of claim 5, wherein the business process configuration interface comprises a process drawing interface, the business process configuration operation comprises a process drawing operation, the process drawing operation comprises a business processing node selection operation, a business processing logic configuration operation for the selected business processing node, and a node authority configuration operation.
7. The service processing method according to claim 2, wherein the flow configuration information includes: at least one service processing node, node authority information of each service processing node and service processing logic sequence among each service processing node.
8. The service processing method according to claim 7, wherein the processing the service data to be processed based on the service processing flow file and recording the service processing data generated by each service processing node in the service flow record table includes:
processing the corresponding target service data through each service processing node, and storing the processed service processing data in the service flow record table;
aiming at a first service processing node in the service processing logic sequence, the target service data corresponding to the first service processing node is the service data to be processed;
and aiming at each service processing node except the first service processing node, the target service data corresponding to the service processing node is the service processing data generated by the last service processing node in the service processing logic sequence.
9. The traffic processing method according to claim 7, wherein,
when any service processing node in the service processing logic sequence has at least two corresponding next service processing nodes, the flow configuration information further comprises execution conditions respectively corresponding to the at least two next service processing nodes, a target service processing node is determined according to the service processing data corresponding to the service processing nodes and the execution conditions respectively corresponding to the at least two next service processing nodes, the service processing data corresponding to the service processing nodes are processed through the target processing node, and the service processing data obtained after processing is stored in the service flow record table.
10. A service processing apparatus, comprising:
the receiving module is used for receiving a service processing request sent by the service system, wherein the service processing request comprises a service flow record table identifier and service data to be processed;
the determining module is used for determining a corresponding business process record table and a business process flow file based on the business process record table identification, wherein the business process flow file comprises at least one business process node;
The processing module is used for processing the business data to be processed based on the business processing flow file and recording business processing data generated by each business processing node in the business flow record table;
and the result sending module is used for generating a service data processing result corresponding to the service processing request based on the service processing data recorded in the service flow record table and sending the service data processing result to the service system.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory, characterized in that the processor executes the computer program to carry out the steps of the method according to any one of claims 1-9.
12. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the service processing method according to any of claims 1-9.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210107310.8A CN116579593A (en) | 2022-01-28 | 2022-01-28 | Service processing method, device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210107310.8A CN116579593A (en) | 2022-01-28 | 2022-01-28 | Service processing method, device, electronic equipment and computer readable storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN116579593A true CN116579593A (en) | 2023-08-11 |
Family
ID=87541834
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210107310.8A Pending CN116579593A (en) | 2022-01-28 | 2022-01-28 | Service processing method, device, electronic equipment and computer readable storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN116579593A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117273628A (en) * | 2023-08-21 | 2023-12-22 | 杭州微宏科技有限公司 | Business processing system, method, device and medium based on flow automation |
-
2022
- 2022-01-28 CN CN202210107310.8A patent/CN116579593A/en active Pending
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117273628A (en) * | 2023-08-21 | 2023-12-22 | 杭州微宏科技有限公司 | Business processing system, method, device and medium based on flow automation |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5080447B2 (en) | Method and apparatus for context recognition in groupware clients | |
RU2400814C2 (en) | Hierarchical projects in system and method of project control supported by computer | |
US8151208B2 (en) | Workflow tracking information preview | |
US20140278663A1 (en) | Electronic discovery systems and workflow management method | |
US20080255997A1 (en) | Enterprise integrated business process schema | |
US8959475B2 (en) | Generating a semantic graph that allows a user to intelligently and efficiently connect with people and assets involved in projects | |
US20140040791A1 (en) | Development platform for software as a service (saas) in a multi-tenant environment | |
US20090183063A1 (en) | System and method of integrating a plurality of form related workflow tools | |
TW201405452A (en) | Workflow management device and workflow management method | |
US20210224300A1 (en) | Centralized cloud service management | |
US20240086400A1 (en) | Systems and methods for managing designated content in collaboration systems | |
US20140324518A1 (en) | Autotagging business processes | |
JP6963062B1 (en) | Information processing device and information processing method | |
Sidorova et al. | The role of information technology in business process management | |
Ferreira et al. | A semantic approach to the discovery of workflow activity patterns in event logs | |
JP7277877B2 (en) | Signboard-based business processing device and business processing method | |
CN116579593A (en) | Service processing method, device, electronic equipment and computer readable storage medium | |
CN114693283B (en) | Cross-system business process approval processing method and device and computer equipment | |
Sukarsa et al. | Data exchange between information system at low bandwidth quality using messaging | |
JP2023110808A (en) | Smart tag-based work processing device and work processing method | |
JP2007524886A (en) | System and method for managing a distributed design network | |
US20160328457A1 (en) | Information System with Temporal Data | |
US20190172068A1 (en) | Method and system for implementing a crm quote and order capture context service | |
KR20160044074A (en) | Method and system for generating and managing mark for supporting collaboration based BIM between multi-user at 3D object viewer | |
Putro et al. | Collaboration of Progressive Web App (PWA) And Firebase Cloud Messaging (FCM) for Optimal Performance Mailing Software |
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 |