Graphical event configuration methods, devices, equipment, and storage media

By automatically configuring tasks in the collaborative office system through a graphical interface, the problems of complex operation and error-proneness in existing technologies are solved, and safe and reliable business task configuration is achieved.

CN115048091BActive Publication Date: 2026-11-17GUANGZHOU HUIRUI SITONG INFORMATION SCI & TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210588202.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-05-30
Publication Date
2026-11-17
Estimated Expiration
2042-05-30

AI Technical Summary

Technical Problem

Existing collaborative office systems require technicians to manually modify configuration codes when configuring collaborative office tasks involving multiple personnel. This process is complex, error-prone, and cannot adapt to complex business iterations.

Method used

This paper provides a graphical method for configuring tasks. It determines the permissions of the user through a graphical interface, parses the user's operation instructions, and automatically configures the user's identity and tasks within the scope of permissions. It supports task decomposition, version control, and status synchronization.

Benefits of technology

It reduces the operational complexity of configuring business items, improves the security and reliability of configuration, and enables convenient and efficient configuration of collaborative office business items.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115048091B_ABST
    Figure CN115048091B_ABST
Patent Text Reader

Abstract

This disclosure provides a graphical method, apparatus, device, and storage medium for configuring business items. The method includes: determining whether the user has the corresponding permissions based on the user information of the user and the operation command executed by the user on the icon corresponding to the target user; if the user has the corresponding permissions, configuring the identity information carried by the operation command for the target user in the graphical interface and assigning the target item corresponding to the operation command to the target user, thereby obtaining the configuration information of the target user and its target item. Therefore, the business item configuration method provided by this disclosure can reduce the operational complexity of the business item configuration process, improve the security and reliability of business item configuration, and achieve convenient and efficient completion of collaborative office business item configuration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to a graphical method, apparatus, device, and storage medium for configuring events. Background Technology

[0002] Collaborative office systems provide a platform for multiple users to communicate, share, and collaborate on business tasks. Currently, existing collaborative office systems typically configure multi-person collaborative tasks based on pre-defined, relatively fixed workflows. This usually requires configuration personnel to set up fixed lists and forms for the tasks and participants, placing a high demand on their programming skills. Summary of the Invention

[0003] Research into relevant technologies revealed that existing collaborative office systems cannot adapt to complex business iterations. When new business items or new collaborators are involved, technical personnel need to modify configuration code from the backend, which is complex and error-prone. Therefore, how to conveniently and efficiently implement collaborative office business item configuration is a pressing technical problem that needs to be solved in this field.

[0004] In view of the above problems, the first aspect of this disclosure provides a graphical event configuration method, the method comprising:

[0005] Determine the user information of the user who is operating, wherein the user who is operating is the user who configures the candidate items in the graphical interface;

[0006] Obtain the operation instruction executed by the operating user on the icon corresponding to the target user, wherein the target user is any user in the candidate user list in the graphical interface;

[0007] The operation instruction executed by the user on the icon corresponding to the target user is parsed, and the identity configuration information carried by the operation instruction and the target item corresponding to the operation instruction are determined, wherein the target item is one or more of the candidate items in the graphical interface;

[0008] Based on the user information of the user performing the operation, determine whether the user has the permissions matching the operation command.

[0009] If the user has permissions matching the operation instruction, then in the graphical interface, the user is configured with the identity corresponding to the identity configuration information and the target item corresponding to the operation instruction is assigned to the user to obtain the configuration information of the target item.

[0010] As an optional implementation, in the first aspect of this disclosure, determining whether the operating user has permissions matching the operating instruction based on the user information of the operating user includes:

[0011] Determine the first user identity information corresponding to the operating user based on the user information of the operating user;

[0012] Determine the second user identity information corresponding to the identity configuration information carried by the operation instruction;

[0013] Based on the first user identity information and the second user identity information, determine whether the operating user has the authority to configure the identity for the target user;

[0014] If the operating user does not have the permission to configure the identity of the target user, then it is determined that the operating user does not have the permission matching the operating instruction.

[0015] If the operating user has the permission to configure the identity of the target user, then obtain the first item set associated with the operating user, and determine whether the first item set contains the target item;

[0016] If the first set of items does not contain the target item, then it is determined that the user does not have the permissions matching the operation instruction.

[0017] If the first set of items includes the target item, then it is determined that the user has the permissions matching the operation instruction.

[0018] As an optional implementation, in the first aspect of this disclosure, after obtaining the configuration information of the target item, the method further includes:

[0019] Determine whether the user performing the operation has version release permissions;

[0020] If the user performing the operation has version release permission, the version of the item is updated according to the configuration information of the target item to obtain the first version of the item to be pushed, and the first version of the item to be pushed is pushed to all users included in the first version of the item.

[0021] If the user performing the operation does not have version release permissions, the configuration information of the target item will be synchronously sent to the user performing the operation who has version release permissions.

[0022] As an optional implementation, in the first aspect of this disclosure, after determining that the operating user has version release permissions, the method further includes:

[0023] Receive event configuration information sent by one or more other operating users;

[0024] Summarize the item configuration information received from one or more other operating users to obtain one or more items to be updated and their corresponding configuration information;

[0025] The historical item version is updated based on one or more items to be updated and their corresponding configuration information to obtain the second item version to be pushed.

[0026] Push the second version of the item to be pushed to all users included in the second version of the item.

[0027] As an optional implementation, in the first aspect of this disclosure, after determining the user information of the operating user, the method further includes:

[0028] Determine the first set of items associated with the user performing the operation;

[0029] Obtain the task breakdown instructions from the user in the graphical interface and the target task to be broken down according to the task breakdown instructions;

[0030] When the first set of matters associated with the operating user contains the target dismantling matter corresponding to the dismantling instruction, it is determined whether the operating user has the dismantling permission for the target dismantling matter based on the user information of the operating user.

[0031] If the user has the permission to disassemble the target disassembly item, then in the graphical interface, the target disassembly item is disassembled into one or more sub-target disassembly items according to the disassembly instruction.

[0032] As an optional implementation, in the first aspect of this disclosure, the method further includes:

[0033] Determine the first set of items associated with the user performing the operation;

[0034] Obtain the status annotation information of the user on any item in the first item set;

[0035] For each item in the first item set, the graphical display form of the item is determined based on the status annotation information of the operation user for the item, and the display form of the item is updated in the graphical interface;

[0036] The graphical representation of any item in the first item set is simultaneously pushed to all users associated with the candidate item in the graphical interface.

[0037] As an optional implementation, in the first aspect of this disclosure, determining the graphical display format of each item in the first item set based on the status annotation information of the operating user for that item includes:

[0038] For each item in the first item set, determine whether the status label information of the operation user for the item is completed or ended item label information;

[0039] If the user's status label for the matter is the completed or ended matter label, then it is further determined whether there are any sub-matters associated with the matter, wherein there are one or more sub-matters associated with the matter;

[0040] If there are sub-items associated with this item, then the display format of this item and the display format of each sub-item associated with this item will be updated to the display format corresponding to the completion or end status.

[0041] If there are no sub-items associated with this item, then the display format of this item will be updated to the display format corresponding to the completed or ended state.

[0042] A second aspect of this disclosure provides a graphical event configuration device, the device comprising:

[0043] The determination module is used to determine the user information of the operating user, wherein the operating user is the user who configures the candidate items in the graphical interface;

[0044] The acquisition module is used to acquire the operation instructions executed by the operating user on the icon corresponding to the target user, wherein the target user is any user in the candidate user list in the graphical interface;

[0045] The parsing module is used to parse the operation instructions executed by the user on the icon corresponding to the target user, and to determine the identity configuration information carried by the operation instructions and the target item corresponding to the operation instructions, wherein the target item is one or more of the candidate items in the graphical interface;

[0046] The judgment module is used to determine, based on the user information of the operating user, whether the operating user has the permissions matching the operation instruction;

[0047] An execution module is configured, if the judgment module determines that the operating user has permissions matching the operation instruction, to configure the identity corresponding to the identity configuration information for the target user and to assign the target item corresponding to the operation instruction to the target user in the graphical interface, so as to obtain the configuration information of the target item.

[0048] As an optional implementation, in the second aspect of this disclosure, the method by which the determining module determines whether the operating user has permissions matching the operating instruction based on the user information of the operating user specifically includes:

[0049] Determine the first user identity information corresponding to the operating user based on the user information of the operating user;

[0050] Determine the second user identity information corresponding to the identity configuration information carried by the operation instruction;

[0051] Based on the first user identity information and the second user identity information, determine whether the operating user has the authority to configure the identity for the target user;

[0052] If the operating user does not have the permission to configure the identity of the target user, then it is determined that the operating user does not have the permission matching the operating instruction.

[0053] If the operating user has the permission to configure the identity of the target user, then obtain the first item set associated with the operating user, and determine whether the first item set contains the target item;

[0054] If the first set of items does not contain the target item, then it is determined that the user does not have the permissions matching the operation instruction.

[0055] If the first set of items includes the target item, then it is determined that the user has the permissions matching the operation instruction.

[0056] As an optional implementation, in a second aspect of this disclosure, the apparatus further includes: a version release module, wherein the version release module is configured to:

[0057] Determine whether the user performing the operation has version release permissions;

[0058] If the user performing the operation has version release permission, the version of the item is updated according to the configuration information of the target item to obtain the first version of the item to be pushed, and the first version of the item to be pushed is pushed to all users included in the first version of the item.

[0059] If the user performing the operation does not have version release permissions, the configuration information of the target item will be synchronously sent to the user performing the operation who has version release permissions.

[0060] As an optional implementation, in the second aspect of this disclosure, after the version release module determines that the operating user has version release permissions, the version release module is further configured to:

[0061] Receive event configuration information sent by one or more other operating users;

[0062] Summarize the item configuration information received from one or more other operating users to obtain one or more items to be updated and their corresponding configuration information;

[0063] The historical item version is updated based on one or more items to be updated and their corresponding configuration information to obtain the second item version to be pushed.

[0064] Push the second version of the item to be pushed to all users included in the second version of the item.

[0065] As an optional implementation, in a second aspect of this disclosure, the apparatus further includes: a task breakdown module, wherein the task breakdown module is used for:

[0066] Determine the first set of items associated with the user performing the operation;

[0067] Obtain the task breakdown instructions from the user in the graphical interface and the target task to be broken down according to the task breakdown instructions;

[0068] When the first set of matters associated with the operating user contains the target dismantling matter corresponding to the dismantling instruction, it is determined whether the operating user has the dismantling permission for the target dismantling matter based on the user information of the operating user.

[0069] If the user has the permission to disassemble the target disassembly item, then in the graphical interface, the target disassembly item is disassembled into one or more sub-target disassembly items according to the disassembly instruction.

[0070] As an optional implementation, in a second aspect of this disclosure, the apparatus further includes: a status labeling module, wherein the status labeling module is used for:

[0071] Determine the first set of items associated with the user performing the operation;

[0072] Obtain the status annotation information of the user on any item in the first item set;

[0073] For each item in the first item set, the graphical display form of the item is determined based on the status annotation information of the operation user for the item, and the display form of the item is updated in the graphical interface;

[0074] The graphical representation of any item in the first item set is simultaneously pushed to all users associated with the candidate item in the graphical interface.

[0075] As an optional implementation, in the second aspect of this disclosure, the status labeling module is used to determine the graphical display format of each item in the first item set based on the status labeling information of the user for that item. Specifically, this includes:

[0076] For each item in the first item set, determine whether the status label information of the operation user for the item is completed or ended item label information;

[0077] If the user's status label for the matter is the completed or ended matter label, then it is further determined whether there are any sub-matters associated with the matter, wherein there are one or more sub-matters associated with the matter;

[0078] If there are sub-items associated with this item, then the display format of this item and the display format of each sub-item associated with this item will be updated to the display format corresponding to the completion or end status.

[0079] If there are no sub-items associated with this item, then the display format of this item will be updated to the display format corresponding to the completed or ended state.

[0080] A third aspect of this disclosure provides an electronic device, the electronic device comprising:

[0081] Memory containing executable program code;

[0082] A processor coupled to the memory;

[0083] The processor calls the executable program code stored in the memory to execute the graphical event configuration method disclosed in the first aspect of this disclosure.

[0084] The fourth aspect of this disclosure provides a computer-readable storage medium storing computer program instructions, which, when invoked, are used to execute the graphical event configuration method disclosed in the first aspect of this disclosure.

[0085] The advantages of the graphical event configuration method, apparatus, device, and storage medium provided in this disclosure are as follows:

[0086] This disclosure determines whether the user has the permissions matching the operation command by analyzing the user information of the operating user and the operation command executed by the operating user on the icon corresponding to the target user. If the operating user has the permissions matching the operation command, the graphical interface configures the identity corresponding to the identity configuration information carried by the operation command for the target user and assigns the target item corresponding to the operation command to the target user, thereby obtaining the configuration information of the target person and their target item. Therefore, the business item configuration method provided by this disclosure can reduce the operational complexity of the business item configuration process, improve the security and reliability of business item configuration, and achieve convenient and efficient completion of collaborative office business item configuration. Attached Figure Description

[0087] The accompanying drawings described herein are for illustrative purposes only and are not intended to represent all possible implementations, nor are they intended to limit the scope of this disclosure.

[0088] Figure 1 This is a flowchart illustrating a graphical item configuration method provided in an embodiment of this disclosure;

[0089] Figure 2 This is a flowchart illustrating yet another graphical item configuration method provided in this embodiment of the present disclosure;

[0090] Figure 3 This is a schematic diagram of the structure of a graphical item configuration device provided in an embodiment of this disclosure;

[0091] Figure 4 This is a schematic diagram of another graphical item configuration device provided in this embodiment of the present disclosure;

[0092] Figure 5 This is a schematic diagram of an electronic device structure provided in an embodiment of this disclosure. Detailed Implementation

[0093] In the following description, certain specific details are set forth in order to provide a thorough understanding of the various embodiments of this disclosure. However, those skilled in the art will understand that this disclosure may be practiced without these specific details.

[0094] To enable those skilled in the art to better understand the present disclosure, the technical solutions of the present disclosure will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of the present disclosure, and not all embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present disclosure.

[0095] The terms "first," "second," etc., in this disclosure, claims, and accompanying drawings are used to distinguish different objects and not to describe a particular order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or end that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or ends.

[0096] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this disclosure. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0097] This disclosure provides a graphical method, apparatus, device, and storage medium for configuring business tasks. The graphical operation reduces the complexity of the business task configuration process, while authentication ensures the security and reliability of the configuration, enabling convenient and efficient configuration of collaborative office tasks. These are described in detail below.

[0098] Example 1

[0099] Figure 1 This is a flowchart illustrating a graphical item configuration method provided in an embodiment of this disclosure. Figure 1 The described method can be applied to both clients and servers. Clients include computer client applications, mobile client applications, tablet client applications, and web pages accessed through a browser. The term "client" as used below refers to a collective term for computer client applications, mobile client applications, tablet clients, and browser web pages; it means the user end and is not limited to using client applications and web page displays. Figure 1 As shown, this graphical event configuration method may include the following steps:

[0100] S101. Determine the user information of the user who is operating, wherein the user who is operating is the user who configures the candidate items in the graphical interface.

[0101] In this embodiment of the disclosure, candidate items in the graphical interface are displayed to the user in a graphical form, including but not limited to graphical interfaces represented and presented in the form of tree diagrams, logic diagrams, organizational charts, balanced diagrams, and fishbone diagrams. The user information of the operating user carries the operating user's identity information and / or the related item information associated with the operating user.

[0102] Furthermore, user identity information includes user role information and corresponding permission information. Specifically, user roles can be divided into four different roles: Creator, Organizer, Collaborator, and Observer. The permission levels corresponding to these roles are: Creator > Organizer > Collaborator > Observer. Authorization is granted downwards according to the permission level of the role. That is, the Creator can assign the roles of Organizer, Collaborator, and Observer. In a candidate item version, the Creator, who has the highest permissions, can be the actual controller of the collaborative office system or can delegate the creation of identities to designated individuals. The Organizer can assign the roles of Collaborator and Observer, and the Collaborator can assign the role of Observer. Optionally, the Organizer and Collaborator can assign role permissions at the same level. Observers only have viewing permissions and cannot add other Observers.

[0103] Furthermore, the associated items related to the operating user can be one or more. For example, if the operating user is a bystander, the associated items related to that operating user are the items that the user directly participates in; if the operating user is an organizer or collaborator, the associated items related to that operating user include the items that the user directly participates in as well as the items that the user indirectly participates in; if the operating user is a creator, the associated items related to that operating user are all items in the current version of the item.

[0104] S102. Obtain the operation instruction executed by the user on the icon corresponding to the target user, wherein the target user is any user in the candidate user list in the graphical interface.

[0105] S103. Parse the operation instructions executed by the user on the icon corresponding to the target user, and determine the identity configuration information carried by the operation instructions and the target item corresponding to the operation instructions. The target item is one or more of the candidate items in the graphical interface.

[0106] In this embodiment, the operator uses a graphical user interface (GUI) to drag and drop target users from a candidate user list within the GUI. These operations can include adding, removing, and / or authorizing target users. Specifically, taking the operator as an organizer as an example: the organizer adds / removes target users or changes their permissions by dragging and dropping. Upon detecting the operation, the corresponding target user and target item are saved to a locally cached database. The data is then parsed to obtain business object data, including the identity configuration information carried by the operation instruction and the target item corresponding to the operation instruction (which is the business object). Optionally, when the server is executing this method, after saving the data to the locally cached database, the permission data packet or updated permission data packet is submitted to the server via XML / JSON over the network. The server receives the submitted data packet, parses the data, and obtains the corresponding parsing results.

[0107] S104. Based on the user information of the user, determine whether the user has the permissions that match the operation command.

[0108] S105. If the user has the permissions matching the operation command, then in the graphical interface, configure the identity corresponding to the identity configuration information for the target user and assign the target item corresponding to the operation command to the target user to obtain the configuration information of the target item.

[0109] In this embodiment of the disclosure, when the identity configuration information carried by the operation instruction and the target item corresponding to the operation instruction are determined, data security is ensured through authentication. For example, after the server parses the XML / JSON data into business object data, it determines whether the object being operated on is within the scope of permissions. If it is within the scope of permissions, the server saves and updates the database with the parsed business object data by type, using the personnel ID as a unique identifier as a judgment condition. New personnel and permissions are inserted into the database as new data records, while removed personnel are removed from the database records; the permissions of personnel in the database are updated to the latest permissions.

[0110] As can be seen, implementing the graphical task configuration method provided in this disclosure can reduce the operational complexity of the business task configuration process through graphical operation, while ensuring the security and reliability of the business task configuration through authentication operation, thus realizing convenient and efficient completion of collaborative office business task configuration.

[0111] In this embodiment of the disclosure, optionally, see [link to relevant documentation]. Figure 2 , Figure 2This is a flowchart illustrating another graphical event configuration method provided in this disclosure. Specifically, S104, determining whether the user has the permissions matching the operation command based on the user's user information, includes:

[0112] S1041. Determine the first user identity information corresponding to the operating user based on the user information of the operating user;

[0113] S1042. Determine the second user identity information corresponding to the identity configuration information carried by the operation instruction;

[0114] S1043. Based on the first user's identity information and the second user's identity information, determine whether the operating user has the permission to configure the target user's identity. If the operating user does not have the permission to configure the target user's identity, proceed to S1044; if the operating user has the permission to configure the target user's identity, execute S1045.

[0115] S1044. The user does not have the permissions matching the operation command.

[0116] S1045. Obtain the first set of items associated with the operation user, and determine whether the first set of items contains the target item. If the first set of items does not contain the target item, proceed to S1044; if the first set of items contains the target item, proceed to S1046.

[0117] S1046. The user has permissions that match the operation instructions.

[0118] In an optional embodiment of this disclosure, the user information of the operating user carries the identity information corresponding to the operating user and / or the associated information of the operating user. By parsing the operating user's operation instructions, the second user identity information corresponding to the identity configuration information carried in the operation instructions can be obtained. By comparing the operating user's identity information with the permission level of the identity information to be assigned to the target user, it can be determined whether the operating user has the permission to configure the identity for the target user. For example, if the user is the creator, they have the highest privileges and can configure identity information for all users in the candidate list. If the user is the organizer, they have the privilege to add, modify, and / or remove user identities for collaborators and observers with lower privileges than themselves, but not for creators or organizers at the same level. However, they do have the privilege to add organizers at the same level. If the user is the collaborator, they have the privilege to add, modify, and / or remove user identities for observers with lower privileges than themselves, but not for creators, organizers, or collaborators at the same level. However, they do have the privilege to add collaborators at the same level. If the user is the observer, they have no control or allocation privileges and can only view the items. Furthermore, when the operating user has the permission to configure the identity of the target user, it is determined whether the operating user has the permission to associate the target item with the target user. That is, the operating user only has the permission to associate the target item with the target user when the first set of items associated by the operating user contains the target item.

[0119] As can be seen, by implementing this optional embodiment, when verifying user identity, multi-layered authentication based on roles and related matters can prevent unauthorized users from controlling the operation of matters, thereby improving the security and reliability of data operations.

[0120] In this embodiment of the disclosure, optionally, after obtaining the configuration information of the target item, the method further includes:

[0121] Determine if the user has version release permissions;

[0122] If the user has version release permissions, the version of the item is updated according to the configuration information of the target item to obtain the first version of the item to be pushed, and the first version of the item to be pushed is pushed to all users included in the first version of the item.

[0123] If the user performing the operation does not have version release permissions, the configuration information for the target item will be synchronously sent to the user performing the operation who has version release permissions.

[0124] In optional embodiments of this disclosure, when the user's identity information is that of a creator, the user has version release permissions. For example, the creator submits the configuration information of the target item, formed by drag-and-drop operations in the graphical interface, to the server. Upon receiving the version release instruction from the user, the server updates the item version according to the submitted configuration information of the target item, forming a version to be pushed and saving it to the database. Simultaneously, the server iterates through the data in the version to be pushed, generates a message notification, and pushes the version to be pushed to all users included in that version. When the user's identity information is that of an organizer or collaborator, by saving the modified version, the temporarily modified and saved data is stored in the organizer's or collaborator's client cache. The organizer's or collaborator's client pushes the configuration information of the target item to the server or the creator's client by submitting a release operation.

[0125] In this embodiment of the disclosure, optionally, after determining that the user has version release permissions, the method further includes:

[0126] Receive event configuration information sent by one or more other operating users;

[0127] Summarize the item configuration information received from one or more other operating users to obtain one or more items to be updated and their corresponding configuration information;

[0128] The historical item version is updated based on one or more items to be updated and their corresponding configuration information to obtain the second item version to be pushed.

[0129] Push the second version of the item to be pushed to all users included in the second version of the item.

[0130] In an optional embodiment of this disclosure, after determining that the operating user has version release permissions, the system pushes a collaborative message to the operating user with version release permissions. The server or operator's client receives item configuration information sent by one or more other operating users, first verifies whether the user permissions are consistent, and then saves one or more item configuration information to the database. The saved one or more item configuration information are isolated from existing version information. The submitted one or more item configuration information are then merged and supplemented according to the needs of the actual application, and the latest merged version is submitted and saved to the database. The latest version is then pushed to all users included in the latest merged version.

[0131] As can be seen, by implementing this optional embodiment and configuring version release permissions, version control of graphical matters can be achieved based on a graphical interface and secured by permission roles, while also improving data security.

[0132] In this embodiment of the disclosure, optionally, after determining the user information of the user performing the operation, the method further includes:

[0133] Determine the first set of items associated with the user performing the operation;

[0134] Obtain the task breakdown instructions from the user in the graphical interface, as well as the target task to be broken down according to the task breakdown instructions;

[0135] When the first set of items associated with the operating user contains the target item to be disassembled corresponding to the item disassembly instruction, the user information of the operating user is used to determine whether the operating user has the disassembly permission for the target item to be disassembled.

[0136] If the user has the permission to disassemble the target item, the target item will be disassembled into one or more sub-target items in the graphical interface according to the item disassembly instructions.

[0137] In an optional embodiment of this disclosure, if the target decomposition item A in the current graphical interface requires more people to complete, the operators associated with target decomposition item A can split target decomposition item A into one or more sub-target decomposition items. The processing method of the sub-target decomposition items is consistent with the implementation method of the main target decomposition item. Furthermore, for one of the sub-target decomposition items Aa of target decomposition item A, if the operators associated with sub-target decomposition item Aa are unable to complete sub-target decomposition item Aa and more people are needed, they can choose to further decompose sub-target decomposition item Aa into smaller-level sub-items Aa_a. Decomposition can achieve infinite recursion and decomposition, supporting more flexible methods.

[0138] For example, in a graphical task / item, the creator, organizer, and collaborator can all break down large tasks / items into one or more sub-tasks / items based on the current graphical representation. When a creator, organizer, or collaborator adds a sub-item via graphical drag-and-drop, the client triggers an event and saves it to the local data cache. The client sends the XML / JSON and sub-task / item creation data to the server over the network. The server receives the XML / JSON and sub-task / item creation data from the client. The server parses the XML / JSON data into business object data and determines whether the object being operated on is within the scope of permissions. If it is, the server saves and updates the data in the database. Upon receiving the sub-task / item creation request, the server creates the new sub-task / item data and establishes a connection with the current task / item, saving the data. Regardless of whether the person creating the sub-task is a collaborator or organizer, they become the creator within the sub-task / item and have the highest management authority over the sub-task. After the server completes the update, it returns the status to the client.

[0139] As can be seen, implementing this optional embodiment can adapt to complex business iterations and can also complete the configuration of business matters conveniently and efficiently when new business matters / new collaborators are involved.

[0140] Optionally, in this embodiment of the disclosure, the method further includes:

[0141] Determine the first set of items associated with the user performing the operation;

[0142] Obtain the status annotation information of any item in the first item set by the operating user;

[0143] For each item in the first item set, the graphical display form of the item is determined based on the status annotation information of the user, and the display form of the item is updated in the graphical interface.

[0144] The graphical representation of any item in the first item set is simultaneously pushed to all users associated with the candidate item in the graphical interface.

[0145] In optional embodiments of this disclosure, the status of an item is represented graphically in the graphical interface. For example, a completed item is marked in green, an incomplete item in red, and an item in progress is displayed with a small icon and a "working" indicator. When a user changes the status of an item, the graphical display format of the item is determined based on the user's status annotation information. The data is saved to a local cache database, and the XML / JSON data is pushed to the server via the network. The server receives the pushed XML / JSON data and saves it to its database. After the server completes the saving of the client data, it synchronously updates the status of the graphical item, changes the graphical presentation style according to the actual status, and synchronously pushes the graphical display format of the item to all users associated with the candidate item in the graphical interface.

[0146] In this embodiment of the disclosure, optionally, for each item in the first item set, the graphical display format of the item is determined based on the status annotation information of the operating user for the item, including:

[0147] For each item in the first item set, determine whether the status label information of the operating user for the item is completed or ended;

[0148] If the user marks the status of the matter as completed or ended, then it is further determined whether there are any sub-matters associated with the matter, wherein there are one or more sub-matters associated with the matter;

[0149] If there are sub-items associated with this item, then the display format of this item and the display format of each sub-item associated with this item will be updated to the display format corresponding to the completed or ended status.

[0150] If there are no sub-items associated with this item, then the display format of this item will be updated to the display format corresponding to the completed or ended status.

[0151] In an optional embodiment of this disclosure, when an operator triggers an operation to complete or end a task, the corresponding status data is saved to a local cache database. After saving the status data, the status XML / JSON data is sent to the server via the network; the server receives the XML / JSON data and updates it to the database; the server further detects whether there are sub-tasks for the task targeted by the operator's operation. If sub-tasks exist, the server synchronously updates the status of the associated sub-tasks to complete or end, and returns the result to all users.

[0152] It is evident that the advantage of graphical status synchronization lies in its simplicity and intuitiveness. During system use, the collaborative synchronization of the status of tasks and sub-tasks significantly improves office efficiency. Graphical status updates are intuitively displayed through differences in style, form, and change methods, allowing users to understand the information clearly and at a glance. Furthermore, the shapes are customizable and better suit individual needs.

[0153] Example 2

[0154] Figure 3 This is a schematic diagram of a graphical item configuration device provided in an embodiment of this disclosure. Figure 3 As shown, the device includes: a determining module 301, an acquiring module 302, a parsing module 303, a judging module 304, and an execution module 305. Wherein:

[0155] The determination module 301 is used to determine the user information of the operating user, wherein the operating user is the user who configures the candidate items in the graphical interface.

[0156] In this embodiment of the disclosure, candidate items in the graphical interface are displayed to the user in a graphical form, including but not limited to graphical interfaces represented and presented in the form of tree diagrams, logic diagrams, organizational charts, balanced diagrams, and fishbone diagrams. The user information of the operating user carries the operating user's identity information and / or the related item information associated with the operating user.

[0157] Furthermore, user identity information includes user role information and corresponding permission information. Specifically, user roles can be divided into four different roles: Creator, Organizer, Collaborator, and Observer. The permission levels corresponding to these roles are: Creator > Organizer > Collaborator > Observer. Authorization is granted downwards according to the permission level of the role. That is, the Creator can assign the roles of Organizer, Collaborator, and Observer. In a candidate item version, the Creator, who has the highest permissions, can be the actual controller of the collaborative office system or can delegate the creation of identities to designated individuals. The Organizer can assign the roles of Collaborator and Observer, and the Collaborator can assign the role of Observer. Optionally, the Organizer and Collaborator can assign role permissions at the same level. Observers only have viewing permissions and cannot add other Observers.

[0158] Furthermore, the associated items related to the operating user can be one or more. For example, if the operating user is a bystander, the associated items related to that operating user are the items that the user directly participates in; if the operating user is an organizer or collaborator, the associated items related to that operating user include the items that the user directly participates in as well as the items that the user indirectly participates in; if the operating user is a creator, the associated items related to that operating user are all items in the current version of the item.

[0159] The acquisition module 302 is used to acquire the operation instructions executed by the operating user on the icon corresponding to the target user, wherein the target user is any user in the candidate user list in the graphical interface.

[0160] The parsing module 303 is used to parse the operation instructions executed by the user on the icon corresponding to the target user, and to determine the identity configuration information carried by the operation instructions and the target item corresponding to the operation instructions. The target item is one or more of the candidate items in the graphical interface.

[0161] In this embodiment, the operator uses a graphical user interface (GUI) to drag and drop target users from a candidate user list within the GUI. These operations can include adding, removing, and / or authorizing target users. Specifically, taking the operator as an organizer as an example: the organizer adds / removes target users or changes their permissions by dragging and dropping. Upon detecting the operation, the organizer saves the corresponding target user and target item to a locally cached database and submits the permission data packet or updated permission data packet to the server via XML / JSON over the network. The server receives the submitted data packet, parses it, and extracts business object data to obtain the identity configuration information carried by the operation instruction and the target item corresponding to the operation instruction as the business object data.

[0162] The judgment module 304 is used to determine whether the operating user has the permissions that match the operation command based on the user information of the operating user.

[0163] The execution module 305 is used to configure the identity corresponding to the identity configuration information of the target user and assign the target item corresponding to the operation instruction to the target user in the graphical interface if the judgment module 304 determines that the operation user has the permissions matching the operation instruction, so as to obtain the configuration information of the target item.

[0164] In this embodiment of the disclosure, when the identity configuration information carried by the operation instruction and the target item corresponding to the operation instruction are determined, data security is ensured through authentication. For example, after the server parses the XML / JSON data into business object data, it determines whether the object being operated on is within the scope of permissions. If it is within the scope of permissions, the server saves and updates the database with the parsed business object data by type, using the personnel ID as a unique identifier as a judgment condition. New personnel and permissions are inserted into the database as new data records, while removed personnel are removed from the database records; the permissions of personnel in the database are updated to the latest permissions.

[0165] As can be seen, implementing the graphical task configuration method provided in this disclosure can reduce the operational complexity of the business task configuration process through graphical operation, while ensuring the security and reliability of the business task configuration through authentication operation, thus realizing convenient and efficient completion of collaborative office business task configuration.

[0166] In this embodiment of the disclosure, optionally, the method by which the determining module 304 determines whether the operating user has the permissions matching the operating instruction based on the user information of the operating user specifically includes:

[0167] Determine the first user identity information corresponding to the user who is operating based on the user information of the user who is operating.

[0168] Determine the second user identity information corresponding to the identity configuration information carried in the operation command;

[0169] Based on the first user's identity information and the second user's identity information, determine whether the operating user has the authority to configure the identity of the target user;

[0170] If the user performing the operation does not have the permission to configure the identity of the target user, then it is determined that the user performing the operation does not have the permission matching the operation command.

[0171] If the user performing the operation has the permission to configure the identity of the target user, then obtain the first set of items associated with the user performing the operation, and determine whether the first set of items contains the target item.

[0172] If the first set of items does not contain the target item, it is determined that the user does not have the permissions matching the operation instruction.

[0173] If the first set of items contains the target item, then the user is determined to have permissions matching the operation instruction.

[0174] In an optional embodiment of this disclosure, the user information of the operating user carries the identity information corresponding to the operating user and / or the associated information of the operating user. By parsing the operating user's operation instructions, the second user identity information corresponding to the identity configuration information carried in the operation instructions can be obtained. By comparing the operating user's identity information with the permission level of the identity information to be assigned to the target user, it can be determined whether the operating user has the permission to configure the identity for the target user. For example, if the user is the creator, they have the highest privileges and can configure identity information for all users in the candidate list. If the user is the organizer, they have the privilege to add, modify, and / or remove user identities for collaborators and observers with lower privileges than themselves, but not for creators or organizers at the same level. However, they do have the privilege to add organizers at the same level. If the user is the collaborator, they have the privilege to add, modify, and / or remove user identities for observers with lower privileges than themselves, but not for creators, organizers, or collaborators at the same level. However, they do have the privilege to add collaborators at the same level. If the user is the observer, they have no control or allocation privileges and can only view the items. Furthermore, when the operating user has the permission to configure the identity of the target user, it is determined whether the operating user has the permission to associate the target item with the target user. That is, the operating user only has the permission to associate the target item with the target user when the first set of items associated by the operating user contains the target item.

[0175] As can be seen, by implementing this optional embodiment, when verifying user identity, multi-layered authentication based on roles and related matters can prevent unauthorized users from controlling the operation of matters, thereby improving the security and reliability of data operations.

[0176] In this embodiment of the disclosure, optionally, see [link to relevant documentation]. Figure 4 , Figure 4 This is a schematic diagram of another graphical item configuration device provided in this disclosure. Figure 4 As shown, the device also includes: a version release module 306, wherein the version release module is used for:

[0177] Determine if the user has version release permissions;

[0178] If the user has version release permissions, the version of the item is updated according to the configuration information of the target item to obtain the first version of the item to be pushed, and the first version of the item to be pushed is pushed to all users included in the first version of the item.

[0179] If the user performing the operation does not have version release permissions, the configuration information for the target item will be synchronously sent to the user performing the operation who has version release permissions.

[0180] In optional embodiments of this disclosure, when the user's identity information is that of a creator, the user has version release permissions. For example, the creator submits the configuration information of the target item, formed by drag-and-drop operations in the graphical interface, to the server. Upon receiving the version release instruction from the user, the server updates the item version according to the submitted configuration information of the target item, forming a version to be pushed and saving it to the database. Simultaneously, the server iterates through the data in the version to be pushed, generates a message notification, and pushes the version to be pushed to all users included in that version. When the user's identity information is that of an organizer or collaborator, by saving the modified version, the temporarily modified and saved data is stored in the organizer's or collaborator's client cache. The organizer's or collaborator's client pushes the configuration information of the target item to the server or the creator's client by submitting a release operation.

[0181] In this embodiment of the disclosure, optionally, after determining that the operating user has version release permissions, the version release module 306 is further configured to:

[0182] Receive event configuration information sent by one or more other operating users;

[0183] Summarize the item configuration information received from one or more other operating users to obtain one or more items to be updated and their corresponding configuration information;

[0184] The historical item version is updated based on one or more items to be updated and their corresponding configuration information to obtain the second item version to be pushed.

[0185] Push the second version of the item to be pushed to all users included in the second version of the item.

[0186] In an optional embodiment of this disclosure, after determining that the operating user has version release permissions, the system pushes a collaborative message to the operating user with version release permissions. The server or operator's client receives item configuration information sent by one or more other operating users, first verifies whether the user permissions are consistent, and then saves one or more item configuration information to the database. The saved one or more item configuration information are isolated from existing version information. The submitted one or more item configuration information are then merged and supplemented according to the needs of the actual application, and the latest merged version is submitted and saved to the database. The latest version is then pushed to all users included in the latest merged version.

[0187] As can be seen, by implementing this optional embodiment and configuring version release permissions, version control of graphical matters can be achieved based on a graphical interface and secured by permission roles, while also improving data security.

[0188] In this embodiment of the disclosure, optional, such as Figure 4 As shown, the device further includes: a task breakdown module 307, wherein the task breakdown module 307 is used for:

[0189] Determine the first set of items associated with the user performing the operation;

[0190] Obtain the task breakdown instructions from the user in the graphical interface, as well as the target task to be broken down according to the task breakdown instructions;

[0191] When the first set of items associated with the operating user contains the target item to be disassembled corresponding to the item disassembly instruction, the user information of the operating user is used to determine whether the operating user has the disassembly permission for the target item to be disassembled.

[0192] If the user has the permission to disassemble the target item, the target item will be disassembled into one or more sub-target items in the graphical interface according to the item disassembly instructions.

[0193] In an optional embodiment of this disclosure, if the target decomposition item A in the current graphical interface requires more people to complete, the operators associated with target decomposition item A can split target decomposition item A into one or more sub-target decomposition items. The processing method of the sub-target decomposition items is consistent with the implementation method of the main target decomposition item. Furthermore, for one of the sub-target decomposition items Aa of target decomposition item A, if the operators associated with sub-target decomposition item Aa are unable to complete sub-target decomposition item Aa and more people are needed, they can choose to further decompose sub-target decomposition item Aa into smaller-level sub-items Aa_a. Decomposition can achieve infinite recursion and decomposition, supporting more flexible methods.

[0194] For example, in a graphical task / item, the creator, organizer, and collaborator can all break down large tasks / items into one or more sub-tasks / items based on the current graphical representation. When a creator, organizer, or collaborator adds a sub-item via graphical drag-and-drop, the client triggers an event and saves it to the local data cache. The client sends the XML / JSON and sub-task / item creation data to the server over the network. The server receives the XML / JSON and sub-task / item creation data from the client. The server parses the XML / JSON data into business object data and determines whether the object being operated on is within the scope of permissions. If it is, the server saves and updates the data in the database. Upon receiving the sub-task / item creation request, the server creates the new sub-task / item data and establishes a connection with the current task / item, saving the data. Regardless of whether the person creating the sub-task is a collaborator or organizer, they become the creator within the sub-task / item and have the highest management authority over the sub-task. After the server completes the update, it returns the status to the client.

[0195] As can be seen, implementing this optional embodiment can adapt to complex business iterations and can also complete the configuration of business matters conveniently and efficiently when new business matters / new collaborators are involved.

[0196] In this embodiment of the disclosure, optional, such as Figure 4 As shown, the device further includes a status labeling module 308, wherein the status labeling module 308 is used for:

[0197] Determine the first set of items associated with the user performing the operation;

[0198] Obtain the status annotation information of any item in the first item set by the operating user;

[0199] For each item in the first item set, the graphical display form of the item is determined based on the status annotation information of the user, and the display form of the item is updated in the graphical interface.

[0200] The graphical representation of any item in the first item set is simultaneously pushed to all users associated with the candidate item in the graphical interface.

[0201] In optional embodiments of this disclosure, the status of an item is represented graphically in the graphical interface. For example, a completed item is marked in green, an incomplete item in red, and an item in progress is displayed with a small icon and a "working" indicator. When a user changes the status of an item, the graphical display format of the item is determined based on the user's status annotation information. The data is saved to a local cache database, and the XML / JSON data is pushed to the server via the network. The server receives the pushed XML / JSON data and saves it to its database. After the server completes the saving of the client data, it synchronously updates the status of the graphical item, changes the graphical presentation style according to the actual status, and synchronously pushes the graphical display format of the item to all users associated with the candidate item in the graphical interface.

[0202] In this embodiment of the disclosure, optionally, the status labeling module 308 is used to determine the graphical display form of each item in the first item set based on the status labeling information of the user for that item. Specifically, this includes:

[0203] For each item in the first item set, determine whether the status label information of the operating user for the item is completed or ended;

[0204] If the user marks the status of the matter as completed or ended, then it is further determined whether there are any sub-matters associated with the matter, wherein there are one or more sub-matters associated with the matter;

[0205] If there are sub-items associated with this item, then the display format of this item and the display format of each sub-item associated with this item will be updated to the display format corresponding to the completed or ended status.

[0206] If there are no sub-items associated with this item, then the display format of this item will be updated to the display format corresponding to the completed or ended status.

[0207] In an optional embodiment of this disclosure, when an operator triggers an operation to complete or end a task, the corresponding status data is saved to a local cache database. After saving the status data, the status XML / JSON data is sent to the server via the network; the server receives the XML / JSON data and updates it to the database; the server further detects whether there are sub-tasks for the task targeted by the operator's operation. If sub-tasks exist, the server synchronously updates the status of the associated sub-tasks to complete or end, and returns the result to all users.

[0208] It is evident that the advantage of graphical status synchronization lies in its simplicity and intuitiveness. During system use, the collaborative synchronization of the status of tasks and sub-tasks significantly improves office efficiency. Graphical status updates are intuitively displayed through differences in style, form, and change methods, allowing users to understand the information clearly and at a glance. Furthermore, the shapes are customizable and better suit individual needs.

[0209] Example 3

[0210] This disclosure also provides an electronic device, such as... Figure 5 As shown, Figure 5 This is a schematic diagram of an electronic device structure provided in an embodiment of this disclosure. The electronic device includes:

[0211] Memory 501 storing executable program code;

[0212] Processor 502 coupled to memory 501;

[0213] The processor 502 calls the executable program code stored in the memory 501 to execute some or all of the steps in the graphical event configuration method described in Embodiment 1 of this disclosure.

[0214] For example, the electronic device may be a base station or a terminal. Those skilled in the art will understand that... Figure 5 This is merely one example of an electronic device and does not constitute a limitation on the electronic device. It may include more components than shown, or combine certain components, or conventionally replace different components. For example, the electronic device may also include input / output interfaces, buses, etc.

[0215] The processor 502 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0216] The memory 501 can be an internal storage unit of the electronic device, such as a hard drive or memory. The memory 501 can also be an external storage device of the electronic device, such as a plug-in hard drive, Smart Media Card (SMC), Secure Digital (SD) card, Flash Card, USB flash drive, etc. Furthermore, the memory 501 can include both internal and external storage units. The memory 501 is used to store the computer program and other programs and data required by the electronic device. The memory 501 can also be used to temporarily store data that has been output or will be output.

[0217] Example 4

[0218] This disclosure also provides a computer-readable storage medium storing computer program instructions that, when invoked, execute some or all of the steps in the graphical event configuration method described in Embodiment 1 of this disclosure. The computer-readable storage medium may be one or more of the types of memory 501 listed in the above-described electronic device embodiments.

[0219] The various embodiments described above can be combined to provide further embodiments. If necessary, modifications can be made to various aspects of the embodiments to incorporate the concepts of various patents, applications, and publications to provide even more further embodiments.

[0220] In view of the above detailed description, these and other changes may be made to the embodiments. Generally, the terminology used in the following claims should not be construed as limiting the claims to the specific embodiments disclosed in this specification and the claims, but should be construed as including all possible embodiments and the entire scope of equivalents entitled to be obtained by those claims. Accordingly, the claims are not limited by this disclosure.

Claims

1. A graphical-based matter configuration method, characterized by, The method includes: The user information of the operating user is determined, wherein the operating user is the user who configures the candidate items in the graphical interface; the user information carries the identity information of the operating user and / or the associated item information of the operating user, wherein the identity information includes the user's role information and the permission information corresponding to the role information, and the role information is divided into creator, organizer, collaborator and spectator; Obtain the operation instruction executed by the operating user on the icon corresponding to the target user, wherein the target user is any user in the candidate user list in the graphical interface; The operation instruction executed by the user on the icon corresponding to the target user is parsed, and the identity configuration information carried by the operation instruction and the target item corresponding to the operation instruction are determined, wherein the target item is one or more of the candidate items in the graphical interface; Based on the user information of the user performing the operation, determine whether the user has the permissions matching the operation command. If the user has permissions matching the operation instruction, then in the graphical interface, the user is configured with the identity corresponding to the identity configuration information and the target item corresponding to the operation instruction is assigned to the user to obtain the configuration information of the target item. After determining the user information of the operating user and before obtaining the operation instruction executed by the operating user on the icon corresponding to the target user, the method further includes: Determine the first set of items associated with the user performing the operation; Obtain the task breakdown instructions from the user in the graphical interface and the target task to be broken down according to the task breakdown instructions; When the first set of matters associated with the operating user contains the target dismantling matter corresponding to the dismantling instruction, it is determined whether the operating user has the dismantling permission for the target dismantling matter based on the user information of the operating user. If the user has the permission to disassemble the target disassembly item, then in the graphical interface, the target disassembly item is disassembled into one or more sub-target disassembly items according to the disassembly instruction.

2. The graphical item configuration method according to claim 1, characterized in that, The step of determining whether the user has the permissions matching the operation command based on the user information of the user includes: Determine the first user identity information corresponding to the operating user based on the user information of the operating user; Determine the second user identity information corresponding to the identity configuration information carried by the operation instruction; Based on the first user identity information and the second user identity information, determine whether the operating user has the authority to configure the identity for the target user; If the operating user does not have the permission to configure the identity of the target user, then it is determined that the operating user does not have the permission matching the operating instruction. If the operating user has the permission to configure the identity for the target user, then obtain the first set of items associated with the operating user, and determine whether the first set of items contains the target item; If the first set of items does not contain the target item, then it is determined that the user does not have the permissions matching the operation instruction. If the first set of items includes the target item, then it is determined that the user has the permissions matching the operation instruction.

3. The graphical item configuration method according to claim 1, characterized in that, After obtaining the configuration information of the target item, the method further includes: Determine whether the user performing the operation has version release permissions; If the user performing the operation has version release permission, the historical item version is updated according to the configuration information of the target item to obtain the first item version to be pushed, and the first item version to be pushed is pushed to all users included in the first item version; If the user performing the operation does not have version release permissions, the configuration information of the target item will be synchronously sent to the user performing the operation who has version release permissions.

4. The graphical item configuration method according to claim 3, characterized in that, After determining that the user performing the operation has version release permissions, the method further includes: Receive event configuration information sent by one or more other operating users; Summarize the item configuration information received from one or more other operation users to obtain one or more items to be updated and their corresponding configuration information; The historical item version is updated based on one or more items to be updated and their corresponding configuration information to obtain the second item version to be pushed. Push the second version of the item to be pushed to all users included in the second version of the item.

5. The graphical item configuration method according to claim 1, further comprising: Determine the first set of items associated with the user performing the operation; Obtain the status annotation information of the user on any item in the first item set; For each item in the first item set, the graphical display form of the item is determined based on the status annotation information of the operation user for the item, and the display form of the item is updated in the graphical interface; The graphical representation of any item in the first item set is simultaneously pushed to all users associated with the candidate item in the graphical interface.

6. The graphical item configuration method according to claim 5, wherein determining the graphical display form of each item in the first item set based on the status annotation information of the user on the item includes: For each item in the first item set, determine whether the status label information of the operation user for the item is completed or ended item label information; If the user's status label for the matter is the completed or ended matter label, then it is further determined whether there are any sub-matters associated with the matter, wherein there are one or more sub-matters associated with the matter; If there are sub-items associated with this item, then the display format of this item and the display format of each sub-item associated with this item will be updated to the display format corresponding to the completion or end status. If there are no sub-items associated with this item, then the display format of this item will be updated to the display format corresponding to the completed or ended state.

7. A graphical task configuration device, characterized in that, The device includes: The determination module is used to determine the user information of the operating user, wherein the operating user is the user who configures the candidate items in the graphical interface; the user information carries the identity information of the operating user and / or the associated item information of the operating user, the identity information includes the user's role information and the permission information corresponding to the role information, the role information is divided into creator, organizer, collaborator and spectator; The acquisition module is used to acquire the operation instructions executed by the operating user on the icon corresponding to the target user, wherein the target user is any user in the candidate user list in the graphical interface; The parsing module is used to parse the operation instructions executed by the user on the icon corresponding to the target user, and to determine the identity configuration information carried by the operation instructions and the target item corresponding to the operation instructions, wherein the target item is one or more of the candidate items in the graphical interface; The judgment module is used to determine, based on the user information of the operating user, whether the operating user has the permissions matching the operation instruction; An execution module is configured to, if the judgment module determines that the operating user has permissions matching the operation instruction, configure the identity corresponding to the identity configuration information for the target user in the graphical interface and assign the target item corresponding to the operation instruction to the target user, so as to obtain the configuration information of the target item; The item decomposition module is used to determine the first item set associated with the operation user; obtain the item decomposition instruction from the operation user in the graphical interface and the target item to be decomposed corresponding to the item decomposition instruction; when the first item set associated with the operation user contains the target item to be decomposed corresponding to the item decomposition instruction, determine whether the operation user has the decomposition permission for the target item based on the operation user's user information; if the operation user has the decomposition permission for the target item, then decompose the target item to one or more sub-target items in the graphical interface according to the item decomposition instruction.

8. An electronic device, characterized in that, The electronic device includes: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the graphical event configuration method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when invoked, are used to execute the graphical event configuration method according to any one of claims 1-6.

Citation Information

Patent Citations

  • Authority management method and device thereof, computer equipment and storage medium

    CN112989298A

  • Service authorization processing method and device

    CN114139200A