Demand information processing method and device, computer equipment and storage medium

Abstract

The invention relates to a demand information processing method and device, computer equipment and a storage medium. The method comprises the steps that a user login request is received, the user login request carries a user identifier, a target user role corresponding to the user identifier is recognized according to the user login request, a matched demand form is obtained according to the target user role, the demand form comprises demand information matched with the target user role, and user-defined operation is conducted on the demand form. And determining target demand information according to the custom operation, and rendering and displaying the target demand information. By adopting the method, the working efficiency of different types of user roles can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, apparatus, computer device and storage medium for processing demand information. Background Art

[0002] In an enterprise, R&D personnel, product operations personnel, and testers all have their own work requirements. These requirements must be manually created using spreadsheets, which then communicate their work requirements to other personnel. For example, R&D personnel A needs to send a work requirement form to R&D personnel B, who then uses the form to learn about their own work requirements. This approach is not only time-consuming, but also prevents different personnel from viewing only their own requirements and unrelated work requirements of the same type. Summary of the Invention

[0003] Based on this, it is necessary to provide a demand information processing method, apparatus, computer equipment and storage medium that can improve the work efficiency of different types of user roles in response to the above technical problems.

[0004] A method for processing demand information, the method comprising:

[0005] Receive a user login request, which carries a user ID;

[0006] Identify the target user role corresponding to the user ID according to the user login request;

[0007] Obtain a matching demand form based on the target user role, where the demand form includes demand information that matches the target user role;

[0008] Customize the demand form and determine the target demand information based on the customized operation;

[0009] Render and display the target demand information.

[0010] In one embodiment, identifying a target user role corresponding to a user identifier according to a user login request includes:

[0011] Obtain a candidate user role set corresponding to the user ID according to the user login request;

[0012] receiving a selection operation on a candidate user role set;

[0013] A target role is determined from a set of candidate user roles based on a selection operation.

[0014] In one embodiment, a matching requirement form is obtained according to the target user role, wherein the requirement form includes requirement information matching the target user role, including:

[0015] Obtain matching first demand information based on target user roles;

[0016] Acquire second demand information associated with the target user role, where the second demand information also includes demand information of other user roles;

[0017] Get the target key fields specific to the target user role;

[0018] A demand form is obtained according to the first demand information, the second demand information and the target key field.

[0019] In one embodiment, performing a custom operation on the demand form and determining target demand information according to the custom operation includes:

[0020] receiving a first operation on a page edit control of a requirement form;

[0021] Displaying a custom edit page corresponding to the requirement form according to the first operation, the custom edit page including at least one requirement form filter item;

[0022] receiving a second operation on each requirement form filter item in the custom edit page, determining a target requirement form filter item according to the second operation, and displaying the target requirement form filter item in the requirement form;

[0023] Receive input operations on target requirement form filter items, and obtain matching target requirement information based on the input operations.

[0024] In one embodiment, rendering and displaying target demand information includes:

[0025] Render the target demand information in a list and display it in the form of a target demand information table;

[0026] Performing a hiding operation on the column options of the target demand information table, and hiding the target column options in the target demand information table according to the hiding operation;

[0027] Perform a new operation on the column options of the target demand information table, add target column options to the target demand information table according to the new operation, and display the data corresponding to the target column options.

[0028] In one embodiment, rendering and displaying target demand information includes:

[0029] Create a visual area and obtain the area content of the visual area from the target demand information;

[0030] Render the regional content and display it in the visible area.

[0031] In one embodiment, the method further includes:

[0032] Create candidate requirement information corresponding to candidate user roles;

[0033] Create candidate key requirement fields corresponding to candidate user roles;

[0034] Configure associated requirement information corresponding to the associated user role for the candidate requirement information;

[0035] A candidate requirement form corresponding to the candidate user role is obtained according to the candidate requirement information, associated requirement information and candidate key requirement fields.

[0036] A demand information processing device, comprising:

[0037] A receiving module, configured to receive a user login request, wherein the user login request carries a user identifier;

[0038] An identification module is used to identify the target user role corresponding to the user ID according to the user login request;

[0039] An acquisition module is used to acquire a matching demand form according to the target user role, where the demand form includes demand information that matches the target user role;

[0040] The operation module is used to perform customized operations on the demand form and determine the target demand information based on the customized operations;

[0041] The rendering module is used to render and display the target demand information.

[0042] A computer device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are implemented:

[0043] Receive a user login request, which carries a user ID;

[0044] Identify the target user role corresponding to the user ID according to the user login request;

[0045] Obtain a matching demand form based on the target user role, where the demand form includes demand information that matches the target user role;

[0046] Customize the demand form and determine the target demand information based on the customized operation;

[0047] Render and display the target demand information.

[0048] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0049] Receive a user login request, which carries a user ID;

[0050] Identify the target user role corresponding to the user ID according to the user login request;

[0051] Obtain a matching demand form based on the target user role, where the demand form includes demand information that matches the target user role;

[0052] Customize the demand form and determine the target demand information based on the customized operation;

[0053] Render and display the target demand information.

[0054] The above-mentioned demand information processing method, device, computer equipment and storage medium receive a user login request, which carries a user identifier, identify the target user role corresponding to the user identifier based on the user login request, obtain a matching demand form based on the target user role, the demand form includes demand information matching the target user role, perform customized operations on the demand form, determine the target demand information based on the customized operations, render the target demand information, and display it.

[0055] Among them, the demand information of all user roles is concentrated on the same platform to avoid duplication and inconsistency of data between different systems. The unified platform makes communication between different user roles more direct, reducing communication costs. Different users with the same user role can share demand information to ensure that everyone pays attention to the progress of the demand in a timely manner. The entire process is automated, which improves the work efficiency between different types of user roles and the efficiency of processing demand forms. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 is an application environment diagram of a method for processing demand information in one embodiment;

[0057] Figure 2 1 is a flow chart of a method for processing demand information in one embodiment;

[0058] Figure 3 Schematic diagram of the process of identifying the target user role in one embodiment;

[0059] Figure 4 A flowchart of the steps for obtaining a demand form in one embodiment;

[0060] Figure 5 A flowchart of steps for customizing a demand form in one embodiment;

[0061] Figure 6-1 A flowchart of a target requirement information rendering step in one embodiment;

[0062] Figure 6-2 This is a schematic diagram showing a target demand information table in one embodiment;

[0063] Figure 7 A flowchart of a target requirement information rendering step in one embodiment;

[0064] Figure 8 1 is a flow chart of a method for processing demand information in one embodiment;

[0065] Figure 9 is a structural block diagram of a demand information processing device in one embodiment;

[0066] Figure 10 is a diagram of the internal structure of a computer device in one embodiment;

[0067] Figure 11 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0068] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0069] The demand information processing method provided in this application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 104 via a network. The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented as an independent server or a server cluster consisting of multiple servers.

[0070] Specifically, the terminal 102 obtains a user login request, which carries a user ID, and sends it to the server 104. The server 104 receives the user login request, identifies the target user role corresponding to the user ID according to the user login request, obtains a matching demand form according to the target user role, and the demand form includes demand information that matches the target user role. Custom operations are performed on the demand form, and the target demand information is determined according to the customized operations and returned to the terminal 102. The terminal 102 renders the target demand information and displays it.

[0071] In another embodiment, the terminal 102 receives a user login request, the user login carries a user ID, identifies the target user role corresponding to the user ID according to the user login request, obtains a matching demand form according to the target user role, the demand form includes demand information matching the target user role, performs a customized operation on the demand form, determines the target demand information according to the customized operation, renders the target demand information, and displays it.

[0072] In one embodiment, Figure 2 As shown, a method for processing demand information is provided, which is applied to Figure 1 The following steps are used as an example to illustrate the terminal or server in the example:

[0073] Step 202: Receive a user login request, which carries a user ID.

[0074] Among them, a user login request refers to the process in which a user submits identity credentials such as a user name and password to verify his identity and obtain access rights when accessing a website or application. The user login request carries a user ID.

[0075] Among them, the user ID is used to identify the user who triggers the generation of the user login request. Different users correspond to different user IDs. The user ID can be used to search for user-related data of the user login request, such as user behavior data, user information, user type, etc.

[0076] Specifically, a user may log in to the demand information processing system through a login interface. During the login process, a terminal or a server receives the user's login operation, triggering the generation of a user login request that carries a user identifier.

[0077] Step 204: Identify the target user role corresponding to the user identification according to the user login request.

[0078] Among them, the target user role is the role played and assumed by the user in the business, such as R&D personnel, product personnel, operations personnel or testers. Different user roles correspond to different work requirements, and they can also be related. The work requirements corresponding to the same user role may be the same or different, depending on the actual business needs, actual product needs or actual application scenarios.

[0079] Specifically, after receiving a user login request, user configuration information that matches the user identifier is searched according to the user login request. The user configuration information may include but is not limited to the configuration of the user role, the configuration of the requirement, the configuration of the user associated with the requirement, etc. The target user role corresponding to the user identifier can be determined through the configuration of the user role in the user configuration information.

[0080] Step 206: Obtain a matching requirement form according to the target user role, where the requirement form includes requirement information that matches the target user role.

[0081] The requirements form is a list of requirements related to the target user role. It includes not only requirements related to the user ID, but all requirements related to the target user role, including requirements for the same user role but with different user IDs. For example, if the target user role is a product person, the requirements form includes requirements for all product people, not just those related to a specific product person.

[0082] Specifically, after determining the target user role, all relevant requirement information is searched for within that role to create a requirements form. This form includes all relevant requirement information for the target user role. This requirement information includes the requirement name, priority, and iteration number, among other things. This information can be determined based on actual business needs, product requirements, or application scenarios.

[0083] Step 208: Customize the demand form and determine target demand information based on the customized operation.

[0084] Among them, custom operations can be actions such as setting, adjusting, editing, and selecting the requirement form of the target user role based on actual business needs, actual product needs, or actual application scenarios. The target requirement information can be determined from the requirement form through custom operations, and different custom operations correspond to different target requirement information.

[0085] For example, if the custom operation is a selection operation, the matching requirement information is selected from the requirement form according to the selection operation and determined as the target requirement information. If the custom operation is an editing operation, the requirement information edited in the requirement form is determined as the target requirement information according to the editing operation. If the custom operation is an adjustment operation, the requirement information adjusted in the requirement form is determined as the target requirement information according to the adjustment operation.

[0086] Step 210: Render and display the target demand information.

[0087] Specifically, after obtaining the target demand information, the target demand information is rendered into content that can be displayed on the front end. During rendering, consideration can be given to rendering only the demand information within the visible area. By utilizing virtualization technology, rather than rendering the entire target demand information, only the visible area of ​​the target demand information can be rendered, reducing the rendering burden.

[0088] Alternatively, key demand information in the target demand information may be rendered. These key demand information are relatively important and are rendered and displayed to the user, thus avoiding the rendering of unnecessary demand information.

[0089] In the above-mentioned demand information processing method, a user login request is received, the user login request carries a user ID, the target user role corresponding to the user ID is identified according to the user login request, a matching demand form is obtained according to the target user role, the demand form includes demand information matching the target user role, a customized operation is performed on the demand form, the target demand information is determined according to the customized operation, the target demand information is rendered, and then displayed.

[0090] Among them, the demand information of all user roles is concentrated on the same platform to avoid duplication and inconsistency of data between different systems. The unified platform makes communication between different user roles more direct, reducing communication costs. Different users with the same user role can share demand information to ensure that everyone pays attention to the progress of the demand in a timely manner. The entire process is automated, which improves the work efficiency between different types of user roles and the efficiency of processing demand forms.

[0091] In one embodiment, Figure 3 As shown, identifying the target user role corresponding to the user ID according to the user login request includes:

[0092] Step 302: Obtain a candidate user role set corresponding to the user identification according to the user login request.

[0093] Step 304: Receive a selection operation on a candidate user role set.

[0094] Step 306: Determine a target role from the candidate user role set according to the selection operation.

[0095] If a user plays multiple roles in the business at the same time, the target role needs to be determined based on the user's selection operation of the multiple roles.

[0096] Specifically, after receiving a user login request, all candidate user roles associated with the user ID are obtained according to the user login request to obtain a candidate user role set. That is, the candidate user role set includes all roles played by the user with the user ID in the business.

[0097] Furthermore, after receiving a user login request, all candidate user roles associated with the user identifier are searched based on the user login request to form a candidate user role set. The user can select a target role from the candidate user role set based on actual business needs, product requirements, or application scenarios. Specifically, this can include receiving a user selection operation from the candidate user role set and determining the target role from the candidate user role set based on the selection operation.

[0098] For example, the candidate user role set of the user identifier includes product personnel and R&D personnel. If a selection operation is performed on the user role of product personnel, it can be determined that the user role played by the user login request is product personnel based on the selection operation.

[0099] In one embodiment, Figure 4 As shown, a matching requirement form is obtained based on the target user role. The requirement form includes requirement information that matches the target user role, including:

[0100] Step 402: Acquire matching first requirement information according to the target user role.

[0101] Step 404: Acquire second demand information associated with the target user role, where the second demand information also includes demand information of other user roles.

[0102] Step 406: Obtain target key fields specific to the target user role.

[0103] Step 408: Obtain a requirement form based on the first requirement information, the second requirement information, and the target key field.

[0104] The requirements form includes requirements matching the target user role, including key fields specific to the target user role. This means that, in addition to requirements related to the target user role, the requirements form can also include requirements related to other user roles that are associated with the target user role. This means that if a requirement is divided among multiple user roles and is associated with multiple user roles, the target user role can be identified through key fields in the requirements of the associated user roles. However, this does not necessarily include all the requirements for the associated user role, but only a portion of them.

[0105] Specifically, exclusive demand information may be first obtained through the target user role as the first demand information. That is, the first demand information is exclusive to the target user role and has nothing to do with other user roles.

[0106] Furthermore, since the requirement list also includes requirement information of other user roles, but this requirement information is not specific to the user role, and some of the requirement information may belong to other user roles, these two user roles can be linked to achieve collaborative work between the two user roles. Specifically, the second requirement information associated with the target user role can be searched. The second requirement information is not specific to the target user role and may also include the requirement information of other user roles.

[0107] Among them, the target key fields here are key requirement fields exclusive to the target user role. Some fields are configured with matching user roles during configuration and are used to specifically remind the user role to pay attention.

[0108] Therefore, the target key fields that match the target user role can be determined through the relationship between the key fields and the user roles, and the requirement form of the target user role can be obtained based on the first requirement information exclusive to the target user role, the second requirement information of other user roles associated with the target user role, and the target key fields exclusive to the target user role.

[0109] In one embodiment, Figure 5 As shown, customize the demand form and determine the target demand information based on the customized operation, including:

[0110] Step 502: Receive a first operation on a page editing control of a requirement form.

[0111] Step 504: Display a custom edit page corresponding to the requirement form according to the first operation, where the custom edit page includes at least one requirement form filter item.

[0112] Step 506: receiving a second operation on each requirement form filter item in the custom edit page, determining a target requirement form filter item according to the second operation, and displaying the target requirement form filter item in the requirement form.

[0113] Step 508: receiving an input operation for a target requirement form filter item, and obtaining matching target requirement information according to the input operation.

[0114] Among them, custom operations can be actions such as setting, adjusting, editing, and selecting the requirement form of the target user role based on actual business needs, actual product needs, or actual application scenarios. The target requirement information can be determined from the requirement form through custom operations, and different custom operations correspond to different target requirement information.

[0115] Among them, a page editing control is set on the page of the requirement form. By operating the page editing control, the requirement form can be modified or adjusted. Therefore, the first operation here is the operation of the page editing control of the requirement form. The operation can be a click operation, a voice operation, or a timed event trigger operation.

[0116] Specifically, a custom edit page corresponding to the requirement form is obtained according to the first operation and displayed, and at least one requirement form filter item is provided in the custom edit page for controlling items of the requirement form.

[0117] Furthermore, after the custom edit page for the requirement form is displayed, you can perform an operation on the form filter items in the custom edit page, which is a second operation. This second operation is understood as an operation on the form filter items in the custom edit page. Based on the second operation, the target requirement form filter items are determined from the various requirement form filter items and displayed on the requirement form.

[0118] Finally, enter the target requirement form filter item in the requirement form. You can enter the specific condition information to be filtered. The specific information can be determined based on actual business needs, actual product needs, or actual application scenarios. In this way, you can find matching target requirement information based on the entered filter condition information.

[0119] For example, on the requirement form page, the default number of form filter items is 8, of which the default filter items can be controlled according to JSONSchema. Click the Add Condition button and select the filter items you want to add to customize the display of the filter items. You can also check the two form options, Cancellation Reason and Customer Name. After clicking OK, you can see two new corresponding filter items in the form filter items. Enter the filter conditions for these two new filter items to find the matching target requirement information.

[0120] In one embodiment, Figure 6-1 As shown, the target demand information is rendered and displayed, including:

[0121] Step 602 : Render the target demand information in a list and display it in the form of a target demand information table.

[0122] Step 604 : performing a hiding operation on the column options of the target demand information table, and hiding the target column options in the target demand information table according to the hiding operation.

[0123] Step 606 , performing a new adding operation on the column options of the target demand information table, adding target column options to the target demand information table according to the new adding operation, and displaying data corresponding to the target column options.

[0124] The target demand information can be rendered in a table format to obtain a target demand information table and displayed. However, the user can hide the displayed target demand information table, or hide irrelevant or unnecessary target column options in the target demand information table. Specifically, after displaying the target demand information table, the target column options in the target demand information table can be hidden. The specific target column options can be determined based on actual business needs, actual product needs, or actual application scenarios.

[0125] Then, in addition to hiding the column options of the target demand information table, you can also add target column options. Specifically, you can add new operations to the column options of the target demand information table, add new target column options, and display the data corresponding to the target column options in the target demand information table.

[0126] For example, Figure 6-2 As shown, Figure 6-2 The following is a diagram showing the display of a target demand information table in an embodiment. The default configuration of the table column options can also be controlled in JSON Schema. In the table header of the operation column options, click the header to see all the column options that can be added or deleted. All configurable column option information is also configured in JSON Schema. Click the column option you want to display, and the table will add this column. Similarly, uncheck the selected column option to hide the corresponding column item. Figure 6-2 As shown in the figure, by checking the last modified person and last modified time, you can add corresponding column options to the table.

[0127] In one embodiment, Figure 7 As shown, the target demand information is rendered and displayed, including:

[0128] Step 702: Create a visible area and obtain the area content of the visible area from the target demand information.

[0129] Step 704: Render the region content and display the region content in the visible area.

[0130] The state management of each form field is delegated to the corresponding FormItem component, rather than being managed centrally in the top-level Form component. This way, only changes to a specific field trigger a re-render of that field, or only partial content is displayed, rather than the entire form being re-rendered. This local state management is achieved through React's useState and useReducer.

[0131] Among them, virtualization technology: using the react-window library can render only the list items within the visible area, rather than the entire list. This is particularly useful for long lists containing a large number of form items because it reduces the number of DOM nodes, thereby reducing the rendering burden.

[0132] Avoid unnecessary component re-rendering: Use React.memo higher-order components, which re-render only when the component's props change. For function components, you can use React.memo to avoid unnecessary rendering.

[0133] Code splitting: Use React.lazy and Suspense for lazy loading. For large forms, you can split the code of infrequently used form parts and use React.lazy to dynamically load them, which can reduce the first screen loading time.

[0134] Among them, the regional content is part of the demand information in the target demand information used to display in the visual area. Specifically, a visual area is created, and the regional content that can be displayed in the visual area is obtained from the target demand information. Finally, the regional content is rendered and displayed in the visual area.

[0135] In one embodiment, Figure 8 As shown, the above method also includes:

[0136] Step 802: Create candidate requirement information corresponding to the candidate user role.

[0137] Step 804: Create candidate key requirement fields corresponding to the candidate user roles.

[0138] Step 806: configuring associated requirement information corresponding to the associated user role for the candidate requirement information.

[0139] Step 808 : Obtain a candidate requirement form corresponding to the candidate user role according to the candidate requirement information, the associated requirement information, and the candidate key requirement fields.

[0140] It is necessary to establish a relationship between the user role and the demand information, so that the demand information set matching the user role can be found according to the relationship to obtain the demand form.

[0141] Specifically, a candidate user role is created, and candidate requirement information and candidate key requirement fields configured for the candidate user role are obtained. If the candidate requirement information needs to be associated with the associated requirement information of other user roles, the candidate requirement information is bound to the associated requirement information of the associated user role. Finally, a candidate requirement form corresponding to the candidate user role is obtained based on the candidate requirement information, associated requirement information, and candidate key requirement fields, and the candidate user role is associated with the candidate requirement form.

[0142] It should be understood that, although the various steps in the above flow chart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the above flow chart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these sub-steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0143] In one embodiment, Figure 9 As shown, a demand information processing device 900 is provided, comprising: a receiving module 902, an identification module 904, an acquisition module 906, an operation module 908 and a rendering module 910, wherein:

[0144] Receiving module 902, configured to receive a user login request, the user login request carrying a user identifier;

[0145] The identification module 904 is configured to identify the target user role corresponding to the user identification according to the user login request.

[0146] The acquisition module 906 is configured to acquire a matching requirement form according to the target user role, where the requirement form includes requirement information matching the target user role.

[0147] The operation module 908 is used to perform a customized operation on the demand form and determine target demand information according to the customized operation.

[0148] The rendering module 910 is used to render and display the target demand information.

[0149] In one embodiment, the identification module 904 obtains a candidate user role set corresponding to the user identification according to a user login request, receives a selection operation on the candidate user role set, and determines a target role from the candidate user role set according to the selection operation.

[0150] In one embodiment, the acquisition module 906 obtains the matching first requirement information based on the target user role, obtains the second requirement information associated with the target user role, the second requirement information also includes the requirement information of other user roles, obtains the target key field exclusive to the target user role, and obtains the requirement form based on the first requirement information, the second requirement information and the target key field.

[0151] In one embodiment, the operation module 908 receives a first operation on the page editing control of the requirement form, displays the custom editing page corresponding to the requirement form according to the first operation, the custom editing page includes at least one requirement form filter item, receives a second operation on each requirement form filter item in the custom editing page, determines the target requirement form filter item according to the second operation, and displays it in the requirement form, receives an input operation on the target requirement form filter item, and obtains matching target requirement information according to the input operation.

[0152] In one embodiment, the rendering module 910 renders the target demand information in a list, displays it in the form of a target demand information table, hides the column options of the target demand information table, hides the target column options in the target demand information table according to the hiding operation, adds the column options of the target demand information table, adds the target column options to the target demand information table according to the adding operation, and displays the data corresponding to the target column options.

[0153] In one embodiment, the rendering module 910 creates a visible area, obtains the area content of the visible area from the target demand information, renders the area content, and displays the area content in the visible area.

[0154] In one embodiment, the demand information processing device 900 creates candidate demand information corresponding to the candidate user role, creates candidate key demand fields corresponding to the candidate user role, configures associated demand information corresponding to the associated user role for the candidate demand information, and obtains a candidate demand form corresponding to the candidate user role based on the candidate demand information, the associated demand information and the candidate key demand fields.

[0155] The specific definition of the demand information processing device can be found in the definition of the demand information processing method above and will not be repeated here. Each module in the demand information processing device described above may be implemented in whole or in part through software, hardware, or a combination thereof. Each of the modules described above may be embedded in or independent of a processor in a computer device in hardware form, or may be stored in a memory in a computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0156] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 10As shown. The computer device includes a processor, memory, network interface, and database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store demand information. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a demand information processing method is implemented.

[0157] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 11 As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a method for processing demand information is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a key, trackball or touchpad provided on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0158] Those skilled in the art will understand that Figure 10 or Figure 11 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0159] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented: receiving a user login request, the user login request carrying a user identifier, identifying a target user role corresponding to the user identifier based on the user login request, obtaining a matching demand form based on the target user role, the demand form including demand information matching the target user role, performing a custom operation on the demand form, determining target demand information based on the custom operation, rendering the target demand information, and displaying it.

[0160] In one embodiment, when the processor executes the computer program, the processor further implements the following steps: obtaining a candidate user role set corresponding to the user identifier according to a user login request, receiving a selection operation on the candidate user role set, and determining a target role from the candidate user role set according to the selection operation.

[0161] In one embodiment, when the processor executes the computer program, it also implements the following steps: obtaining matching first requirement information based on the target user role, obtaining second requirement information associated with the target user role, the second requirement information also including requirement information of other user roles, obtaining a target key field exclusive to the target user role, and obtaining a requirement form based on the first requirement information, the second requirement information, and the target key field.

[0162] In one embodiment, when the processor executes the computer program, it also implements the following steps: receiving a first operation on the page editing control of the requirement form, displaying the custom editing page corresponding to the requirement form according to the first operation, the custom editing page including at least one requirement form filter item, receiving a second operation on each requirement form filter item in the custom editing page, determining the target requirement form filter item according to the second operation, and displaying it in the requirement form, receiving an input operation on the target requirement form filter item, and obtaining matching target requirement information according to the input operation.

[0163] In one embodiment, when the processor executes the computer program, it also implements the following steps: rendering the target demand information in a list, displaying it in the form of a target demand information table, hiding the column options of the target demand information table, hiding the target column options in the target demand information table according to the hiding operation, adding the column options of the target demand information table, adding the target column options to the target demand information table according to the adding operation, and displaying the data corresponding to the target column options.

[0164] In one embodiment, when executing the computer program, the processor further implements the following steps: creating a visible area, obtaining area content of the visible area from the target demand information, rendering the area content, and displaying the area content in the visible area.

[0165] In one embodiment, when the processor executes the computer program, it also implements the following steps: creating candidate requirement information corresponding to the candidate user role, creating candidate key requirement fields corresponding to the candidate user role, configuring associated requirement information corresponding to the associated user role for the candidate requirement information, and obtaining a candidate requirement form corresponding to the candidate user role based on the candidate requirement information, the associated requirement information and the candidate key requirement fields.

[0166] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: receiving a user login request, the user login request carrying a user identifier, identifying a target user role corresponding to the user identifier based on the user login request, obtaining a matching demand form based on the target user role, the demand form including demand information matching the target user role, performing a custom operation on the demand form, determining the target demand information based on the custom operation, rendering the target demand information, and displaying it.

[0167] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: obtaining a candidate user role set corresponding to the user identifier according to a user login request, receiving a selection operation on the candidate user role set, and determining a target role from the candidate user role set according to the selection operation.

[0168] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented: obtaining matching first requirement information based on the target user role, obtaining second requirement information associated with the target user role, the second requirement information also including requirement information of other user roles, obtaining a target key field exclusive to the target user role, and obtaining a requirement form based on the first requirement information, the second requirement information, and the target key field.

[0169] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented: receiving a first operation on the page editing control of the requirement form, displaying a custom editing page corresponding to the requirement form based on the first operation, the custom editing page including at least one requirement form filter item, receiving a second operation on each requirement form filter item in the custom editing page, determining a target requirement form filter item based on the second operation, and displaying it in the requirement form, receiving an input operation on the target requirement form filter item, and obtaining matching target requirement information based on the input operation.

[0170] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: rendering the target demand information in a list, displaying it in the form of a target demand information table, hiding the column options of the target demand information table, hiding the target column options in the target demand information table according to the hiding operation, adding the column options of the target demand information table, adding the target column options to the target demand information table according to the adding operation, and displaying the data corresponding to the target column options.

[0171] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: creating a visible area, obtaining area content of the visible area from the target demand information, rendering the area content, and displaying the area content in the visible area.

[0172] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: creating candidate requirement information corresponding to the candidate user role, creating candidate key requirement fields corresponding to the candidate user role, configuring associated requirement information corresponding to the associated user role for the candidate requirement information, and obtaining a candidate requirement form corresponding to the candidate user role based on the candidate requirement information, the associated requirement information and the candidate key requirement fields.

[0173] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchl ink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0174] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0175] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A method for processing demand information, the method comprising: receiving a user login request, wherein the user login request carries a user identifier; Identifying a target user role corresponding to the user identifier according to the user login request; Acquire a matching requirement form according to the target user role, wherein the requirement form includes requirement information matching the target user role; Performing a custom operation on the demand form, and determining target demand information according to the custom operation; The target demand information is rendered and displayed.

2. The method according to claim 1, characterized in that The identifying, according to the user login request, a target user role corresponding to the user identifier, includes: Obtaining a set of candidate user roles corresponding to the user identifier according to the user login request; receiving a selection operation on the candidate user role set; A target role is determined from a set of candidate user roles according to the selection operation.

3. The method according to claim 1, characterized in that The step of obtaining a matching requirement form according to the target user role, wherein the requirement form includes requirement information matching the target user role, includes: Acquire matching first demand information according to the target user role; Acquire second demand information associated with the target user role, where the second demand information also includes demand information of other user roles; Obtain target key fields specific to the target user role; The requirement form is obtained according to the first requirement information, the second requirement information and the target key field.

4. The method according to claim 1, wherein The performing of a custom operation on the demand form and determining target demand information according to the custom operation includes: receiving a first operation on a page editing control of the requirement form; Displaying a custom editing page corresponding to the requirement form according to the first operation, wherein the custom editing page includes at least one requirement form filtering item; receiving a second operation on each of the requirement form filter items in the custom edit page, determining a target requirement form filter item according to the second operation, and displaying the target requirement form filter item in the requirement form; An input operation on a target requirement form filter item is received, and matching target requirement information is obtained according to the input operation.

5. The method according to claim 1, wherein The rendering and displaying of the target demand information includes: Rendering the target demand information in a list and displaying it in the form of a target demand information table; Performing a hiding operation on the column options of the target demand information table, hiding the target column options in the target demand information table according to the hiding operation; A new adding operation is performed on the column options of the target demand information table, a target column option is added to the target demand information table according to the new adding operation, and data corresponding to the target column option is displayed.

6. The method according to claim 1, characterized in that The rendering and displaying of the target demand information includes: Creating a visual area, and obtaining area content of the visual area from the target demand information; The regional content is rendered and displayed in the visible area.

7. The method according to claim 1, characterized in that The method further comprises: Create candidate requirement information corresponding to candidate user roles; Create candidate key requirement fields corresponding to the candidate user roles; Configuring associated demand information corresponding to an associated user role for the candidate demand information; A candidate requirement form corresponding to the candidate user role is obtained according to the candidate requirement information, the associated requirement information and the candidate key requirement fields.

8. A demand information processing device, characterized in that: The device comprises: A receiving module, configured to receive a user login request, wherein the user login request carries a user identifier; An identification module, configured to identify a target user role corresponding to the user identifier according to the user login request; An acquisition module, configured to acquire a matching requirement form according to the target user role, wherein the requirement form includes requirement information matching the target user role; An operation module, configured to perform a customized operation on the demand form and determine target demand information according to the customized operation; The rendering module is used to render and display the target demand information.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images