Kanban configuration method and device, equipment and storage medium

Abstract

The invention provides a billboard configuration method and device, equipment and a storage medium, and the method comprises the steps: constructing a mapping relation between digital employees and rules, determining a rule associated with each digital employee, the rules being used as a business component for reconstructing an automatic process, and each rule having reusability; selecting a digital employee and adding the digital employee to a target Kanban, enabling the target Kanban to synchronize a rule associated with the digital employee, the target Kanban being a Kanban of any level in preset multi-level Kanban, and the preset multi-level Kanban including a Kanban open for an enterprise, a Kanban open for a team and a Kanban open for a project with levels from high to low; and starting or closing each rule synchronized in the target billboard to complete configuration of the target billboard. Therefore, the improvement of rule reusability and the support of multi-level configuration are realized in the billboard configuration, the efficiency and the flexibility of the billboard configuration are improved, and the working efficiency and the cooperative capability of the billboard system are high.

Description

Technical Field

[0001] The present application relates to the technical field of kanban boards, and in particular to a kanban board configuration method, device, equipment and storage medium. Background Art

[0002] Kanban system is a visual task management and process control tool, which is widely used in various fields, such as project management, software development, manufacturing, supply chain management and daily work, and has become an effective means to promote teamwork, improve work efficiency and reduce waste. The traditional Kanban system is physical. With the transformation of digital management of enterprises, the digital Kanban system has become an important tool for modern enterprise management. It not only transforms the traditional physical Kanban into a digital Kanban, but also provides more functions by introducing an online platform, such as real-time collaboration, notification reminders and statistical reports. Among them, the digital Kanban is configured with automation rules, that is, according to the preset conditions and logic, a series of rules for automatically executing operations or processes are used to further improve efficiency and reduce manual intervention. In the related art, the Kanban system mainly focuses on the automation configuration of a single Kanban. A Kanban is only associated with one project of the enterprise. For similar automation requirements in multiple Kanbans, users need to configure automation rules for each Kanban one by one, or copy existing automation rules to different Kanbans for reuse.

[0003] However, this configuration method, on the one hand, requires users to manually configure similar automation rules for each dashboard, which will generate a lot of repetitive work, increase users' learning costs and operational burdens, and lead to poor efficiency of dashboard configuration and reusability of rules. Even when the number of rules is large and the similarity is high, it will seriously consume system resources and reduce overall work efficiency. On the other hand, there is a lack of automated configuration between different levels such as enterprises and teams, and it is impossible to cover tasks and processes between different levels, which limits the work efficiency and coordination ability of the dashboard system and makes it difficult to adapt to the multi-level management needs of large enterprises or organizations. Summary of the invention

[0004] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0005] In view of the above-mentioned shortcomings of the prior art, the present application discloses a kanban configuration method, device, equipment and storage medium to solve at least one of the above-mentioned technical problems.

[0006] In a first aspect, the present application provides a method for configuring a dashboard, the method comprising: constructing a mapping relationship between digital employees and rules, determining the rules associated with each digital employee, the rules being used as business components for reconstructing an automated process, and each of the rules being reusable; selecting a digital employee to add to a target dashboard, so that the target dashboard synchronizes the rules associated with the digital employee, the target dashboard being a dashboard of any level in a preset multi-level dashboard, the preset multi-level dashboard including dashboards open to enterprises, dashboards open to teams, and dashboards open to projects, with levels from high to low; enabling or disabling each of the rules synchronized in the target dashboard to complete the configuration of the target dashboard.

[0007] In one embodiment of the present application, before constructing the mapping relationship between digital employees and rules, it also includes: configuring the trigger event, execution condition and execution action of each rule until multiple rules are configured, wherein the trigger event is a start event for the preset rule to start execution, the execution condition is a constraint condition for determining the execution of the rule, and the execution action is used to define the operation process that the rule execution needs to respond to; and customizing the execution order between the rules to complete the automatic configuration of the rules.

[0008] In one embodiment of the present application, the selecting a digital employee to add to the target dashboard includes: creating a corporate address book of an enterprise, the corporate address book including the enterprise, each team and each employee under the enterprise; adding each digital employee to the corporate address book; selecting a digital employee in the corporate address book to add to the target dashboard, and the data access scope of the added digital employee is determined by the target dashboard.

[0009] In one embodiment of the present application, the selecting a digital employee to add to a target dashboard includes: if the digital employee is added to the enterprise, all dashboards open to the enterprise are determined to be the target dashboards; if the digital employee is added to any of the teams, all dashboards open to the team are determined to be the target dashboards; if the digital employee is added to any of the projects, the dashboard facing the project is determined to be the target dashboard, and the data access scope of the digital employee is determined by the added object, and the added object includes the enterprise, the team and the project.

[0010] In one embodiment of the present application, after completing the rule configuration of the target dashboard, it also includes: if the triggering events and the execution conditions of multiple rules in the target dashboard are met, each rule is screened according to the execution order to determine the target rule currently being executed; execute the execution action corresponding to the target rule, and record the operation data of the target rule, the operation data at least including the triggering object and triggering time corresponding to the triggering event of the target rule, and the execution status of the execution action; if an abnormality is detected in the execution of the target rule, an abnormality warning is generated; if it is detected that the execution of the target rule is completed, a new target rule is determined.

[0011] In one embodiment of the present application, enabling or disabling each of the rules synchronized in the target dashboard includes: screening each of the rules synchronized in the target dashboard to determine the rules to be executed; configuring the rules to be executed to be enabled and configuring the remaining rules to be disabled.

[0012] In one embodiment of the present application, the rules for determining the association with each digital employee include: configuring virtual attributes of each data employee and at least one functional attribute to which each rule applies, the virtual attributes including a unique identifier, name, visual avatar, position and the functional attributes; associating each rule with different data employees with the same functional attributes; or, customizing the association of different rules with each data employee.

[0013] In a second aspect, the present application provides a kanban configuration device, the device comprising: an association module, used to construct a mapping relationship between digital employees and rules, determine the rules associated with each digital employee, the rules are used as business components for reconstructing automated processes, and each of the rules is reusable; a synchronization module, used to select a digital employee to add to a target kanban, so that the target kanban is synchronized with the rules associated with the digital employee, the target kanban is a kanban of any level in a preset multi-level kanban, and the preset multi-level kanban includes kanbans open to enterprises, kanbans open to teams, and kanbans for projects with levels from high to low; a configuration module, used to enable or disable each of the rules synchronized in the target kanban to complete the configuration of the target kanban.

[0014] In a third aspect, the present application also provides an electronic device, comprising: a processor, a memory and a communication bus; the communication bus is used to connect the processor and the memory; the processor is used to execute a computer program stored in the memory to implement the signboard configuration method as described in the above embodiments.

[0015] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor of a computer, the computer executes the kanban configuration method as described in the above embodiments.

[0016] Beneficial effects of the present application: The present application proposes a method, device, equipment and storage medium for configuring a kanban board. By constructing a mapping relationship between digital employees and rules, the rules associated with each digital employee are determined. The rules are used as business components for reconstructing the automated process, and each rule is reusable; a digital employee is selected to be added to the target kanban board, so that the target kanban board synchronizes the rules associated with the digital employee. The target kanban board is a kanban board at any level in the preset multi-level kanban board. The preset multi-level kanban board includes kanban boards open to enterprises, kanban boards open to teams, and kanban boards for projects from high to low levels; each rule synchronized in the target kanban board is enabled or disabled to complete the configuration of the target kanban board. In this way, by associating rules with digital employees, the rules are highly reusable, and the rules can be directly synchronized to kanban boards at any level, avoiding repeated creation of rules while achieving support for multi-level configuration, significantly improving the efficiency and flexibility of kanban board configuration, so as to improve the work efficiency and collaboration capabilities of the kanban board system.

[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0019] Figure 1 is a flow chart of a kanban configuration method shown in an exemplary embodiment of the present application;

[0020] Figure 2 is a schematic diagram of a multi-layer architecture within an enterprise shown by an exemplary embodiment of the present application;

[0021] Figure 3 is a schematic diagram of creating a digital employee shown in an exemplary embodiment of the present application;

[0022] Figure 4 is a schematic diagram of a rule configuration shown in an exemplary embodiment of the present application;

[0023] Figure 5This is a schematic diagram of an association rule and a digital employee shown in an exemplary embodiment of the present application.

[0024] Figure 6 is a schematic diagram of adding digital employees to a team, shown in an exemplary embodiment of the present application;

[0025] Figure 7 is a schematic diagram of adding a digital employee to a project shown in an exemplary embodiment of the present application;

[0026] Figure 8 is a schematic diagram of a rule enabling configuration shown in an exemplary embodiment of the present application;

[0027] Fig. 9 is a schematic diagram of another rule-enabling configuration shown in an exemplary embodiment of the present application;

[0028] Fig.10 is a block diagram of a kanban configuration device shown in an exemplary embodiment of the present application;

[0029] Fig.11 It is a structural diagram of a computer system suitable for implementing the electronic device of the present application, shown as an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0030] The following will describe the implementation methods of the present application with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be understood that the preferred embodiments are only for illustrating the present application, not for limiting the scope of protection of the present application.

[0031] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the form, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0032] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0033] It should be noted that Kanban is a system used for production control. The traditional Kanban system is physically present and is usually made of whiteboards, sticky notes and stickers. Team members record tasks, time, members, status and progress information on cards and arrange them in different columns or areas to indicate the status of tasks. This method visualizes the workflow and helps team members track tasks and make decisions quickly. In the development of digitalization, the Kanban system has become a virtual tool that provides a visual interface for organizing, tracking and managing various tasks and their status changes in the project process. It usually contains multiple lists to show the different stages or status of tasks. Among them, each task is displayed on the Kanban board in the form of a card. The card can contain detailed information, instructions, deadlines, etc. of the task, so as to instantly reflect the actual progress and dynamic changes of the task.

[0034] At present, the digital kanban system mainly provides automated management at the kanban level. For example, by setting automated rules for reminders and task assignments in a kanban, automated processes such as reminders and task assignments can be realized, effectively reducing the burden of manual operations and partially improving business efficiency and accuracy. However, some common automation rules are also applicable to other levels, such as the enterprise or the team as a whole, but the existing configuration method can only set automation rules for each kanban one by one, or apply existing rules to new kanbans through a cumbersome copy-and-paste process. This method is not only inefficient and cumbersome to operate, but also limits the efficient and large-scale reuse of rules, hindering the widespread adoption of automation rules at the enterprise level, and thus unable to achieve multi-level on-demand automation from the enterprise, team, and even specific to each kanban, and unable to improve work efficiency, organization, and team collaboration from a global perspective.

[0035] Based on this, the present application proposes a kanban configuration method to simplify the process of kanban configuration rules, improve the reusability of the rules, and realize multi-level configuration.

[0036] See also Figure 1 , is a flowchart of a kanban configuration method shown in an exemplary embodiment of the present application. The kanban configuration method can be executed by a computer device, such as Figure 1 As shown, in an exemplary embodiment, the kanban configuration method includes at least steps S110 to S130, which are described in detail as follows:

[0037] Step S110, constructing a mapping relationship between digital employees and rules, determining the rules associated with each digital employee, the rules are used as business components for reconstructing the automation process, and each rule is reusable.

[0038] Specifically, before associating digital employees and rules, it is necessary to create digital employees and multiple rules, wherein creating digital employees includes: configuring virtual attributes of each digital employee, and the virtual attributes include a unique identifier, name, visual avatar, position, and functional attributes.

[0039] See also Figure 2 , which is a schematic diagram of creating a digital employee as shown in an exemplary embodiment of the present application. Figure 2 The name of the digital employee created is R&D Assistant, the visual avatar is not uploaded, and the profile is used to fill in the digital employee's position and functional attributes, as well as descriptions of other content. The unique identifier of the digital employee can be automatically generated by the system.

[0040] In one embodiment of the present application, in the kanban system, users can create virtual digital employees for their companies, who can have access rights to a specified data range. The specified data range can be customized according to actual needs, and can also be adjusted according to the added objects of the digital employees. The unique identification of the digital employee is used to ensure that the system can accurately identify, manage and track each digital employee, effectively avoiding operational confusion; the name of the digital employee is displayed in the system's tasks, processes, notifications and other collaborative elements, which helps company members quickly identify and interact with the digital employee, enhancing the fluency of team collaboration; the visual avatar is a visual display of the digital employee in the system, which can be designed as an image or symbol to make it easier to identify; the position is used to describe the duties or roles of the digital employee to better demonstrate the responsibilities of the digital employee; the functional attributes are used to describe the functions that the digital employee can achieve, so as to better understand the role of the digital employee.

[0041] In one embodiment of the present application, before a user creates a digital employee, the user's identity needs to be authenticated.

[0042] See also Figure 3 , which is a schematic diagram of a multi-layer architecture within an enterprise shown in an exemplary embodiment of the present application. The digital employee is used to control the access rights of multi-level data in the enterprise, and the rights added to the project level and above in the enterprise, such as Figure 3As shown, an exemplary multi-layer architecture within an enterprise includes enterprises, teams, projects (corresponding to Kanban boards), cards, checklist items and comments from high to low levels, wherein the enterprise level is the highest level and may correspond to a company, department, organization or team in an actual working environment, and the enterprise level may include multiple teams in the team level; the team level may correspond to a department, project group or specific team in an actual working environment, and the team level may include multiple projects, i.e., multiple Kanban boards; Kanban boards are the core units in the Kanban system and are used to effectively manage specific tasks or workflows. Each Kanban board represents a project and may contain multiple cards, checklist items and related attachments; cards are the most basic working units in the system, and each card represents a specific work item, including detailed information such as task description, deadline, attachments, task list, person in charge and labels. Cards are usually embedded in Kanban boards and represent specific tasks that need to be completed; checklist items are part of cards, and they help to subdivide large cards into smaller, more manageable subtasks. Checklist items have their own deadlines and persons in charge to facilitate better collaboration and tracking of task details.

[0043] Specifically, configuring multiple rules includes: configuring the trigger event, execution condition and execution action of each rule until multiple rules are configured, wherein the trigger event is the start event for the preset rule to start execution, the execution condition is the constraint condition for determining the rule execution, and the execution action is used to define the operation process that the rule execution needs to respond to; custom configure the execution order between the rules to complete the automatic configuration of the rules.

[0044] In one embodiment of the present application, the trigger event is a start event for the execution of a pre-set rule, which is used to specify the circumstances under which the rule starts to execute. The user can select a single or multiple trigger events for the rule according to actual needs, and combine them through logical or and logical and operations to adapt to complex and changeable business scenarios. The types of trigger events include but are not limited to task creation, task assignment, deadline change, new project creation, etc., which are adjusted according to actual needs. The trigger condition is used to constrain the execution of the rule, ensuring that the rule will only be executed when specific conditions are met. The trigger condition can be set around factors such as task attributes (such as tags, responsible persons, deadlines), task status (such as completed, unfinished) and task-related dashboards. Like the trigger event, the user can also flexibly select and combine multiple conditions, and use logical operations to further refine the scope of application of the rule to achieve more accurate process control.

[0045] In one embodiment of the present application, after a trigger event occurs and the trigger condition is met, the execution action defines the operation process that the rule should execute, covering at least multiple types such as changes in task status, reallocation of tasks, sending of notifications, and creation of new tasks, aiming to automate key tasks in business processes, and may include one or more execution actions, wherein only logical AND operations are supported between multiple execution actions to ensure that all execution actions can be executed. The execution order between different rules is used to avoid competition or conflict among the rules. Users can flexibly adjust the execution order of the rules according to the actual business logic and priority requirements to ensure the efficiency and order of the automation process.

[0046] See also Figure 4 , is a schematic diagram of a rule configuration shown in an exemplary embodiment of the present application. Figure 4 In the rule configuration interface shown, the trigger event of the rule is configured as "Move the card to the board", the trigger condition is configured as the trigger event is triggered by a member, and the execution action is configured as adding a comment with the content "A new task has been added to the board. Please make task plans, assign members and time."

[0047] Specifically, determining the rules associated with each digital employee includes: determining at least one functional attribute applicable to each rule, and associating each rule with different digital employees with the same functional attribute; or, customizing the association of different rules with each digital employee.

[0048] In one embodiment of the present application, a rule is associated with a digital employee, and the digital employee can obtain the authority to execute the rule, and the same rule is associated with different digital employees. In this way, multiple rules can be configured on the dashboard by simply adding the digital employee associated with multiple rules to the dashboard.

[0049] See also Figure 5 , is a schematic diagram of an association rule and a digital employee shown in an exemplary embodiment of the present application. Figure 5 The left side of the page shows digital employees, and the right side shows multiple rules. You only need to select the rule to be associated and drag it from the right side of the page to the left page where the digital employee is located to establish the association between the rule and the digital employee. Figure 5 This is only an example of actual association operation, and association can also be performed through other page operation methods.

[0050] In this application, the execution order of multiple rules associated with the same digital employee can be adjusted according to actual needs.

[0051] In the above way, the same rule can be associated with different digital employees, significantly improving the reusability of the rules.

[0052] Step S120, select a digital employee to add to the target dashboard, so that the target dashboard synchronizes the rules associated with the digital employee. The target dashboard is a dashboard at any level in the preset multi-level dashboards. The preset multi-level dashboards include dashboards open to the enterprise, dashboards open to the team, and dashboards oriented to the project, with levels from high to low.

[0053] In one embodiment of the present application, usually, there are multiple kanban boards open to any enterprise or to any team, and there is only one kanban board for a project. Digital employees have the authority to be quickly added to teams or projects by other members of the enterprise, allowing them to join different teams or projects more conveniently without going through cumbersome processes to obtain data access rights to specific teams and projects, thereby improving the flexibility and efficiency of collaboration. In addition, the same digital employee can be associated with multiple kanban boards at different levels, and the rules can be automatically synchronized and configured on each kanban board at different levels, so that the rules can be quickly reused on a large scale, improving the efficiency and flexibility of kanban board configuration.

[0054] Specifically, create an enterprise address book of an enterprise, which includes the enterprise, each team under the enterprise and each employee; add each digital employee to the enterprise address book; select a digital employee in the enterprise address book to add to the target dashboard, and the data access scope of the added digital employee is determined by the target dashboard.

[0055] In one embodiment of the present application, adding digital employees to the corporate address book means that digital employees can access enterprise-level data, including various teams, dashboards, and task information, giving them the ability to collaborate on data at the entire enterprise level. Therefore, it is necessary to limit the data access scope of digital employees and control it according to the level of the target dashboard.

[0056] Specifically, if a digital employee is added to an enterprise, all dashboards open to the enterprise are determined as target dashboards; if a digital employee is added to any team, all dashboards open to the team are determined as target dashboards; if a digital employee is added to any project, the dashboard facing the project is determined as the target dashboard. The data access scope of the digital employee is determined by the added object, which includes the enterprise, team, and project. The project level in this application is actually the dashboard level, and projects and dashboards correspond one to one.

[0057] See also Figure 6 and Figure 7 , are schematic diagrams of adding digital employees to a team or project, respectively, according to an exemplary embodiment of the present application. The user first needs to select a board corresponding to a team or a project, then open the corporate address book to select one or more digital employees and add them to the team or the board. Figure 6As shown in the figure, select a team with 8 members, open the corporate address book, select a digital employee named Design Assistant from the corporate address book, and then confirm to add him to the team. Then, the digital employee association rule can be configured on all dashboards open to the team. Figure 7 As shown, select the dashboard corresponding to a project, that is Figure 7 , then open the corporate address book, select a digital employee named Design Assistant from the corporate address book, and confirm to add him to the work board. Then, you can configure the digital employee association rule on the work board.

[0058] By adding digital employees to dashboards at different levels in the above way, more flexible associations and controls can be achieved, forming hierarchical data management for enterprises, teams, and projects. This hierarchical structure provides data isolation and control to ensure data security and compliance.

[0059] Step S130 , enabling or disabling each rule synchronized in the target dashboard to complete the configuration of the target dashboard.

[0060] Specifically, the rules synchronized in each target dashboard are screened to determine the rules to be executed; the rules to be executed are configured to be enabled, and the remaining rules are configured to be disabled.

[0061] In one embodiment of the present application, by enabling or disabling the rules associated with digital employees added to the target dashboard, the configuration of the dashboard can be made more flexible, suitable for meeting automation requirements in similar but different situations, and facilitating resource management and improving performance of the dashboard system.

[0062] See also Figure 8 and Fig. 9 , which is a schematic diagram of a rule-enabling configuration shown in an exemplary embodiment of the present application. Figure 8 and Fig. 9 Taking the configuration interface shown as an example, users can search for digital employees, i.e. design assistants, added to a team or project, and then open the activation page for setting the rules associated with the digital employee, and select the rules to be activated to enable or disable them. In this way, the rules that can be executed by the same digital employee in different teams or projects are different, ensuring that each digital employee has the appropriate automation rules in different teams and projects.

[0063] In this way, users can add virtual digital employees to different teams and projects, or even different cooperating companies, to ensure the accuracy and flexibility of adjusting the scope of rule execution, providing more efficient task and process control, which is particularly beneficial for large organizations or complex project management.

[0064] Specifically, after completing the configuration of the target dashboard, if the trigger events and execution conditions of multiple rules in the target dashboard are met, the rules are screened according to the execution order to determine the currently executed target rule; the execution action corresponding to the target rule is executed, and the running data of the target rule is recorded, and the running data at least includes the trigger object and trigger time corresponding to the trigger event of the target rule, and the execution status of the execution action; if an abnormality is detected in the execution of the target rule, an abnormality warning is generated; if the execution of the target rule is completed, a new target rule is determined.

[0065] In one embodiment of the present application, the rules associated with the digital employee are monitored in real time to identify whether the triggering events and triggering conditions of the rules are met. If they are met, the execution actions included in the rules are automatically executed based on the execution order of the rules, such as adding comments, creating tasks, etc., to ensure the continuity and efficiency of the business process. In addition, in order to further improve the transparency and traceability of rule execution, the operating data during rule execution will be recorded in detail for tracking the execution of the rules. In addition, the rules synchronized by multiple digital employees in different target dashboards can be detected at the same time.

[0066] The kanban configuration method provided in the present application has the following advantages: by associating rules and digital employees, the rules are highly reusable, and the rules can be directly synchronized to any level of the kanban, avoiding repeated creation of rules while supporting multi-level configurations, significantly improving the efficiency and flexibility of the kanban configuration, thereby improving the work efficiency and collaboration capabilities of the kanban system.

[0067] See also Fig.10 , is a block diagram of a kanban configuration device shown as an exemplary embodiment of the present application. Fig.10 As shown, in an exemplary embodiment, the kanban configuration device at least includes an association module 1010, a synchronization module 1020 and a configuration module 1030, which are described in detail as follows:

[0068] The association module 1010 is used to construct a mapping relationship between digital employees and rules, and determine the rules associated with each digital employee. The rules are used as business components for reconstructing the automation process, and each rule is reusable;

[0069] A synchronization module 1020 is used to select a digital employee to add to a target dashboard, so that the target dashboard synchronizes the rules associated with the digital employee, the target dashboard is a dashboard at any level in a preset multi-level dashboard, and the preset multi-level dashboard includes a dashboard open to the enterprise, a dashboard open to the team, and a dashboard open to the project from high to low levels;

[0070] The configuration module 1030 is used to enable or disable each rule synchronized in the target dashboard to complete the configuration of the target dashboard.

[0071] It should be noted that the kanban configuration device provided in the above embodiment and the kanban configuration method provided in the above embodiment belong to the same concept, wherein the contents of the operations performed by each module have been described in detail in the method embodiment and will not be repeated here.

[0072] The present application also provides an electronic device, comprising: a processor, a memory and a communication bus; the communication bus is used to connect the processor and the memory; the processor is used to execute a computer program stored in the memory to implement the signboard configuration method as in the above embodiment.

[0073] See also Fig.11 , shows a schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application. It should be noted that, Fig.11 The computer system 1100 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0074] like Fig.11 As shown, the computer system 1100 includes a central processing unit (CPU) 1101, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1102 or the program loaded from the storage part 1108 to the random access memory (RAM) 1103, such as executing the method in the above embodiment. In the RAM 1103, various programs and data required for system operation are also stored. The CPU 1101, the ROM 1102 and the RAM 1103 are connected to each other through the bus 1104. The input / output (I / O) interface 1105 is also connected to the bus 1104.

[0075] The following components are connected to the I / O interface 1105: an input section 1106 including a keyboard, a mouse, etc.; an output section 1107 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to the I / O interface 1109 as needed. A removable medium 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1110 as needed so that a computer program read therefrom is installed into the storage section 1108 as needed.

[0076] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1109, and / or installed from a removable medium 1111. When the computer program is executed by a central processing unit (CPU) 1101, various functions defined in the system of the present application are executed.

[0077] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer, the computer executes the above-mentioned signboard configuration method. The computer-readable storage medium may be included in the electronic device described in the above-mentioned embodiment, or may exist independently without being assembled into the electronic device.

[0078] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, system or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, system or device. A computer program contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0079] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0080] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0081] The above embodiments are merely illustrative of the principles and effects of the present application, and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A kanban configuration method, characterized in that: The method comprises: Constructing a mapping relationship between digital employees and rules, determining the rules associated with each digital employee, wherein the rules are used as business components for reconstructing the automation process, and each rule is reusable; Selecting a digital employee to add to a target dashboard, so that the target dashboard synchronizes the rule associated with the digital employee, the target dashboard is a dashboard at any level in a preset multi-level dashboard, and the preset multi-level dashboard includes a dashboard open to the enterprise, a dashboard open to the team, and a dashboard open to the project from high to low levels; An enabling or disabling operation is performed on each of the rules synchronized in the target dashboard to complete the configuration of the target dashboard.

2. The method for configuring a signboard according to claim 1, characterized in that: Before building the mapping relationship between digital employees and rules, it also includes: Configure the trigger event, execution condition and execution action of each rule until multiple rules are configured, wherein the trigger event is a start event for the preset rule to start execution, the execution condition is a constraint condition for determining the execution of the rule, and the execution action is used to define the operation process that the rule execution needs to respond to; Customize the execution order of the rules to complete the automatic configuration of the rules.

3. The method for configuring a signboard according to claim 1, characterized in that: The step of selecting one and adding the digital employee to the target dashboard includes: Creating a corporate address book for an enterprise, the corporate address book including the enterprise, each team and each employee under the enterprise; Adding each of the digital employees to the corporate address book; A digital employee is selected from the enterprise address book and added to the target dashboard, and the data access scope of the added digital employee is determined by the target dashboard.

4. The method for configuring a signboard according to claim 1, characterized in that: The step of selecting one and adding the digital employee to the target dashboard includes: Add the digital employee to the enterprise, and determine all dashboards open to the enterprise as the target dashboards; If the digital employee is added to any of the teams, all dashboards open to the teams are determined as the target dashboards; If the digital employee is added to any of the projects, the dashboard facing the project is determined as the target dashboard, and the data access scope of the digital employee is determined by the added object, which includes the enterprise, the team and the project.

5. The method for configuring a signboard according to claim 2, characterized in that: After completing the rule configuration of the target dashboard, the method further includes: If the triggering events and the execution conditions of the multiple rules in the target dashboard are met, the rules are screened according to the execution order to determine the target rule currently being executed; Execute the execution action corresponding to the target rule, and record the operation data of the target rule, wherein the operation data at least includes the trigger object and trigger time corresponding to the trigger event of the target rule, and the execution status of the execution action; If an abnormality is detected during the execution of the target rule, an abnormality warning is generated; If it is monitored that the execution of the target rule is completed, a new target rule is determined.

6. The method for configuring a signboard according to any one of claims 1 to 5, characterized in that: The enabling or disabling of each rule synchronized in the target dashboard includes: Screening the rules synchronized in each target dashboard to determine the rules to be executed; The rules to be executed are configured to be in an enabled state, and the remaining rules are configured to be in a disabled state.

7. The method for configuring a signboard according to any one of claims 1 to 5, characterized in that: The determining the rule associated with each digital employee includes: Configuring virtual attributes of each of the data employees and at least one functional attribute to which each of the rules applies, the virtual attributes including a unique identifier, a name, a visual avatar, a position, and the functional attributes; Associating each of the rules with different data employees of the same functional attribute; or, Customize to associate different rules to each data employee.

8. A kanban configuration device, characterized in that: The device comprises: An association module, used to construct a mapping relationship between digital employees and rules, and determine the rules associated with each digital employee, wherein the rules are used as business components for reconstructing the automation process, and each rule is reusable; A synchronization module, used for selecting a digital employee to add to a target dashboard, so that the target dashboard synchronizes the rule associated with the digital employee, wherein the target dashboard is a dashboard at any level in a preset multi-level dashboard, wherein the preset multi-level dashboard includes a dashboard open to the enterprise, a dashboard open to the team, and a dashboard open to the project from high to low levels; The configuration module is used to enable or disable each rule synchronized in the target dashboard to complete the configuration of the target dashboard.

9. An electronic device, characterized in that: include: processor, memory, and communications bus; The communication bus is used to connect the processor and the memory; The processor is configured to execute the computer program stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is used to make a computer execute the method according to any one of claims 1 to 7.

Images