Page generation method and device, electronic equipment and storage medium

Abstract

Embodiments of the present application disclose a page generation method and device, electronic equipment and a storage medium. The method comprises: when a data acquisition request is received, determining service attribute information in the data acquisition request; based on each service configuration item corresponding to the service attribute information and a pre-configured data structure, generating a target process node page and determining a process step sequence; based on a current process step and response data corresponding to the current process step, determining a to-be-displayed detail page corresponding to a next process step of the current process step; and based on the target process node page and the to-be-updated detail page, determining a target service process page. The method solves the problem in the prior art that all process steps of service processing are hard configured in a code flow, which leads to high development code cost, low reusability and poor flexibility, and achieves the effects of reducing the development cost of the process node page, improving the accuracy of process step page jumping and meeting the user application experience.

Description

Technical Field

[0001] The embodiments of the present invention relate to computer processing technology, and more particularly to a page generation method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the development of business applications on the Internet, the processing progress of business processes is usually displayed when users use these applications, making it convenient for users to view the process.

[0003] Currently, the typical method for setting up the display method involves using hard-coded partitions to divide the business process page corresponding to all process nodes into two parts. One part displays a list of all process nodes on the left side of the page; the other part usually displays some specific details of the current process node. Users can click on a completed node in the node list, and the corresponding detailed information of the node will be displayed on the main screen accordingly.

[0004] However, in actual business process scenarios, different business processes contain different process nodes, and different process nodes also contain different process node states. Therefore, there are a large number of process steps. The existing display settings adopt the method of hard-configuring all business processing process steps in the code flow, which leads to problems such as high code development cost, low code reusability, and poor flexibility. Summary of the Invention

[0005] This invention provides a page generation method, apparatus, electronic device, and storage medium to reduce the development cost of process node pages while improving the accuracy of process step page navigation, thereby achieving the technical effect of satisfying user application experience.

[0006] In a first aspect, embodiments of the present invention provide a page generation method, the method comprising:

[0007] When a data acquisition request is received, the business attribute information in the data acquisition request is determined;

[0008] Based on the business configuration items corresponding to the business attribute information and the pre-configured data structure, a target process node page is generated, and a process step sequence is determined; wherein, the process step sequence includes at least one process step;

[0009] Based on the current process step and the response data corresponding to the current process step, determine the details page to be displayed for the next process step of the current process step, and use it as the details page to be displayed for the current process step again;

[0010] Based on the target process node page and the details page to be updated, the target business process page is determined.

[0011] Secondly, embodiments of the present invention also provide a page generation apparatus, the apparatus comprising:

[0012] The business attribute information determination module is used to determine the business attribute information in the data acquisition request when a data acquisition request is received.

[0013] The target process node page generation module is used to generate a target process node page based on the business configuration items corresponding to the business attribute information and the pre-configured data structure, and to determine the process step sequence; wherein the process step sequence includes at least one process step.

[0014] The module for determining the details page to be displayed is used to determine the details page to be displayed corresponding to the next process step of the current process step based on the current process step and the response data corresponding to the data acquisition request, and to re-designate it as the details page to be displayed corresponding to the current process step.

[0015] The target business process page determination module is used to determine the target business process page based on the target process node page and the details page to be updated.

[0016] Thirdly, embodiments of the present invention also provide an electronic device, the device comprising:

[0017] One or more processors;

[0018] Storage device for storing one or more programs.

[0019] When the one or more programs are executed by the one or more processors, the one or more processors implement the page generation method as described in any embodiment of the present invention.

[0020] Fourthly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the page generation method as described in any of the embodiments of the present invention.

[0021] The technical solution of this invention, upon receiving a data acquisition request, determines the business attribute information in the request, generates a target process node page based on the corresponding business configuration items and a pre-configured data structure, and determines the process step sequence. Then, based on the current process step and the response data corresponding to the data acquisition request, it determines the next process step's corresponding detail page to be displayed and uses it as the current process step's corresponding detail page. Finally, based on the target process node page and the detail page to be updated, it determines the target business process page. This solves the problem of high development costs, low code reusability, and poor flexibility caused by hard-coding all business processing steps in the code flow in existing technologies. By retrieving the pre-configured data structure upon acquiring the business configuration items, the invention quickly generates the target process node page for displaying the process nodes, significantly reducing the development cost of the process node page. Simultaneously, by determining the arrangement relationship between each process step based on the process step sequence, it quickly jumps to the next process step's corresponding detail page upon receiving the response data corresponding to the current process step, improving the accuracy of process step page jumps and achieving a better user experience. Attached Figure Description

[0022] To more clearly illustrate the technical solutions of exemplary embodiments of the present invention, the accompanying drawings used in describing the embodiments are briefly introduced below. Obviously, the accompanying drawings described are only a portion of the drawings of the embodiments to be described in this invention, and not all of the drawings. For those skilled in the art, other drawings can be obtained from these drawings without any creative effort.

[0023] Figure 1 This is a flowchart of a page generation method provided in Embodiment 1 of the present invention;

[0024] Figure 2 This is a schematic diagram of a page generation method provided in Embodiment 2 of the present invention;

[0025] Figure 3 This is a structural block diagram of a page generation device provided in Embodiment 3 of the present invention;

[0026] Figure 4 This is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of the present invention. Detailed Implementation

[0027] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0028] Example 1

[0029] Figure 1 This is a flowchart of a page generation method provided in Embodiment 1 of the present invention. This embodiment is applicable to process display scenarios. The method can be executed by the page generation device in this embodiment, which can be implemented in software and / or hardware, optionally through an electronic device, such as a mobile terminal, PC, or server. The device can be configured in a computing device. The page generation method provided in this embodiment specifically includes the following steps:

[0030] S110. When a data acquisition request is received, determine the business attribute information in the data acquisition request.

[0031] The business attribute information may include, but is not limited to, card number identifier, user identifier, and business identifier. For example, in a scenario where actual business processes are displayed, a corresponding process display page can be configured based on basic user information and business requirements, such as user card number ID, user account ID, and business type, which can be physical examination appointment, registration appointment, etc.

[0032] In practical applications, a data acquisition request can be considered received when a user triggers a control on the client-side page using an input device. Input devices can include physical keyboards, virtual keyboards, sound acquisition devices, handwriting devices, and touch screens, etc. Alternatively, a data acquisition request can be considered received when uploaded task information is detected. In this case, business attribute information can be queried from the data acquisition request.

[0033] It should be noted that when a data acquisition request is received, the business attribute information in the data acquisition request is determined. The business attribute information can be the information carried in the data acquisition request initiated by the client. At this time, the data acquisition request can be processed, such as parsing, to extract the business attribute information carried in the data acquisition request.

[0034] Optionally, when a data acquisition request is received, the business attribute information in the data acquisition request is determined, including: receiving a data acquisition request generated based on a user-triggered operation; parsing the data acquisition request to obtain the business attribute information in the data acquisition request.

[0035] The triggering operation may include at least one of the following: click operation, touch operation, and swipe operation.

[0036] In practical applications, interfaces can be used to receive data retrieval requests generated by user actions on client-side pages. These requests can then be parsed and processed to retrieve the business attribute information they carry. For example, in a health checkup appointment scenario, when a user clicks a submit application control on the appointment page, it's considered that the server has received a data retrieval request corresponding to the page display. This request can then be parsed to obtain business attribute information such as the user card ID, user account ID, and business identifier. This information can then be used to configure the appropriate workflow display page later.

[0037] S120. Based on the business configuration items corresponding to the business attribute information and the pre-configured data structure, generate the target process node page and determine the process step sequence.

[0038] In this context, business configuration items can be understood as the configuration information required for the configuration process page. For example, in practical applications, at least one business configuration item and its corresponding configuration data can be pre-set based on business needs and the corresponding business process. For instance, in a physical examination appointment scenario, the appointment process node can be used as a business configuration item, and the corresponding configuration data can be pre-examination assessment, customized physical examination, health check-up, physical examination report interpretation, health follow-up, etc.; alternatively, the physical examination service time can be used as a business configuration item, and the corresponding configuration data can be start time, end time, etc. The data structure can include at least one pre-set business configuration item. The target process node page refers to the page used to display the business process steps. The process step sequence includes at least one process step. For example, pre-examination assessment can be considered as one process step, or the pre-examination assessment step can be further subdivided into waiting state and completed state, resulting in two process steps.

[0039] In this embodiment, to improve the convenience of generating process pages, a set of data structures for displaying process pages can be pre-defined based on business requirements. When the business configuration items corresponding to the business attribute information are obtained, the configuration data corresponding to the business configuration items can be filled into the pre-configured data structure to generate a data structure that includes all business configuration items and configuration data. At this time, the data structure includes all process nodes and all node states contained under the process nodes, and other data information. Based on this information, a page for displaying business process steps can be generated. Correspondingly, the process step sequence can also be determined based on the process nodes and their corresponding node states. The process steps can be organized and displayed based on the process step sequence to obtain the target process node page.

[0040] It should be noted that when obtaining business attribute information, the necessary business configuration items for the process display page can be retrieved from the returned business attribute information. These can include multiple process steps in the business process, such as node information and node status information. The node information and node status information can be populated into a pre-configured data structure to obtain the process display page corresponding to each process step, i.e., the target process node page. To improve code reusability and reduce the amount of code development, the pre-configured data structure can correspond to one process node. Similarly, if there are multiple process nodes, the data structure can be called multiple times. The populated data structures can then be integrated to obtain a data structure that includes all process nodes, thus obtaining the target process node page.

[0041] Optionally, based on the business configuration items corresponding to the business attribute information and the pre-configured data structure, a target process node page is generated, including: determining at least one process node and at least one node status corresponding to each process node in each business configuration item corresponding to the business attribute information; for each process node, filling the current process node and the node status corresponding to the current process node into the pre-configured data structure to obtain the filled data structure; parsing the filled data structure to generate the target process node page.

[0042] The specific configuration data for process nodes and node statuses can be determined by technical personnel based on work conditions, and is not limited here. For example, in the experience appointment service, process nodes may include pre-examination assessment, customized physical examination, health check-up, physical examination report interpretation, health follow-up, etc. The node status for pre-examination assessment may include status information such as no assessment report initiated, pre-examination assessment initiated but assessment questionnaire not completed, and assessment questionnaire completed but assessment report not generated. The node status for customized physical examination may include status information such as assessment report generated but physical examination request not submitted, and assessment questionnaire completed but assessment report not generated. The node status for health check-up may include status information such as customized plan generated but physical examination not scheduled, and physical examination scheduled but physical examination report not generated. The node status for physical examination report interpretation may include status information such as physical examination report generated but interpretation report not generated, and follow-up plan generated but follow-up task not executed. The node status for health follow-up may include status information such as follow-up plan generated but follow-up task not executed, and follow-up task started.

[0043] In practical applications, after determining the business attribute information, at least one corresponding business configuration item can be retrieved. Correspondingly, multiple process nodes and at least one corresponding node status can be found from each business configuration item. If there is only one process node, a pre-configured data structure can be retrieved, and the process node and its corresponding node statuses can be filled into the data structure. Based on parsing the processed data structure, a process node display page (the target process node page) can be generated based on the process node and its corresponding node status. If there are multiple process nodes, a number of data structures matching the number of process nodes can be retrieved, and each process node and its corresponding node statuses can be filled into the corresponding data structures. Parsing the filled data structures allows all process nodes and their respective statuses to be filled into the preset process page configuration data, generating the target process node page. This allows users to view the progress of the business processing flow based on the target process node page.

[0044] It should be noted that, in order to achieve accurate jumps in process steps, once the business process nodes and their corresponding node states are determined, the process steps can be planned in detail. Accordingly, the sequence of process steps can be determined based on the execution order of each process node and the execution order of the states of each node under the process node, so as to display the details page of the business node based on the sequence of process steps.

[0045] Optionally, determining the process step sequence includes: obtaining at least one process step based on each process node and its corresponding node status; arranging the process steps to obtain the process step sequence.

[0046] In this embodiment, each process step in the business processing can be determined and sorted based on the execution order of each process node and its corresponding node state, thus obtaining a process step sequence. For example, the number of steps can be integrated according to the form of process node (type) + node state (state), arranged from 1 to N, where N is a normal natural number. For example, when the first node is in the first state (type=1, state=1), the corresponding process step (step) = 1; when type=1, state=2, the corresponding step = 2, and so on, to count the total number of required process steps and obtain a process step sequence. This allows for automatic jump to the next operation after the current step is completed, making it convenient for the client to determine which process step the business has been executed at when the process steps are obtained. Accordingly, the business processing details page corresponding to that process step can be displayed. For example, when the fifth node is in the second state, it can indicate that the follow-up task has started.

[0047] S130. Based on the current process step and the response data corresponding to the current process step, determine the details page to be displayed for the next process step of the current process step, and use it as the details page to be displayed for the current process step.

[0048] The "Details to be Displayed" page can be understood as the page that displays details of the process steps, where users can also complete the corresponding process operations.

[0049] It should be noted that when the page process is first triggered, the details page corresponding to the first process step (type=1, state=1) will be displayed. Furthermore, when feedback data is received after the first process step is completed, the second process step (type=1, state=2) can be found based on the process step sequence, and the user can jump to the details page corresponding to the second process step. Accordingly, subsequent business processing operations can be completed on the details page.

[0050] Specifically, after determining the sequence of process steps, when the response data of the current process step is received, the processing details page corresponding to the next process step can be determined, i.e. the details page to be displayed, so as to realize the automatic jump of process steps. At this time, the details page to be displayed can be used again as the details page to be displayed corresponding to the current process step, so that when the response data after the process step is received again, the jump to the details page corresponding to the next process step of the current process step will be restarted.

[0051] It should be noted that before generating the details page to be displayed for the corresponding process steps, the page data corresponding to the process nodes and node status can be pre-configured based on business needs. For example, based on the pre-examination assessment node, a page A to be filled can be configured; or based on the customized physical examination node, a page B to be filled can be configured. When the specific data information of the process node is obtained, the information can be directly filled into the corresponding pre-configured page to obtain the details page to be displayed.

[0052] Optionally, based on the current process step and the response data corresponding to the current process step, determine the details page to be displayed for the next process step, and use it again as the details page to be displayed for the current process step. This includes: when the response data corresponding to the current process step is received, determining the next process step corresponding to the current process step; generating the details page to be displayed based on the process node and node status corresponding to the next process step, as well as the preset page configuration data, and using it again as the details page to be displayed for the current process step.

[0053] In practical applications, after the current process step is completed, the response data corresponding to the current process step can be received. At this time, the next process step corresponding to the current process step can be found in the process step sequence. Then, the next process step (type + state) can be parsed to obtain the corresponding process node (type) and node status (state). Then, based on the preset page configuration data, the process node and node status can be processed to generate the details page to be displayed. Alternatively, when the process node and node status are parsed, the details page of the business processing corresponding to the node status under that process node can be directly retrieved from the system and used as the details page to be displayed. For example, in the step of completing a physical examination appointment, the details page to be displayed can show appointment details, the physical examination appointment node, and the appointment completion status. In this case, the details page to be displayed can be reused as the details page to be displayed for the current process step. It should be noted that, in order to improve the convenience of page generation while reducing system performance waste, the process node and node status corresponding to the next process step can be sent to the page configuration factory class, such as the PhysicalFragmentFactory class. When the PhysicalFragmentFactory receives the process node and its corresponding status, it can generate the corresponding display page, that is, the details page to be displayed, based on the preset page configuration data. At this time, the target process node page is also anchored to the corresponding process node.

[0054] It should also be noted that in practical applications, when a user clicks on a completed process node on the target process node page, the process node and its corresponding processing data can be passed to the target process node page to update the display of anchor points on the target process node page. At the same time, PhysicalFragmentFactory can parse the process node and its corresponding processing data to display the result details page corresponding to that process node.

[0055] Furthermore, it should be noted that when generating the details page to be displayed based on the process node and node status corresponding to the next process step, as well as the preset page configuration data, the process node and node status can be matched with the fields in the preset page configuration data, and then the specific information corresponding to the process node and node status can be inserted into the matching field position to generate the details page to be displayed corresponding to the process step.

[0056] Optionally, based on the process node and node status corresponding to the next process step, and the preset page configuration data, a details page to be displayed is generated, including: filling the process node and node status corresponding to the next process step into the preset page configuration data, and generating the details page to be displayed.

[0057] In practical applications, to enhance the richness of the process step page display, the process nodes and node status in the next process step can be filled into the preset positions in the preset page configuration data to generate the corresponding details page to be displayed, so that users can accurately know the process nodes and node status corresponding to the details page to be displayed.

[0058] It should be noted that before obtaining the details page to be displayed for the next process step, the details page A to be displayed for the previous process step is currently being shown. After obtaining the details page B to be displayed for the next process step, details page B can be displayed.

[0059] Optionally, after determining the next process step to be displayed based on the current process step and the response data corresponding to the current process step, the method further includes: replacing the currently displayed details page with the updated details page to be displayed.

[0060] In practical applications, after obtaining the details page B to be displayed for the next process step, the displayed details page A can be replaced based on the details page to be displayed, and details page B can be displayed.

[0061] S140. Based on the target process node page and the details page to be updated, determine the target business process page.

[0062] Specifically, the target process node page and the details page to be updated can be displayed together. For example, on the client's screen, the target process node page is displayed on the left, and the details page to be updated corresponding to the current process step is displayed on the right. When the user clicks on a process node in the target process node page, the result page corresponding to that process node will be displayed in the details page to be updated on the right. The target process node page and the details page to be updated can be used as the target business process page.

[0063] The technical solution of this embodiment, upon receiving a data acquisition request, determines the business attribute information in the request, generates a target process node page based on the business configuration items corresponding to the business attribute information and a pre-configured data structure, and determines the sequence of process steps. Then, based on the current process step and the response data corresponding to the data acquisition request, it determines the next process step's corresponding detail page to be displayed and uses it as the new detail page for the current process step. Based on the target process node page and the detail page to be updated, the target business process page is determined. This solves the problem of high development costs, low reusability, and poor flexibility caused by hard-coding all business processing steps in the code flow in existing technologies. By retrieving the pre-configured data structure when the business configuration items are obtained, the target process node page can be quickly generated to display the process nodes, greatly reducing the development cost of process node pages. Simultaneously, by determining the arrangement relationship between process steps based on the process step sequence, and quickly jumping to the next process step's corresponding detail page upon receiving the response data for the current process step, the accuracy of process step page jumps is improved, achieving a better user experience.

[0064] Example 2

[0065] As an optional embodiment of the above embodiments, Figure 2 This is a schematic diagram of a page generation method provided in Embodiment 2 of the present invention, with a specific application scenario example given. For details, please refer to the following specific content.

[0066] See Figure 2The server uses an interface to send pre-defined data structure data, which includes all process nodes and the status of all nodes within each process node. Process nodes can include pre-examination assessment, customized physical examination, health check-up, physical examination report interpretation, health follow-up, etc. The pre-examination assessment node status can include information such as no assessment report initiated, pre-examination assessment initiated but questionnaire not completed, and questionnaire completed but report not generated. The customized physical examination node status can include information such as assessment report generated but check-up request not submitted, and questionnaire completed but report not generated. The health check-up node status can include information such as customized plan generated but check-up not scheduled, and check-up scheduled but report not generated. The physical examination report interpretation node status can include information such as check-up report generated but interpretation report not generated, and follow-up plan generated but follow-up task not executed. The health follow-up node status can include information such as follow-up plan generated but follow-up task not executed, and follow-up task started. The client parses the data structure data to obtain all process nodes, which can then be displayed in the target process node page (ListView). When the server sends the process node and corresponding node status of the user's current business operation, the client displays the progress of the user's current process step, with the ListView anchored to the corresponding process node. The PhysicalFragmentFactory generates the details display page corresponding to the current process step, i.e., the details page to be updated. It should be noted that after receiving the data structure data from the server, the client parses the data, displays all process nodes in the ListView, and anchors to the process node corresponding to the user's current operation. Simultaneously, the PhysicalFragmentFactory obtains the data structure data, parses the process node (type) and node status (state) to obtain the corresponding process step (type + state = step), generates the details page to be updated (ContentView), replaces the displayed details page to be updated, and displays it. When the user clicks on a completed process node in the left-hand ListView, the process step and corresponding configuration data can be passed to the ListView, updating the display of the anchor point on the ListView. The PhysicalFragmentFactory parses the process steps and corresponding data, and displays the result page corresponding to each step. After the user completes an operation on the details page to be updated, the details page to be updated will call the next() method. This method will save step+1 and some common data to the cache (bundle), and then call the stepIncrease() method, which will automatically jump to the details page to be updated corresponding to step+1 based on the step.

[0067] Based on the above scheme, all process nodes (type) can be integrated into an array, which represents all nodes in the process. The node state (state) corresponds to different states within the process node. Other fields can also be set to describe information, such as business transaction ID (bizId), redirect link (url), status description (stateDesc), service history log (text), service start time (startTime), last follow-up time (lastFllowUpTime), next follow-up time (nextFllowUpTime), and a unique third-party ID (uniqueid), etc. The data structure of a specific process node can take the following form:

[0068] "data":[{"bizId":"follow-up ID",

[0069] "lastFollowUpTime":1621328470868,

[0070] "nextFollowUpTime":1621328470868,

[0071] "startTime":1621328470868,

[0072] "state":2,

[0073] "stateDesc":"Follow-up procedures for the current patient have begun."

[0074] "type":5}]

[0075] This can be represented as the user starting to execute the follow-up task when the user is in the 2nd node state of the 5th process node.

[0076] Building upon the above approach, the client can further integrate corresponding process steps based on the format of process node (type) + node state (state), arranged from 1 to N, where N is a normal natural number. For example, in the first node and first state (type=1, state=1), the corresponding process step (step) is 1; when type=1 and state=2, the corresponding step is 2, and so on, counting all required process steps to obtain a process step sequence. This allows the user to automatically jump to the next process step after completing the current step and display the corresponding details page for that step.

[0077] The technical solution of this embodiment, upon receiving a data acquisition request, determines the business attribute information in the request, generates a target process node page based on the business configuration items corresponding to the business attribute information and a pre-configured data structure, and determines the sequence of process steps. Then, based on the current process step and the response data corresponding to the data acquisition request, it determines the next process step's corresponding detail page to be displayed and uses it as the new detail page for the current process step. Based on the target process node page and the detail page to be updated, the target business process page is determined. This solves the problem of high development costs, low reusability, and poor flexibility caused by hard-coding all business processing steps in the code flow in existing technologies. By retrieving the pre-configured data structure when the business configuration items are obtained, the target process node page can be quickly generated to display the process nodes, greatly reducing the development cost of process node pages. Simultaneously, by determining the arrangement relationship between process steps based on the process step sequence, and quickly jumping to the next process step's corresponding detail page upon receiving the response data for the current process step, the accuracy of process step page jumps is improved, achieving a better user experience.

[0078] Example 3

[0079] Figure 3 This is a structural block diagram of a page generation device provided in Embodiment 3 of the present invention. The device includes: a business attribute information determination module 310, a target process node page generation module 320, a details page to be displayed determination module 330, and a target business process page determination module 340.

[0080] The system includes the following modules: a business attribute information determination module 310, used to determine the business attribute information in a data acquisition request when a data acquisition request is received; a target process node page generation module 320, used to generate a target process node page based on the business configuration items corresponding to the business attribute information and a pre-configured data structure, and to determine a process step sequence, wherein the process step sequence includes at least one process step; a details page to be displayed determination module 330, used to determine the details page to be displayed corresponding to the next process step of the current process step based on the current process step and the response data corresponding to the data acquisition request, and to re-establish it as the details page to be displayed corresponding to the current process step; and a target business process page determination module 340, used to determine the target business process page based on the target process node page and the details page to be updated.

[0081] The technical solution of this embodiment, upon receiving a data acquisition request, determines the business attribute information in the request, generates a target process node page based on the business configuration items corresponding to the business attribute information and a pre-configured data structure, and determines the sequence of process steps. Then, based on the current process step and the response data corresponding to the data acquisition request, it determines the next process step's corresponding detail page to be displayed and uses it as the new detail page for the current process step. Based on the target process node page and the detail page to be updated, the target business process page is determined. This solves the problem of high development costs, low reusability, and poor flexibility caused by hard-coding all business processing steps in the code flow in existing technologies. By retrieving the pre-configured data structure when the business configuration items are obtained, the target process node page can be quickly generated to display the process nodes, greatly reducing the development cost of process node pages. Simultaneously, by determining the arrangement relationship between process steps based on the process step sequence, and quickly jumping to the next process step's corresponding detail page upon receiving the response data for the current process step, the accuracy of process step page jumps is improved, achieving a better user experience.

[0082] Optionally, based on the above-mentioned device, the business attribute information determination module 310 includes a data acquisition request receiving unit and a business attribute information acquisition unit.

[0083] The data acquisition request receiving unit is used to receive data acquisition requests generated based on user-triggered operations.

[0084] The business attribute information acquisition unit is used to parse the data acquisition request and obtain the business attribute information in the data acquisition request.

[0085] Optionally, based on the above-mentioned device, the target process node page generation module 320 includes a business configuration item determination unit, a data structure acquisition unit, and a target process node page generation unit.

[0086] A business configuration item determination unit is used to determine at least one process node and at least one node status in each business configuration item corresponding to the business attribute information.

[0087] The data structure acquisition unit is used to fill the current process node and the state of each node corresponding to the current process node into a pre-configured data structure for each process node, so as to obtain the filled data structure.

[0088] The target process node page generation unit is used to parse the populated data structures and generate the target process node page.

[0089] Optionally, based on the above-mentioned device, the target process node page generation module 320 includes a process step acquisition unit and a process step sequence acquisition unit.

[0090] The process step acquisition unit is used to obtain at least one process step based on each process node and the corresponding node status.

[0091] The process step sequence acquisition unit is used to arrange each process step to obtain a process step sequence.

[0092] Optionally, based on the above-mentioned device, the detail page to be displayed determination module 330 includes a next process step determination unit and a detail page to be displayed update unit.

[0093] The next process step determination unit is used to determine the next process step corresponding to the current process step when the response data corresponding to the current process step is received.

[0094] The pending details page update unit is used to generate a pending details page based on the process node and node status corresponding to the next process step and the preset page configuration data, and then use it as the pending details page corresponding to the current process step.

[0095] Optionally, based on the above-mentioned device, the details page update unit to be displayed may include a details page generation subunit.

[0096] The "Details Page to be Displayed" sub-unit is used to fill the process node and node status corresponding to the next process step into the preset page configuration data to generate the details page to be displayed.

[0097] Optionally, based on the above-mentioned device, the detail page determination module 330 may further include a detail page replacement unit.

[0098] The pending details page replacement unit is used to replace the currently displayed pending details page based on the pending details page to obtain the updated pending details page.

[0099] The page generation apparatus provided in the embodiments of the present invention can execute the page generation method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0100] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of the present invention.

[0101] Example 4

[0102] Figure 4 This is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of the present invention. Figure 4 A block diagram is shown of an exemplary electronic device 40 suitable for implementing embodiments of the present invention. Figure 4 The electronic device 40 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.

[0103] like Figure 4 As shown, electronic device 40 is represented in the form of a general-purpose computing device. The components of electronic device 40 may include, but are not limited to: one or more processors or processing units 401, system memory 402, and bus 403 connecting different system components (including system memory 402 and processing unit 401).

[0104] Bus 403 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0105] Electronic device 40 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by electronic device 40, including volatile and non-volatile media, removable and non-removable media.

[0106] System memory 402 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 404 and / or cache memory 405. Electronic device 40 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 406 may be used to read and write non-removable, non-volatile magnetic media (… Figure 4 Not shown; usually referred to as a "hard drive"). Although Figure 4 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 403 via one or more data media interfaces. Memory 402 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.

[0107] A program / utility 408 having a set (at least one) of program modules 407 may be stored, for example, in memory 402. Such program modules 407 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 407 typically perform the functions and / or methods described in the embodiments of the present invention.

[0108] Electronic device 40 can also communicate with one or more external devices 409 (e.g., keyboard, pointing device, display 410, etc.), and with one or more devices that enable a user to interact with the electronic device 40, and / or with any device that enables the electronic device 40 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 411. Furthermore, electronic device 40 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 412. As shown, network adapter 412 communicates with other modules of electronic device 40 via bus 403. It should be understood that, although... Figure 4 As not shown, other hardware and / or software modules may be used in conjunction with electronic device 40, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0109] The processing unit 401 executes various functional applications and data processing by running programs stored in the system memory 402, such as implementing the page generation method provided in the embodiments of the present invention.

[0110] Example 5

[0111] Embodiment 5 of the present invention also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a page generation method. The method includes:

[0112] When a data acquisition request is received, the business attribute information in the data acquisition request is determined;

[0113] Based on the business configuration items corresponding to the business attribute information and the pre-configured data structure, a target process node page is generated, and a process step sequence is determined; wherein, the process step sequence includes at least one process step;

[0114] Based on the current process step and the response data corresponding to the current process step, determine the details page to be displayed for the next process step of the current process step, and use it as the details page to be displayed for the current process step again;

[0115] Based on the target process node page and the details page to be updated, the target business process page is determined.

[0116] The computer storage medium of this invention can be any combination of one or more computer-readable media. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0117] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0118] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0119] Computer program code for performing the operations of embodiments of the present invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0120] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A page generation method, characterized in that, include: When a data acquisition request is received, the business attribute information in the data acquisition request is determined; Based on the business configuration items corresponding to the business attribute information and the pre-configured data structure, a target process node page is generated, and a process step sequence is determined; wherein, the process step sequence includes at least one process step; wherein, the business configuration items are the configuration information required to configure the process page; Based on the current process step and the response data corresponding to the current process step, determine the details page to be displayed corresponding to the next process step of the current process step, and replace the displayed details page with the details page to be displayed to obtain the updated details page to be displayed; Based on the target process node page and the updated details page to be displayed, the target business process page is determined; The process of generating a target process node page based on the business configuration items corresponding to the business attribute information and the pre-configured data structure includes: Determine at least one process node and at least one node status in each business configuration item corresponding to the business attribute information; For each process node, the current process node and the status of each node corresponding to the current process node are filled into a pre-configured data structure to obtain the filled data structure; The populated data structures are parsed to generate the target process node page; The step of determining the next process step to be displayed based on the current process step and the response data corresponding to the current process step, and then using it as the next process step to be displayed, includes: When the response data corresponding to the current process step is received, the next process step corresponding to the current process step is determined; Based on the process node and node status corresponding to the next process step, as well as the preset page configuration data, a details page to be displayed is generated and used as the details page to be displayed for the current process step.

2. The method according to claim 1, characterized in that, When a data acquisition request is received, determining the business attribute information in the data acquisition request includes: Receive data retrieval requests generated based on user-triggered actions; The data acquisition request is parsed to obtain the business attribute information in the data acquisition request.

3. The method according to claim 1, characterized in that, The determined process step sequence includes: Based on each process node and its corresponding state, at least one process step is obtained; Arrange the steps of each process to obtain a process step sequence.

4. The method according to claim 1, characterized in that, The step of generating a details page to be displayed based on the process node and node status corresponding to the next process step, and preset page configuration data, includes: The process node and node status corresponding to the next process step are filled into the preset page configuration data to generate the details page to be displayed.

5. A page generation device, characterized in that, include: The business attribute information determination module is used to determine the business attribute information in the data acquisition request when a data acquisition request is received. The target process node page generation module is used to generate a target process node page based on the business configuration items corresponding to the business attribute information and the pre-configured data structure, and to determine the process step sequence; wherein the process step sequence includes at least one process step; wherein the business configuration items are the configuration information required to configure the process page; The module for determining the details page to be displayed is used to determine the details page to be displayed corresponding to the next process step of the current process step based on the current process step and the response data corresponding to the data acquisition request, and to re-designate it as the details page to be displayed corresponding to the current process step. The module for determining the details page to be displayed further includes a replacement unit for the details page to be displayed. The detail page replacement unit is used to replace the displayed detail page based on the detail page to be displayed, so as to obtain the updated detail page to be displayed; The target business process page determination module is used to determine the target business process page based on the target process node page and the updated details page to be displayed; The target process node page generation module includes a business configuration item determination unit, a data structure acquisition unit, and a target process node page generation unit. The business configuration item determination unit is used to determine at least one process node and at least one node status in each business configuration item corresponding to the business attribute information. The data structure acquisition unit is used to fill the current process node and the state of each node corresponding to the current process node into a pre-configured data structure for each process node, so as to obtain the filled data structure. The target process node page generation unit is used to parse the filled data structures and generate the target process node page. The module for determining the details page to be displayed includes a next process step determination unit and a details page update unit. The next process step determination unit is used to determine the next process step corresponding to the current process step when it receives the response data corresponding to the current process step. The page to be displayed update unit is used to generate a page to be displayed based on the process node and node status corresponding to the next process step and the preset page configuration data, and then use it as the page to be displayed for the current process step.

6. An electronic device, characterized in that, The device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the page generation method as described in any one of claims 1-4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the page generation method as described in any one of claims 1-4.

Images