Data processing method, apparatus, device, and medium

Abstract

Embodiments of the present application provide a data processing method, device and equipment and a medium. The method comprises: displaying a template management page corresponding to a first operation object in an object management application; the first operation object refers to an object that is granted a template creation permission by a management object in the object management application; in response to a template creation operation in the template management page, creating a target approval template in the object management application, and sending the target approval template to objects in a candidate cluster; the candidate cluster is used to represent a template use range corresponding to the target approval template, and the target approval template is managed by the first operation object. By using the embodiments of the present application, the approval management efficiency of the approval template in the object management application can be improved.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a data processing method, apparatus, device, and medium. Background Technology

[0002] Enterprise management applications, as office tools for optimizing enterprise workflows, are gradually becoming daily office tools for various enterprises to improve administrative efficiency and accelerate workflows. Current enterprise management applications can digitize enterprise approval processes (e.g., leave applications, business trip applications, attendance record checks, etc.); however, the approval templates in current enterprise management applications are created and managed by enterprise administrators. When an enterprise is large and has a complex organizational structure, different teams may have different needs for approval templates. This requires enterprise administrators to create various types of approval templates to meet the approval scenarios of different teams. A large number of approval templates inevitably puts pressure on enterprise administrators in template management, thus affecting the efficiency of approval template management. Summary of the Invention

[0003] This application provides a data processing method, apparatus, device, and medium that can improve the approval management efficiency of approval templates in object management applications.

[0004] One embodiment of this application provides a data processing method, including:

[0005] The template management page corresponding to the first operation object is displayed in the object management application; the first operation object refers to the object that has been granted template creation permission by the management object in the object management application.

[0006] In response to the template creation operation on the template management page, a target approval template is created in the object management application and sent to the object in the candidate cluster. The candidate cluster is used to characterize the scope of use of the template corresponding to the target approval template, and the target approval template is managed by the first operation object.

[0007] One embodiment of this application provides a data processing apparatus, including:

[0008] The management page display module is used to display the template management page corresponding to the first operation object in the object management application; the first operation object refers to the object that has been granted template creation permission by the management object in the object management application.

[0009] The template creation module is used to respond to the template creation operation on the template management page, create the target approval template in the object management application, and send the target approval template to the object in the candidate cluster. The candidate cluster is used to characterize the template usage scope corresponding to the target approval template, and the target approval template is managed by the first operation object.

[0010] The device also includes:

[0011] A permission acquisition module is created to determine if the first operation object is added within the permission scope of the managed object, and to add a template management entry point for the first operation object in the object management application. The permission scope includes objects with template creation permissions in the group or organization to which the managed object belongs.

[0012] The management page display module is specifically used for:

[0013] In response to a trigger action on the template management entry point, the template management page indicated by the template management entry point will be displayed in the object management application.

[0014] The device also includes:

[0015] The module for canceling permissions is used to cancel the template creation permission of the first operation object if the managed object removes the first operation object within the scope of permissions enabled, and to delete the template management entry corresponding to the first operation object in the object management application.

[0016] The template creation operation includes template addition and template editing operations;

[0017] The template creation module includes:

[0018] The candidate template display unit is used to respond to the template addition operation in the template management page and display M candidate templates associated with the first operation object in the object management application; M is a positive integer.

[0019] The template editing unit is used to respond to template editing operations for M candidate templates, edit the candidate templates determined by the template editing operations, and obtain the target approval template.

[0020] The candidate template display unit includes:

[0021] The identifier acquisition sub-unit is used to respond to the template addition operation in the template management page, and to obtain the organization identifier information corresponding to the group organization and the operation identifier information corresponding to the first operation object in the object management application; the first operation object belongs to the group organization.

[0022] The recommended template acquisition sub-unit is used to obtain a recommended template associated with the industry information in the object management application if the organization identification information and the operation identification information pass the verification.

[0023] The candidate template determination subunit is used to obtain the configured template that matches the operation identification information. Based on the recommended template, the configured template, and the creation control, it determines M candidate templates associated with the first operation object and displays the M candidate templates. The creation control is used to represent the blank template in the object management application.

[0024] Specifically, the candidate template determination subunit is used for:

[0025] In the object management application, obtain the set of publishing templates corresponding to the organization identification information, and obtain the first object identifier set corresponding to each publishing template in the publishing template set; an object identifier in a first object identifier set has the permission to view the publishing template corresponding to that first object identifier set;

[0026] The publishing template corresponding to the first object identifier set to which the operation identifier information belongs is determined as the configured template that matches the operation identifier information.

[0027] The device also includes:

[0028] The identifier set acquisition module is used in object management applications to acquire the second object identifier set managed by the organization identifier information; the second object identifier set includes object identifiers corresponding to objects in the group organization;

[0029] The verification module is used to determine that the organization identification information and the operation identification information pass the verification if the second object identification set contains operation identification information and the permission opening scope includes the first operation object; the permission opening scope includes objects in the group organization that have template creation permissions.

[0030] The device also includes:

[0031] The verification failure module generates a permission error message if the organization identification information and operation identification information fail to pass verification. This message is then displayed in the object management application. The permission error message instructs the first operation object to reactivate the template creation permission.

[0032] The template editing unit includes:

[0033] The editing page displays a sub-unit, which is used to respond to template editing operations for M candidate templates. It identifies the candidate templates determined by the template editing operation as the templates to be processed and displays the editing page corresponding to the templates to be processed. The editing page includes a template information area, a template process area, and a template rules area.

[0034] The basic information input subunit is used to respond to input operations on the template information area and display the basic information of the template to be processed in the template information area.

[0035] The approval process setting sub-unit is used to respond to triggered operations for the template process area and to set up the template approval process for the template to be processed.

[0036] The approval rule setting sub-unit is used to respond to the triggered operation of the template rule area, set the template approval rules for the template to be processed, and determine the template to be processed, which includes the template basic information, template approval process and template approval rules, as the target approval template.

[0037] The template information area includes a name sub-area, an icon sub-area, and a control sub-area; the input operations include a first editing operation, a second editing operation, and a control addition operation.

[0038] The basic information input subunit is specifically used for:

[0039] In response to the first edit operation on the Name sub-region, display the template name entered in the Name sub-region.

[0040] In response to a second editing operation on the icon sub-area, display the template icon entered in the second editing operation in the icon sub-area;

[0041] In response to the control addition operation for the control sub-area, the control library in the object management application is displayed, the template control is added to the template to be processed from the control library, and the template name, template icon and template control are identified as the template basic information corresponding to the template to be processed.

[0042] Specifically, the basic information input sub-unit executes a response to the control addition operation for the control sub-area, displays the control library in the object management application, and adds template controls to the template to be processed from the control library.

[0043] In response to a control addition operation targeting a sub-region of the control, the control library in the object management application is displayed, and N controls are selected from the control library for the template to be processed; N is a positive integer greater than 1.

[0044] Combine the functions of the first and second controls among N controls to obtain a composite control, and identify the controls other than the first and second controls among the N controls as candidate controls;

[0045] Arrange the combo controls and candidate controls to obtain template controls, and add template controls to the template to be processed.

[0046] The approval process setting sub-unit is specifically used for:

[0047] Respond to triggered operations in the template process area, and set the process start node, approval object cluster, and copy objects for the template to be processed;

[0048] In response to the sorting operation for the approval object cluster, the order of the approval objects in the approval object cluster is adjusted to obtain the adjusted approval object cluster. The process start node, the adjusted approval object cluster, and the copied objects are identified as the template approval process corresponding to the template to be processed.

[0049] The approval rule setting sub-unit is specifically used for:

[0050] In response to a trigger operation targeting a template rule area, obtain the organizational structure of the group to which the first operation object belongs, and determine the grouping of the first operation object in the organizational structure as the template usage scope corresponding to the template to be processed;

[0051] Set up an approval exception handling strategy for the template to be processed, and define the template's scope of use and the approval exception handling strategy as the template approval rules corresponding to the template to be processed.

[0052] Optionally, the approval rule setting sub-unit is specifically used for:

[0053] In response to a triggered operation in the template rule area, display a list of objects in the group or organization to which the first operation object belongs;

[0054] In response to a selection operation on the object list, the object triggered by the selection operation is identified as the template scope corresponding to the template to be processed;

[0055] Set up an approval exception handling strategy for the template to be processed, and define the template's scope of use and the approval exception handling strategy as the template approval rules corresponding to the template to be processed.

[0056] The approval rule setting sub-unit is specifically used for:

[0057] The pending configurations, which include basic template information, template approval process, and template approval rules, are identified as templates to be published.

[0058] Obtain the second operation object from the group organization to which the first operation object belongs; the second operation object refers to the object that has been granted template creation permission by the managed object, and the permission priority of the second operation object is higher than the permission priority of the first operation object;

[0059] The template to be published is submitted to the second operation object, which reviews the template and determines the approved template as the target approval template.

[0060] The template creation module includes:

[0061] The template addition unit is used to respond to the release operation for the target approval template. Based on the template usage scope corresponding to the target approval template, the candidate cluster is determined, and the target approval template is added to the objects in the candidate cluster in the object management application.

[0062] The message sending unit is used to generate a template release message corresponding to the target approval template and send the template release message to the objects in the candidate cluster. The template release message is used to instruct the objects in the candidate cluster to submit an approval application based on the target approval template in the object management cluster.

[0063] One aspect of this application provides a computer device, including a memory and a processor. The memory is connected to the processor, the memory is used to store computer programs, and the processor is used to call the computer programs so that the computer device executes the method provided in one aspect of this application.

[0064] One aspect of this application provides a computer-readable storage medium storing a computer program adapted to be loaded and executed by a processor, so that a computer device having a processor performs the method provided in one aspect of this application.

[0065] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method provided in the above aspect.

[0066] In this embodiment, when a first operation object is granted template creation permission by a management object in an object management application, a template management page corresponding to the first operation object can be displayed in the object management application. The first operation object can then respond to the template creation operation on the template management page, create a target approval template in the object management application, and send the target approval template to objects in a candidate cluster. The candidate cluster represents the scope of use of the template corresponding to the target approval template, and the target approval template can be managed by the first operation object. Therefore, the management object can set template creation permission for the first operation object, enabling the first operation object to create target approval templates in the object management application and manage the target approval templates it creates. In other words, approval templates in the object management application can be jointly managed by the management object and other objects (e.g., the first operation object) that have been granted template creation permission by the managed object. This reduces the management pressure on the management object and improves the efficiency of approval template management in the object management application. Attached Figure Description

[0067] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0068] Figure 1 This is a schematic diagram of a network architecture provided in an embodiment of this application;

[0069] Figure 2 This is a schematic diagram of a data processing scenario provided in an embodiment of this application;

[0070] Figure 3 This is a flowchart illustrating a data processing method provided in an embodiment of this application;

[0071] Figure 4 This is a schematic diagram of a permission management page for a web page management entry provided in an embodiment of this application;

[0072] Figure 5 This is a schematic diagram of a permission management page for a terminal management entry provided in an embodiment of this application;

[0073] Figure 6 This is a schematic diagram of a candidate template provided in an embodiment of this application;

[0074] Figure 7 This is a diagram of an editing interface for basic template information provided in an embodiment of this application;

[0075] Figure 8 This is a diagram of the editing interface for a template approval rule provided in an embodiment of this application;

[0076] Figure 9a This is a diagram of the editing interface of a template approval process provided in an embodiment of this application;

[0077] Figure 9b This is an image of the editing interface for another template approval process provided in this application embodiment;

[0078] Figure 10 This is a schematic diagram of a preview interface of an approval template provided in an embodiment of this application;

[0079] Figure 11 This is a schematic diagram of the publishing interface of an approval template provided in an embodiment of this application;

[0080] Figure 12 This is a flowchart illustrating the setting of template creation permissions according to an embodiment of this application;

[0081] Figure 13This is a flowchart illustrating the creation of an approval template provided in an embodiment of this application;

[0082] Figure 14 This is a flowchart illustrating the editing process of an approval template provided in an embodiment of this application;

[0083] Figure 15 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application;

[0084] Figure 16 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0085] 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 of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0086] Please see Figure 1 , Figure 1 This is a schematic diagram of a network architecture provided in an embodiment of this application. Figure 1 As shown, this network architecture may include a server 10d and a user terminal cluster. The user terminal cluster may include one or more user terminals; the number of user terminals will not be limited here. Figure 1 As shown, multiple user terminals may specifically include user terminal 10a, user terminal 10b, and user terminal 10c, etc.; Figure 1 As shown, user terminal 10a, user terminal 10b and user terminal 10c can each connect to server 10d via the network so that each user terminal can interact with server 10d through the network connection.

[0087] Server 10d can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. User terminals 10a, 10b, and 10c can all include: smartphones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches and smart bracelets), smart voice interaction devices, smart home appliances (such as smart TVs), in-vehicle devices, and other electronic devices with object management functions.

[0088] like Figure 1 Any user terminal in the user terminal cluster shown can install an object management application. This object management application can refer to an office tool that can digitize approval processes, such as an enterprise management application. Through the object management application, the approval processes of groups and organizations (e.g., enterprises, departments, institutions, etc.) can be processed electronically. Management objects within the group (e.g., enterprise administrators) can create and manage approval templates in the object management application. Because objects within the group (e.g., enterprise employees) have diverse approval scenario needs (e.g., teams with different functions require different types of approval templates, and even different approval rules or processes need to be set for the same type of approval template), the management object cannot provide templates that meet all approval scenarios. Therefore, the management object can grant template creation permissions to some objects within the group; that is, the management object can distribute template creation work to all objects within the group, providing a more flexible approval experience for the group.

[0089] Among them, such as Figure 1 User terminal 10a can be the electronic device corresponding to the managed object, or a management device; user terminal 10b can be the electronic device corresponding to the object with template creation permissions, or an authorized device; user terminal 10c can be the electronic device corresponding to the object without template creation permissions. The object management application installed on user terminals 10a and 10b can include a template management entry point, through which approval templates can be created and managed. In other words, a template management entry point can be added to the object management application for objects with template creation permissions. The object management application installed on user terminal 10c does not include a template management entry point; that is, objects without template creation permissions cannot participate in the creation and management of approval templates. For example, after the managed object (enterprise administrator) of enterprise B1 sets template creation permissions for the head of department xx, a template management entry point can be added to the object management application logged in based on the head's account information. Server 10d can be a backend server for object management applications. Server 10d can be used to store relevant information about each object in the group organization (e.g., object identifier, whether it has template creation permission, etc.), the set of authorized objects that have been granted template creation permission, and the configuration information corresponding to each approval template in the group organization (e.g., template identifier, template name, template icon, template approval process, and template approval rules, etc.).

[0090] Please see Figure 2 , Figure 2 This is a schematic diagram of a data processing scenario provided in an embodiment of this application. For example... Figure 2As shown, the approval process for a group organization can be digitized through an object management application. This group organization can include K objects (K is a positive integer, such as 1, 2, ...), such as managed object 20a, object 20b, object 20c, and object 20d. Managed object 20a can be used to design and manage the electronic approval templates for this group object in the object management application. Assuming the group organization is a company, the K objects can be the employees included in that company. Managed object 20a can set template creation permissions for some or all non-managed objects (the remaining objects besides managed object 20a) in the group organization through the corresponding permission management entry in the object management application. That is, managed object 20a distributes template creation permissions to some or all non-managed objects in the group organization, allowing some or all non-managed objects to customize and create new approval templates. It should be noted that this permission management entry is only for managed object 20a in the group organization. For example, when logging into the object management application using the account information of managed object 20a, the permission management entry can be displayed in the object management application; when logging into the object management application using the account information of a non-managed object (such as object 20c), the permission management entry will be hidden in the object management application, that is, the permission management entry will not be displayed.

[0091] like Figure 2 As shown, managed object 20a can select a subset of objects from the group organization as the scope of permissions through the permission management entry point, i.e., set template creation permissions for the selected objects. The objects within this permission scope can be called the authorized object set 20e. If the authorized object set 20e includes objects 20b and 20c, it means that managed object 20a has set template creation permissions for object 20c. Object 20d does not belong to the authorized object set 20e, indicating that object 20d does not have template creation permissions. The authorized object set 20e (permission scope) can be submitted to server 20f along with the organization identification information (e.g., enterprise ID) corresponding to the group organization, the management identification information (e.g., user ID) corresponding to managed object 20a, and the first timestamp (the time point when the permission scope is set). Server 20f, upon receiving the authorized object set 20e, organization identification information, management identification information, and the first timestamp, stores them in database 20j.

[0092] When objects 20b and 20c have template creation permissions, a template management entry can be added to objects 20b and 20c in the object management application. For ease of description, the following description uses object 20b as an example. Figure 2As shown, when logging into the object management application using the account information of object 20b, a template management entry 20h can be added to the approval function of the object management application. When object 20b performs a trigger operation on the template management entry 20h in the object management application, it can respond to the trigger operation for the template management entry 20h and display the template management page 20g in the object management application. Through the control 20i in the template management page 20g, a new approval template can be created. In other words, the template management page 20g is a page added for objects with template creation permissions. Assuming that object 20b creates a new approval template A1 in the object management application through the control 20i in the template management page 20g and submits the information of the approval template A1 to the server 20f, the server 20f can store the information of the approval template A1 in the database 20j. The information of the approval template A1 can include the template identifier (template ID) of the approval template A1 and the configuration information of the approval template A1 (e.g., template name, template icon, template control, template approval process, and template approval rules, etc.). Optionally, after object 20b creates approval template A1, it can send approval template A1 to relevant objects in the organization. For example, the approval template rules can include the template usage scope corresponding to approval template A1. Objects in the template usage scope can be considered as relevant objects receiving approval template A1. In the object management application, approval template A1 can be added to objects in the template usage scope so that objects in the template usage scope can submit approval applications based on approval template A1 in the object management application.

[0093] For object 20d in an organization that does not have template creation permissions, when logging into the object management application using object 20d's account information, the approval function of the object management application can include a new application entry, an approved entry, and a submitted entry, but will not include a template management entry. For example, the application page 20d indicated by the new application entry can be displayed in the object management application. This application page 20d can include the approval templates published in the object management application (e.g., template 1, template 2, template 3, and template 4, etc.). Object 20d can submit an approval application through the approval templates displayed on the application page 20d.

[0094] In this embodiment of the application, the management object 20a can reduce the management pressure of the approval template by issuing template creation permissions to some objects in the group organization; by adding a template management entry for objects with template creation permissions in the object management application, the creation efficiency of approval templates in the object management application can be improved.

[0095] Please see Figure 3 , Figure 3This is a flowchart illustrating a data processing method provided in an embodiment of this application. It can be understood that this data processing method can be performed by a first operation object (such as...) with template creation permissions. Figure 2 The computer device used by object 20b in the corresponding embodiment executes the commands. This computer device can be a user terminal (e.g., ...). Figure 1 The corresponding embodiment's user terminal 10b), or a server (such as... Figure 1 The user terminal 10d in the corresponding embodiment may be a computer program product or a computer program (including program code), and this application does not limit this. Figure 3 As shown, the data processing method may include the following steps:

[0096] Step S101: Display the template management page corresponding to the first operation object in the object management application; the first operation object refers to the object that has been granted template creation permission by the management object in the object management application.

[0097] In this embodiment of the application, for a first operation object with template creation permissions, the template management page corresponding to the first operation object can be displayed in the object management application (e.g., ...). Figure 2 The template management page 20g in the corresponding embodiment; wherein, the first operation object can refer to any one of all objects for which the management object has set template creation permissions; the management object can refer to the group administrator of the group organization, which can include but is not limited to enterprises, units, institutions and departments, etc., and this application does not limit this, the first operation object and the management object belong to the same group organization; the object management application can refer to an office tool that digitizes the approval process of the group organization, and the template management page in the object management application can be used to create new approval templates, and can also be used to manage the approval templates created by the first operation object.

[0098] Setting template creation permissions for the first operation object is a prerequisite for the computer device to execute step S101. Therefore, this embodiment first describes the process of setting template creation permissions. The object management application can open a permission management entry point for the managed objects of a group organization. Through this permission management entry point, object creation permissions can be enabled, and the scope of permission can be set. For example, if the managed object can enable template creation permissions for all objects in the group organization, then the scope of permission can be all objects in the group organization; or if the managed object can enable template creation permissions for a specified object in the group organization, then the scope of permission can be the object specified by the managed object from the group organization. The permission management entry point can include a web page management entry point (web page management terminal) and a terminal management entry point (mobile management terminal). This permission management entry point is only open to managed objects within the group organization.

[0099] Please see Figure 4 , Figure 4 This is a schematic diagram of a permission management page for a webpage management entry provided in an embodiment of this application. For example... Figure 4 As shown, assuming the electronic device corresponding to the managed object is called the management device (which can be a user terminal), the web management entry point opened by the object management application for the managed object can display the permission management page 30a corresponding to the group organization in the browser of the management device. This permission management page 30a can display the application details of the group organization in the object management application. For example, the approval function in the group organization can be enabled or disabled through the control 30g in the permission management page 30a. The visible scope corresponding to the current managed object can be displayed on the permission management page 30a. This visible scope can refer to the management scope of the current managed object in the group organization. For example, if the visible scope is the organizational structure, it means that the current managed object can manage all objects in the group organization. The permission management page 30a can also display all managed objects within the visible scope. For example, objects A, B, C, and D in area 30b are all managed objects of the group organization. That is, the number of managed objects of the group organization can be one or more; this application does not limit the number of managed objects. Optionally, the visibility of the current managed object can be modified on the permission management page 30a. After the visibility is modified, the managed objects within that visibility range may also change accordingly.

[0100] like Figure 4 As shown, when a managed object has object creation permissions enabled, such as "Allow members to create approval templates," members (objects) in the team organization can create appropriate approval templates for their own team. The managed object can also set the scope of permissions (e.g., ...). Figure 2In the corresponding embodiment, the authorized object set 20e) can be used to determine all members (all objects in the group organization) as the scope of permission opening. When the management object wants to select some objects from the group organization as the scope of permission opening, it can perform a trigger operation on area 30c. The management device can respond to the trigger operation on area 30c and display the selection panel 30d. The selection panel 30d can display the list of members in the group organization. The current management object can select P objects from the list of members displayed on the selection panel 30d (for example, member 1, member 3, member 4, and member 7, etc., where P is a positive integer). After completing the selection operation, the management device can perform a trigger operation on the "OK" control 30e in the selection panel 30d. At this time, the management device can respond to the trigger operation on the "OK" control 30e, determine the P objects selected by the management object as the scope of permission opening, and display the P objects in the scope of permission opening in area 30f. The selection panel 30d can refer to a portion of the permission management page 30a, a subpage independent of the permission management page 30a, or a page accessed from the permission management page 30a. This application does not limit the display method of the selection panel 30d. Optionally, when the number of objects within the permission opening range exceeds a quantity threshold (which can be determined based on the page size of the permission management page 30a, for example, a quantity threshold of 5), the objects within the quantity threshold (e.g., 5 objects) can be displayed in area 30f, and the remaining objects within the permission opening range can be hidden. When the managed object performs a trigger operation on area 30f, all objects within the permission opening range can be fully displayed.

[0101] like Figure 4 As shown, on the permission management page 30a, you can also set up an application responsible object in the team organization. This responsible object can create and manage approval templates in the object management application; the permission management page 30a can also display the approval templates created by this managed object, and can also re-edit existing approval templates. New approval templates can be created in the object management application using the control 30h in the permission management page 30a.

[0102] Optionally, please see Figure 5 , Figure 5 This is a schematic diagram of a permission management page for a terminal management entry provided in an embodiment of this application. For example... Figure 5The management device 40a shown refers to the electronic device corresponding to the managed object. The managed object can launch the object management application installed on the management device 40a. By executing a trigger operation on the template management entry in the approval function of the object management application, the template management page 40b indicated by the template management entry can be displayed. The template management page 40b can display the published approval templates associated with the group organization in the object management application, such as group leave, travel application, group item application, leave, expense reimbursement, and procurement approval templates. It can also display the status of each approval template. For example, when the procurement approval template is marked as "disabled", it means that the procurement approval template is temporarily unavailable, that is, objects in the group organization cannot use the procurement approval template to submit approval applications. The template management page 40b can also include an "add template" control (also known as a creation control), through which new approval templates can be created.

[0103] In the object management application, a terminal management entry 40c (permission management entry) can be opened for the managed object. When the managed object performs a trigger operation on the terminal management entry 40c, the management device 40a can respond to the trigger operation on the terminal management entry 40c and display the permission management page 40d. The permission management page 40d can include controls 40e and 40f. Through control 40e, object creation permissions in a group organization can be enabled or disabled. When the managed object enables object creation permissions, such as "allow members to create approval templates", members (objects) in the group organization can create appropriate approval templates for their own team. The managed object can also set the permission scope, such as all members in the group organization. The operation of setting the permission scope is similar to the operation of setting the permission scope in the permission management page 30a corresponding to the aforementioned web page management entry, and will not be described again here. The managed object can reduce the management burden of approval templates by issuing template creation permissions to objects within the permission scope through the permission management entry.

[0104] Furthermore, when the scope of permissions set by the managed object includes the first operation object, or when a new first operation object is added within the scope of permissions, it can be determined that the first operation object possesses the template creation permission granted by the managed object. In the object management application, a template management entry can be added for this first operation object. The scope of permissions can include all objects in the organization that possess template creation permissions. When the first operation object performs a trigger operation on the template management entry in the object management application, the computer device (the electronic device used by the first operation device) can respond to the trigger operation on the template management entry, displaying the template management page indicated by the template management entry in the object management application. Where no approval templates have yet been created in the organization to which the managed object belongs, the display format of the template management page is as follows: Figure 2 The template management page shown is 20g. When the organization to which the managed object belongs has published approval templates, the template management page will be displayed as follows: Figure 5 The template management page 40b is shown. It should be noted that the object creation permission function corresponding to control 40c in template management page 40b can be enabled for the managed objects, but not for the first operation object. That is, the template management page for the first operation object can be as shown in template management page 40b, the only difference being that the object creation permission function corresponding to control 40c is unavailable. By adding a template management entry point for objects within the permission scope in the object management application, objects within the permission scope can quickly create new approval templates in the object management application, improving the efficiency of approval template creation.

[0105] Optionally, when the first operation object leaves the organization or undergoes a change in position within the organization, having template creation permissions for that first operation object becomes meaningless. In this case, the first operation object can be considered an invalid object, and therefore can be removed from the permission scope. If the managed object removes the first operation object from the permission scope, the template creation permission for the first operation object can be revoked, and the template management entry corresponding to the first operation object can be deleted from the object management application. Removing invalid objects from the permission scope can save memory space.

[0106] It should be noted that the aforementioned template management entry point can be pre-integrated into the framework of the object management application. This entry point is activated and displayed in the object management application only when an object in the group / organization has template creation permissions. When an object in the group / organization does not have template creation permissions, the template management entry point remains inactive and cannot be displayed in the object management application. In other words, when the first object being managed has template creation permissions set, there is no need to update the object management application, and the template management entry point can be directly displayed in the current object management application, reducing operational steps and saving time.

[0107] Step S102: Respond to the template creation operation in the template management page, create a target approval template in the object management application, and send the target approval template to the object in the candidate cluster; the candidate cluster is used to characterize the template usage scope corresponding to the target approval template, and the target approval template is managed by the first operation object.

[0108] In this embodiment, the first operation object can perform a template creation operation on the template management page. At this time, the computer device can respond to the template creation operation on the template management page and create a target approval template in the object management application. The newly created target approval template can be sent to objects in the candidate cluster. The template creation operation can include one or more operations, such as template addition and template editing operations, which are not limited in this application. The candidate cluster can be used to characterize the template usage scope corresponding to the target approval template. For example, during the creation of the target approval template, the template usage scope can be set for the target approval template (such as the department to which the first operation object belongs in the group organization, or the object specified by the first operation object). The target approval template can be managed by the first operation object, that is, the first operation object that creates the target approval template can also participate in the target approval template. The created target approval template can be sent to the objects within the template usage scope corresponding to the target approval template, and the target approval template can be added to the objects within the template usage scope in the approval workbench of the object management application.

[0109] Specifically, template creation operations can include template addition and template editing operations. The template management page corresponding to the first operation object can include an "Add Template" control or a "Create" control (such as...). Figure 2The control 20i in the template management page 20j shown can be called a template addition control, whether it is the "Add Template" control or the "Create" control. When the first operation object performs a trigger operation on the template addition operation, the computer device can respond to the template addition operation in the template management page (the trigger operation for the template addition operation) and display M candidate templates associated with the first operation object in the object management application. M is a positive integer, such as M can take the value 1, 2, ... Then, any template can be selected from the M candidate templates for editing to obtain the target approval template. If the first operation object performs an operation on any candidate template among the M candidate templates, the computer device can respond to the template editing operation for the M candidate templates and edit the candidate template determined by the template editing operation to obtain the target approval template. The template editing operation here can refer to the operation performed after selecting a candidate template from the M candidate templates and entering the editing page of that candidate template.

[0110] The process of obtaining M candidate templates can include: when a computer device performs a template addition operation on the template management page, it can obtain the organization identification information (organization ID, or enterprise ID if the organization is an enterprise) and the operation identification information (such as the ID of the first operation object, or operation object ID) corresponding to the group organization in the object management application. The first operation object belongs to the group organization. If the organization identification information and the operation identification information pass the verification, the recommended template associated with the industry information is obtained in the object management application based on the industry information corresponding to the organization identification information (specific recommended templates can be set for each different industry in the object management application). At the same time, the configured template (or existing template) matching the operation identification information can also be obtained. The configured template can refer to the published template that the first operation object can view among all the approval templates published by the group organization. Then, based on the recommended template, the configured template, and the creation control, M candidate templates associated with the first operation object are determined, and the M candidate templates are displayed, that is, the recommended template, the configured template, and the creation control are displayed in the object management application. The creation control is used to represent a blank template in the object management application.

[0111] Optionally, the computer device can obtain the set of publishing templates corresponding to the organization identification information in the object management application, and then obtain the first object identifier set corresponding to each publishing template in the publishing template set. An object identifier in a first object identifier set has the permission to view the publishing template corresponding to that first object identifier set. The publishing template corresponding to the first object identifier set to which the operation identification information belongs is determined as the configured template matching the operation identification information. This publishing template set includes all templates published in the organization. Each published template can correspond to a template scope of use. For example, if approval template A1 is for the entire organization, then the scope of use for approval template A1 is the entire organization, and the object identifiers corresponding to the objects within the template's scope of use can form the first object identifier set corresponding to approval template A1; or if approval template A2 is for a single department, then the scope of use for approval template A2 is the single department, and the object identifiers corresponding to the objects within the template's scope of use can form the first object identifier set corresponding to approval template A2. When a certain first object identifier set contains operation identifier information corresponding to the first operation object, it means that the first operation object has the permission to view the published templates corresponding to the first object identifier set, and the published templates can be identified as configured modules; similarly, published templates that the first operation object has the permission to view can be obtained from the published template set, and the published templates that have the permission to view can be identified as the configured templates corresponding to the first operation object.

[0112] Optionally, if the organization identification information and the operation identification information fail to pass the verification, a permission error message can be generated and displayed in the object management application. The permission error message is used to indicate that the first operation object needs to reactivate the template creation permission. If the first operation object has been removed from the permission scope, or if there are errors in the operation identification information and the organization identification information, the permission error message can be displayed.

[0113] Optionally, the verification process for operation identification information and organization identification information may include: obtaining a second set of object identifiers managed by the organization identification information in the object management application, the second set of object identifiers including object identifiers corresponding to objects in the group organization; if the second set of object identifiers contains operation identification information and the permission scope includes the first operation object, then it is determined that the organization identification information and operation identification information pass the verification; if the second set of object identifiers does not contain operation identification information, or the permission scope does not include the first operation object, then it is determined that the organization identification information and operation identification information fail the verification.

[0114] Please see Figure 6 , Figure 6 This is a schematic diagram of a candidate template provided in an embodiment of this application. For example... Figure 6 The current interface shown is template display page 50a, which displays M candidate templates corresponding to the first operation object. When the first user adds a control to a template in the template management page and triggers the operation, template display page 50a is displayed in the object management application. Template display page 50a can include controls 50c and 50d. Control 50c can be used to indicate adding a new approval template from the recommended templates, and control 50d can be used to indicate adding a new template from an existing template (a configured template). When the first operation object triggers control 50c, the template display page 50a displays the recommended template (the approval template displayed in area 50e) and the "Create New" control 50b (also called a creation control, used to represent a blank template in the object management application). When the first operation object triggers control 50d, the template display page 50a displays an existing template and the "Create New" control 50b. Optionally, the approval template, existing template, and "Create New" control 50b displayed in area 50e can also be simultaneously displayed on the template display page 50a. This application does not limit the display method of candidate templates. During the creation of the target approval template, by displaying the recommended template, the configured template, and the "Create New" control 50b to the first operation object, diverse choices can be provided to the first operation object. Template editing based on the recommended template and the configured template can improve the efficiency of approval template construction.

[0115] Optionally, during the construction of the approval template, M candidate templates are obtained. Based on actual needs, any one candidate template can be selected as the template to be processed, and this template can be edited to obtain the target approval template. The editing process of the template to be processed can include: responding to template editing operations on the M candidate templates, identifying the candidate template determined by the template editing operation as the template to be processed, and displaying the corresponding editing page for the template to be processed. This editing page can include a template information area, a template process area, and a template rules area. The template information area can be used to input basic template information (e.g., template name, template icon, template controls, template groups, etc.), the template process area is used to set the template approval process for the template to be processed, and the template rules area is used to set the template approval rules for the template to be processed. When the first operation object performs an input operation in the template information area, it can respond to the input operation in the template information area and display the basic template information corresponding to the template to be processed in the template information area; it can also respond to the trigger operation in the template process area and set the template approval process for the template to be processed; it can also respond to the trigger operation in the template rules area and set the template approval rules for the template to be processed, and determine the template to be processed containing the basic template information, template approval process, and template approval rules as the target approval template. In other words, when editing the template to be processed, the basic template information, template approval process, and template approval rules of the template to be processed can be set. It should be noted that the above traversal of the processing flow is only an example in this application. It is also possible to set the template approval rules first, then the template approval process, and finally the basic template information. This application does not limit the order in which the basic template information, template approval process, and template approval rules are set.

[0116] The following is combined Figures 7 to 11 The process of creating the template to be processed is described in detail.

[0117] Please see Figure 7 , Figure 7 This is a diagram of an editing interface for basic template information provided in an embodiment of this application. For example... Figure 7 As shown, when the first operation object is on the aforementioned Figure 6When the "Create New" control 50b (creation control) in the template display page 50a, or any recommended template, or any existing template (configured template) executes a trigger operation, the computer device (which can be the user terminal used by the first operation object) can respond to the trigger operation, refer to the template triggered by the first operation object as the template to be processed, and enter the editing page 60a of the template to be processed. This editing page 60a may include a name sub-area 60b, an icon sub-area 60c, a grouping sub-area 60d, a text editing sub-area 60d, and a control sub-area 60f. These sub-areas can be collectively referred to as the template information area. It should be noted that the above sub-areas are only one example of the template information area; the template information area may also contain only some of the above sub-areas, such as the name sub-area 60b, icon sub-area 60c, and control sub-area 60f. This application does not limit this.

[0118] The input operations in the template information area can include a first editing operation, a second editing operation, and a control addition operation. When the first operation object edits the template name in the name sub-area 60b, the computer device can respond to the first editing operation in the name sub-area 60b (i.e., the editing operation in the name sub-area 60b) and display the template name entered in the first editing operation in the name sub-area 60b, such as "Group Leave". When the first operation object edits the template icon in the icon sub-area 60c, the computer device can respond to the second editing operation in the icon sub-area 60c (i.e., the editing operation in the icon sub-area 60c) and display the template icon entered in the second editing operation in the icon sub-area 60c. When the first operation object performs a trigger operation on the "Add Control" control in the control sub-area 60f, the computer device can respond to the control addition operation on the "Add Control" control in the control sub-area 60f, display the control library 60i in the object management application, add template controls from the control library 60i to the template to be processed, and determine the template name, template icon, and template controls as the template basic information corresponding to the template to be processed. The control library 60i can include multiple controls, such as single-line text controls, multi-line text controls, number controls, date controls, date and time controls, duration controls, radio buttons, and checkboxes. Different controls correspond to different functions. The first operation object can add appropriate template controls to the template to be processed from the control library 60i according to the type of the template and the approval scenario. For example, when the first operation object selects a multi-line text control and a date control from the control library 60i, the computer device can add the multi-line text control and the date control to the template to be processed. It should be noted that when the first operation object performs a trigger operation on any recommended template or any existing template (configured template), the control library 60i can be directly displayed in the editing page 60a. When the first operation object performs a trigger operation on the "Create New" control 50b, the controls in the editing page 60a are empty. The control library 60i will only be displayed after the first operation object performs a trigger operation on the "Add Control" control in the control sub-area 60f.

[0119] Optionally, if the functionality of a single control in the control library 60i cannot meet the needs of the approval scenario, the first operation object can combine multiple controls in the control library 60i to obtain a combined control. For example, after the computer device responds to the control addition operation for the "Add Control" control in the control sub-area 60f, it can display the control library 60i in the object management application. In the control sub-area 60f, N controls can be selected for the template to be processed, where N is a positive integer greater than 1. Then, the first and second controls among the N controls can be combined to obtain a combined control. The controls other than the first and second controls among the N controls are determined as candidate controls. Then, the combined control and candidate controls can be arranged to obtain a template control, and the template control is added to the template to be processed. For example, suppose the template to be processed is a leave application template. The first control is a date control, and the second control is a selection control. By combining the functions of the date control and the selection control, a combined control containing the functions of both date controls and selection controls can be obtained. Adding this combined control to the template allows members of an organization to apply for two or more leave periods with different intervals in one approval application within this template. For example, if the leave start date is January 8th and the end date is after January 9th, and the leave start date is January 11th and the end date is January 12th, then the total leave duration can be calculated as 4 days. In other words, two leave applications can be submitted in one approval application, which can reduce repetitive approval application operations and simplify the approval application process.

[0120] Optionally, such as Figure 7 As shown, the template information area also includes a grouping sub-area 60d and a text editing sub-area 60d. The first operation object can edit the template grouping in the grouping sub-area 60d, that is, edit the group to which the template to be processed belongs, and add a group label to the template to be processed. By adding group labels, it is beneficial to improve the management effectiveness of approval templates in the group organization. The first operation object can also edit the title of the template to be processed in the text editing sub-area 60d, such as editing a simple description of the template to be processed. The template title edited by the first operation object can be displayed in the text editing sub-area 60d. Optionally, the text editing sub-area 60d can also include a setting control. Through the setting control, the content type in the text editing sub-area 60d can be set, such as text content or image content. This application does not limit this.

[0121] Optionally, the editing page 60a may also include a template workflow area 60g and a template rules area 60h. In the template workflow area 60g, a template approval workflow can be set for the template to be processed, and in the template rules area 60h, template approval rules can be set for the template to be processed. For the template rules area 60h, please refer to... Figure 8 , Figure 8 This is a diagram of an editing interface for a template approval rule provided in this application embodiment. When the first operation object performs a trigger operation on the template rule area 60h, the computer device can respond to the trigger operation on the template rule area 60h, obtain the organizational structure corresponding to the group organization to which the first operation object belongs, and determine the group of the first operation object in the organizational structure as the template usage scope corresponding to the template to be processed. The template usage scope can refer to the members who can submit applications using the template to be processed; for example, when the first operation object belongs to Design Group in the organizational structure corresponding to the group organization, the members (objects) included in Design Group can be determined as the template usage scope corresponding to the template to be processed. Optionally, when the computer device responds to the trigger operation on the template rule area 60h, it can also display a selection panel (similar to the aforementioned) on the editing page 60a. Figure 4 The selection panel 30d in the corresponding embodiment (which will not be described in detail here) displays a list of objects in the group organization (which may include all members of the group organization, or may include objects in the group organization that have the same function as the first operation object, etc.); and can then respond to the selection operation on the object list, and determine the object triggered by the selection operation as the template usage scope corresponding to the template to be processed, that is, the first object operation can specify an object from the group object as the template usage scope corresponding to the template to be processed.

[0122] In this embodiment of the application, the computer device can also set an approval exception handling strategy for the template to be processed, and determine the template's scope of use and the approval exception handling strategy as the template approval rules corresponding to the template to be processed. For example... Figure 8As shown, when the first operation object performs a trigger operation on the template rule area 60h, the rule settings items corresponding to the template to be processed can be displayed in the editing page 60a, such as the exception handling strategy. The exception handling strategy can include control 60j ("Exception Handling" control), control 60k ("Auto-Agree" control), control 60m ("Allow Submission of Applications on Behalf of Others" control), control 60n ("Only Relevant Persons Can View" control), control 60p ("Allow Revocation After Approval" control), and control 60q ("Electronic Signature Required for Agreement" control). Among them, control 60j, control 60k, and control 60n are all functional controls for situations where there are members leaving the company or the page is empty in the approval node of the template to be processed. Control 60j is used to indicate that when there are members leaving the company or the page is empty in the approval node of the template to be processed, it can be set to automatically agree to execute the approval process of the template to be processed normally. Control 60k is used to indicate that when there are members leaving the company or the page is empty in the approval node of the template to be processed, except for the first section, the application can be automatically approved. Except for the node requiring approval, all other nodes can be set to automatic approval; Control 60m indicates whether it is allowed to submit applications on behalf of others. When Control 60m is closed, it means that submitting applications on behalf of others is not allowed. When Control 60m is open, it means that if there are members leaving the company or the node is empty in the approval node of the pending template, relevant people (such as direct supervisors) are not allowed to view the application approval of the pending template. When Control 60m is open, it means that if there are members leaving the company or the node is empty in the approval node of the pending template, relevant people (such as direct supervisors) are allowed to view the application approval of the pending template. Control 60p is closed, it means that the application cannot be withdrawn after approval. When Control 60p is open, it means that the application can be withdrawn after approval with the approver's consent. Control 60q is closed, it means that no electronic signature is required after the approver's consent. When Control 60q is open, it means that an electronic signature is required after the approver's consent. Based on the rule settings of controls 60j to 60q and the set template usage scope, the template approval rules corresponding to the template to be processed can be determined.

[0123] Optionally, for the 60g template process area, please refer to... Figure 9a and Figure 9b , Figure 9aThis is an illustration of an editing interface for a template approval process provided in this application embodiment. When the first operation object performs a trigger operation on the template process area 60g, the computer device can respond to the trigger operation on the template process area 60g and set the process start node (submit application), approval object cluster (which can be called approver), and copy object (which can be called copy recipient) for the template to be processed. When the approval object cluster includes multiple approval objects, the order of the approval objects in the approval object cluster can be adjusted. For example, when the first operation object performs a sorting operation on the approval objects in the approval object cluster, the computer device can respond to the sorting operation on the approval object cluster and adjust the order of the approval objects in the approval object cluster to obtain the adjusted approval object cluster. The process start node, the adjusted approval object cluster, and the copy recipient are determined as the template approval process corresponding to the template to be processed.

[0124] like Figure 9a As shown, when the first operation object performs a trigger operation on the template process area 60g, the approval process settings page 60r can be displayed. This page displays the basic process corresponding to the template to be processed, which may include a process start node, consecutive multi-level superior approvals, copy recipients, and a process end node. Assuming the template is used within a design group, all members of that group can submit applications as applicants, and submission indicates the start of the approval process. Long names of consecutive multi-level superior approvals can be displayed with line breaks, meaning the complete approval object may not be visible on the approval process settings page 60r. There can be one or more copy recipients, and applicants can specify copy recipients. Additionally, applicants can select copy recipients themselves when submitting an application, such as copying the application to themselves. By triggering the control 60s corresponding to consecutive multi-level superior approvals, a panel 60t can be displayed on the approval process settings page 60r. This panel 60t can include controls such as adjusting order, modifying name, deleting, and canceling. The adjusting order control is used to reorder the approvers involved in consecutive multi-level superior approvals (such as adjusting the order of approval objects in the approval object cluster). The modifying name control can be used to modify the approver, and the delete control can be used to delete the approval process of the pending template.

[0125] When the first operation object performs a trigger operation on the adjustment order control in panel 60t, the computer device can respond to the sorting operation of the adjustment order control, display page 60t, display the approval object in page 20t, and adjust the order of the approval object according to actual needs. Then, the approval process after the order adjustment can be determined as the template approval process corresponding to the template to be processed.

[0126] Optionally, Figure 9b This is an image of the editing interface for another template approval process provided in this application embodiment. For example... Figure 9b As shown, the approval process settings page 60r displays the conditional processes corresponding to the templates to be processed. These conditional processes can include the process start node, the conditional processes, and the default process. When a conditional process does not meet the conditions, the approval can proceed according to the default process. The approval process settings page 60r also includes an "Add Conditional Process" control 60w, which allows adding new conditional processes to the templates to be processed. If the first operation object performs a trigger operation on the control 60v corresponding to the conditional process, a panel 60x can be displayed on the approval process settings page 60r. This panel 60x can include controls for adjusting the order, modifying the name, copying (for copying existing conditional processes), deleting, and canceling. Subsequent operations are the same as described above. Figure 9a The subsequent operations of panel 60t are similar, and will not be repeated here.

[0127] Optionally, after the template to be processed is edited, the edited template can be designated as the target approval template. When the publish control in the editing page is triggered, the computer device can respond to the publish operation for the target approval template, determine the candidate cluster based on the template usage scope corresponding to the target approval template, add the target approval template to the objects in the candidate cluster in the object management application, generate a template publish message corresponding to the target approval template, and send the template publish message to the objects in the candidate cluster. The template publish message is used to instruct the objects in the candidate cluster to submit an approval application based on the target approval template in the object management cluster. After the target approval template is published, it can be automatically added to the approval workbench of the objects in the candidate cluster, and a template publish message can also be sent to the objects in the candidate cluster in one step to notify them that they can use the target approval template to submit an approval application.

[0128] Optionally, after creating the target approval template, the first operation object can edit the target approval template, including enabling / disabling / deleting, editing template controls, modifying template rules, modifying template processes, modifying template names and icons, and modifying the scope of application of the template.

[0129] Please see Figure 10 , Figure 10 This is a preview interface diagram of an approval template provided in an embodiment of this application. For example... Figure 10The current interface shown is the editing page 70b of the target approval template. This editing page 70b can include preview controls and publish controls. When the preview control in the editing page 70b is triggered, the user terminal 70a (the computer device used by the first operation object) can respond to the trigger operation of the preview control and display the preview page 70c corresponding to the target approval template. This preview page 70c can include the template content (such as template name, template icon, template controls, etc.), editing controls, and deactivation controls corresponding to the target approval template. By triggering the deactivation control, the target approval template can be temporarily deactivated in the object management application. By triggering the editing control, the template content, template approval process, template approval rules, etc. of the target approval template can be re-edited. The target approval template can also be deleted by triggering the delete control. When the delete control corresponding to the target approval template is triggered, page 70g can be displayed. If the delete control in page 70g is selected, the target approval template will be deleted from the object management application. If the cancel control in page 70g is selected, the target approval template will be retained in the object management application.

[0130] Optionally, if the publish control in the edit page 70b is triggered, the target approval template can be added to the object management application corresponding to the object in the candidate cluster (template usage scope) corresponding to the target approval template, and a template publish reminder (template publish message) can be asynchronously sent to the object in the candidate cluster. For example... Figure 10 As shown, user terminal 70d is the electronic device used by object C1. Since object C1 belongs to the candidate cluster, after the target approval template is published, the object management application corresponding to object C1 can receive the template publication reminder 70e. Through link 70f in the template publication reminder 70e, users can directly access the target approval template. By sending the template publication reminder 70e to objects within the template's scope, users within the template's scope can be promptly reminded to use the target approval template for approval applications. Furthermore, by directly accessing the target approval template through the reminder 70e, the efficiency of approval applications can be improved.

[0131] Optionally, the computer device can identify the pending configuration, which includes basic template information, template approval process, and template approval rules, as the template to be published; obtain a second operation object from the group organization to which the first operation object belongs. This second operation object is also an object granted template creation permission by the managed object, and its permission priority is higher than that of the first operation object; submit the template to be published to the second operation object, which will then review it and designate the approved template as the target approval template. In other words, if the permission priority of the first operation object is lower than the priority threshold, the template to be published created by the first operation object can be submitted to the second operation object with higher permission priority. The second operation object will review and approve the template before publishing it; otherwise, it will not be published. This improves the effectiveness of template approval.

[0132] In this system, after setting the visibility scope of permissions for the management objects of a group or organization, permission priorities can be set for objects within that scope. For example, the permission priority of a higher-level object is higher than that of a lower-level object. When the permission priority is greater than the priority threshold, the object is determined to have template publishing permissions, meaning it can directly publish the approval template after it has been created. When the permission priority is less than or equal to the priority threshold, the object is determined to not have template publishing permissions. These objects without template publishing permissions submit their approval templates to a second operation object that has template publishing permissions. The second operation object reviews and publishes the templates. This second operation object can be the management object of the group or organization, or a team leader (e.g., a department head in a company) with template creation and publishing permissions. When the second operation object is a management object, it means that each object within the visibility scope submits its approval template to the management object after it has created one. The management object can review the approval templates submitted by each object, such as merging identical approval templates. Only after the review is passed can the templates be published. This ensures the uniformity of approval templates within the group or organization and avoids the publication of duplicate approval templates. When the second operation target is a team leader with template creation and publishing permissions, it means that after creating the target approval template, the object within the scope of the permissions (e.g., the first operation target) can submit it to the team leader of the team to which the first operation target belongs (e.g., the head of the department to which the first operation target belongs). The team leader can review the target approval template submitted by the first operation target, such as merging identical approval templates, and publish it after the review is approved; or the team leader can be given the right to edit it again. This ensures the uniformity of approval templates within the team, and also improves the diversity and team characteristics of approval templates in different teams within the team organization.

[0133] Please see Figure 11, Figure 11 This is a schematic diagram of the publishing interface of an approval template provided in an embodiment of this application. For example... Figure 11 As shown, when the first operation object does not have template publishing permissions, after creating the "Group Leave Request" approval template, the editing page 70b of the "Group Leave Request" approval template can include preview and submit controls, but not publish controls. When the submit control is triggered, the user terminal 70a (the computer device used by the first operation object) can respond to the trigger operation for the submit control and display page 70h. On page 70h, the object to be submitted, i.e., the reviewer, such as the second operation object, can be an object with template creation and template publishing permissions. When the reviewer is selected and the confirm control on page 70h is triggered, the user terminal 70a can submit the "Group Leave Request" approval template to the second operation object.

[0134] After receiving the "Group Leave Request" approval template, the object management application in the user terminal 70i (the electronic device used by the second operator) can detect the unpublished approval template received by the second operator. If the similarity between the "Group Leave Request" approval template and the "xxx1" approval template is greater than a similarity threshold (e.g., 90%), a template merging reminder message 70j can be generated and displayed in the object management application. If the second operator triggers the "Direct Publish" control, the "Group Leave Request" approval template is published in the object management application; if the second operator triggers the "Merged Publish" control, the "Group Leave Request" approval template and the "xxx1" approval template are merged to obtain a merged approval template, which is then published in the object management application.

[0135] In this embodiment, the management object can set template creation permissions for the first operation object, enabling the first operation object to create target approval templates in the object management application and manage the target approval templates it creates. In other words, the approval templates in the object management application can be jointly managed by the management object and other objects (e.g., the first operation object) that have been granted template creation permissions by the managed object. This reduces the approval template management burden on the management object and improves the approval management efficiency of the approval templates in the object management application. The object that obtains template creation permissions (e.g., the first operation object) can define approval templates according to its own needs, improving the flexibility and efficiency of the team approval process.

[0136] Optionally, the following example uses a company as the organizational form. Figures 12 to 14 The process of setting template creation permissions, creating approval templates, and editing approval templates is described.

[0137] Please see Figure 12 , Figure 12 This is a flowchart illustrating the setting of template creation permissions according to an embodiment of this application. For example... Figure 12 As shown, the template creation permission setting can be performed by the management device corresponding to the management object. The management device may include the approval management terminal, the approval backend, and the database. The template creation permission setting process can be implemented through the following steps S201 to S207.

[0138] S201, Set the scope of creation permissions.

[0139] Specifically, management devices can access the permission management page of the approval management terminal through the permission management entry point opened by the object management application for enterprise administrators (the management objects of the group organization) (as mentioned above). Figure 3 The permission management page shown is 30a, or Figure 4 The permission management page (40d) shown allows setting the scope of creation permissions (also known as the visibility scope of permissions). After the enterprise administrator completes the settings, the approval management terminal can obtain the scope of creation permissions set by the enterprise administrator. The permission management entry point can include a web management entry point and a terminal management entry point. The web management entry point can be a web-based management terminal, and the terminal management entry point can be a mobile management terminal (e.g., a mobile phone management terminal). The approval management terminal can be either a web-based or mobile management terminal. The scope of creation permissions can include all members for whom the enterprise administrator has set template creation permissions. For specific instructions on setting the scope of creation permissions, please refer to the aforementioned... Figure 4 and Figure 5 The descriptions in the corresponding embodiments will not be repeated here.

[0140] S202, Send a request to save creation permission.

[0141] Specifically, after obtaining the creation permission scope set by the enterprise administrator, the approval management terminal can send a save creation permission request to the approval backend. This save creation permission request can carry encrypted permission settings, which may include the enterprise ID (organizational identification information), the first operator ID (management identification information), the first timestamp, and the creation permission scope.

[0142] S203, Check parameter verification administrator privileges.

[0143] Specifically, after receiving a request to save creation permissions, the approval backend can decrypt the encrypted permission settings carried in the request to obtain the decrypted permission settings. Then, it can verify parameters such as the enterprise ID, first operator ID, first timestamp, and creation permission scope within the decrypted permission settings. For example, it verifies whether the first operator ID has administrator privileges (only enterprise administrators have editing permissions for the permission management entry point), and the validity of the enterprise ID, first timestamp, and creation permission scope. When the first operator ID is an enterprise administrator ID, it confirms that the first operator ID has administrator privileges, meaning the first operator ID verification passes. When the first operator ID is not an enterprise administrator ID, it confirms that the first operator ID does not have administrator privileges, meaning the first operator ID verification fails. When all objects within the creation permission scope are members of the enterprise corresponding to the enterprise ID, the creation permission scope verification succeeds; when any object within the creation permission scope is not a member of the enterprise corresponding to the enterprise ID, the creation permission scope verification fails. If any parameter in the decrypted permission settings fails to be validated, the validation of the decrypted permission settings will fail, and a validation failure result will be returned to the approval management terminal. Only when all the decrypted permission settings are validated successfully can it be said that the validation of the decrypted permission settings is successful.

[0144] S204, save creation permissions.

[0145] Specifically, if the enterprise ID, the first operator ID, the first timestamp, and the creation permission scope are all successfully verified, the decrypted permission settings can be stored in the database (DB), with the enterprise ID as the primary key.

[0146] S205, database returned.

[0147] S206, Request successful response.

[0148] S207, settings returned successfully.

[0149] Specifically, after the database successfully stores the decrypted permission settings, it can return the storage result for the decrypted permission settings to the approval backend. Upon receiving the result from the database, the approval backend can return a success message to the approval management end. Upon receiving this success message, the approval management end can confirm that the permission scope settings were successfully created.

[0150] Please see Figure 13 , Figure 13 This is a flowchart illustrating the creation of an approval template provided in an embodiment of this application. For example... Figure 13As shown, the creation of the approval template can be performed by the computer device used by an enterprise employee (the first operation object) who has the authority to create the template. The computer device may include a first client, an approval backend, a database, a message push system, and a second client. The process of creating the approval template can be achieved through the following steps S301 to S315.

[0151] S301, Create an approval template.

[0152] Specifically, when an employee (referred to as the target employee for ease of description) has template management permissions set by the enterprise administrator, a template management entry point can be added to the first client. This entry point displays the template management page, which may contain either a "Create" control or an "Add Template" control (both can be called template addition controls). The first client can refer to the user terminal used by the target employee, or the client of the object management application installed on that user terminal.

[0153] When the target employee performs a trigger operation on the "Create" control or the "Add Template" control, the first client can package and encrypt the enterprise ID, the second operator ID (operation identification information), and the second timestamp together to obtain encrypted data, and then send the encrypted data to the approval backend.

[0154] S302, retrieve recommended templates and existing template data.

[0155] Specifically, after receiving the encrypted data from the first client, the approval backend can decrypt the data to obtain the decrypted data. It then verifies the validity of the enterprise ID and the second operator ID within the decrypted data, checking whether the second operator ID has template creation permissions. If the verification fails, a verification failure result (the corresponding error type) is returned to the first client. If the verification succeeds, recommended templates and existing template data from the enterprise are retrieved. The verification process for the enterprise ID and the second operator ID can be found above. Figure 3 Step S102 in the corresponding embodiment will not be described again here.

[0156] S303, query recommended templates and existing template database.

[0157] S304, database returned.

[0158] S305, Return to recommended templates or existing templates.

[0159] Specifically, the approval backend can query the industry information corresponding to the enterprise ID in the database. Based on the industry information, the database can return the recommended template configured for that industry information to the approval backend (each industry will set some recommended templates). The database can query the templates that the target employee can view for the enterprise as existing templates (configured templates). The recommended templates and existing templates are packaged together, encrypted, and returned to the first client.

[0160] S306 displays recommended templates and existing templates.

[0161] Specifically, after receiving the recommended template and the existing template, the first client can display the recommended template and the existing template in the first client.

[0162] S307, choose a recommended template, an existing template, or create a new one.

[0163] Specifically, target employees can select a recommended template, an existing template, or create a new one from the object management application. When a target employee performs a trigger operation on any recommended template, any existing template, or a newly created control, they can enter the editing page.

[0164] S308, edit template content, template rules, and visibility range.

[0165] Specifically, if the target employee enters the template editing page by clicking on any recommended template or an existing template, the controls in the recommended template will be directly displayed on the editing page. If they enter via the "Create New" control, the editing page will be empty. On the editing page, the target employee can edit the template name, template icon, control list (template controls), approval process (template approval process), approval rules (template approval rules), and visibility scope (the default visibility scope is the employee's department, but it can also be specified by the target employee; this application does not limit this, and the visibility scope can also be called the template usage scope), and choose whether to send a reminder notification to employees within the visibility scope after publishing.

[0166] S309, save template content, template rules, and visibility range.

[0167] Specifically, when the target employee completes template editing and publishes it, the configuration parameters, including the company ID, second operator ID, template name, template icon, template control list, and template rules, can be packaged, encrypted, and sent to the approval backend. Upon receiving this encrypted data, the approval backend can decrypt it to obtain the configuration parameters corresponding to the customized approval template.

[0168] S310, retrieve creation permission settings.

[0169] Specifically, the approval backend can retrieve the creation permission settings from the database, that is, the permission settings of the enterprise administrator.

[0170] S311, check creation permissions, check request parameters.

[0171] Specifically, the configuration parameter information is validated based on the permission settings, and the template creation permission of the second operator ID is validated. If the validation fails, a validation failure result is returned; if the validation succeeds, a unique ID is generated for the custom approval template, and the configuration parameter information of the approval template is stored in the database (DB), where the template ID is used as the key.

[0172] S312, created successfully.

[0173] Specifically, if the database returns a message to the approval backend indicating that the data storage was successful, it means that the custom approval template has been created successfully.

[0174] S313 displays a success page, allowing users to view the template or continue creating.

[0175] Specifically, after the first client receives the success message, it can display a success page; the target employee can also view the published approval templates or continue to create custom approval templates.

[0176] S314, asynchronously push reminder messages to members within the visible range of the template.

[0177] S315, send a reminder message.

[0178] Specifically, if a target employee needs to send a notification to members within their visible range, a template message is asynchronously constructed and sent. After receiving the notification, members within the visible range can display it on a second client. The notification can be displayed in the form of a message card, and clicking the message card will submit an approval application. The second client can refer to the user terminal used by the member within the visible range, or the client of the object management application installed on that user terminal.

[0179] Please see Figure 14 , Figure 14 This is a flowchart illustrating the editing process of an approval template provided in an embodiment of this application. For example... Figure 14 As shown, the creation of the approval template can be performed by the computer device used by an enterprise employee (the first operation object) who has the authority to create the template. The computer device may include a first client, an approval backend, a database, a message push system, and a second client. The editing process of the approval template can be achieved through the following steps S401 to S409.

[0180] S401, Editing and Approval Template.

[0181] S402, Edit template rules, template content request.

[0182] S403, retrieve creation permission settings.

[0183] S404, check editing permissions, check request parameters.

[0184] S405, Update template content, template rules, and visibility.

[0185] S406, database returned.

[0186] S407, Editing successful.

[0187] S408, asynchronously push reminder messages to members within the visible range of the template.

[0188] S409, Send reminder message.

[0189] Specifically, after creating a custom approval template (target approval template), the target employee can edit it, including enabling / disabling / deleting, editing template controls, modifying template rules, and modifying template workflows. For example, when the target employee performs an editing operation on the custom approval template, they can package and encrypt information such as the enterprise ID, second operator ID, template ID, enable / disable switch, template controls, and template rules, and send it to the approval backend. After receiving the request, the approval backend decrypts the encrypted package to obtain the decrypted custom template information. The approval backend can perform validity checks on the parameters in the custom template information. If the check fails, it returns a validation failure result. It can also check whether the operator has template editing permissions; if not, it returns a permission error. The new configuration updates the template configuration in the database, and the update success information is encrypted and returned to the first client. For the updated custom template, the approval backend can asynchronously construct and send a template update message. Members within the visible range can display the notification on the second client after receiving it.

[0190] Please see Figure 15 , Figure 15 This is a schematic diagram of the structure of a data processing apparatus provided in an embodiment of this application. It can be understood that the aforementioned data processing apparatus can be a computer program (including program code) applied to a computer device. For example, the data processing apparatus can be an object management application, and can be used to execute corresponding steps in the method provided in the embodiments of this application. Figure 15 As shown, the data processing device 1 may include: a management page display module 11 and a template creation module 12;

[0191] The management page display module 11 is used to display the template management page corresponding to the first operation object in the object management application; the first operation object refers to the object that has been granted template creation permission by the management object in the object management application.

[0192] The template creation module 12 is used to respond to the template creation operation in the template management page, create the target approval template in the object management application, and send the target approval template to the object in the candidate cluster; the candidate cluster is used to characterize the template usage scope corresponding to the target approval template, and the target approval template is managed by the first operation object.

[0193] The specific implementation methods of the management page display module 11 and the template creation module 12 can be found in the above description. Figure 3 Steps S101 to S102 in the corresponding embodiments will not be described again here.

[0194] In one or more embodiments, the data processing device 1 further includes: a permission acquisition module 13 and a permission cancellation module 14;

[0195] The permission acquisition module 13 is used to determine that the first operation object has the template creation permission granted by the management object if the managed object adds the first operation object within the permission scope, and to add a template management entry for the first operation object in the object management application; the permission scope includes objects with template creation permission in the group organization to which the managed object belongs.

[0196] The management page display module 11 is specifically used for:

[0197] In response to a trigger action on the template management entry point, the template management page indicated by the template management entry point will be displayed in the object management application.

[0198] The creation permission cancellation module 14 is used to cancel the template creation permission of the first operation object if the managed object removes the first operation object within the permission enabled scope, and delete the template management entry corresponding to the first operation object in the object management application.

[0199] The specific implementation methods of the creation permission acquisition module 13 and the creation permission cancellation module 14 can be found above. Figure 3 Step S101 in the corresponding embodiment will not be described again here.

[0200] In one or more embodiments, the template creation operation includes a template adding operation and a template editing operation;

[0201] The template creation module 12 includes: a candidate template display unit 121 and a template editing unit 122;

[0202] The candidate template display unit 121 is used to respond to the template addition operation in the template management page and display M candidate templates associated with the first operation object in the object management application; M is a positive integer.

[0203] The template editing unit 122 is used to respond to template editing operations for M candidate templates, edit the candidate templates determined by the template editing operations, and obtain the target approval template.

[0204] The specific functional implementation of the candidate template display unit 121 and the template editing unit 122 can be found in the above description. Figure 3 Step S102 in the corresponding embodiment will not be described again here.

[0205] In one or more embodiments, the candidate template display unit 121 includes: an identifier acquisition subunit 1211, a recommended template acquisition subunit 1212, and a candidate template determination subunit 1213;

[0206] The identifier acquisition subunit 1211 is used to respond to the template addition operation in the template management page, and to obtain the organization identifier information corresponding to the group organization and the operation identifier information corresponding to the first operation object in the object management application; the first operation object belongs to the group organization.

[0207] The recommended template acquisition sub-unit 1212 is used to obtain a recommended template associated with the industry information in the object management application if the organization identification information and the operation identification information pass the verification.

[0208] The candidate template determination subunit 1213 is used to obtain the configured template that matches the operation identification information, determine M candidate templates associated with the first operation object based on the recommended template, the configured template and the creation control, and display the M candidate templates; the creation control is used to represent the blank template in the object management application.

[0209] Specifically, candidate template determination subunit 1213 is used for:

[0210] In the object management application, obtain the set of publishing templates corresponding to the organization identification information, and obtain the first object identifier set corresponding to each publishing template in the publishing template set; an object identifier in a first object identifier set has the permission to view the publishing template corresponding to that first object identifier set;

[0211] The publishing template corresponding to the first object identifier set to which the operation identifier information belongs is determined as the configured template that matches the operation identifier information.

[0212] The specific implementation methods of the identifier acquisition subunit 1211, the recommended template acquisition subunit 1212, and the candidate template determination subunit 1213 can be found above. Figure 3 Step S102 in the corresponding embodiment will not be described again here.

[0213] In one or more embodiments, the data processing device 1 further includes: an identifier set acquisition module 15, a verification pass module 16, and a verification fail module 17;

[0214] The identifier set acquisition module 15 is used to acquire, in the object management application, a second object identifier set managed by the organization identifier information; the second object identifier set includes object identifiers corresponding to objects in the group organization;

[0215] The verification module 16 is used to determine that the organization identification information and the operation identification information pass the verification if the second object identification set contains operation identification information and the permission opening scope includes the first operation object; the permission opening scope includes objects in the group organization that have template creation permissions.

[0216] The verification failure module 17 is used to generate a permission error message if the organization identification information and the operation identification information fail to pass the verification. The permission error message is displayed in the object management application. The permission error message is used to instruct the first operation object to reactivate the template creation permission.

[0217] The specific implementation methods of the identifier set acquisition module 15, the verification pass module 16, and the verification fail module 17 can be found above. Figure 3 Step S102 in the corresponding embodiment will not be described again here.

[0218] In one or more embodiments, the template editing unit 122 includes: an editing page display subunit 1221, a basic information input subunit 1222, an approval process setting subunit 1223, and an approval rule setting subunit 1224;

[0219] The editing page displays sub-unit 1221, which is used to respond to template editing operations for M candidate templates, determine the candidate templates identified by the template editing operations as templates to be processed, and display the editing page corresponding to the template to be processed; the editing page includes a template information area, a template process area, and a template rules area;

[0220] The basic information input subunit 1222 is used to respond to input operations on the template information area and display the basic information of the template to be processed in the template information area.

[0221] The approval process setting sub-unit 1223 is used to respond to trigger operations for the template process area and set up the template approval process for the template to be processed.

[0222] The approval rule setting sub-unit 1224 is used to respond to the trigger operation for the template rule area, set the template approval rules for the template to be processed, and determine the template to be processed, which includes the template basic information, template approval process and template approval rules, as the target approval template.

[0223] The template information area includes a name sub-area, an icon sub-area, and a control sub-area; the input operations include a first editing operation, a second editing operation, and a control addition operation.

[0224] The basic information input subunit 1222 is specifically used for:

[0225] In response to the first edit operation on the Name sub-region, display the template name entered in the Name sub-region.

[0226] In response to a second editing operation on the icon sub-area, display the template icon entered in the second editing operation in the icon sub-area;

[0227] In response to the control addition operation for the control sub-area, the control library in the object management application is displayed, the template control is added to the template to be processed from the control library, and the template name, template icon and template control are identified as the template basic information corresponding to the template to be processed.

[0228] Among them, the basic information input subunit 1222 executes the response to the control addition operation for the control sub-area, displays the control library in the object management application, and adds template controls to the template to be processed from the control library, specifically for:

[0229] In response to a control addition operation targeting a sub-region of the control, the control library in the object management application is displayed, and N controls are selected from the control library for the template to be processed; N is a positive integer greater than 1.

[0230] Combine the functions of the first and second controls among N controls to obtain a composite control, and identify the controls other than the first and second controls among the N controls as candidate controls;

[0231] Arrange the combo controls and candidate controls to obtain template controls, and add template controls to the template to be processed.

[0232] Specifically, the approval process setting sub-unit 1223 is used for:

[0233] Respond to triggered operations in the template process area, and set the process start node, approval object cluster, and copy objects for the template to be processed;

[0234] In response to the sorting operation for the approval object cluster, the order of the approval objects in the approval object cluster is adjusted to obtain the adjusted approval object cluster. The process start node, the adjusted approval object cluster, and the copied objects are identified as the template approval process corresponding to the template to be processed.

[0235] Specifically, the approval rule setting sub-unit 1224 is used for:

[0236] In response to a trigger operation targeting a template rule area, obtain the organizational structure of the group to which the first operation object belongs, and determine the grouping of the first operation object in the organizational structure as the template usage scope corresponding to the template to be processed;

[0237] Set up an approval exception handling strategy for the template to be processed, and define the template's scope of use and the approval exception handling strategy as the template approval rules corresponding to the template to be processed.

[0238] Optionally, the approval rule setting sub-unit 1224 is specifically used for:

[0239] In response to a triggered operation in the template rule area, display a list of objects in the group or organization to which the first operation object belongs;

[0240] In response to a selection operation on the object list, the object triggered by the selection operation is identified as the template scope corresponding to the template to be processed;

[0241] Set up an approval exception handling strategy for the template to be processed, and define the template's scope of use and the approval exception handling strategy as the template approval rules corresponding to the template to be processed.

[0242] Optionally, the approval rule setting sub-unit 1224 can also be specifically used for:

[0243] The pending configurations, which include basic template information, template approval process, and template approval rules, are identified as templates to be published.

[0244] Obtain the second operation object from the group organization to which the first operation object belongs; the second operation object refers to the object that has been granted template creation permission by the managed object, and the permission priority of the second operation object is higher than the permission priority of the first operation object;

[0245] The template to be published is submitted to the second operation object, which reviews the template and determines the approved template as the target approval template.

[0246] The specific implementation methods of the editing page display sub-unit 1221, basic information input sub-unit 1222, approval process setting sub-unit 1223, and approval rule setting sub-unit 1224 can be found above. Figure 3Step S102 in the corresponding embodiment will not be described again here.

[0247] In one or more embodiments, the template creation module 12 may further include: a template adding unit 123 and a message sending unit 124;

[0248] The template adding unit 123 is used to respond to the release operation for the target approval template, determine the candidate cluster based on the template usage scope corresponding to the target approval template, and add the target approval template to the objects in the candidate cluster in the object management application.

[0249] The message sending unit 124 is used to generate a template release message corresponding to the target approval template and send the template release message to the objects in the candidate cluster. The template release message is used to instruct the objects in the candidate cluster to submit an approval application based on the target approval template in the object management cluster.

[0250] The specific functional implementation methods of the template adding unit 123 and the message sending unit 124 can be found in the above description. Figure 3 Step S102 in the corresponding embodiment will not be described again here.

[0251] In this embodiment, the management object can set template creation permissions for the first operation object, enabling the first operation object to create target approval templates in the object management application and manage the target approval templates it creates. In other words, the approval templates in the object management application can be jointly managed by the management object and other objects (e.g., the first operation object) that have been granted template creation permissions by the managed object. This reduces the approval template management burden on the management object and improves the approval management efficiency of the approval templates in the object management application. The object that obtains template creation permissions (e.g., the first operation object) can define approval templates according to its own needs, improving the flexibility and efficiency of the team approval process.

[0252] Please see Figure 16 , Figure 16 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 16 As shown, the computer device 1000 can be a user terminal, for example, the one described above. Figure 1 The user terminal 10a in the corresponding embodiment can also be a server, for example, as described above. Figure 1The server 10d in the corresponding embodiment will not be limited here. For ease of understanding, this application takes a computer device as a user terminal as an example. The computer device 1000 may include: a processor 1001, a network interface 1004, and a memory 1005. In addition, the computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. The communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen and a keyboard. Optionally, the user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk storage device. Optionally, the memory 1005 may also be at least one storage device located away from the aforementioned processor 1001. Figure 16 As shown, the memory 1005, which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device management application.

[0253] In such Figure 16 In the computer device 1000 shown, the network interface 1004 provides network communication functionality; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve:

[0254] The template management page corresponding to the first operation object is displayed in the object management application; the first operation object refers to the object that has been granted template creation permission by the management object in the object management application.

[0255] In response to the template creation operation on the template management page, a target approval template is created in the object management application and sent to the object in the candidate cluster. The candidate cluster is used to characterize the scope of use of the template corresponding to the target approval template, and the target approval template is managed by the first operation object.

[0256] It should be understood that the computer device 1000 described in the embodiments of this application can execute the foregoing text. Figure 3 , Figures 12 to 14 The description of the data processing method in any of the corresponding embodiments can also be performed as described above. Figure 15 The description of the data processing device 1 in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated here.

[0257] Furthermore, it should be noted that this application embodiment also provides a computer-readable storage medium, which stores a computer program executed by the aforementioned data processing device 1. The computer program includes program instructions, and when the processor executes the program instructions, it can execute the aforementioned... Figure 3 , Figures 12 to 14 The description of the data processing method in any corresponding embodiment is omitted here. Similarly, the beneficial effects of using the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiments related to this application, please refer to the description of the method embodiments of this application. As an example, program instructions can be deployed and executed on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network. These multiple computing devices distributed across multiple locations and interconnected via a communication network can constitute a blockchain system.

[0258] Furthermore, it should be noted that this application also provides a computer program product or computer program, which may include computer instructions, which may be stored in a computer-readable storage medium. The processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor may execute the computer instructions, causing the computer device to perform the aforementioned actions. Figure 3 , Figures 12 to 14 The description of the data processing method in any corresponding embodiment is already provided, and therefore will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the computer program products or computer program embodiments related to this application, please refer to the description of the method embodiments of this application.

[0259] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0260] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0261] The modules in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0262] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0263] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A data processing method, characterized in that, include: Display the template management page corresponding to the first operation object in the object management application; The first operation object refers to the object that has been granted template creation permission by the management object in the object management application; In response to the template addition operation on the template management page, the organization identification information corresponding to the group organization and the operation identification information corresponding to the first operation object are obtained in the object management application. The first target of the operation belongs to the group or organization; If the organization identification information and the operation identification information pass the verification, then a recommended template associated with the industry information is obtained in the object management application based on the industry information corresponding to the organization identification information. Obtain the configured template that matches the operation identifier information; determine M candidate templates associated with the first operation object based on the recommended template, the configured template, and the creation control; and display the M candidate templates. The creation control is used to represent a blank template in the object management application, where M is a positive integer; In response to a template editing operation for the M candidate templates, the candidate templates determined by the template editing operation are edited to obtain the target approval template, and the target approval template is sent to the object in the candidate cluster; The candidate cluster is used to characterize the scope of application of the target approval template, and the target approval template is managed by the first operation object.

2. The method according to claim 1, characterized in that, Also includes: If the managed object adds the first operation object within the scope of the permissions, it is determined that the first operation object has the template creation permission granted by the managed object, and a template management entry is added to the first operation object in the object management application; the scope of permissions includes objects in the group organization to which the managed object belongs that have the template creation permission; The step of displaying the template management page corresponding to the first operation object in the object management application includes: In response to a trigger operation on the template management entry point, the template management page indicated by the template management entry point is displayed in the object management application.

3. The method according to claim 2, characterized in that, Also includes: If the managed object removes the first operation object within the scope of the enabled permissions, then the template creation permission of the first operation object is cancelled, and the template management entry corresponding to the first operation object is deleted from the object management application.

4. The method according to claim 1, characterized in that, The step of obtaining the configured template that matches the operation identifier information includes: In the object management application, obtain the set of publishing templates corresponding to the organization identification information, and obtain the first object identifier set corresponding to each publishing template in the set of publishing templates; an object identifier in a first object identifier set has the permission to view the publishing template corresponding to that first object identifier set; The publishing template corresponding to the first object identifier set to which the operation identifier information belongs is determined as the configured template that matches the operation identifier information.

5. The method according to claim 1, characterized in that, Also includes: In the object management application, a second set of object identifiers managed by the organization identifier information is obtained; the second set of object identifiers includes object identifiers corresponding to objects in the group organization; If the second object identifier set contains the operation identifier information, and the permission opening scope includes the first operation object, then it is determined that the organization identifier information and the operation identifier information pass the verification; the permission opening scope includes objects in the group organization that have the template creation permission.

6. The method according to claim 1, characterized in that, Also includes: If the organization identification information and the operation identification information fail to pass the verification, a permission error message is generated and displayed in the object management application. The permission error message is used to instruct the first operation object to reactivate the template creation permission.

7. The method according to claim 1, characterized in that, The response is for the template editing operation of the M candidate templates, and edits the candidate templates determined by the template editing operation to obtain the target approval template, including: In response to the template editing operation for the M candidate templates, the candidate template determined by the template editing operation is identified as the template to be processed, and the editing page corresponding to the template to be processed is displayed; the editing page includes a template information area, a template process area, and a template rules area; In response to an input operation to the template information area, the template basic information corresponding to the template to be processed is displayed in the template information area; In response to a trigger operation in the template process area, set up a template approval process for the template to be processed; In response to a trigger operation targeting the template rules area, template approval rules are set for the template to be processed, and the template to be processed containing the template basic information, the template approval process, and the template approval rules is identified as the target approval template.

8. The method according to claim 7, characterized in that, The template information area includes a name sub-area, an icon sub-area, and a control sub-area; the input operations include a first editing operation, a second editing operation, and a control addition operation; The response is to an input operation in the template information area, displaying the basic template information corresponding to the template to be processed in the template information area, including: In response to a first edit operation on the name sub-region, the template name entered in the first edit operation is displayed in the name sub-region; In response to a second editing operation on the icon sub-area, the template icon entered in the second editing operation is displayed in the icon sub-area; In response to the control addition operation for the control sub-area, the control library in the object management application is displayed, a template control is added to the template to be processed from the control library, and the template name, the template icon, and the template control are determined as the template basic information corresponding to the template to be processed.

9. The method according to claim 8, characterized in that, The response refers to the control addition operation for the control sub-area, displaying the control library in the object management application, and adding template controls from the control library to the template to be processed, including: In response to a control addition operation targeting the sub-region of the control, the control library in the object management application is displayed, and N controls are selected from the control library for the template to be processed; N is a positive integer greater than 1. The first and second controls among the N controls are combined to obtain a combined control, and the controls other than the first and second controls among the N controls are determined as candidate controls; Arrange the combined control and the candidate control to obtain a template control, and add the template control to the template to be processed.

10. The method according to claim 7, characterized in that, The response is a trigger operation for the template process area, setting a template approval process for the template to be processed, including: In response to a trigger operation targeting the template process area, set the process start node, approval object cluster, and copy object for the template to be processed; In response to the sorting operation for the cluster of approval objects, the order of the approval objects in the cluster of approval objects is adjusted to obtain the adjusted cluster of approval objects. The process start node, the adjusted cluster of approval objects, and the copied objects are determined as the template approval process corresponding to the template to be processed.

11. The method according to claim 7, characterized in that, The response is a trigger operation for the template rule area, setting template approval rules for the template to be processed, including: In response to a trigger operation targeting the template rule area, the organizational structure corresponding to the group to which the first operation object belongs is obtained, and the grouping of the first operation object in the organizational structure is determined as the template usage scope corresponding to the template to be processed. Set an approval exception handling strategy for the template to be processed, and determine the template's scope of use and the approval exception handling strategy as the template approval rules corresponding to the template to be processed.

12. The method according to claim 7, characterized in that, The response is a trigger operation for the template rule area, setting template approval rules for the template to be processed, including: In response to a trigger operation targeting the template rule area, a list of objects in the group organization to which the first operation object belongs is displayed; In response to a selection operation on the object list, the object triggered by the selection operation is determined as the template usage scope corresponding to the template to be processed; Set an approval exception handling strategy for the template to be processed, and determine the template's scope of use and the approval exception handling strategy as the template approval rules corresponding to the template to be processed.

13. The method according to claim 7, characterized in that, The step of determining the unprocessed template, which includes the template basic information, the template approval process, and the template approval rules, as the target approval template includes: The pending configuration containing the template basic information, the template approval process, and the template approval rules is identified as the template to be published. Obtain a second operation object from the group organization to which the first operation object belongs; the second operation object refers to the object that has been granted the template creation permission by the management object, and the permission priority of the second operation object is higher than the permission priority of the first operation object; The template to be published is submitted to the second operation object, which then approves the template and determines the approved template as the target approval template.

14. The method according to claim 1, characterized in that, Sending the target approval template to objects in the candidate cluster includes: In response to the release operation for the target approval template, the candidate cluster is determined based on the template usage scope corresponding to the target approval template, and the target approval template is added to the objects in the candidate cluster in the object management application; Generate a template release message corresponding to the target approval template, and send the template release message to the objects in the candidate cluster; the template release message is used to instruct the objects in the candidate cluster to submit an approval application based on the target approval template in the object management cluster.

15. A data processing apparatus, characterized in that, include: The management page display module is used to display the template management page corresponding to the first operation object in the object management application; The first operation object refers to the object that has been granted template creation permission by the management object in the object management application; The template creation module is used to respond to the template addition operation in the template management page, and to obtain the organization identification information corresponding to the group organization and the operation identification information corresponding to the first operation object in the object management application; the first operation object belongs to the group organization. The template creation module is further configured to, if the organization identification information and the operation identification information pass the verification, obtain a recommended template associated with the industry information in the object management application based on the industry information corresponding to the organization identification information; The template creation module is further configured to obtain a configured template that matches the operation identifier information, determine M candidate templates associated with the first operation object based on the recommended template, the configured template, and the creation control, and display the M candidate templates; the creation control is used to represent a blank template in the object management application, where M is a positive integer; The template creation module is also used to respond to template editing operations for the M candidate templates, edit the candidate templates determined by the template editing operations to obtain the target approval template, and send the target approval template to the object in the candidate cluster; The candidate cluster is used to characterize the scope of application of the target approval template, and the target approval template is managed by the first operation object.

16. A computer device, characterized in that, Including memory and processor; The memory is connected to the processor, the memory is used to store computer programs, and the processor is used to invoke the computer programs so that the computer device performs the method according to any one of claims 1-14.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded and executed by a processor to cause a computer device having the processor to perform the method of any one of claims 1-14.

18. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the method described in any one of claims 1-14.

Images