A process processing method, a page display method and a computing device

Abstract

The embodiment of the application provides a process processing method, a page display method and a computing device, relates to the technical field of servers, and is used for improving the data entry efficiency in a process submission process, thereby optimizing the smoothness of the overall business process. The process processing method comprises the following steps: in response to receiving an application request of a target process, outputting a process application page; in response to a user inputting field content based on the process application page, matching each component template in a plurality of component templates with the input field content, so as to determine the template weight corresponding to each component template; based on a target component template in which the matching degree represented by the template weight in the plurality of component templates satisfies a preset matching degree, outputting an updated process application page; the updated process application page comprises components corresponding to each field that needs to be displayed in the target component template; and in response to receiving a creation instruction of the target process, creating the target process based on the field content filled in the process application page.

Description

Technical Field

[0001] This application relates to the field of server technology, and in particular to a process processing method, a page display method, and a computing device. Background Technology

[0002] In complex business process management, the same type of process (such as project initiation process) often includes multiple business scenarios (such as R&D projects, engineering construction projects, etc.). These different scenarios have both overlapping commonalities and differentiated individual requirements for form information, thus forming the core contradiction between process standardization and scenario customization. Related technologies typically design a single static form template for the entire process.

[0003] However, using static form templates displays all potentially required fields to each user, resulting in a large amount of redundant information for fields not needed in the current scenario. Users then have to expend effort filtering for relevant information, which not only reduces data entry efficiency but also affects the focus on key information and the overall workflow experience. Summary of the Invention

[0004] This application provides a process processing method, a page display method, and a computing device to improve the data entry efficiency in the process submission process, thereby optimizing the smoothness of the overall business process.

[0005] In a first aspect, embodiments of this application provide a process processing method, the method comprising: in response to receiving an application request for a target process, outputting a process application page; the process application page is used to display a locking component corresponding to a locking field; the locking component is used to receive field content input by a user for the locking field; the locking component is used to represent a component that must be displayed on the process application page; in response to receiving field content input based on the process application page, matching the input field content with each of a plurality of component templates to determine the template weight corresponding to each component template; the component template is used to represent several field display rules corresponding to the target process, the display rules including: display status and / or required status; the template weight is used to characterize the degree of matching between the corresponding component template and the input field content; based on a target component template whose matching degree characterized by the template weight among the plurality of component templates satisfies a preset matching degree, outputting an updated process application page; the updated process application page includes a locking component and a target component, the target component being the component corresponding to each field that needs to be displayed in the target component template.

[0006] The process processing method provided in this application, upon receiving an application request for a target process, outputs a process application page. This page displays locked components corresponding to locked fields, i.e., it shows some required fields for the user to fill in. After the user fills in the content, a component template is matched in real-time based on the user's input. The display status and / or required status of subsequent fields on the process application page are adjusted using the matched target component template. This ensures that the updated process application page includes locked components and target components, without needing to display all fields corresponding to the target process. This achieves on-demand field presentation, reducing input delays and errors from the source, thereby improving data entry efficiency in the process submission process. It ensures that the process can flow quickly and accurately to subsequent stages, enhancing the smoothness of the business process and providing highly adaptable technical support for complex and ever-changing online scenarios.

[0007] In one possible implementation, the target components are all the components to be displayed in the target component template, excluding the locked component. Accordingly, based on the target component template whose matching degree, represented by the template weights among multiple component templates, satisfies a preset matching degree, an updated process application page is output, including: determining the component corresponding to the first field in the process application page based on the target component template; the first field is the field other than the locked field and the target field among the fields corresponding to the components displayed in the process application page; if the process application page displays a component with the first field, then the component with the first field is removed from the process application page so that the updated process application page only includes the locked component and the target component.

[0008] This implementation identifies and retains locked components in the interface, while determining other target fields to be displayed based on the matched target component template. When updating the page, it proactively removes components that are neither locked nor target fields for the first field, effectively purifying interface elements and avoiding information redundancy. This ensures that the process application page always displays only the necessary and valid field components for the current stage, reducing the user's cognitive load and minimizing the performance overhead of rendering unnecessary components on the front end, thereby improving page loading efficiency and operational clarity.

[0009] In one possible implementation, the target component is any component to be displayed in the target component template, excluding the locked component and the component corresponding to the second field; the second field is any field in the component field displayed on the process application page that has been filled in, excluding the locked field; based on the target component template whose matching degree, represented by the template weights in multiple component templates, satisfies a preset matching degree, the updated process application page is output, including: adding the target component to the process application page and outputting the updated process application page, so that the updated process application page includes the locked component, the component corresponding to the second field, and the target component.

[0010] In this implementation, when determining the target field, locked fields and second fields with content already filled in by the user are excluded. This ensures that the updated page retains locked components, user-filled components, and the target component to be added simultaneously. This fully respects the user's completed input, avoids duplicate entries, and ensures both process continuity and data integrity. It not only improves the accuracy of interface updates but also enhances user experience and satisfaction in multi-step processes.

[0011] In one possible implementation, before outputting the updated process application page, the method further includes: if the process application page displays a component with a third field, then remove the component with the third field from the process application page; the third field is any field in the field corresponding to the component displayed on the process application page, excluding the locked field, the second field, and the target field.

[0012] This implementation removes all field components except those explicitly defined as "locked field, second field, and target field." This ensures that the application interface always presents only three absolutely necessary elements: those the user requested to lock, those the user has already filled out, and those displayed according to the currently matched component template. This avoids interference from outdated, redundant, or irrelevant field components, ensuring a highly focused interface, optimizing visual presentation, and improving front-end performance by removing unnecessary component listeners and rendering.

[0013] In one possible implementation, each component template corresponds to a component matching rule; the component matching rule is used to represent the component matching condition corresponding to the first weight field participating in the weight configuration among multiple fields; based on the input field content, the template weight corresponding to each component template is determined by matching with each of the multiple component templates, including: for each component template: based on the filled field content, matching with the component matching condition of each first weight field of the corresponding component template, and determining the weight corresponding to each first weight field based on the matching result; determining the template weight corresponding to the component template based on the weight corresponding to each first weight field.

[0014] In this implementation, by integrating the weights of the first weight field in the template matching rules to form the overall template weight, the template adaptability can be upgraded from a scattered field evaluation to an intuitive overall quantitative result. This makes the selection of subsequent component templates not only meet the core business needs, but also have the characteristics of efficiency, objectivity and reusability.

[0015] In one possible implementation, the component template is also used to configure the locking state of each field; the locking state of a locked field is locked.

[0016] In one possible implementation, the method further includes: determining multiple sub-processes corresponding to the target process; sub-processes representing the approval objects and / or approval rules of the target process; for each sub-process, matching the field content filled in the updated process application page with the corresponding process matching rules to obtain the process weight of the sub-process; wherein, the process matching rules characterize the process matching conditions corresponding to the second weight field participating in the weight configuration, and the process weight characterizes the degree of matching between the corresponding sub-process and the filled field content; and processing the target process based on the approval objects and / or approval rules indicated by the target sub-process whose process weights meet the conditions.

[0017] In this implementation, multiple sub-processes and matching rules for each sub-process are pre-defined, transforming the originally fixed approval path into an objective, quantifiable, data-driven process. By calculating and comparing the "process weight" of each sub-process, the system can identify the sub-process from multiple candidate sub-processes that meets the matching criteria (e.g., the highest) for the current business scenario, and automatically process it according to the approval object and / or approval rules defined in that sub-process, without requiring manual intervention. This shortens the distribution time at the front end of the process and improves overall processing efficiency.

[0018] In one possible implementation, the process weight of a subprocess is obtained by matching the field content filled in on the process application page with the process matching rules corresponding to the subprocess. This includes: for each subprocess, matching the field content filled in on the process application page with the process matching conditions of each second weight field, and determining the weight of each second weight field based on the matching results; and determining the process weight of the subprocess based on the weight of each second weight field.

[0019] In this implementation, by integrating the weights of the second weight field in the process matching rules to form the overall process weight, the adaptability of the process can be upgraded from a scattered field evaluation to an intuitive overall quantitative result, so that the selection of subsequent sub-processes meets the core business needs.

[0020] In one possible implementation, the method further includes: obtaining all fields required by the business function corresponding to the target process; in response to the new template operation, outputting a component template configuration interface; the component template configuration interface is used to configure the display rules of each field in all fields; in response to the confirmation operation based on the component template configuration interface, saving the display rules configured based on the component template configuration interface as a component template.

[0021] In this implementation, all fields that the process may require are first identified. Then, a component template configuration interface is provided for users to select the display rules for each field, so that users can quickly set the rules for each component (such as setting "project nature" as a required field), reducing operational errors and avoiding subsequent application rejections due to ambiguous rules. Finally, the set rules are saved as templates, which can be directly reused in subsequent similar processes (such as R&D project changes) without repeated configuration, and the field rules of all processes are consistent.

[0022] In one possible implementation, multiple component templates include a default component template; the method further includes: when the matching degree represented by the template weight in multiple component templates does not meet the preset matching degree, an updated process application page is output based on the default component template.

[0023] In this implementation, a default component template is set as a fallback mechanism to ensure stable operation and normal page display even when no dedicated template is available, effectively improving the robustness of the process processing system and the continuity of user experience.

[0024] In one possible implementation, in response to receiving an application request from a target process, outputting a process application page includes: in response to receiving an application request from a target process, obtaining multiple component templates that match the target process; determining all locked fields in the multiple component templates that are in a locked state; and outputting the process application page based on the locked components corresponding to the locked fields.

[0025] In this implementation, by uniformly analyzing the locked fields of all component templates corresponding to the target process, the locked components that must be fixedly displayed on the process application page are determined in advance. This ensures that regardless of how users switch between different business scenarios, the display state and layout structure of those key fields on the page remain unchanged, thus achieving the stability required by the business from a technical perspective. Subsequent scenario switching only requires handling the dynamic content of the unlocked parts, greatly simplifying the complexity of page state management and improving overall interaction performance.

[0026] Secondly, embodiments of this application provide a page display method, comprising: in response to receiving a display instruction for a target page, obtaining project information of the project to which the target page belongs; matching the field content of the project information with each of a plurality of page component templates to determine the page weight corresponding to each page component template; the page component template is used to represent the display status of each field among a plurality of fields corresponding to the target process; and outputting the target page to a display device based on the target page component template whose matching degree represented by the page weights among the plurality of page component templates satisfies a preset matching degree, wherein the display device is used to display the target page.

[0027] The page display method provided in this embodiment achieves flexible control over the display state of page components by introducing a weighted matching mechanism to match the target page component template when a target page needs to be displayed. When new project attributes or business rules need to be added, only the corresponding weighted matching rules need to be updated to achieve functional adaptation, without modifying the underlying system code. By abstracting business logic into configurable templates and weighted rules, centralized management and maintenance of interface logic are achieved.

[0028] Thirdly, embodiments of this application provide a computing device, which includes a processor and a memory; the processor is coupled to the memory; the memory is used to store computer instructions, which are loaded and executed by the processor to enable the computing device to implement the methods provided by the first aspect and its possible implementations or the methods provided by the second aspect and its possible implementations.

[0029] Fourthly, embodiments of this application provide a computer-readable storage medium comprising: computer software instructions; which, when executed in a computing device, cause the computing device to implement the method provided by the first aspect and its possible implementations or the method provided by the second aspect and its possible implementations.

[0030] Fifthly, embodiments of this application provide a computer program product that, when run on a computing device, causes the computing device to execute the steps of the related method described in the first aspect to implement the method of the first aspect; or causes the computing device to execute the steps of the related method described in the second aspect to implement the method of the second aspect.

[0031] The beneficial effects of the third to fifth aspects mentioned above can be referred to the corresponding descriptions of the first or second aspects, and will not be repeated here. Attached Figure Description

[0032] Figure 1 A schematic diagram of a process processing method provided in an embodiment of this application; Figure 2This is a schematic diagram of a template creation method provided in an embodiment of this application; Figure 3 A schematic diagram of a component template configuration interface provided in an embodiment of this application; Figure 4 This is a schematic diagram of a process processing method provided in an embodiment of this application; Figure 5 A schematic diagram of a process application page provided for an embodiment of this application. Figure 1 ; Figure 6 A schematic diagram of a process application page provided for an embodiment of this application. Figure 2 ; Figure 7 This is a schematic diagram of a page display method provided in an embodiment of this application; Figure 8 A schematic diagram of the architecture of a process processing device provided in an embodiment of this application; Figure 9 A flowchart illustrating a process processing method provided in an embodiment of this application; Figure 10 This is a schematic diagram of the architecture of a computing device provided in an embodiment of this application. Detailed Implementation

[0033] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0034] It should be noted that in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0035] To facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with essentially the same function and effect. Those skilled in the art can understand that the terms "first" and "second" are not intended to limit the quantity or execution order.

[0036] This application provides a process processing method. After receiving an application for a target process, it displays locked components corresponding to locked fields on the process application page, i.e., displays some required fields for the user to fill in. Then, after the user fills in the content, a component template is matched in real time based on the user's field content. This allows adjustment of the display status and / or required status of subsequent fields using the matched target component template, without needing to display all fields on the process application page. This achieves on-demand field presentation, reducing input delays and errors from the source, thereby improving data entry efficiency in the process submission process. It ensures that the process can flow quickly and accurately to subsequent stages, thus enhancing the smoothness of the business process and providing highly adaptable technical support for complex and ever-changing online scenarios.

[0037] It should be noted that the "real-time matching of component templates based on the field content filled in by the user" mentioned in this application embodiment can mean that after the user completes the content of each component (such as losing focus, pressing Enter to confirm, etc.), the component template that meets the conditions is immediately rematched based on the combination of the currently filled field values; or it can mean that after the user fills in one or more components, when the matching control (such as submit, match button, etc.) in the process application page is triggered, the component template that meets the conditions is matched. This application embodiment does not limit this.

[0038] The process processing method provided in this application can be applied to a computing device, which can be a personal computer (PC), laptop computer, mobile device, tablet computer, or other electronic device. This application does not limit the specific form of computing. Alternatively, the computing device can be a single server or a server cluster consisting of multiple servers. In some implementations, the server cluster can be a distributed cluster server. This application does not impose any restrictions in this regard.

[0039] Figure 1 This illustration shows a scenario provided by an embodiment of this application. Figure 1 As shown, the embodiments of this application can be executed by computing device 100.

[0040] The computing device 100 and the display device 110 can be separate or integrated. In separate mode, the computing device 100 interacts with the user-side display device 110; while in integrated mode, the display device 110 can be a component of the computing device 100. This application does not limit the specific form of the embodiments. For ease of description, the solution provided in this application is illustrated using the separation of the computing device 100 and the display device 110 as an example.

[0041] The display pages of the process processing system (such as the process application page and component template configuration page) can be displayed on the user-side display device 110. The user-side display device 110 can be a device with interface display capabilities; for example, the user-side display device 110 can display the process processing system's display pages through a browser. Optionally, the user-side display device 110 can be a smartphone, tablet, personal portable computer, etc., and there is no limitation thereto.

[0042] As one implementation method, when displaying a webpage, the computing device can handle all the rendering work. It combines business data with a webpage template to generate a final, complete HTML page, and then sends this page as a whole to the display device. The display device simply receives this ready-made page and displays it, without needing to perform complex logic processing.

[0043] As an alternative implementation, when a page needs to be displayed, the computing device can forgo page rendering and instead send the structured data and business logic that constitute the page to the display device. Upon receiving this raw data, the display device's processor dynamically constructs and updates the display page based on this raw data.

[0044] As one implementation method, the display device 110 can also integrate or connect to external input devices, such as a mouse, keyboard, touchpad, touch screen, etc., so that users can input field content and other information on the display page.

[0045] For example, if the process processing system operates through computing device 100, when the user-side display device 110 accesses the process processing system, computing device 100 can determine that it has received an application operation for the target process and display the process application page on display device 110. The user can fill in field content on the display device, which will then send the filled-in field content to the computing device. Computing device 100 can update the process application page presented on display device 110 in real time based on the field content filled in by the user, thereby reducing the risk of information omissions and errors at the source of data entry and ensuring the quality of process data.

[0046] The computing device 100 can be a personal computer (PC), a laptop computer, a mobile device, a tablet computer, or a laptop computer, etc. Alternatively, the computing device 100 can be a single server or a server cluster consisting of multiple servers. In some implementations, the server cluster can be a distributed cluster server. This application does not limit the specific form of the computing device 100.

[0047] It should be noted that the system architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0048] The process processing method provided in this application embodiment can be applied to Figure 1 In the computing device shown, the method can be specifically executed by the processor of the computing device. To illustrate the process handling method provided in the embodiments of this application, the creation process of the component template in this application will be introduced first.

[0049] In some embodiments, this application also provides a template creation method, which can be applied to Figure 1 For the computing devices shown, please refer to Figure 2 The template creation method includes: S201. Obtain all fields required by the business function corresponding to the target process.

[0050] Obtain all fields required for the business functions corresponding to the target process to clarify the "field boundaries" of the template configuration and ensure that the field set accurately matches the business requirements of the target process. During the configuration phase, a series of fields need to be pre-associated and defined for the target process. These fields together constitute the complete data set required to complete the business functions corresponding to the process. In other words, all potentially involved data items need to be pre-set in the background based on the business logic and form requirements of the process, serving as the "field library" for the process. Therefore, obtaining all fields required for the business functions corresponding to the target process essentially involves retrieving the pre-set, static field set of the process, rather than dynamically generating fields at runtime. This field set provides a stable data foundation and judgment criteria for subsequent dynamic filtering (such as showing or hiding specific fields based on conditions).

[0051] For example, all the fields required for the business functions corresponding to the leave application process are predefined during the process design phase, forming a complete "leave application field library." This library typically includes, but is not limited to, the following fields: applicant, department, leave type, start time, end time, number of leave days, reason for leave, emergency contact person, work handover person, and uploaded supporting documents. When it is necessary to generate or update component templates, the entire set of fields needs to be retrieved from this pre-set static field library, laying a precise data foundation for subsequent template configuration.

[0052] S202. In response to the new template operation, output the component template configuration interface.

[0053] The component template configuration interface is used to configure the display rules for each field in all fields. It provides a visual configuration tool, allowing users to define the display rules for fields within the target process.

[0054] It should be noted that the output component template configuration interface can be displayed by the computing device through its own display, or the computing device can send the rendered component template configuration interface or related data to the display device for display. This application does not limit the output method of the component template configuration interface.

[0055] For example, please refer to Figure 3 Taking the field configuration of the project change process as an example, all fields corresponding to the project change process include: "Project Type," "Change Type," "Project Nature," "Project Level," "Project Number," and "Project Description." When a user triggers the new template operation, the displayed component template configuration interface can include the configuration components corresponding to each field. For example... Figure 3 As shown, for the "Project Type" field, users can check "Show" (to ensure that the project category is clearly specified when making a change request) and set it to "Required" (to avoid deviations in the review direction due to missing project types); for "Project Nature", "Show + Required" can also be configured to ensure that the project attributes are clear; and for some special scenarios (such as departmental project changes that do not require additional project descriptions), the "Provide Project Description" field can be configured to "Hidden" and "Not Required".

[0056] This application does not impose specific restrictions on the page structure of the component template configuration interface. The design of the component template configuration interface can be simple and focused. As one implementation method, such as... Figure 3 As shown, you can set "Show / Hide" and "Required / Optional" checkboxes. Alternatively, you can set a toggle button for "Show / Hide" and "Required / Optional". No extra redundant functions are needed, allowing users to quickly complete rule definitions.

[0057] As one implementation method, the component template configuration interface is also used to configure the weight matching rules for component templates. It should be understood that the weight matching rules are essentially the matching conditions for templates. By configuring the weight matching rules, the application scenarios of the component template can be defined so that the component template can be matched during the application process.

[0058] For example, in a certain area of ​​the component template configuration interface, a matching area for weight matching rules can be set. Users can select the "first weight fields" that will participate in the template matching calculation from all fields in the process within this area, and then set specific "component matching conditions" for each selected "first weight field." For example... Figure 3 As shown, the condition for the "Project Level" field is set to "Value equals 'Level 1'"; the condition for the "Change Type" field is set to "All".

[0059] As one implementation method, the component template configuration interface is also used to configure the locking status of fields. The component template configuration interface can also include a "Locked / Unlocked" selection control (toggle button or checkbox, etc.) for each field, which users can use to configure the locking status of each field.

[0060] In some business scenarios, certain fields carry critical information that must always be displayed, regardless of which component template is used to configure the target process. Take a business trip application process as an example: fields like "Employee Name," "Employee ID," and "Application Date" can be set as locked fields. Regardless of the component template chosen to configure the business trip application process, this basic information will be forcibly displayed. This is because this information is crucial for identifying the applicant and recording the application time throughout the entire process; its absence would prevent the application process from starting and being tracked correctly. Therefore, as an implementation method, once a field is set as a locked field, it will always remain displayed, unaffected by any display or hiding settings for that field in other templates, ensuring absolute display stability.

[0061] In some embodiments, when a process involves multiple component templates, users need to remember the locking configurations of various fields in a large number of different templates. Due to the limitations of human memory, as the number of templates increases and the complexity of fields increases, users may forget whether a certain parameter has been configured with a locking state in a specific template. This may result in some key fields not being locked correctly in some templates, thus affecting the stable display of key information in the business process; it may also lead to duplicate locking, causing resource waste and unnecessary operational redundancy.

[0062] Therefore, as a feasible implementation method, users can configure the lock state in only one component template (such as the default component template) during configuration. Users only need to complete the lock state settings on one template, without having to remember and check back and forth between multiple templates, which greatly reduces the probability of forgetting and confusion, ensures the accuracy and consistency of the lock configuration, and guarantees the stable operation of the system.

[0063] S203. In response to the confirmation command based on the component template configuration interface, save the display rules configured based on the component template configuration interface as a component template.

[0064] This application does not limit the triggering method of the confirmation command in its embodiments. For example, such as Figure 3 As shown, the component template configuration interface also includes a confirmation control. If the display device detects that the confirmation control has been triggered, the display device can determine that it has received a confirmation operation and send a corresponding confirmation command to the computing device. This allows the computing device to convert the defined simple rules into directly callable templates, facilitating template invocation during use.

[0065] As can be seen from S201-S203, the solution provided in this embodiment first determines all the fields that the process may need. Secondly, it allows users to select the display rules for each field through a component template configuration interface, so that users can quickly set the rules for each component (such as setting "project nature" as a required field), reducing operational errors and avoiding subsequent application rejections due to ambiguous rules. Finally, the set rules are saved as templates, which can be directly reused in subsequent similar processes (such as R&D project changes) without repeated configuration, and can also ensure that the field rules of all processes are consistent.

[0066] After configuring one or more component templates based on S201-S203 above, you can then process application requests based on those component templates. Please refer to [link / reference]. Figure 4 , Figure 4 This is a flowchart illustrating a process processing method provided in an embodiment of this application. For example, the process processing method provided in this embodiment can be applied to... Figure 1 In the computing device shown, the method can specifically be executed by the processor of the computing device. For example... Figure 4 As shown, the process processing method provided in this application embodiment may include the following steps: S401. In response to receiving the application request for the target process, output the process application page.

[0067] The process application page is used to display the locking components corresponding to the locked fields; the locking components are used to receive the field content entered by the user for the locked fields; and the locking components are used to represent the components that must be displayed on the process application page.

[0068] When a user needs to initiate a transaction that requires multi-stage collaboration, confirmation, or approval, an application process is required. For example, after logging into the system via a display device, the user can find the entry point for the target process (such as a "leave application process" or "reimbursement process") through a navigation menu displayed on the display device (e.g., "Initiate Process" or "Create Application"). Clicking the "Apply" or "Create" button for the target process sends the operation to the computing device, which then confirms that it has received the application request for the target process.

[0069] Locked fields typically represent the most critical, universal, and unchangeable information items in the target process. Regardless of the specific scenario a user applies for, this information must be displayed and its state must remain fixed. Therefore, when outputting a process application page, the computing device must first determine the locked fields corresponding to the target process. Examples include fields like "Project Type," "Project Nature," and "Project Level" in a project change process, and fields like "Leave Type," "Start and End Dates," and "Leave Reason" in a leave application process. Then, the locked components corresponding to these locked fields, such as input boxes, dropdown selectors, and date pickers, are displayed on the process application page, allowing users to input or select content.

[0070] As a feasible implementation method, S401 can be specifically implemented as follows: S4011. In response to receiving the application request for the target process, obtain multiple component templates that match the target process.

[0071] Multiple component templates that match the target process, i.e., component templates pre-configured for the target process. For specific configuration methods, please refer to the above embodiments, which will not be repeated here.

[0072] Each matched component template (such as the "Annual Leave," "Sick Leave," and "Business Trip" templates in the leave application process) defines the composition, logic, and status (including locked status) of fields in the leave application process under a specific scenario. Therefore, upon receiving an application request for the target process (such as an employee's leave application), a template matching mechanism needs to be activated to identify all possible business scenarios or variations involved in the process, providing the necessary component resources for the subsequent generation of the application page.

[0073] S4012. Identify all locked fields in a locked state in multiple component templates.

[0074] All component templates obtained from S4011 are analyzed, and fields marked as "locked" in each template are extracted. Then, these locked fields from different templates are logically aggregated (usually by taking the union) to finally generate a global set of locked fields.

[0075] A target process (such as "employee leave application" or "project initiation") may correspond to multiple business scenarios or subtypes. For example, a "leave application process" may include different scenarios such as "annual leave," "sick leave," and "business trip." The fields and rules for each scenario (corresponding to a component template) may differ slightly. Locked fields represent the most core, general, and unchangeable information items in the process. Regardless of the specific scenario the user applies for, this information must be displayed and its state must be fixed. By identifying all locked fields, it is clear which information must be presented and whose display state cannot be arbitrarily changed. This provides a crucial basis for accurately constructing the process application page, ensuring that key information is stably displayed on the page, and avoiding the impact of uncertainty in the field display state on the normal progress of the process application.

[0076] It's important to note that the locked fields need to be determined based on all component templates corresponding to the target process, not just a single component template. Different component templates may have different locked fields due to different scenarios, but these locked fields are all key information to ensure the smooth progress of the process in their respective scenarios. Therefore, when displaying the process application page, it is necessary to obtain and display the locked fields from all component templates to ensure that no mandatory requirements in any sub-scenario are missed or circumvented, thereby solidifying the compliance baseline of the business process at the page level.

[0077] Furthermore, by determining the locked fields upon receiving the application request from the target process, the calculation of the locked fields can be pre-calculated and fixed. This means that the basic page framework does not need to be recalculated or changed throughout the subsequent page interaction lifecycle. This simplifies the complex state management of the front end and allows subsequent loading and replacement of the unlocked content only, improving rendering efficiency and system response speed.

[0078] S4013, Output process application page based on the locking component corresponding to the locking field.

[0079] Once the locked fields are determined, the corresponding locked components can be identified. Locked components are UI elements that handle the display and interaction of the locked fields, presenting them appropriately according to preset rules and styles. Based on these locked components, they are combined according to preset layouts and logic to ultimately obtain the complete application process page.

[0080] As shown in S4011-S4013, this implementation method pre-determines the locked components that must be fixedly displayed on the process application page by uniformly analyzing the locked fields of all component templates corresponding to the target process. This ensures that the display state and layout structure of those locked fields on the page remain unchanged regardless of how users switch between different business scenarios, thus achieving the stability required by the business requirements from a technical perspective. Subsequent scenario switching only requires handling the dynamic content of the unlocked parts, greatly simplifying the complexity of page state management and improving overall interaction performance.

[0081] As another feasible implementation method, when configuring any component template of the target process, if a certain field is set as a locked field, the status of that field can be synchronously updated to locked in all component templates corresponding to the target process. In this way, when the process application page needs to be displayed, the field in the locked state can be identified as the locked field in any component template.

[0082] In some embodiments, since the locked field must be displayed on the page, the weight score corresponding to the locked field can be set to a large value so that it can be directly matched. For example, the weight score corresponding to the locked field can be 99999.

[0083] As another feasible implementation method, S401 can be specifically implemented as follows: in response to receiving the application request of the target process, obtain the weight score corresponding to each field among the multiple fields of the target process; determine the fields whose weight scores are greater than or equal to the preset weight threshold as locked fields; and output the process application page based on the locked fields.

[0084] The weight score of locked fields is pre-set to a maximum value (e.g., 99999), while ordinary fields are assigned lower scores (e.g., a range of 1-1000) or no weight score based on their business importance. When a request for the target process is received, the weight score of each field is compared with a preset weight threshold (e.g., 90000), and only fields with scores greater than or equal to the threshold are retained as locked fields. Due to the extremely high score of locked fields, they are inevitably prioritized, ensuring their mandatory display on the page. This weight score mechanism also provides flexibility in field priority management, making it suitable for complex business scenarios requiring strict control over the display order of required fields.

[0085] In this embodiment, the output of the process application page can be as follows: The computing device sends structured data (e.g., field content, lock status, etc.) describing the page state to the display device, and the display device uses this data to call the corresponding UI component (e.g., a locked input box) to render the process application page seen by the user in real time. Alternatively, the computing device can render the process application page based on this data and then send it to the display device for display to the user. Or, the computing device can display the process application page through its connected monitor. This embodiment does not limit the specific method of outputting the process application page.

[0086] For example, please refer to Figure 5 , Figure 5 A schematic diagram of a process application page provided for an embodiment of this application. Figure 1 .like Figure 5 As shown, when a request for a target process is received, the process request page includes a locked component but excludes unlocked components. The locked component may include: such as... Figure 5 The fields shown include "Project Type", "Project Nature", and "Project Level", along with their corresponding input components.

[0087] In some embodiments, when displaying the output process application page, the content of certain fields can be automatically filled based on preset information of the target process. Specifically, the computing device can determine whether a specific field contains predefined fixed content based on the relevant attributes of the target process. If the field content is a fixed value, the computing device can automatically render it to the corresponding position on the page, without requiring manual input from the user. Figure 5 As shown, the content of the "Project Type" field can be preset to "Research and Development" according to the process configuration and displayed directly when the page is initialized.

[0088] As a feasible implementation method, the display order of components corresponding to fields on the process application page can be determined based on a pre-defined field order for the target process. A pre-defined list of pre-defined field orders (e.g., [Field A, Field B, Field C, Field D]) needs to be defined for the target process. When rendering or updating the page: first determine which fields need to be displayed, then match the pre-defined field order list to the set of fields to be displayed. Ultimately, the page components will be rendered strictly according to the order in which these fields appear in the pre-defined order list.

[0089] For example, even if field B is dynamically added when updating the application page, it will be inserted before field C, not at the end of the page. This ensures that regardless of how the process branches or how fields are dynamically shown or hidden, the relative positions of the fields seen by the user remain stable. This consistency reduces the user's search cost, establishes stable psychological expectations, and improves filling efficiency.

[0090] As another feasible implementation method, the process application page includes a first area and a second area. The first area is used to display the locking component (which can be displayed in a preset field order); the second area is used to display other components (in a preset field order).

[0091] The first area contains locked components that remain unchanged throughout the target process, and must be displayed regardless of which component template is matched. The second area displays other components besides the locked components (such as the target component and components corresponding to already filled fields, see the examples below), which may change during the target process. By including both the first and second areas on the application page, the fields that must always be displayed (locked fields) and fields that change dynamically based on conditions are physically separated, thus establishing a clear page structure. This allows both users and the system to clearly distinguish between the "unchanging framework" and the "variable content," preventing all fields from being mixed together and difficult to manage and identify during dynamic updates.

[0092] Furthermore, the first and second areas can be displayed according to the preset field order, ensuring that even if the fields are divided into different areas in terms of business logic, their overall arrangement still strictly follows a unified visual and logical sequence, thereby maintaining the consistency and predictability of the page layout, avoiding confusion in the field order due to area separation, and further improving the continuity of user operations and the rigor of the interface structure.

[0093] It should be noted that this application embodiment does not impose any limitations on the specific size and relative position of the first and second regions. In practical applications, the layout can be flexibly adjusted according to actual needs. For example, the size of the first region can be dynamically adjusted based on the number of locked fields, or it can be fixed at the top of the process application page for users to view first.

[0094] In this implementation, a clear logical and visual separation of the page structure is achieved by setting up a first area and a second area on the application page. This makes the first area an independent and stable module, and the locked components displayed within it will not be affected by the dynamic updates, additions, or removals of fields in the second area, thus ensuring the persistent stability of the core page framework. This separation design improves development and maintenance efficiency: the front-end can implement differentiated style strategies and interaction logic management for the "locked area" and the "dynamic area" respectively, resulting in a clearer code structure and a higher degree of modularity. At the same time, this layout also provides users and testers with an intuitive interface, effectively reducing the cost of understanding and operating the interface.

[0095] S402. In response to receiving the field content input on the process application page, match the input field content with each of the multiple component templates to determine the template weight corresponding to each component template.

[0096] The component template represents the display rules for one or more fields corresponding to the target process. These display rules include display status and / or required field status. Template weight represents the degree of matching between the corresponding component template and the entered field content. Display status indicates whether the field needs to be displayed on the page, while required field status not only indicates the display method but also serves as a page validation rule. When a user attempts to submit a process application, the computing device validates all required fields according to the required field rules defined in the currently active component template. If any required field is empty or its content does not conform to the specifications, the computing device will block the submission and return a clear error message, forcing the user to complete the field. This ensures the data completeness required for business process advancement from a rule-based perspective.

[0097] As a feasible implementation method, in order to more accurately determine the status of each field in the target process, the component template is used to configure the display rules of each field in all fields corresponding to the target process.

[0098] When a user enters field content on the application page displayed on the display device, the display device can simultaneously send the user's input to the computing device. The computing device then triggers a component template matching mechanism: comparing the user's input with multiple component templates one by one, and calculating a "template weight" for each template based on the degree of matching. Essentially, a component template is a set of display rules for each field in the target process (e.g., which fields are displayed, which are hidden, which are required, and which are optional), while the template weight quantifies the fit between a particular template and the current user input. The higher the weight, the better the template's display rules (display / required status) match the user's input.

[0099] Component templates can construct the "form" of a specific scenario through field display rules (show / hide, required / optional). For example, although both belong to the project change process, the template for the "strategic project change" scenario will include unique fields such as "senior management approval opinion" and "resource reallocation plan" (displayed as "shown" and "required"), while the template for the "routine project change" scenario will not include these fields and only needs to display basic fields such as "explanation of the reason for the change" and "department head confirmation".

[0100] Matching the entered field content with each of the multiple component templates is essentially a process of locating the "current business scenario" through user input. Only when the scenario is determined can the computing device call the display rules corresponding to that scenario template, so that the process application page fits the actual needs of the current scenario.

[0101] As can be seen, the solution provided in this application's embodiments, by inferring the most suitable display rule template from user input, avoids the redundancy (displaying unnecessary fields) or omissions (missing required fields) that may result from fixed templates. This allows the page to intelligently adjust based on the user's actual input, improving the smoothness and accuracy of the process. For example, in a reimbursement process, if the user inputs "travel type is international," the system may match a template containing the required field "passport information"; if the user inputs "travel type is domestic," it will match a template without this field, thus reducing interference from invalid fields.

[0102] It should be noted that this application embodiment does not restrict the triggering conditions of S402. As one implementation, in the application process interface, when input content is detected in a component, the input field content is matched against each of the multiple component templates to determine the template weight corresponding to each component template. As another implementation, S402 can be triggered after the user inputs N field contents, similarly matching these input field contents against multiple component templates to determine the template weight corresponding to each component template.

[0103] S403. The computing device outputs an updated process application page based on the target component template whose matching degree, represented by the template weights among multiple component templates, meets the preset matching degree.

[0104] The updated process application page includes a locking component and a target component. The target component is the component corresponding to each field that needs to be displayed in the target component template.

[0105] This application does not restrict the method of achieving a preset matching degree. As one implementation, the component template with the highest matching degree can be selected as the target component template. As another implementation, a matching degree threshold can be set, and component templates with all weights exceeding the threshold can be selected as candidate component templates. Then, the final target component template can be determined from these qualified candidate component templates through preset priority rules (such as historical reuse success rate, field integrity, etc.).

[0106] In one possible implementation, the target components are all the components to be displayed in the target component template, excluding the locked components. Accordingly, based on the target component template whose matching degree, represented by the template weights among multiple component templates, satisfies a preset matching degree, an updated process application page is output, including: S4031. Based on the target component template, determine the component corresponding to the first field in the process application page.

[0107] The first field refers to the fields corresponding to the components displayed on the process application page, excluding the lock field and the target field.

[0108] First, the target component template is read and parsed, and all fields whose "display status" is configured as "display" are selected. Then, fields that the user has actively set to "locked" in the front-end interface (i.e. "locked fields") are excluded from these fields to be displayed, thus obtaining the target fields that need to be dynamically rendered.

[0109] After determining the target field that needs to be added and displayed, it is necessary to check all the field components that have been rendered on the current application page and identify all those components that are neither protected "locked fields" nor "target fields" to be added in this round, and obtain the first field.

[0110] S4032. If the process application page displays a component with the first field, then remove the component with the first field from the process application page so that the updated process application page only includes the locking component and the target component.

[0111] If a component corresponding to the first field exists on the workflow application page, these components will be safely removed from the page. This ensures that only locked and target components remain on the page. For example, in a leave application process, when a user changes their leave type from "sick leave" to "annual leave," a new target component template will be matched. The "Upload Sick Leave Certificate" field, which was previously dynamically displayed for sick leave, will be removed as the "first field," while the "Work Handover Person" field, which is displayed for annual leave, will be added according to the newly matched target component template. This prevents outdated or invalid fields from remaining on the page, avoids incorrect submission of these residual field values ​​leading to data pollution, and also eliminates visual confusion and operational interference for users. It ensures that users encounter a clean, accurate form interface relevant only to the current operation at every step, thereby guaranteeing the data accuracy and smooth operation of the business process.

[0112] As one implementation method, outputting the updated process application page also includes adding target components that are not displayed on the process application page to the process application page.

[0113] Some of the identified target components may already be displayed on the process application page and do not require readjustment. Therefore, it is necessary to add the target components not displayed on the process application page. This means generating corresponding "target components" (such as input boxes, dropdown menus, etc.) based on the predefined component types and attributes of the target fields, and adding or updating these new components to the user's "process application page" through the front-end rendering engine. Ultimately, the updated output page will contain two parts: the previously displayed "locked components" that retain their original state and data, and the "target components" dynamically generated and inserted based on the latest matched template.

[0114] For example, in combination Figure 5 As shown, when a user opens the application page, the page only displays the most basic lock fields. Figure 6 As shown, in actual operation, the user selects "New Product Development" as the project type and "Level 1" as the project level. The user's entered fields are then matched against the rules of all templates. The application page is updated based on the target component template with the highest matching degree.

[0115] If the target component template is used to display the three fields: Change Type, Project Description, and Project Number, and all three fields are required, the updated process application page will look like this: Figure 6 As shown. While keeping the locked components unchanged, the page will dynamically display three previously hidden components: Change Type, Project Description, and Project Number, and mark them as required fields. Figure 6 middle (As shown). Other irrelevant fields will be hidden.

[0116] This implementation identifies and retains locked components in the interface, while dynamically updating other fields that need to be displayed based on the matched target component template (adding a target component while removing the first component). This ensures the stability of the core data (locked fields) of the target process during workflow. Simultaneously, it can adjust the display of other fields according to the matched business scenario, effectively purifying interface elements and avoiding information redundancy. It ensures that the workflow application page always displays only the necessary and effective field components for the current stage, reducing the user's cognitive load and minimizing the performance overhead of rendering unnecessary components on the front end, thereby improving page loading efficiency and operational clarity.

[0117] In one possible implementation, the target component is any component in the target component template that needs to be displayed, excluding the locked component and the component corresponding to the second field; the second field is any field in the process application page that is filled in, excluding the locked field; S403 can be implemented as follows: add the target component to the process application page and output the updated process application page so that the updated process application page includes the locked component, the component corresponding to the second field, and the target component.

[0118] The second field, excluding the locked fields, consists of fields that have already been filled in. Its components already include the user's input. Removing it or replacing it with a new component when updating the process application page would erase all the user's completed work. Users might then need to re-enter these fields, resulting in repetitive work and wasted time, severely damaging user confidence and potentially causing them to abandon the process due to its cumbersome operation. Furthermore, the filled second field often contains crucial contextual information for matching the component template. Clearing the second field could lead to completely incorrect field sets or prevent the process from continuing, disrupting the consistency and integrity of the business process.

[0119] Therefore, when determining the target fields, it is necessary to first identify the locked fields and already filled second fields (such as the leave type selected by the user) on the page. Then, based on all fields configured as "displayable" in the target component template of the matching component, the previously existing "locked fields" and "second fields" are removed from this set. Finally, the remaining fields are determined as the "target fields" that need to be added and displayed this time. Filled fields are not only input values, but also represent the user's filling process and the matching rules when matching component templates. Removing them will interrupt the user's process and may cause the system to calculate the wrong set of subsequent fields due to the loss of key context. Retaining them means presenting the current state of the form completely to the user, giving them a clear sense of control over their operation history, thereby providing a basis for the correct filling in of the next step.

[0120] For example, in the leave application process, the user first selects "Business Trip" as the "Leave Type" and then fills in the "Destination" and "Budget" in detail. Even if subsequent operations (such as modifying the date) match a new component template, the previously filled "Business Trip" related information will not be cleared or hidden, and the user does not need to fill it in again.

[0121] In this implementation, when determining the target field, locked fields and second fields with content already filled in by the user are excluded. This ensures that the updated page retains locked components, user-filled components, and the target component to be added simultaneously. This fully respects the user's completed input, avoids duplicate entries, and ensures both process continuity and data integrity. It not only improves the accuracy of interface updates but also enhances user experience and satisfaction in multi-step processes.

[0122] In one possible implementation, before outputting the updated process application page, the method further includes: if the process application page displays a component with a third field, then remove the component with the third field from the process application page; the third field is any field in the field corresponding to the component displayed on the process application page, excluding the locked field, the second field, and the target field.

[0123] The third field, excluding the locked field, the filled second field, and the target field, will be removed from the process application page. In other words, when updating the process application page, the components corresponding to the locked field and the filled field need to remain in the display state. The composition, display state, or default value of the remaining fields (including the target field and the third field) will be refilled and presented according to the rules defined in the currently matched target component template.

[0124] For example, when component template 1 is matched, the fields displayed on the process application page may include: Field 1 (locked field), Field 3 (target field corresponding to component template 1), and Field 4 (target field corresponding to component template 1). After Field 1 and Field 3 are filled in, component template 2 is matched. In component template 2, the display state of Field 4 is hidden, and the display state of Field 2 is shown. At this time, the updated process application page includes: Field 1, Field 2, and Field 3, and Field 4 is removed.

[0125] This implementation removes all field components except those explicitly defined as "locked field, second field, and target field." This ensures that the application interface always presents only three absolutely necessary elements: those the user requested to lock, those the user has already filled out, and those displayed according to the currently matched component template. This avoids interference from outdated, redundant, or irrelevant field components, ensuring a highly focused interface, optimizing visual presentation, and improving front-end performance by removing unnecessary component listeners and rendering.

[0126] It should be noted that this application embodiment does not limit the method of determining the target component. For example, after determining the target component template, the field structure of the target field can be determined first, and then the attribute information of each field (such as field name, data type, validation rules, display format, etc.) can be clarified to provide a basis for subsequent component generation. Then, the corresponding target component is generated based on the attribute information of the field. According to the attribute mapping rules of the field, each field is converted into an interactive component in the process application page. For example, the "start and end time" field corresponds to a date picker component, "leave type" corresponds to a drop-down selection box component, "approver" corresponds to a personnel selection component, etc. Finally, the process application page is updated and rendered. All generated target components are integrated into the DOM structure of the process application page, replacing the old components or blank areas that do not match in the original page. During the update process, it is also necessary to associate the interaction logic of the components (such as field linkage, form validation triggering) to ensure that the page not only displays the correct components, but also responds normally to user operations (such as input, selection, submission, etc.). After the update is completed, the updated process application page is output to the display device. Display devices can use the front-end rendering engine to present new pages to users, achieving precise matching between the process application page and the target component template.

[0127] In some embodiments, the component template also includes a required field status for each field. Therefore, as an implementation, when updating the application page, the required field status of the target field can be synchronously updated on the page. The target component template will clearly indicate whether a field is required, and the page will provide visual indications. For example, a red required field symbol can be added next to the component label, and the required field attribute can be integrated into the form validation logic. When a user attempts to submit or proceed to the next step without filling in the required field, a corresponding error message will be triggered, informing the user that the required information needs to be completed. Simultaneously, validation interception will be added to the submit or next step button logic, preventing the process from progressing if the required field is not filled in, thereby ensuring the integrity of data at each stage.

[0128] As can be seen from S401-S403, the process processing method provided in this application embodiment, after receiving the application operation of the target process, displays the locking components corresponding to the locked fields on the process application page, that is, displays some fields that must be displayed for the user to fill in. Then, after the user fills in the content, the component template is matched in real time according to the field content filled in by the user, so as to adjust the display status and / or mandatory status of subsequent fields through the matched target component template, without having to display all fields on the process application page. In this way, the fields are presented on demand, reducing the input delay and errors from the source, thereby improving the data input efficiency in the process submission process. This ensures that the process can flow quickly and accurately to the subsequent links, thereby enhancing the smoothness of the business process and providing highly adaptable technical support for complex and ever-changing online scenarios.

[0129] In some embodiments, the process processing method provided in this application further includes: S404, in response to receiving the creation instruction of the target process, creating the target process based on the field content filled in the process application page.

[0130] The fields filled in during the initial input phase are only in a temporary editing state. If the user does not submit, the information may be lost due to page closure, system cache clearing, etc. Therefore, after completing the input, the user needs to perform a confirmation operation, such as clicking the "Confirm Submission" control on the process application page. At this point, the computing device can confirm that it has received the creation instruction for the target process. Therefore, after receiving the creation instruction, the computing device needs to integrate the information filled in by the user into a complete process data model, persist it to the database, and thus officially create a target process with a status of "In Progress," laying the foundation for subsequent approval workflows.

[0131] In some embodiments, each component template corresponds to a component matching rule; the component matching rule represents the component matching condition corresponding to the first weight field among multiple fields involved in the weight configuration. The component matching rule (composed of the first weight field and the component matching condition) defines "how to determine whether the user's current input matches this scenario". For example, the matching rule for the "strategic project change" scenario might be set as follows: the first weight field is "project level", and the component matching condition is "project level = strategic level". When the user's input "project level" meets this condition, it will be determined that the current scenario matches the template, and then the display rule of the template will be called, that is, the specific required fields such as "senior approval opinion" will be displayed.

[0132] The first weight field is a key field selected from multiple fields in the target process that directly affects the template matching degree (weight). Its core feature is that it "participates in weight configuration." That is, only the user input content in these fields will be included in the template matching calculation; input from non-first weight fields does not affect the template weight result. The component matching condition is a specific judgment rule preset for each first weight field, used to clarify "under what conditions the user input content meets for the field to be considered a match with the current template."

[0133] As a feasible implementation method, the corresponding template weight of each component template can be determined in the following way: S4021. Based on the filled-in field content, match it with the component matching conditions of each first weight field of the corresponding component template, and determine the weight corresponding to each first weight field based on the matching results.

[0134] The computing device first extracts the specific content of the filled fields, and then compares them one by one with the preset matching conditions of the first weight field in each component template. Based on the degree of matching (such as complete match, partial match, or no match), a corresponding weight value is assigned to each first weight field, thereby quantifying the degree of fit between the field content and the template conditions, laying the foundation for the subsequent calculation of template weights.

[0135] As a feasible implementation method, the configuration range of component weights can be divided into: exact match, range match, fuzzy match, and no match, with the weight scores decreasing sequentially. Among them, exact match receives the highest score because it completely meets the conditions, reflecting its optimal adaptability; range match and fuzzy match scores decrease accordingly, corresponding to cases where the conditions are partially met; while no match is set to an extremely low negative score, which can directly exclude it from being a priority option. This scoring rule can efficiently distinguish the weight differences of different matching states.

[0136] For example, as a specific implementation, the corresponding weight scores can be 4, 2, 1, and -999, respectively. This scoring configuration method not only conforms to the logic that the degree of matching is positively correlated with the weight, but also can quickly filter out invalid matches through significant score differences (such as -999 for unmatched matches), reducing interference in subsequent calculations. It should be understood that the score of each weight can be adjusted according to the actual scenario, but its core is to make the calculation results of component weights more closely match the matching accuracy requirements in actual business through gradient scoring design, providing a clear quantitative basis for template selection. This application does not impose specific restrictions on the scores of the weights.

[0137] S4022. Determine the template weight corresponding to the component template based on the weight corresponding to each first weight field.

[0138] Based on the weights of the first weight field obtained in S4021, the overall weight of the component template is calculated. Typically, a preset algorithm (such as weighted summation or taking the maximum value) is used to integrate the weights of each first weight field, ultimately yielding the template weight corresponding to the component template. This provides a clear indication of the overall matching degree between the component template and the filled-in field content, offering crucial information for subsequent template selection or priority ranking.

[0139] As can be seen from S4021 and S4022, by integrating the weight of the first weight field in the template matching rule to form the overall template weight, the template adaptability can be upgraded from a scattered field evaluation to an intuitive overall quantitative result, so that the selection of subsequent component templates not only meets the core business needs, but also has the characteristics of efficiency, objectivity and reusability.

[0140] In some embodiments, to better adapt to diverse business scenarios, users can pre-configure multiple component templates, each tailored to specific scenario requirements (such as different types of approval and application processes). This facilitates computing devices in quickly calling the matching template in different scenarios, eliminating the need to repeatedly build page structures. This satisfies the differentiated requirements of personalized business for field combinations (such as project applications requiring "budget details," while daily expense reimbursements focus on "consumption vouchers"), while also improving process reusability and response efficiency through standardized template configuration.

[0141] In some embodiments, there may be situations where none of the component templates meet the preset matching degree. Therefore, in practical applications, a default component template can be set in advance. When the target component template cannot be matched, the default component template can be used as the target component template, thereby ensuring that the process application page can be updated and displayed normally.

[0142] As a feasible implementation method, the process processing method provided in this application embodiment further includes: when the matching degree represented by the template weight in multiple component templates does not meet the preset matching degree, updating the process application page based on the default component template.

[0143] For example, as a feasible implementation, the component matching condition corresponding to the first weight field in the component matching rules of the default component template can be set to accept any input (such as setting it to "all" or a wildcard). With this configuration, the default template can be automatically triggered when other dedicated templates are not applicable, thereby ensuring that the process application page can be updated and displayed normally.

[0144] In this embodiment, by setting a default component template as a fallback mechanism, it is ensured that the system can still run stably and display the page normally when there is no dedicated template to match, which effectively improves the robustness of the process processing system and the continuity of user experience.

[0145] In some embodiments, the different fields entered by users are associated with distinctly different business processes. For example, software development projects, due to frequent requirement changes, are typically delivered using an agile model. Based on this characteristic, change management is often delegated directly to full-function teams. Hardware development projects, due to large hardware investments and high upfront design costs, often employ a waterfall model. Changes have a wide impact, so change reviews are generally required before notifying relevant parties. Engineering construction projects involve even larger investments and broader coordination, typically establishing change review committees to systematically address various changes during the project process. Therefore, different approval processes can be pre-set so that when submitting updated process request fields, different approval processes can be matched based on the field content.

[0146] As a feasible implementation method, the method provided in this application embodiment further includes: S501. Determine the multiple sub-processes corresponding to the target process.

[0147] The sub-process is used to represent the approval object and / or approval rules of the target process. The approval object is used to define the specific approval object, which can be a specific person (such as "Project Manager Li X"), a role (such as "Department Director"), or an organization (such as "Finance Department"). The approval rules are used to define the rules and conditions that trigger the approval step, such as "When the number of leave days is greater than 3 days, the process must be routed to the Human Resources Department for approval".

[0148] As a feasible implementation method, since the target process can only be triggered after the user has filled in the information on the process application page, S501 can be specifically implemented as follows: in response to receiving the creation instruction for the target process, determine the multiple sub-processes corresponding to the target process. It should be understood that the specific implementation method of the creation instruction for the target process can refer to S404 above, and will not be repeated here.

[0149] The computing device needs to determine all possible sub-processes that may be triggered based on the business function represented by the target process. For example, a main process of "project change" may have multiple different sub-processes pre-defined based on its business characteristics, such as "direct handling by the agile team", "review by the change review meeting", and "reporting to the change control committee".

[0150] It should be noted that this application embodiment does not restrict the pre-configuration process of sub-processes. In actual application, staff can set the approval object and matching rules for each sub-process according to their needs. This allows the entered content to be sent to the approval object defined for that sub-process after the sub-process is matched according to the matching rules.

[0151] As one implementation method, sub-processes can also be used to define validation rules when submitting the process. That is, the application is only sent to the approval object if the entered content meets the validation rules.

[0152] For example, the matching rule for the sub-process could be: the heavyweight team is the Computing Power Business Unit, and all other matching fields are ALL. The process is set to first check if the item exists in the wide table; if it does, the development representative is set as the approver. In this case, if the user enters information stating that the heavyweight team is the Computing Power Business Unit, this rule will match. Then, the rule "first check if the item exists in the wide table" needs to be validated; if it does, it is sent to the development representative for approval.

[0153] S502. For each sub-process, based on the field content filled in on the updated process application page, match it with the process matching rules corresponding to the sub-process to obtain the process weight corresponding to the sub-process.

[0154] Among them, the process matching rule is used to characterize the process matching condition corresponding to the second weight field that participates in the weight configuration among multiple fields, and the process weight is used to characterize the degree of matching between the corresponding subprocess and the filled field content.

[0155] For each sub-process identified in the previous step, a matching degree calculation is performed. This involves comparing the fields currently filled in by the user on the application page with the matching rules corresponding to each sub-process. These matching rules define the key secondary weight fields and their matching conditions. By calculating the matching results of all key fields, a process weight score is derived for each sub-process. This score directly represents the degree to which the sub-process matches the application content currently filled in by the user in the relevant business scenario.

[0156] As one implementation method, S502 can be implemented as follows: for each sub-process, based on the field content filled in on the process application page, match it with the process matching conditions of each second weight field, and determine the weight corresponding to each second weight field based on the matching results; determine the process weight corresponding to the sub-process based on the weight corresponding to each second weight field.

[0157] For each sub-process, the actual content entered by the user on the current process application page is compared with the preset "process matching conditions" for each second weight field in the sub-process's process matching rules, thereby deriving an independent, quantified matching weight for each field. This weight reflects the degree to which the user's input matches the ideal conditions for that field.

[0158] Subsequently, based on the weights of these individual second weight fields, the final overall "process weight" of the sub-process is calculated using predefined aggregation rules (such as weighted average, maximum value, or logical combination). This process weight is a comprehensive quantitative indicator that characterizes the suitability of this sub-process as a processing path in the current user input business scenario, providing accurate data for selecting the optimal sub-process.

[0159] It should be understood that the specific calculation method for process weights can refer to the calculation method for template weights in the above embodiments. That is, the process weight configuration range only includes exact match, range match, fuzzy match (ALL), and no match, and their corresponding weight scores can be 4, 2, 1, and -999, respectively. This application will not elaborate further here.

[0160] S503. Process the target process based on the approval objects and / or approval rules indicated by the target sub-process that meet the process weight conditions.

[0161] The computing device compares the weight scores of all sub-processes and automatically selects the sub-process whose weight meets the criteria as the target sub-process. It should be understood that meeting the criteria for process weight can mean that the sub-process has the highest weight score of one or more, or that the sub-process's weight score is higher than or equal to a preset threshold, or that the sub-process's weight score is higher than the weight scores of all other candidate sub-processes by a preset difference / proportion. This application embodiment does not limit this.

[0162] The entire application for the target process (i.e., all fields filled in on the updated page) will be submitted and processed according to the approval objects and / or approval rules indicated by this optimally matched sub-process. This ensures that each user's application is guided to the most suitable and efficient business processing path.

[0163] As can be seen from S501-S503, the solution provided in this embodiment transforms the originally fixed approval path into an objective, quantifiable, data-driven process by pre-setting multiple sub-processes and process matching rules for each sub-process. By calculating and comparing the "process weight" of each sub-process, the target sub-process that meets the matching conditions of the current business scenario can be accurately identified from multiple candidate sub-processes. The target process is then processed based on the approval object and / or approval rules indicated by the target sub-process, without the need for manual intervention. This significantly shortens the distribution time at the front end of the process and improves the overall processing efficiency.

[0164] The following example illustrates the process handling method provided in the embodiments of this application.

[0165] S1. Staff pre-create component templates for the project coding application process.

[0166] Assume the project coding application process includes four fields: Project Type, Project Nature, Project Level, Human Resources Budget, and Key Team. Staff can then pre-configure three component templates on the computing device. In the first component template, all first-weighted components have all weight matching conditions set to "All," serving as the default template. The second component template sets the first-weighted components to "Project Type, Project Nature, Project Level," with weight matching conditions of "Project Type: Innovation Incubation, Project Nature: Self-developed, Project Level: Level 1." Human Resources Budget is optional; other fields are the same as the default template. The third template sets the Key Team to the Computing Power Business Unit, and all other project requirements are set to "All," with the baseline set to "Show" (other business units are hidden by default).

[0167] S2, a sub-process of the staff creating a project code application process.

[0168] To facilitate the management of multiple sub-processes, the project coding application process can be viewed as a parent process. This parent process acts as a unified logical container, not handling specific business rules. Its core responsibility is to define the entry point and host a set of potential sub-processes. Each sub-process represents a specific approval path and rules within a particular business scenario.

[0169] Specifically, staff can pre-set the following three sub-processes in the computing device: Sub-process 1: All heavyweight components are set to "All" and the development representative is set as the approver. This is the default sub-process. Sub-process 2: The heavyweight team is set to the Computing Power Business Unit, and all others are set to "ALL". The process is to first check if the project exists in the wide table; if it does, the development representative is set as the approver. Sub-process 3: The heavyweight team is set to the City Enterprise Business Unit, and the PMO is set as the approver.

[0170] S3. The user begins the project coding application process.

[0171] Users can trigger the application control corresponding to the project coding application process to open the corresponding process application page. On the initial process application page, locked components are displayed by pre-filtering locked fields from multiple component templates, allowing users to fill in information based on these locked components.

[0172] When the amount of information entered is limited, the computing device will match the first component template because all the weight matching conditions for the first weighted components of the first component template are set to "all". This means the default template will be automatically loaded. When the user selects "Innovation Incubation", "Self-developed", "Level 1", and "Heavyweight Team" as the Computing Power Business Unit, multiple component templates are weighted and scored. The weights for the three template components are 8, 17, and 13, respectively. At this point, the computing device can select the second component template according to the rules, and the application page will automatically change the "Human Resources Budget" field from mandatory to optional as defined by the second component template.

[0173] S4, User Submission Process.

[0174] After the user fills in all the data on the page and clicks submit, the computing device can automatically match all the sub-processes under the parent project coding application process and automatically score and select the sub-processes. The scores of the three sub-processes are as follows: 8, 13, and -992. Based on the weight, sub-process two is returned, and the process nodes set in sub-process two are executed downwards.

[0175] As can be seen, the solution provided in this application, by introducing a weighted calculation mechanism, enables the system to dynamically adjust the display status and required attributes of page components within the same template framework based on combinations of different project attributes, achieving a high degree of configuration flexibility. This solution supports the smooth expansion of business requirements; when new project attributes or business rules are added, only the corresponding weighted rules need to be updated to complete the adaptation, without modifying the underlying system logic. Simultaneously, by abstracting business logic into configurable templates and weighted rules, centralized management and maintenance of the interface logic are achieved, greatly improving the maintainability of the system. Furthermore, functional components and processes have good isolation, with each template corresponding to independent matching rules, effectively avoiding the impact on the overall system stability caused by adjustments to local components.

[0176] This application also provides a page display method, which can be applied to... Figure 1 The computing device shown can also be applied to other computing devices, and this application does not limit this application. Please refer to... Figure 7 The methods for displaying this page include: S701. In response to receiving a display instruction for the target page, obtain the project information of the project to which the target page belongs.

[0177] When a user requests to open a target page (such as the display page of the project to which the target page belongs), it is necessary to proactively obtain the "project information" of the target project that is closely related to the current page context. This information is the objective data basis for subsequent page matching. The project information can contain multiple predefined fields (such as project type, current status, key attributes, etc.) and their corresponding field contents, ensuring that the page rendering decision is based on real business data.

[0178] For example, in a "Software Development Project Details Page," project information might include the following fields and their specific contents: coding stoppage date (content: "2023-06-30"), suspension / suspension date (content: "2023-03-15"), actual start date (content: "2022-08-01"), and actual end date (content: "2024-05-20"). These fields collectively constitute a complete dataset describing the project, providing concrete data support for the dynamic rendering of the page.

[0179] S702. Match the field content based on the project information with each page component template in multiple page component templates to determine the page weight corresponding to each page component template.

[0180] The page component template represents the target project category and the display status of each field within that category. Each project category (e.g., R&D projects, operations and maintenance projects, marketing activity projects) has one or more pre-configured page component templates. These templates do not contain specific data but define the display rules for all fields within that category. When displaying project information for the target page, multiple page component templates corresponding to the target project's category are determined. Then, according to the matching conditions set for each page component template, the content of the project information obtained in the previous step is matched and calculated, outputting a quantified "page weight" for each template. This weight value objectively represents the applicability of using that template to display the page under the current project information. It should be understood that the calculation method for page weight can refer to the calculation methods for template weight and process weight in the above embodiments, and will not be repeated here.

[0181] For example, the target project category may have multiple fields including: coding discontinuation date, suspension / suspension date, actual start date, and actual end date. The page component template would then define the coding discontinuation date and suspension / suspension date fields to be displayed, while the actual start date and actual end date fields would be hidden.

[0182] As one implementation approach, since the page component template is only used to determine whether each field needs to be displayed, it can be used solely to set the display status of each field. It should be understood that the creation process of the page component template can refer to the above S201-S203, and will not be repeated here.

[0183] S703. Based on the target page component template whose matching degree, represented by the page weight in multiple page component templates, meets the preset matching degree, output the target page.

[0184] The page weights calculated from all templates are evaluated, and a "target page component template" is selected based on preset rules (such as selecting the template with the highest weight). Then, the target page is dynamically rendered according to the rules defined in this target template (i.e., the display status of each field), thereby achieving differentiated display of the same page in different project scenarios.

[0185] For example, an administrator creates a component template for the "Project Basic Information View Page." The rule sets that when the project type is "Management Improvement Project" and the project workflow is "Management Improvement Project Workflow," the fields for "Code Deactivation Date," "Suspension / Suspension Date," "Actual Start Date," and "Actual End Date" will be hidden. When a user fills in fields that match the above conditions (i.e., match this template) on the workflow application page, these four hidden fields will not be displayed on the project's details page.

[0186] As one implementation method, S703 can be specifically implemented as follows: based on the target page component template and the field content of the project information, output the target page. That is, the target page not only needs to determine the display status of each field according to the target page component template, but also needs to populate it according to the field content. Specifically, it is necessary to first determine the display status of each preset field in the current context according to the rules defined in the target page component template; secondly, for the fields determined to be displayed, their corresponding field content (i.e., specific data values) needs to be extracted from the project information and populated into the page component. For example, for the field "Actual End Date," if the template rules determine that it should be in the "Display" state, then the specific value of "Actual End Date" from the project information (such as "2024-05-20") needs to be further filled into the corresponding date display component of the page, thereby forming a visual page with complete data and correct status.

[0187] It should be noted that the output target page can be output to a display device used to display the target page. The computing device can send structured data describing the page state to the display device, enabling the display device to call the corresponding UI components to render the target page in real time based on this data. Alternatively, the computing device can render the target page based on this data and then send it to the display device for display to the user. This application embodiment does not limit the method of outputting the target page.

[0188] The solution provided in this embodiment, when displaying field content of project information, does not rigidly apply a single template, nor does it display all content. Instead, it calculates the matching degree between the specific content (field content) of the current project and multiple alternative templates, and automatically selects the template with the highest matching degree. This ensures that the final rendered page is the version that best fits the actual situation of the project and carries the most effective information, achieving intelligent and accurate page rendering and ensuring that the output page is most closely aligned with the actual project situation. At the same time, by introducing "page weight" as a quantitative indicator of matching degree, it can flexibly handle situations with diverse project information and complex business scenarios, thereby better adapting to scenario changes. For example, when adding a new business scenario, only the corresponding new template needs to be added without modifying the core matching logic, thus significantly improving the relevance and accuracy of the output results while ensuring efficiency.

[0189] In some embodiments, there may be situations where none of the page component templates meet the preset matching degree. Therefore, in practical applications, a default page component template can be set in advance. When no matching page component template can be found, the target page can be displayed based on the default page component template.

[0190] In an exemplary embodiment, please refer to Figure 8This application also provides a process processing device 60, which may include: an engine calling module 61, a weight configuration module 62, a component template module 63, and a process template module 64.

[0191] Among them, the engine call module 61 serves as the core interaction hub of the device. It is responsible for receiving front-end call requests and triggering subsequent processing flows, coordinating the call weight configuration module and component template module to obtain default component templates and weight configuration information, calling the process engine to connect the entire business process, completing component rendering and user data collection, and finally scheduling the process engine to complete the process advancement based on the process data.

[0192] The weight configuration module 62 manages the weight configuration of various attributes in the system, ensuring reasonable and effective configuration, and provides an interface for obtaining weights. The component template module 63 manages component templates, supports defining template content through configuration, responds to template retrieval requests from engine-calling modules, and provides corresponding component templates. The process template module 64 manages process templates uniformly based on a parent-child relationship structure, supports flexible configuration of process template content, responds to requests to retrieve process templates based on component values, provides process template support to the process engine, and serves as the core input of the process engine.

[0193] As can be seen, the engine invocation module 61 is the coordinating module for the other modules, connecting the other three independent modules. In practical applications, the engine invocation module 61 can calculate the weight score of each template based on the real-time values ​​entered on the page, according to the template and weight module. Based on the score, it can match and select the corresponding component or process template and return it to the front-end page to re-render the page.

[0194] In some embodiments, to avoid the difficulty in managing lock fields across multiple component templates, a lock field can be set in the default component template.

[0195] For example, please refer to Figure 9 Upon receiving an application request triggered by the front-end interface, the engine invocation module 61 can obtain the default component template from the component template module 63. The component is then rendered using the default component template to display the process application page. After the user fills in the fields on the process application page, the engine invocation module 61 obtains the template weight of each component template through the weight configuration module 62, and then obtains the target component template based on the weight. The process application interface is then updated using the target component template, i.e., the component is re-rendered. This process continues until the user completes the submission and the process is completed. The target process template can then be obtained from the process template module 64 based on the user's input, and the process is processed according to the instructions in the target process template.

[0196] In an exemplary embodiment, this application also provides a process processing apparatus. This process processing apparatus may be a computing device that performs the aforementioned process processing method, or it may be a processor within a computing device. The process processing apparatus may include one or more functional modules for implementing the process processing method of the above method embodiments.

[0197] In an exemplary embodiment, this application also provides a page display device. The process processing device may be a computing device that executes the aforementioned process processing method, or it may be a processor within a computing device. The page display device may include one or more functional modules for implementing the page display method of the above method embodiments.

[0198] This application also provides a computing device. Figure 10 This is a schematic diagram of the architecture of a computing device provided in an embodiment of this application. Figure 10 As shown, the computing device 100 includes: one or more memories 120, one or more processors 110, a communication bus 140, and a communication interface 130. The processors 110 and memories 120 are connected via the communication bus 140. The one or more memories 120 are used to store computer program code, which includes computer instructions. When the one or more processors 110 execute the computer instructions, the computing device 100 performs the process processing method or page display method provided in this embodiment.

[0199] Optionally, the memory 120 may be a non-transitory computer-readable storage medium, such as a read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc. The embodiments of this application do not impose any limitations on this.

[0200] The processor 110 may be a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof, and the embodiments of this application do not impose any limitations on this.

[0201] The communication bus 140 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. This communication bus 140 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 10 It is represented by a single thick line, but this does not mean that there is only one bus or one type of communication bus.

[0202] Communication interface 130 uses any transceiver-like device for communicating with other devices or communication networks, such as control systems, radio access networks (RAN), wireless local area networks (WLAN), etc.

[0203] It should be noted that the system architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0204] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware; for example, the related hardware can be a processor of a computing device. The program instructions can be stored in the above-described computer-readable storage medium, and when executed, they can implement the processes of the above method embodiments. The computer-readable storage medium can be memory. The above-described computer-readable storage medium can also be an external storage device, such as a hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc. Further, the above-described computer-readable storage medium can include both memory and external storage devices. The above-described computer-readable storage medium is used to store the above-described computer program instructions and other programs and data required by the above-described process processing method or page display method.

[0205] This application also provides a computer program product, which includes a computer program. When the computer program product is run on a computing device, it causes the computing device to execute any of the process handling methods or page display methods provided in the above embodiments.

[0206] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0207] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

[0208] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A process processing method, characterized in that, include: Upon receiving an application request for the target process, the process application page is output. The process application page is used to display the locking components corresponding to the locking fields; The locking component is used to receive field content input by the user for the locked field; The locking component is used to indicate a component that must be displayed on the process application page; In response to receiving field content input based on the application page of the process, the input field content is matched with each of the multiple component templates to determine the template weight corresponding to each component template; The component template is used to represent several field display rules corresponding to the target process. The display rules include: display status and / or required field status. The template weight is used to characterize the degree of matching between the corresponding component template and the input field content. Based on the target component template whose matching degree, represented by the template weight among the multiple component templates, meets the preset matching degree, an updated process application page is output; the updated process application page includes the locked component and the target component, and the target component is the component corresponding to each field that needs to be displayed in the target component template.

2. The method according to claim 1, characterized in that, The target components are all the components that need to be displayed in the target component template, excluding the locked component; Accordingly, the updated process application page is output based on the target component template whose matching degree, represented by the template weights among the multiple component templates, satisfies a preset matching degree, including: Based on the target component template, the component corresponding to the first field in the process application page is determined; the first field is the other fields besides the locked field and the target field among the fields corresponding to the component displayed in the process application page. If the process application page displays a component of the first field, then the component of the first field is removed from the process application page so that the updated process application page only includes the locking component and the target component.

3. The method according to claim 1, characterized in that, The target components are all the components that need to be displayed in the target component template, excluding the locked component and the component corresponding to the second field; the second field is the filled field among the fields corresponding to the components displayed on the process application page, excluding the locked field. The target component template, whose matching degree, represented by the template weight among the multiple component templates, meets the preset matching degree, outputs the updated process application page, including: Add the target component to the process application page and output the updated process application page so that the updated process application page includes the locking component, the component corresponding to the second field, and the target component.

4. The method according to any one of claims 1-3, characterized in that, Each component template corresponds to a component matching rule; the component matching rule is used to represent the component matching condition corresponding to the first weight field participating in the weight configuration; The process of matching the input field content with each of the multiple component templates to determine the template weight corresponding to each component template includes: For each of the aforementioned component templates: Based on the input field content, the component matching conditions of each first weight field of the corresponding component template are matched, and the weight corresponding to each first weight field is determined based on the matching results. The template weight corresponding to the component template is determined based on the weight corresponding to each of the first weight fields.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Identify multiple sub-processes corresponding to the target process; the sub-processes are used to represent the approval objects and / or approval rules of the target process; For each sub-process, the process weight is obtained by matching the field content filled in on the updated process application page with the process matching rule corresponding to the sub-process; wherein, the process matching rule is used to characterize the process matching condition corresponding to the second weight field participating in the weight configuration, and the process weight is used to characterize the degree of matching between the corresponding sub-process and the filled field content. The target process is processed based on the approval object and / or approval rules indicated by the target sub-process that meets the process weight conditions.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Obtain all fields required by the business functions corresponding to the target process; In response to the creation of a new template, a component template configuration interface is output; the component template configuration interface is used to configure the display rules of each field among all the fields. In response to receiving a confirmation command based on the component template configuration interface, the display rules configured based on the component template configuration interface are saved as the component template.

7. The method according to any one of claims 1-6, characterized in that, The response to receiving a request for the target process, outputting a process request page, includes: In response to receiving an application request for a target process, obtain multiple component templates that match the target process; Identify all locked fields in the multiple component templates that are in a locked state; The process application page is output based on the locking component corresponding to the locking field.

8. A method for displaying a page, characterized in that, include: In response to receiving a display instruction for the target page, obtain the project information of the project to which the target page belongs; The field content of the project information is matched with each page component template in multiple page component templates to determine the page weight corresponding to each page component template. The page component template is used to represent the display status of each field among the multiple fields corresponding to the target process; Based on the target page component template whose matching degree, represented by the page weight in the plurality of page component templates, meets the preset matching degree, the target page is output to the display device, and the display device is used to display the target page.

9. A computer program product, characterized in that, When the computer program product is run on a computing device, it causes the computing device to perform the method as described in any one of claims 1-7; or, causes the computing device to perform the method as described in claim 8.

10. A computing device, characterized in that, The computing device includes a processor and a memory; the processor is coupled to the memory. The memory is used to store computer instructions; The computer instructions are loaded and executed by the processor to enable the computing device to implement the method as described in any one of claims 1-7; or, to implement the method as described in claim 8.

Images