Lifecycle-driven business object progress method, system, device, and medium

Abstract

The present disclosure relates to a life cycle driven business object progress method, system, device and medium, the method comprising the following steps: obtaining a business type of a business object, binding a corresponding life cycle template according to the business type; customizing a layout in the life cycle template and creating a customized life cycle control, setting a default value of the life cycle control as a default state, so that the default state takes the default state in the associated life cycle template; sharing life cycle template data to each business service using distributed cache, the business service directly obtaining multiple node states of the life cycle from the cache, the node states binding multiple processes; associating a process template with a node of the life cycle, and driving the business object from one node state to the next node state according to the process in the process template. The present disclosure easily nests role access and personnel to-do into the life cycle, thereby realizing the management of the life cycle.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the field of project management, in particular to a life cycle driven business object progress method, system, device and medium. BACKGROUND

[0002] Project Management, this management issue has been a professional team in the enterprise to constantly learn a subject, because the project execution efficiency is not only shows the tacit understanding of team communication and cooperation, but also represents the team task execution efficiency, it will directly affect the competitiveness of enterprises in the market. First is the expansion of project management problem, because the project management software developed by the concept and technology applied mostly is inherited from the traditional project management, so the project management mode can also mostly have a given development mode, unable to provide project managers according to project demand can have flexible planning and definition, often resulting in poor effect of project management software assisted; in view of the problems and deficiencies of the existing project management software, it is necessary to have a complete and thorough improvement, especially for the management flexibility of the project and the problem of the execution efficiency of the project, how to effectively put forward a kind of project management software system and method which can solve the above problems, is an important issue in the development of project management software. In view of the problems and deficiencies of the existing project management software, it is necessary to have a complete and thorough improvement, especially for the management flexibility of the project and the problem of the execution efficiency of the project, how to effectively put forward a kind of project management software system and method which can solve the above problems, is an important issue in the development of project management software. SUMMARY

[0003] The present disclosure relates to a life cycle driven business object progress method, system, device and medium, which can solve at least one problem mentioned in the background art, and can easily nest role access and personnel to-do in the life cycle, thereby realizing the management of the life cycle. To solve the above technical problems, the present disclosure provides the following technical solutions:

[0004] As one aspect of the embodiment of the present disclosure, a life cycle driven business object progress method is provided, comprising the following steps:

[0005] Obtaining the business type of the business object, and binding the corresponding life cycle template according to the business type;

[0006] Customizing the layout in the life cycle template and creating a customized life cycle control, setting the default value of the life cycle control as the default state, so that the default state takes the default state in the associated life cycle template;

[0007] The distributed cache is used to share the life cycle template data to each business service, and each business service directly obtains the node states of the life cycle from the cache, and the node states are bound to the processes.

[0008] The processes are associated with the nodes of the life cycle, and the business object is driven from one node state to the next node state according to the processes in the process template.

[0009] Preferably, the process template is provided with an audit node and an audit personnel corresponding to the node state, so as to realize the control of the authority.

[0010] Preferably, one life cycle template is bound to each business type.

[0011] Preferably, the life cycle template further needs to define the state of each stage of the business object, the transition condition between the states, the management process required by each state, and the configuration of the dynamic authority of each stage.

[0012] Preferably, after the distributed cache is used to share the life cycle template data to each business service, the following steps are further included:

[0013] The state of each stage of the business object is set, the process is started, and the dynamic authority is set.

[0014] Preferably, when the business object is driven from one node state to the next node state according to the processes in the process template, the following steps are further included:

[0015] According to the life cycle bound to the business object, the process bound to the current state is found, and if there is a process, the process is started, and if there is no process, the process cannot be started.

[0016] Preferably, the processes are associated with the nodes of the life cycle, and the following steps are further included:

[0017] The process node corresponding to the life cycle is created in the process template, and the approver corresponding to the process node is set; and / or,

[0018] When the process is associated, the process template that has been created is selected or a new process template is created;

[0019] and / or,

[0020] The life cycle state is bound to the process node, and then the state of the business object is modified through the interface callback of the workflow.

[0021] As another aspect of the embodiments of the present disclosure, a system for driving the progress of a business object based on a life cycle is provided, and the system comprises:

[0022] The business object management module acquires a business type of the business object, and binds a corresponding life cycle template according to the business type;

[0023] The life cycle template module customizes a layout in the life cycle template and creates a customized life cycle control, and sets a default value of the life cycle control as a default state, so that the default state takes the default state in the associated life cycle template;

[0024] The model design module shares the life cycle template data to each business service by using a distributed cache, and the business service directly acquires a plurality of node states of the life cycle from the cache, and the node states bind a plurality of processes;

[0025] The workflow driving module associates a process template with a node of the life cycle, and drives the business object to flow from a node state to a next node state according to the process in the process template.

[0026] As another aspect of the embodiments of the present disclosure, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the above-mentioned method for driving a progress of a business object based on a life cycle when executing the computer program.

[0027] As another aspect of the embodiments of the present disclosure, a computer readable storage medium is provided, which stores a computer program, and the program implements the steps of the above-mentioned method for driving a progress of a business object based on a life cycle when executed by a processor.

[0028] The present disclosure can easily nest role access and personnel to-do in a life cycle, thereby achieving management of the life cycle. One business object is bound to one life cycle, and one life cycle has a plurality of node states, and one node state can bind a plurality of processes. When processing the business object, the bound life cycle is found according to the bound life cycle, the bound process in the current state is found, and the process is started if there is a process, and the process cannot be started if there is no process. The process is started using the life cycle. After a plan is added, the state of the business object is changed to the default state of the plan life cycle, and the process is queried according to the state of the business object and the life cycle template corresponding to the business object. After the process in the state is found, the process is started in the process initiation page. BRIEF DESCRIPTION OF DRAWINGS

[0029] Figure 1 The flowchart of the method for driving a progress of a business object based on a life cycle in the embodiments of the present disclosure is shown in FIG. 1;

[0030] Figure 2 The schematic flowchart of the life cycle in the embodiments of the present disclosure is shown in FIG. 2;

[0031] Figure 3 Figure 1 is a diagram illustrating creating a custom life cycle control according to an embodiment of the present disclosure;

[0032] Figure 4 Figure 2 is a diagram illustrating obtaining all node states in a life cycle according to an embodiment of the present disclosure;

[0033] Figure 5 Figure 3 is a diagram illustrating model design according to an embodiment of the present disclosure;

[0034] Figure 6 Figure 4 is a diagram illustrating process-driven business objects according to an embodiment of the present disclosure;

[0035] Figure 7 Figure 5 is a diagram illustrating life cycle walking process according to an embodiment of the present disclosure;

[0036] Figure 8 Figure 6 is a diagram illustrating a system for driving business objects progress based on life cycle. DETAILED DESCRIPTION

[0037] Various exemplary embodiments, features, and aspects of the present disclosure will be described herein below with reference to the accompanying drawings. The same reference numbers in different drawings represent the same or similar elements. Although various aspects of embodiments are illustrated in the drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

[0038] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations.

[0039] The term "and / or" used in the present text is only used to describe associated objects with their associated relationship, indicating that there can be three relationships, for example, A and / or B, which can represent the existence of A alone, the existence of A and B at the same time, and the existence of B alone. In addition, the term "at least one" in the present text means any one of the plurality or any combination of at least two of the plurality, for example, including at least one of A, B, and C, which can mean including any one or more elements selected from the set consisting of A, B, and C.

[0040] In addition, in order to better illustrate the present disclosure, numerous specific details are given in the specific embodiments below. Those skilled in the art should understand that the present disclosure can also be implemented without certain specific details. In some examples, methods, means, elements and circuits that are well known to those skilled in the art are not described in detail in order to highlight the main idea of the present disclosure.

[0041] It can be understood that the above-mentioned various method embodiments mentioned in the present disclosure can be combined with each other to form combined embodiments without deviating from the principle logic. Due to the limited space, the present disclosure will not be repeated.

[0042] In addition, the present disclosure also provides a life cycle driven business object progress system, an electronic device, a computer readable storage medium and a program, which can be used to implement any of the life cycle driven business object progress methods provided by the present disclosure. The corresponding technical solutions and descriptions are described in the method part and are not repeated.

[0043] The execution subject of the life cycle driven business object progress method can be a computer or other device capable of realizing deep learning data privacy protection. For example, the method can be executed by a terminal device or a server or other processing device. The terminal device can be a user equipment (UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. In some possible implementation manners, the life cycle driven business object progress method can be realized by a processor calling computer readable instructions stored in a memory.

[0044] Generally, a life cycle can be represented by a directed graph, which is used to describe states and transitions between states, show the behavior of an object, and show how an object responds to various events, which can include various external and internal behaviors.

[0045] Embodiment 1

[0046] As an aspect of the embodiments of the present disclosure, a life cycle driven business object progress method is provided, which comprises the following steps: Figure 1 as shown, comprising the following steps:

[0047] S10, obtaining a business type of a business object, and binding a corresponding life cycle template according to the business type;

[0048] S20, customizing a layout in the life cycle template and creating a customized life cycle control, and setting a default value of the life cycle control as a default state, so that the default state is associated with a default state in the corresponding life cycle template;

[0049] S30, sharing the life cycle template data to each business service using a distributed cache, and the business service directly obtains a plurality of node states of the life cycle from the cache, and the node states are bound to a plurality of processes;

[0050] S40 is a process template associated with the nodes of the lifecycle. The process template drives the business object to flow from one node state to the next node state.

[0051] Based on the above configuration, this embodiment of the disclosure can easily embed role access and personnel to-do lists into the lifecycle, thereby achieving lifecycle management.

[0052] The steps of each embodiment of this disclosure will be described in detail below.

[0053] S10. Obtain the business type of the business object and bind the corresponding lifecycle template according to the business type;

[0054] Among them, such as Figure 2 As shown, in a project management system, besides project objects, there are also common items such as plans, issues, risks, and requirements. Each object has different business logic, so different business objects need to have different lifecycles created. Each type can only be bound to one lifecycle template. After binding, you can see the status and process within that lifecycle template in the table below.

[0055] S20. Customize the layout and create custom lifecycle controls in the lifecycle template, and set the default value of the lifecycle controls to the default state, so that the default state is taken from the default state in the associated lifecycle template.

[0056] In terms of using business objects, this is achieved by creating custom lifecycle controls through a custom layout, and configuring a control within the layout; for example... Figure 3 As shown, the default value for the lifecycle control is set to "Default State". Figure 4 As shown, the default state here will be taken from the default state in the associated lifecycle template; then the state of all nodes in the lifecycle will be retrieved on the add and modify pages.

[0057] S30. Use a distributed cache to share lifecycle template data to various business services. The business services directly obtain multiple node states of the lifecycle from the cache, and the node states are bound to multiple processes.

[0058] This embodiment defines the states of business objects at each stage, the conditions for transitions between states, the management processes required for each state, and the configuration of dynamic permissions for each stage. In the case of cross-services, it sets the lifecycle for business objects and initiates the management processes required for them. After adding a state, the basic information of the state can be edited. The Chinese name, English name, and data value of the state are required fields, as shown in Table 1. The following is a description of each field:

[0059] Table 1 Field Descriptions

[0060]

[0061] As shown in Figure 5 , the model design includes the following: a lifecycle table, setting the name, version, and other basic information of the lifecycle;

[0062] A lifecycle state table: stores the information of the nodes in the lifecycle, and is a many-to-one relationship with the lifecycle,

[0063] A lifecycle state and process association table: a relationship table of nodes and process templates;

[0064] A business object is bound to only one lifecycle, and there are many node states under a lifecycle, and a node state can be bound to multiple processes;

[0065] Therefore, when processing a business object, according to the bound lifecycle, the bound process in the current state is found, and if there is a process, the process can be started, and if not, it cannot.

[0066] S40, associate a process template with a node of the lifecycle, and drive the business object from one node state to the next node state according to the process in the process template;

[0067] As shown in Figure 6 , the process template needs to be associated in the lifecycle node, and then the business object is driven from one state to the next state through the process, and the open source workflow engine actitit5.22 is used in this scheme; In the process template, the process nodes corresponding to the lifecycle are created, and the approvers corresponding to the related nodes can be set to achieve the purpose of authority control. When associating the process, the created process template can be selected or a new process template can be created through the online process designer; The lifecycle state is bound on the process node, and then the state of the business object is modified through the interface callback of the workflow.

[0068] In this embodiment, the lifecycle is used to go through the process: as shown in Figure 7 , after adding a plan, the state of the business object at this time has become the default state of the plan lifecycle, and at this time the state of the business object and the lifecycle template corresponding to the business object are used to query the process. After finding the process in the state, it enters the process initiation page, and the process can be started.

[0069] Embodiment 2

[0070] As another aspect of the embodiments of the present disclosure, as shown in Figure 8 , a lifecycle-based business object progress driving system 100 is provided, comprising:

[0071] The business object management module obtains the business type of a business object and binds the corresponding lifecycle template according to the business type.

[0072] In the project management system, besides project objects, there are also common items such as plans, issues, risks, and requirements. Within the business management module, each object has different business logic, so different business objects require different lifecycles. Each type can only be bound to one lifecycle template. After binding, the status and process within that lifecycle template can be viewed in the table below.

[0073] The lifecycle template module allows for custom layouts and creation of custom lifecycle controls within the lifecycle template. The default values ​​of the lifecycle controls are set to the default state, which is then taken from the default state in the associated lifecycle template.

[0074] In terms of using business objects, a custom layout is used to create a custom lifecycle control, which is then configured within the layout. The default value of the control is set to "default state". This default state is taken from the default state in the associated lifecycle template. Then, on the add and modify pages, the states of all nodes in the lifecycle are retrieved.

[0075] This embodiment defines the states of business objects at each stage, the conditions for transitions between states, the management processes required for each state, and the configuration of dynamic permissions for each stage. In the case of cross-services, it sets the lifecycle for business objects and initiates the management processes required for them. After adding a state, the basic information of the state can be edited. The Chinese name, English name, and data value of the state are required fields, as shown in Table 2. The following is a description of each field:

[0076] Table 2 Field Descriptions

[0077]

[0078] The model design module uses a distributed cache to share lifecycle template data to various business services. The business services directly obtain multiple node states of the lifecycle from the cache, and the node states are bound to multiple processes.

[0079] The model design module includes the following: a lifecycle table, which sets basic information such as the lifecycle name and version;

[0080] Lifecycle status table: Stores information about nodes in the lifecycle, and has a many-to-one relationship with the lifecycle time.

[0081] Lifecycle status and process association table: a table showing the relationship between nodes and process templates;

[0082] One business object only binds one life cycle, one life cycle has many node states, and one node state can bind multiple processes.

[0083] Therefore, when processing a business object, according to the bound life cycle, the bound process in the current state is found, and if there is a process, the process can be started, and if not, it cannot.

[0084] The workflow driving module associates the process template with the node of the life cycle, and drives the business object from one node state to the next node state according to the process in the process template.

[0085] In the life cycle node, the process template needs to be associated, and then the business object is transferred from one state to the next state through the process driving. The present scheme uses the open source workflow engine actitit5.22. In the process template, the process nodes corresponding to the life cycle are created, and the approvers corresponding to the related nodes can be set to achieve the purpose of authority control. When the process is associated, the created process template can be selected, or a new process template can be created through an online process designer. The life cycle state is bound on the process node, and then the state of the business object is modified through the interface callback of the workflow.

[0086] In the present embodiment, after a plan is added, the state of the business object has become the default state of the plan life cycle, and the state of the business object and the life cycle template corresponding to the business object are used to query the process. After the process in the state is found, the process initiation page is entered, and the process can be started.

[0087] Embodiment 3

[0088] An electronic device includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor implements the method for providing a life cycle-based driving business object progress in embodiment 1 when executing the computer program.

[0089] The embodiment 3 of the present disclosure is only one example, and should not bring any limitation to the function and use range of the embodiment of the present disclosure.

[0090] The electronic device can be in the form of a general computing device, for example, it can be a server device. The components of the electronic device can include but are not limited to at least one processor, at least one memory, a bus connecting different system components including the memory and the processor.

[0091] The bus includes a data bus, an address bus, and a control bus.

[0092] The memory can include volatile memory (e.g., random access memory (RAM)), cache memory, flash memory, or any other suitable memory.

[0093] The memory can further include a program tool having a set (at least one) of program modules that include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, and each of such examples or some combination thereof, can include implementation of a network environment.

[0094] The processor performs various function applications and data processing by executing the computer program stored in the memory.

[0095] The electronic device can also communicate with one or more external devices such as a keyboard or a pointing device, through an input / output (I / O) interface. Also, the electronic device can communicate with one or more networks, such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet, through a network adapter. The network adapter can communicate with the other modules of the electronic device through the bus. It should be appreciated that although not shown in the figure, other hardware and / or software modules could be used in conjunction with the electronic device. These include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

[0096] It should be noted that although several units / modules or sub-units / modules of the electronic device are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, according to the embodiments of the present application, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided into a plurality of units / modules.

[0097] Embodiment 4

[0098] A computer readable storage medium, the readable storage medium stores a computer program, the program is executed by a processor to implement the steps of the method for providing a business object progress based on a life cycle in embodiment 1.

[0099] More specifically, the readable storage medium can include, but is not limited to: a portable disc, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0100] In a possible implementation, the present disclosure can also be implemented in the form of a program product, which includes program codes for causing an end device to perform the steps of providing a life cycle driven business object progress based service as described in embodiment 1 when the program product is run on the end device.

[0101] Wherein the program code for carrying out the present disclosure can be written in any combination of one or more programming languages, which can be executed entirely on the user device, partially on the user device, as a standalone software package, partially on the user device and partially on a remote device, or entirely on a remote device.

[0102] Although the embodiments of the present disclosure have been shown and described, it will be understood by those of ordinary skill in the art that various changes, modifications, alternatives, and variations can be made thereto without departing from the principles and spirit of the present disclosure, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A lifecycle-driven business object progress method, characterized in that, Includes the following steps: Obtain the business type of the business object, and bind the corresponding lifecycle template according to the business type; Custom layout and custom lifecycle controls are created in the lifecycle template. The default value of the lifecycle controls is set to the default state, so that the default state is taken from the default state in the associated lifecycle template. Distributed caching is used to share lifecycle template data to various business services. The business services directly obtain multiple node states of the lifecycle from the cache, and the node states are bound to multiple processes. For each node in the lifecycle, a process template is associated with the process, and the business object is driven to flow from one node state to the next node state according to the process in the process template. The node association process template for the lifecycle specifically includes the following steps: Create process nodes corresponding to the lifecycle in the process template, and set the approvers for the process nodes; When associating processes, select an existing process template or create a new one; Bind lifecycle states to process nodes, and then modify the state of business objects through workflow interface callbacks.

2. The method for driving business object progress based on lifecycle as described in claim 1, characterized in that, The process template sets up review nodes and reviewers corresponding to the node status to control permissions.

3. The lifecycle-driven business object progress method as described in claim 1 or 2, characterized in that, Each business type is bound to a lifecycle template.

4. The lifecycle-driven business object progress method as described in claim 3, characterized in that, The lifecycle template also needs to define the state of the business object at each stage, the conditions for transition between states, the management process required for each state, and the configuration of dynamic permissions for each stage.

5. The lifecycle-driven business object progress method as described in any one of claims 4, characterized in that, After sharing lifecycle template data to various business services using distributed caching, the following steps are also included: Set the status of each stage, start the process, and set dynamic permissions for business objects.

6. The lifecycle-driven business object progress method as described in claim 1 or 2, characterized in that, When the business object is driven to transition from one node state to the next node state according to the process template, the following steps are also included: Based on the lifecycle of the business object, find the process bound to it in the current state. If a process exists, start the process; otherwise, the process cannot be started.

7. A lifecycle-driven business object progress system, characterized in that, include: The business object management module obtains the business type of a business object and binds the corresponding lifecycle template according to the business type. The lifecycle template module allows for custom layouts and creation of custom lifecycle controls within the lifecycle template. The default values ​​of the lifecycle controls are set to the default state, which is then taken from the default state in the associated lifecycle template. The model design module uses a distributed cache to share lifecycle template data to various business services. The business services directly obtain multiple node states of the lifecycle from the cache, and the node states are bound to multiple processes. The workflow-driven module associates lifecycle nodes with process templates, and drives the business object to transition from one node state to the next based on the process in the template. This includes a lifecycle node association process template, specifically comprising: Create process nodes corresponding to the lifecycle in the process template, and set the approvers for the process nodes; When associating processes, select an existing process template or create a new one; Bind lifecycle states to process nodes, and then modify the state of business objects through workflow interface callbacks.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the lifecycle-driven business object progress method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the lifecycle-driven business object progress method according to any one of claims 1 to 6.

Images