Page generation method and device, electronic equipment and storage medium

Abstract

Embodiments of the present disclosure provide a page generation method and device, electronic equipment and storage medium. The method comprises: displaying a plurality of first task configuration items pre-associated with a first task object, the first task configuration items being generated according to a task index in a first task index set associated with the first task object, the task index being metadata configured to describe an attribute field of the task object, and the task configuration item being used for view generation; in response to a screening operation on a second task configuration item in the plurality of first task configuration items, displaying the second task configuration item required by the first task object; and displaying a task page of the first task object according to the second task configuration item required by the first task object. The present application can achieve the customization and differentiated building requirements of the task page through the configuration mode.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a page generation method, apparatus, electronic device, and storage medium. Background Technology

[0002] In real-world task scenarios, the pre-execution review process is a crucial step. Given the diversity of task entities, task scenarios, and the unique characteristics of different task scenarios, the need for customization of the review page within the review process is increasingly strong. There is a desire to flexibly adjust the review page based on the specific concerns of different task scenarios. However, the current development model for review pages heavily relies on customized front-end and back-end development. This model has significant drawbacks; even minor changes require collaborative adjustments from both front-end and back-end personnel, consuming substantial manpower and time, lengthening the development cycle, and severely slowing down task progress. More importantly, it struggles to meet the differentiated review needs arising from diverse tasks and cannot quickly respond to flexible pre-execution review requirements, greatly limiting task execution. Summary of the Invention

[0003] This disclosure provides a page generation method, apparatus, electronic device, and storage medium to enable the rapid completion of customized and differentiated task pages through configurable methods.

[0004] In a first aspect, embodiments of this disclosure provide a page generation method, the method comprising:

[0005] The first task configuration item is pre-associated with a first task object. The first task configuration item is generated by configuring task indicators in the first task indicator set associated with the first task object. The task indicator is metadata configured to describe an attribute field of the task object. The task configuration item is used for view generation.

[0006] In response to a filtering operation on the second task configuration item among the plurality of first task configuration items, the second task configuration item required by the first task object is displayed;

[0007] Based on the second task configuration items required by the first task object, display the task page of the first task object.

[0008] Secondly, embodiments of this disclosure also provide a page generation apparatus, the apparatus comprising:

[0009] The first processing module is used to display multiple first task configuration items pre-associated with the first task object. The first task configuration items are generated by configuring task indicators in the first task indicator set associated with the first task object. The task indicator is metadata configured to describe an attribute field of the task object. The task configuration items are used to generate a view.

[0010] The second processing module is used to respond to the filtering operation of the second task configuration item among the plurality of first task configuration items and display the second task configuration item required by the first task object.

[0011] The third processing module is used to display the task page of the first task object according to the second task configuration items required by the first task object.

[0012] Thirdly, this disclosure also provides an electronic device, the electronic device comprising:

[0013] At least one processor; and

[0014] A memory communicatively connected to the at least one processor; wherein,

[0015] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the page generation method described in any of the above embodiments.

[0016] Fourthly, this disclosure also provides a computer-readable medium storing computer instructions that, when executed by a processor, implement the page generation method described in any of the above embodiments.

[0017] In the technical solution of this disclosure embodiment, task indicators are metadata describing the attribute fields of task objects. The first task configuration item is generated by configuring task indicators in the first task indicator set associated with the first task object. This means that task configuration items can be flexibly customized based on task indicators used to describe the attribute fields of task objects. Multiple task configuration items can be configured through this metadata. The metadata-based configuration method makes the construction of task pages no longer limited to a fixed pattern, but can be flexibly customized according to the attribute characteristics of different tasks to meet diverse needs. At the same time, the content presentation of task pages can be flexibly configured through filtering operations, realizing the personalized construction of task pages, improving the efficiency and targeting of task management. Thus, by configuring different task indicators, different task configuration items are generated. After filtering the task configuration items, differentiated task pages that meet the characteristics and needs of each task are obtained, realizing the customization and differentiated construction of task pages through configuration. Furthermore, when task requirements change or new task types are introduced, the configuration method only requires corresponding adjustments and configurations to the task indicators and task configuration items, without large-scale modifications to the entire page architecture. This greatly improves the adaptability and scalability of the system when building task pages, and reduces the system maintenance cost and development cycle.

[0018] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0019] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0020] Figure 1 This is a schematic flowchart of a page generation method provided in an embodiment of this disclosure;

[0021] Figure 2 This is a design diagram of metadata involved in the page generation process provided in an embodiment of this disclosure;

[0022] Figure 3 This is a schematic diagram of a task configuration item filtering page involved in the page generation process provided in an embodiment of this disclosure;

[0023] Figure 4 This is a schematic diagram of a task view editing page involved in the page generation process provided in an embodiment of this disclosure;

[0024] Figure 5 This is a flowchart of an access process involving view environment isolation during page generation, provided by an embodiment of this disclosure.

[0025] Figure 6 This is a schematic diagram of the structure of a page generation device provided in an embodiment of this disclosure;

[0026] Figure 7 This is a schematic diagram of the structure of an electronic device that implements a page generation method according to an embodiment of this disclosure. Detailed Implementation

[0027] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0028] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0029] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0030] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0031] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0032] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0033] Figure 1This is a flowchart illustrating a page generation method provided in an embodiment of the present disclosure. This embodiment is applicable to situations where task configuration items are processed in a configurable manner based on a task object, and a task page suitable for the task object is constructed accordingly. The page generation method can be executed by a page generation device, which can be implemented in software and / or hardware, and is generally integrated on any electronic device with network communication capabilities, such as a mobile terminal, a PC, or a server.

[0034] like Figure 1 As shown, the page generation method of this disclosure embodiment may include the following process:

[0035] S110. Display multiple first task configuration items pre-associated with the first task object. The first task configuration items are generated by configuring task indicators in the first task indicator set associated with the first task object. The task indicator is metadata configured as an attribute field of the task object. The task configuration items are used to generate the view.

[0036] Considering the diversity of task pages—for example, a task page might be an audit page used to perform audit tasks—different task pages may be similar, but their task configuration items differ. Therefore, the task configuration items used to construct task pages are abstracted into attribute fields, leading to the concept of task metrics. However, individual task metrics are finite, so the concept of a task metric set to which a task metric belongs is also introduced. A task metric set can be similar to a product attribute set or a merchant attribute set. Different task objects have their own task metric set, which includes a selection of task metrics that share the same or similar commonalities. Thus, it can be seen that the difference between task pages of different task objects lies in the different attribute fields. Correspondingly, the difference between task pages of different task objects can be further considered as the difference in task metrics. Therefore, task metrics adapted to the task object can be used to configure and generate one or more task configuration items to construct the task page for that task object.

[0037] In this context, task metrics can be metadata configured as attribute fields to describe a task object. They can be key elements that quantify, qualitatively, or categorize the task object, such as item name, store experience score, store level, or registration record ID. Task metrics can be the smallest unit for updating and retrieving a task object, such as the price comparison information field `price_cmp_result`. A task metric set can be represented as a collection of task metrics that converge through one or more commonalities, such as an item attribute set, a store attribute set (which can be retrieved using item ID and store ID respectively), or an item registration record set (retrieved using registration record ID). In practical business scenarios, this represents a set of related task metrics. The task metric set has a one-to-many relationship with the task metric combination, thus the first task metric set contains metadata describing the various attribute fields of the first task object.

[0038] See Figure 2 Different task objects are pre-associated with different sets of task metrics, and each set of task metrics is associated with a unique task metric set identifier. There is a one-to-many relationship between task metrics and task metric sets; a task metric set is equivalent to a selected group of task metrics that share common characteristics. Task configuration items are used to generate views. These configuration items are generated based on the configuration of one or more task metrics. One or more task configuration items can be used to generate a view, which can then be used to render the corresponding task page.

[0039] In an optional example, before displaying multiple pre-associated first task configuration items for the first task object, in response to configuration operations on task metrics in the set of first task metrics associated with the first task object, multiple pre-associated first task configuration items for the first task object are generated and displayed. The configuration operations on task metrics in the set of first task metrics associated with the first task object can include setting the values ​​of task metrics and the combination methods between task metrics. By configuring task metrics, several task metrics can be combined to form a first task configuration item. The first task configuration item can describe the specific parameters for page generation of the first task object in a specific task object scenario.

[0040] Each pre-associated first task configuration item for the first task object can contain various task indicator information related to the first task object. The task indicators involved in the first task configuration items determine the content to be displayed in the view. When generating the view, the indicator values ​​of each task indicator in the first task configuration items are obtained from the corresponding data source to generate the view. The first task configuration items can also indicate the layout design of the view; for example, the first task configuration items can determine the position and arrangement of different data elements on the page.

[0041] S120. In response to a filtering operation on the second task configuration item among multiple first task configuration items, display the second task configuration item required by the first task object.

[0042] See Figure 3 When faced with numerous first task configuration items related to the first task object, in order to obtain specific task configuration items for specific filtering more efficiently, the filtering operation events of multiple first task configuration items pre-associated with the first task object are detected in real time, and in response to the filtering operation of one or more second task configuration items among the multiple first task configuration items, one or more second task configuration items selected by the filtering operation can be displayed on the task configuration item filtering page, presenting the filtered second task configuration items in a clear and intuitive way.

[0043] See Figure 3 Optionally, the filtering operation for one or more second task configuration items among multiple first task configuration items can be initiated in at least one of the following ways: filtering by entering keywords in the filter input box, where the keywords can match the name, description, and applicable scenario information of the second task configuration item; and filtering by clicking the filter drop-down menu, selecting from the drop-down menu items such as configuration item type (e.g., time-related configuration, permission-related configuration, etc.) and configuration item status (enabled or disabled). Optionally, after completing the filtering operation settings and triggering a confirmation action (e.g., clicking the "Filter" button), the filtering logic begins to execute, traversing all first task configuration items and checking each first task configuration item one by one whether it meets the set filtering conditions, thereby filtering out the second task configuration items.

[0044] See Figure 3 Optionally, displaying one or more selected second task configuration items on the task configuration item filtering page can be achieved in at least one of the following ways: It can be displayed in a list format, with each second task configuration item occupying one row, detailing key information such as the name, specific configuration value, and brief description of the second task configuration item; or it can be displayed in a card layout, with each second task configuration item displayed as an independent card, making it easy to view and distinguish different second task configuration items. Through these methods, specific configuration information of the second task object related to the requirement can be quickly obtained, greatly improving the efficiency of finding and using task configuration information.

[0045] As an optional but not limited implementation, see [link to relevant documentation]. Figure 3 and Figure 4 This displays multiple first task configuration items pre-associated with the first task object, including but not limited to the following steps A1-A3:

[0046] Step A1: Display at least one second task object on the task view editing page. The second task object is the operation object when performing task processing by executing a preset task.

[0047] Step A2: In response to a selection operation on a first task object in at least one second task object, display at least one type of task configuration item editing control associated with the first task object on the task view editing page.

[0048] Step A3: In response to the trigger operation of the task configuration item editing control associated with the first task object, display multiple first task configuration items pre-associated with the first task object.

[0049] The first task object can refer to the task object that needs to be considered when building the page in the current task scenario. The first task object will be pre-associated with multiple first task configuration items. For example, the first task object is the operation object that needs to be reviewed and decided when building the review page in the current task scenario. The second task object can be the operation object when performing task processing in the execution of preset tasks, and at least one of them will be displayed on the preset task view editing page. At least one second task object contains the first task object.

[0050] See Figure 4 The task view editing page can be used to edit the task view. The task view editing page supports editing and displaying task objects and configuration information related to task page construction. The task view editing page presents at least one second task object when executing a preset task. These second task objects constitute a selectable task set so as to filter the first task object of interest.

[0051] Optionally, displaying at least one second task object on the task view editing page may include: displaying at least one second task object on the task view editing page in response to a triggering operation on a drop-down option for the task object type on the task view editing page. Prior to displaying at least one second task object on the task view editing page, the method may further include: rendering and displaying the task view editing page in response to a triggering operation on a view editing control, the task view editing page being used to edit at least one of the following information: view name, task object type, and task configuration items associated with the task object.

[0052] See Figure 4When a first task object is selected from several second task objects displayed on the task view editing page, at least one type of task configuration item editing control associated with the first task object will be displayed on the task view editing page. This at least one type of task configuration item editing control provides an entry point for editing the pre-associated task configuration items of the first task object. For example, taking item A as the first task object, selecting item A will display at least one type of task configuration item pre-associated with item A on the task view editing page. Task configuration item editing controls are interactive elements used to edit task configuration items, such as buttons, drop-down menus, and text boxes. Task configuration item editing controls can be triggered to view, modify, or set task configuration items.

[0053] See Figure 3 and Figure 4 For each type of task configuration item editing control associated with the first task object, when a trigger operation is performed on the task configuration item editing control displayed on the task view editing page, multiple pre-associated first task configuration items of the first task object will be further displayed. The multiple pre-associated first task configuration items displayed on the task configuration item filtering page can indicate detailed settings related to the preset task to be performed by the first task object, and support corresponding modifications. The trigger operation for the task configuration item editing control associated with the first task object can be an interactive action on the task configuration item editing control, such as clicking a button, selecting a drop-down menu option, or entering text. These operations will trigger corresponding responses, displaying or modifying the relevant task configuration items.

[0054] By centrally displaying task objects and related configuration item editing controls on the task view editing page, users can easily find and manipulate the task objects and their configuration items of interest, eliminating the need to search through multiple pages or complex menus. This significantly improves the efficiency and convenience of task configuration, allowing users to view and modify task object configuration items according to task requirements, making task management more flexible and adaptable to different business scenarios and needs. Furthermore, the step-by-step guided operation—first selecting the task object, then displaying the related task configuration item editing controls, and finally displaying the specific task configuration items—effectively reduces operational difficulty and minimizes the occurrence of operational errors.

[0055] As an optional but not limited implementation, see [link to relevant documentation]. Figure 4 When the task configuration item editing control associated with the first task object is displayed on the task view editing page, the task configuration item prompt information associated with the task configuration item editing control associated with the first task object is displayed on the task view editing page. The task configuration item prompt information is used to indicate the number of first task configuration items pre-associated with the first task object.

[0056] See Figure 4 The task view editing page is the interface for editing task-related views. It supports the display and modification of various attributes and configurations related to the task view. Upon entering the task view editing page and selecting the first task object, the task configuration item editing controls associated with that first task object will be displayed. These controls are interactive elements for editing task configuration items. Along with displaying the task configuration item editing controls associated with the first task object, a prompt message for the associated task configuration items will also be displayed. This prompt message indicates the number of pre-associated task configuration items for the first task object. For example, if the first task object has 52 pre-associated task configuration items, the prompt message will be displayed as the number "52" or "52 items associated" on the task view editing page, visually indicating the complexity of the task configuration or the number of task configuration items requiring attention.

[0057] By using the above method and providing task configuration item prompts, one can gain a preliminary understanding of the overall task configuration before starting to edit the task configuration items. This helps to plan the editing operation more efficiently, understand the number of task configuration items that need to be processed, avoid missing some important task configuration items, and improve the accuracy and completeness of task editing.

[0058] S130. Based on the second task configuration items required by the first task object, display the task page of the first task object.

[0059] See Figure 3 and Figure 4The system parses the second task configuration items required by the first task object, and determines the content and layout to be displayed on the task page of the first task object based on the parsing results. For example, regarding the content, if the second task configuration item contains information about the test scope, the task page of the first task object may display an area listing the test scope; if there is a list of participants in the test, this information may be displayed in the form of a list or table. Regarding the layout, the task page of the first task object will be displayed according to the positions of the content areas corresponding to the second task configuration items. For example, basic task information (such as task name, task leader, etc.) will be placed at the top of the page, detailed information such as the test scope and schedule will be placed in the middle area, and operation buttons (such as start test, pause test, etc.) will be placed at the bottom or side of the page. Furthermore, based on the content and layout required to be displayed on the task page of the first task object, front-end technologies (such as HTML, CSS, JavaScript, etc.) can be used to generate and render the task page of the first task object.

[0060] As an optional but not limited implementation, at least one type of task configuration item editing control associated with the first task object is used to edit at least one of the following types of task configuration items: filter items and display items. Filter items are filter items provided on the task page of the first task object for filtering data. Different filter items correspond to different filter dimensions. Display items are display items provided on the task page of the first task object for displaying the filtering results of at least some of the filter items.

[0061] See Figure 3 and Figure 4 Task configuration item editing controls are interactive elements on the task view editing page, such as buttons, drop-down menus, and text boxes. These controls are used to edit the task configuration items within the task view. Having at least one type of task configuration item means there may be multiple different types of task configuration item editing controls, all associated with the first task object. These controls can be manipulated to modify the task's configuration. Taking at least one type of task configuration item as either filter items or display items as examples, a task view for the first task object can consist of a set of custom headers (which can be called a display item set) and a set of filter items. When configuring the task view for the first task object, one or more filter items are configured and placed into a filter item set, and the number of filter items pre-associated with the first task object is displayed. Simultaneously, one or more custom headers are configured and placed into a custom header set, and the number of custom headers pre-associated with the first task object is also displayed. For example, the task configuration item filtering page corresponding to a filter item might display an inspection status, allowing users to filter records based on specified conditions.

[0062] Optionally, see Figure 2 , Figure 3 and Figure 4 Filters can be conditions or attributes used to filter a two-dimensional row list of data. Each filter can correspond to one or more task indicators, used to select data rows from the list that meet the specific conditions of that task indicator. The relationship between filters and task indicators can be one-to-one or one-to-many. Custom headers (also known as display items) are titles defined above the list to identify the meaning of each column of data when displaying a two-dimensional row list. Task indicators are metadata used to describe data attributes or characteristics. A column represented by a custom header can be composed of data from multiple task indicators or reflect relevant information from multiple task indicators, thus forming a one-to-many relationship.

[0063] As an optional but not limited implementation, when the first task object is an operation object that needs to be reviewed and decided in the review task type, the task page of the first task object is the review page used to execute the review task.

[0064] Optionally, see Figure 3 When the first task object is the operation object that needs to be reviewed and decided upon during the construction of the review page in the current task scenario, and the task page of the first task object is the review page, the filter options can be specific items or fields provided on the review page for filtering data. These typically correspond to one or more attributes or columns in the dataset. For example, when reviewing order data, common filter options might include "order number," "order time," and "order amount." These filter options represent the dimensions from which order data can be filtered. Filter conditions are specific restrictions set to retrieve specific data from the fields corresponding to the filter options. They are further refinements and constraints on the filter options and typically consist of comparison operators (such as equal to, greater than, less than, and inclusive) and specific values.

[0065] Optionally, see Figure 3 When the first task object is an operation that requires review and decision-making during the construction of the review page in the current task scenario, and the task page of the first task object is a review page, the display items can be display items provided on the review page of the first task object to display the filtering results of at least some of the filter items. After data that meets the criteria has been filtered out, the display items determine how these filtering results are presented. The display item settings can more intuitively display the relevant information of the filtering results. For example, for filtered order data, the display item could be a table listing information such as order number, product name, and order amount; or it could be a chart, such as a bar chart showing a comparison of different order quantities.

[0066] Optionally, task metrics can be defined as metadata for the attribute fields of task objects in the review task. Each field can be assigned independent behavior. For example, in the product review scenario, the task object in the review task needs to refer to many attribute fields, such as product sales, merchant rating, inventory, review duration, review status, and inventory information. The source of different attribute fields, their timeliness, and their strong or weak dependencies can all be customized, making it highly configurable and flexible.

[0067] As an optional but not limited implementation, the task page of the first task object is displayed based on the second task configuration items required by the first task object, including but not limited to the following steps: generating task view data associated with the first task object based on several second task configuration items required by the first task object; rendering and displaying the task page of the first task object based on the task view data associated with the first task object.

[0068] Optionally, task view data associated with the first task object is generated based on several second task configuration items required by the first task object. This includes: reading and parsing the second task configuration items required by the first task object. The second task configuration items can be stored in a preset data format (such as JSON, XML, etc.), which contains various information about the construction of the task page, such as the task type, query conditions for related data, and view layout information. Then, based on the parsing results of the second task configuration items, data is queried in the corresponding database or data storage, and task view data associated with the first task object is generated based on the queried data and view layout information.

[0069] Optionally, the task page of the first task object is generated and displayed by rendering based on the task view data associated with the first task object, including: embedding the task view associated with the first task object into a specified task view area of ​​the page based on the task view data associated with the first task object, adding interactive functions to the task view in the task page to enable interactive operations with the task page, and displaying the complete task page of the first task object.

[0070] The task page comprises multiple areas, such as a task view area, an action button area, and a details area. For example, in an order approval task page, the task view area displays the generated order-related task view, the action button area may contain buttons such as "Approve" and "Reject," and the details area displays more detailed order information when an order record is clicked. When embedding the task view associated with the first task object into a designated task view area of ​​the page, the task view's code or data can be integrated with the task page's front-end code, thereby inserting the task view associated with the first task object into a specific location within the main component of the task page.

[0071] As an optional but not limited implementation, the task view data associated with the first task object is generated by combining several second task configuration items required by the first task object, including but not limited to the following steps:

[0072] The data acquisition logic associated with the task indicators of several second task configuration items required by the first task object is determined. The data acquisition logic associated with the task indicators is used to obtain the indicator values ​​of the task indicators from the data source. The indicator values ​​of the task indicators included in the second task configuration items are obtained by combining the data acquisition logic associated with the task indicators of several second task configuration items to obtain the task view data associated with the first task object.

[0073] The configuration items for the second task required by the first task object can include one or more task metrics. For example, each filter item can be configured using one task metric, and each display item can be configured using one or more task metrics. Each task metric is pre-associated with data acquisition logic. The data acquisition logic refers to the specific methods and rules for obtaining the corresponding metric value from the data source (such as a database, file system, or interface of other software systems). The data acquisition logic can query the corresponding metric value from the data source based on the unique identifier of the task metric (such as the task metric ID).

[0074] After determining the data acquisition logic for each task indicator, the indicator value for each task indicator is retrieved from the corresponding data source according to the logic. Then, the indicator values ​​of the task indicators contained in the second task configuration item are combined. This combination may follow a certain format or structure to form a complete dataset, which is the task view data associated with the first task object. For example, the values ​​of indicators such as "estimated working hours," "priority," and "responsible person" are combined into a single data record containing the specific values ​​of these indicators. This data record is part of the task view data and is used to display relevant information about the task in the task view. Based on this task view data, the task page for the first task object can be constructed.

[0075] By employing the above approach and clearly defining the data acquisition logic for each task metric, the system can accurately obtain metric values ​​from reliable data sources, ensuring the accuracy of the task view data. Furthermore, the required second task configuration items and their data acquisition logic can be flexibly determined based on different first task objects and business needs. This allows the system to adapt to various task scenarios and data sources, exhibiting strong customizability.

[0076] As an optional but not limited implementation, the page generation method of this disclosure embodiment may also include, but is not limited to, the following steps B1-B2:

[0077] Step B1: In response to a first trigger operation that edits the first task configuration item, at least one editing operation area of ​​the first task configuration item is displayed on the task configuration item editing page of the first task configuration item.

[0078] Step B2: In response to the first editing operation on the first task configuration item, record the first editing operation triggered in the task configuration item editing page of the first task configuration item and display the configuration result of the first task configuration item generated based on the first editing operation.

[0079] Upon detecting a first trigger operation that indicates editing of the first task configuration item, it means that the first task configuration item needs to be edited and updated again. The first trigger operation is identified as a request to edit the first task configuration item. For example, clicking the "Edit" button next to the first task configuration item is the first trigger operation. After detecting the first trigger operation, the corresponding program logic will be executed. The first task configuration item is edited. Edit Page The system displays at least one editing area for the first task configuration item. The task configuration item editing page for the first task configuration item is a loaded and displayed page for editing the first task configuration item. This page supports displaying at least one editing area based on the characteristics of the first task configuration item and the allowed editable content. Each editing area of ​​the first task configuration item is equipped with corresponding interactive controls, such as input areas for editing the first task configuration item or drop-down menus.

[0080] When an operation is performed in the editing area of ​​the task configuration item editing page for the first task configuration item, the first editing operation is recorded. This recording can be done by writing relevant operation records to a log file, including the operation time and specific operation content (e.g., changing the start time from XX to YY). Simultaneously, based on the first editing operation, a new configuration result for the first task configuration item is calculated and generated in real time. This new configuration result is then displayed on the task configuration item editing page for the first task configuration item.

[0081] The clear step-by-step guidance makes editing the first task configuration item easy. From triggering the edit operation to seeing the edit result, the entire process is intuitive and efficient. Modifying the task configuration item can be completed without complicated procedures, reducing the possibility of operational errors. Furthermore, the task configuration item can be edited and adjusted in a timely manner according to actual needs, making it more suitable for specific display requirements. At the same time, the real-time display of the configuration results generated based on the edit operation helps to promptly identify and correct errors during the editing process, ensuring the accuracy of the task configuration item.

[0082] As an optional but not limited implementation, the page generation method of this disclosure embodiment may also include, but is not limited to, the following steps C1-C2:

[0083] Step C1: In response to a second trigger operation that edits a first task indicator in the first task indicator set, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator.

[0084] Step C2: In response to the second editing operation in the editing operation area of ​​the first task indicator, record the second editing operation triggered in the task indicator configuration page of the first task indicator and display the configuration result of the first task indicator generated based on the second editing operation.

[0085] When an editing operation is performed on a specific first task indicator within the first set of task indicators, a second trigger operation is generated. This second trigger operation could be a specific interactive action such as clicking the edit button on the first task indicator or double-clicking it in the task indicator list. Once the second trigger operation is detected, a response is initiated, displaying the task indicator configuration page for the first task indicator on the page. This page presents at least one editing area for the first task indicator. This editing area allows for various editing operations on the first task indicator, such as areas for modifying the task indicator name, setting the task indicator identifier, adjusting the task indicator calculation method, etc. Each editing area corresponds to a different editing function, allowing for corresponding operations within these areas.

[0086] When a second editing operation is performed within the editing area of ​​the first task metric, such as entering a new task metric name in the name editing area or modifying the identifier in the identifier area, this second editing operation triggered on the task metric configuration page will be recorded. This means that the changes made will be saved for subsequent processing and display. Simultaneously, the configuration result of the first task metric generated based on the second editing operation will be displayed in real time. For example, if the user changes the name of the task metric, the new name will immediately appear on the configuration result page. This provides a clear visual representation of the effect of the editing operation, allowing for further adjustments as needed.

[0087] Optionally, when the second triggering operation is a triggering operation for editing the first task indicator in the first task indicator set in the first editing mode, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator, including but not limited to the following steps: at least one second editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator, and the at least one second editing operation area is used to edit at least one of the following information: the task indicator set to which the task indicator belongs, the indicator name of the task indicator, the identifier of the task indicator, and the data acquisition logic used to obtain the indicator value of the task indicator. The first editing mode is a mode used to edit the content of the attribute fields of the first task indicator itself.

[0088] Alternatively, when the second triggering operation is a triggering operation that edits the first task indicator in the first task indicator set in the first editing mode, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator, including but not limited to the following steps: at least one third editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator, and the at least one third editing operation area is used to edit at least one of the following information: whether to synchronize the indicator value of the first task indicator to a preset database, the first task indicator set to which the first task indicator belongs, the second task indicator set that has a reference relationship with the first task indicator, and the identifier of the first task indicator in the second task indicator set, wherein the second task indicator set is a task indicator set that contains the first task indicator in the first task indicator set, and the second editing mode is a mode used to edit the second task indicator set that has a reference relationship with the first task indicator.

[0089] Optionally, for the first task metric, a metric set + reference design is adopted. The first task metric has its own first task metric set and a second task metric set that references it. Each metric set has a unique identifier ID. All task metrics under the first task metric set are retrieved through the unique identifier ID. First task metrics included in the first task metric set can be retrieved in the second task metric set through reference relationships. As long as the first task metric is in the second task metric set, the unique identifier ID of the first task metric set can be obtained. The unique identifier ID of the first task metric set can then be used to retrieve all task metrics under the first task metric set. Finally, the metric value of the task metric is obtained according to the data retrieval logic of all task metrics under the first task metric set. Based on this design, a logically wide table can be formed, allowing N task metrics to be retrieved at the interface level without requiring a physical layer wide table, making it more lightweight and reducing integration costs.

[0090] Optionally, see Figure 2 A collection can be a purely logical collection without any underlying storage, such as a product attribute collection, which simply defines a set of task metrics. A collection can also correspond to underlying storage, such as a database table or an Elasticsearch (ES) index. Since investment promotion review involves filtering, it typically uses an ES index. Task metrics within an ES-indexed collection, if sourced from ES, can be configured as filtering options, while purely logical collections can only be retrieved through in-memory computation. An ES-indexed collection can be associated with one or more purely logical collections, reusing the logic for retrieving data from any metric.

[0091] Optionally, see Figure 5Whether metadata can be accessed securely depends on whether the expected metadata is effective. Views are frequently iterated with tasks, and iterations should not affect the online environment. Therefore, the metadata corresponding to task metrics, filter options, and custom headers all have swimlane ENV identifiers, which allows defining different metadata and behaviors for the online and test environments. For testing convenience, the swimlane ENV identifier can be substituted when accessing the view. The backend will then choose to render the view definition for the online environment or the view definition for the test environment based on this identifier. Views do not have ENV identifiers because a view is actually a shell, and its specific behavior is affected by the dependent task metrics. However, views will be distinguished as views for the online environment and views for the test environment.

[0092] Optionally, if the first task object is the operation object that needs to be reviewed and decided when the review page is built in the current task scenario, and the task page of the first task object is the review page, the review needs to be filtered in multiple dimensions. Therefore, the underlying storage of the review is based on ES, and general interface capabilities are an essential condition for achieving generalization.

[0093] In the technical solution of this disclosure embodiment, task indicators are metadata describing the attribute fields of task objects. The first task configuration item is generated by configuring task indicators in the first task indicator set associated with the first task object. This means that task configuration items can be flexibly customized based on task indicators used to describe the attribute fields of task objects. Multiple task configuration items can be configured through this metadata. The metadata-based configuration method makes the construction of task pages no longer limited to a fixed pattern, but can be flexibly customized according to the attribute characteristics of different tasks to meet diverse needs. At the same time, the content presentation of task pages can be flexibly configured through filtering operations, realizing the personalized construction of task pages, improving the efficiency and targeting of task management. Thus, by configuring different task indicators, different task configuration items are generated. After filtering the task configuration items, differentiated task pages that meet the characteristics and needs of each task are obtained, realizing the customization and differentiated construction of task pages through configuration. Furthermore, when task requirements change or new task types are introduced, the configuration method only requires corresponding adjustments and configurations to the task indicators and task configuration items, without large-scale modifications to the entire page architecture. This greatly improves the adaptability and scalability of the system when building task pages, and reduces the system maintenance cost and development cycle.

[0094] Figure 6This is a schematic diagram of a page generation device provided in an embodiment of the present disclosure. The embodiments of the present disclosure are applicable to the situation where task configuration items are processed in a configurable manner according to the task object and a task page suitable for the task object is constructed accordingly. The page generation device can be implemented in the form of software and / or hardware, and is generally integrated on any electronic device with network communication function, such as a mobile terminal, PC, or server.

[0095] like Figure 6 As shown, the page generation apparatus of this disclosure embodiment may include the following:

[0096] The first processing module is used to display multiple first task configuration items pre-associated with the first task object. The first task configuration items are generated by configuring task indicators in the first task indicator set associated with the first task object. The task indicator is metadata configured to describe an attribute field of the task object. The task configuration items are used to generate a view.

[0097] The second processing module is used to respond to the filtering operation of the second task configuration item among the plurality of first task configuration items and display the second task configuration item required by the first task object.

[0098] The third processing module is used to display the task page of the first task object according to the second task configuration items required by the first task object.

[0099] Based on the above embodiments, optionally, the step of displaying multiple first task configuration items pre-associated with the first task object includes:

[0100] At least one second task object is displayed on the task view editing page. The second task object is the operation object when processing tasks by executing preset tasks.

[0101] In response to a selection operation on a first task object in at least one second task object, at least one type of task configuration item editing control associated with the first task object is displayed on the task view editing page;

[0102] In response to a triggered operation on the task configuration item editing control associated with the first task object, multiple first task configuration items pre-associated with the first task object are displayed.

[0103] Optionally, based on the above embodiments, the device further includes:

[0104] When the task configuration item editing control associated with the first task object is displayed on the task view editing page, task configuration item prompt information associated with the task configuration item editing control associated with the first task object is displayed on the task view editing page. The task configuration item prompt information is used to indicate the number of first task configuration items pre-associated with the first task object.

[0105] Based on the above embodiments, optionally, at least one type of task configuration item editing control associated with the first task object is used to edit at least one of the following types of task configuration items: filter items and display items. The filter items are filter items provided on the task page of the first task object for filtering data. Different filter items correspond to different filter dimensions. The display items are display items provided on the task page of the first task object for displaying the filtering results of at least some of the filter items.

[0106] Based on the above embodiments, optionally, according to the second task configuration items required by the first task object, the task page of the first task object is displayed, including:

[0107] Generate task view data associated with the first task object based on several second task configuration items required by the first task object;

[0108] The task page of the first task object is generated and displayed by rendering based on the task view data associated with the first task object.

[0109] Based on the above embodiments, optionally, task view data associated with the first task object is generated by combining several second task configuration items required by the first task object, including:

[0110] The data acquisition logic associated with the task indicators of several second task configuration items required by the first task object is determined. The data acquisition logic associated with the task indicators is used to obtain the indicator values ​​of the task indicators from the data source.

[0111] The task view data associated with the first task object is obtained by combining the indicator values ​​of the task indicators included in several second task configuration items using data acquisition logic.

[0112] Optionally, based on the above embodiments, the device further includes:

[0113] In response to a first trigger operation that edits the first task configuration item, at least one editing operation area of ​​the first task configuration item is displayed on the task configuration item editing page of the first task configuration item;

[0114] In response to a first editing operation on the first task configuration item, the first editing operation triggered in the task configuration item editing page of the first task configuration item is recorded and the configuration result of the first task configuration item generated based on the first editing operation is displayed.

[0115] Based on the above embodiments, optionally, when the first task object is an operation object that needs to be reviewed and decided in the review task type, the task page of the first task object is a review page for performing the review task.

[0116] Optionally, based on the above embodiments, the device further includes:

[0117] In response to a second triggering operation that edits a first task indicator in the first task indicator set, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator.

[0118] In response to a second editing operation on the editing operation area of ​​the first task indicator, the second editing operation triggered in the task indicator configuration page of the first task indicator is recorded and the configuration result of the first task indicator generated based on the second editing operation is displayed.

[0119] Based on the above embodiments, optionally, when the second triggering operation is a triggering operation for editing a first task indicator in the first task indicator set in a first editing mode, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator, including:

[0120] On the task indicator configuration page of the first task indicator, at least one second editing operation area of ​​the first task indicator is displayed. The at least one second editing operation area is used to edit at least one of the following information: the task indicator set to which the task indicator belongs, the indicator name of the task indicator, the identifier of the task indicator, and the data acquisition logic used to obtain the indicator value of the task indicator.

[0121] Based on the above embodiments, optionally, when the second triggering operation is a triggering operation for editing a first task indicator in the first task indicator set in a first editing mode, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator, including:

[0122] On the task indicator configuration page of the first task indicator, at least one third editing operation area of ​​the first task indicator is displayed. The at least one third editing operation area is used to edit at least one of the following information: whether to synchronize the indicator value of the first task indicator to a preset database, the first task indicator set to which the first task indicator belongs, the second task indicator set that has a reference relationship with the first task indicator, and the identifier of the first task indicator in the second task indicator set. The second task indicator set is a task indicator set that contains the first task indicator in the first task indicator set.

[0123] In the technical solution of this disclosure embodiment, task indicators are metadata describing the attribute fields of task objects. The first task configuration item is generated by configuring task indicators in the first task indicator set associated with the first task object. This means that task configuration items can be flexibly customized based on task indicators used to describe the attribute fields of task objects. Multiple task configuration items can be configured through this metadata. The metadata-based configuration method makes the construction of task pages no longer limited to a fixed pattern, but can be flexibly customized according to the attribute characteristics of different tasks to meet diverse needs. At the same time, the content presentation of task pages can be flexibly configured through filtering operations, realizing the personalized construction of task pages, improving the efficiency and targeting of task management. Thus, by configuring different task indicators, different task configuration items are generated. After filtering the task configuration items, differentiated task pages that meet the characteristics and needs of each task are obtained, realizing the customization and differentiated construction of task pages through configuration. Furthermore, when task requirements change or new task types are introduced, the configuration method only requires corresponding adjustments and configurations to the task indicators and task configuration items, without large-scale modifications to the entire page architecture. This greatly improves the adaptability and scalability of the system when building task pages, and reduces the system maintenance cost and development cycle.

[0124] The page generation apparatus provided in this disclosure can execute the page generation method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects for executing the page generation method.

[0125] 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 this disclosure.

[0126] Figure 7 This is a schematic diagram of the structure of an electronic device implementing a page generation method according to an embodiment of this disclosure. Refer to the following... Figure 7It illustrates an electronic device suitable for implementing embodiments of the present disclosure (e.g., Figure 7 The diagram below shows the structure of the terminal device or server 1000. The terminal device in this embodiment may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and vehicle terminals (e.g., vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 7 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0127] like Figure 7 As shown, the electronic device 1000 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1008 into a random access memory (RAM) 1003. The RAM 1003 also stores various programs and data required for the operation of the electronic device 1000. The processing unit 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An edit / output (I / O) interface 1005 is also connected to the bus 1004.

[0128] Typically, the following devices can be connected to the I / O interface 1005: input devices 1006 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 1007 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1008 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows electronic device 1000 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7 An electronic device 1000 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0129] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the page generation method shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 1009, or installed from storage device 1008, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined above in the page generation method of embodiments of this disclosure.

[0130] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0131] The electronic device provided in this embodiment and the page generation method provided in the above embodiments belong to the same inventive concept. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0132] This disclosure provides a computer storage medium storing a computer program that, when executed by a processor, implements the page generation method provided in the above embodiments.

[0133] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. 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 of a computer-readable storage medium may include, but are not limited to: 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 disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0134] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0135] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0136] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: display a plurality of first task configuration items pre-associated with a first task object, wherein the first task configuration items are generated by configuring task indicators in a set of first task indicators associated with the first task object, wherein the task indicators are metadata configured to describe an attribute field of the task object, and the task configuration items are used for view generation; in response to a filtering operation on a second task configuration item among the plurality of first task configuration items, display a second task configuration item required by the first task object; and display a task page of the first task object based on the second task configuration item required by the first task object.

[0137] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as 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).

[0138] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0139] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0140] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0141] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, 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 devices, magnetic storage devices, or any suitable combination of the foregoing.

[0142] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0143] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0144] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A page generation method, characterized in that, The method includes: The first task configuration item is pre-associated with a first task object. The first task configuration item is generated by configuring task indicators in the first task indicator set associated with the first task object. The task indicator is metadata configured to describe an attribute field of the task object. The task configuration item is used to generate the view. In response to a filtering operation on the second task configuration item among the plurality of first task configuration items, the second task configuration item required by the first task object is displayed; Based on the second task configuration items required by the first task object, display the task page of the first task object.

2. The method according to claim 1, characterized in that, The display of multiple first task configuration items pre-associated with the first task object includes: At least one second task object is displayed on the task view editing page. The second task object is the operation object when processing tasks by executing preset tasks. In response to a selection operation on a first task object in at least one second task object, at least one type of task configuration item editing control associated with the first task object is displayed on the task view editing page; In response to a triggered operation on the task configuration item editing control associated with the first task object, multiple first task configuration items pre-associated with the first task object are displayed.

3. The method according to claim 2, characterized in that, The method further includes: When the task configuration item editing control associated with the first task object is displayed on the task view editing page, task configuration item prompt information associated with the task configuration item editing control associated with the first task object is displayed on the task view editing page. The task configuration item prompt information is used to indicate the number of first task configuration items pre-associated with the first task object.

4. The method according to claim 2, characterized in that, The task configuration item editing control associated with the first task object is used to edit at least one of the following types of task configuration items: filter items and display items. The filter items are filter items provided on the task page of the first task object for filtering data. Different filter items correspond to different filter dimensions. The display items are display items provided on the task page of the first task object for displaying the filtering results of at least some of the filter items.

5. The method according to claim 1, characterized in that, Based on the second task configuration items required by the first task object, display the task page of the first task object, including: Generate task view data associated with the first task object based on several second task configuration items required by the first task object; The task page of the first task object is generated and displayed by rendering based on the task view data associated with the first task object.

6. The method according to claim 5, characterized in that, Based on the combination of several second task configuration items required by the first task object, task view data associated with the first task object is generated, including: The data acquisition logic associated with the task indicators of several second task configuration items required by the first task object is determined. The data acquisition logic associated with the task indicators is used to obtain the indicator values ​​of the task indicators from the data source. The indicator values ​​of the task indicators included in several second task configuration items are obtained by using data acquisition logic associated with the task indicators of the second task configuration items and combined to obtain the task view data associated with the first task object.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: In response to a first trigger operation that edits the first task configuration item, at least one editing operation area of ​​the first task configuration item is displayed on the task configuration item editing page of the first task configuration item; In response to a first editing operation on the first task configuration item, the first editing operation triggered in the task configuration item editing page of the first task configuration item is recorded and the configuration result of the first task configuration item generated based on the first editing operation is displayed.

8. The method according to claim 2 or 5, characterized in that, When the first task object is an operation object that requires review and decision-making in the review task type, the task page of the first task object is the review page used to perform the review task.

9. The method according to claim 1, characterized in that, The method further includes: In response to a second triggering operation that edits a first task indicator in the first task indicator set, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator. In response to a second editing operation on the editing operation area of ​​the first task indicator, the second editing operation triggered in the task indicator configuration page of the first task indicator is recorded and the configuration result of the first task indicator generated based on the second editing operation is displayed.

10. The method according to claim 9, characterized in that, When the second triggering operation is a triggering operation for editing a first task indicator in the first task indicator set in the first editing mode, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator, including: On the task indicator configuration page of the first task indicator, at least one second editing operation area of ​​the first task indicator is displayed. The at least one second editing operation area is used to edit at least one of the following information: the task indicator set to which the task indicator belongs, the indicator name of the task indicator, the identifier of the task indicator, and the data acquisition logic used to obtain the indicator value of the task indicator.

11. The method according to claim 9, characterized in that, When the second triggering operation is a triggering operation for editing a first task indicator in the first task indicator set in the first editing mode, at least one editing operation area of ​​the first task indicator is displayed on the task indicator configuration page of the first task indicator, including: On the task indicator configuration page of the first task indicator, at least one third editing operation area of ​​the first task indicator is displayed. The at least one third editing operation area is used to edit at least one of the following information: whether to synchronize the indicator value of the first task indicator to a preset database, the first task indicator set to which the first task indicator belongs, the second task indicator set that has a reference relationship with the first task indicator, and the identifier of the first task indicator in the second task indicator set. The second task indicator set is a task indicator set that contains the first task indicator in the first task indicator set.

12. A page generation apparatus, characterized in that, The device includes: The first processing module is used to display multiple first task configuration items pre-associated with the first task object. The first task configuration items are generated by configuring task indicators in the first task indicator set associated with the first task object. The task indicator is metadata configured to describe an attribute field of the task object. The task configuration items are used to generate a view. The second processing module is used to respond to the filtering operation of the second task configuration item among the plurality of first task configuration items and display the second task configuration item required by the first task object. The third processing module is used to display the task page of the first task object according to the second task configuration items required by the first task object.

13. An electronic device, characterized in that, The electronic 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 according to any one of claims 1-11.

14. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the page generation method according to any one of claims 1-11.

Images