Business management method and system and related product

Abstract

The embodiment of the invention discloses a business management method and system and related products, and the method abstracts and constructs tasks of all links in a business processing process into task flows, can promote all collaborative tasks to be brought into an online processing process, reduces the traditional offline workload and time delay, and promotes the business progress. In addition, the task flow is preset, so that the front-back execution sequence and the online processing content of each node task can be intuitively reflected, the detail content of each instance task can be efficiently recorded online, and the specification degree of the task can be effectively supervised; and the identity attribute of the task executor is recorded, so that a cooperation mechanism of searching for people by events can be established, and each task processing role can be ensured to quickly and accurately receive and process the task, thereby assisting the completion of the main service online in the whole process, and meeting the handling requirement of online cooperation in a human resource service scene.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of resource management technology, and in particular, to business management methods, systems and related products. Background Art

[0002] There are a large number of collaborative affairs in the process of human resources (HR) business processing. Taking the main business such as "joining, regularization, transfer, and resignation" that frequently occurs in human resources management business scenarios as an example, when an employee undergoes a personnel change, in addition to the professional business centered on HR (such as joining salary, social security registration, etc.) that needs to be processed, there are also collaborative affairs involving different fields or links such as administration, attendance, information technology (IT), and finance. For example, dormitory arrangements at the time of joining, financial settlement at the time of leaving, account recovery, and other transactional work.

[0003] At present, although an online business processing system is provided, the online performance of this business processing system is mainly to provide a single process approval and recording service around the established bill of lading information. Specifically, online, it can only support the task specialists of each node to enter their approval results (agree or disagree) and / or approval opinions. In fact, it still relies on offline manual processing methods (such as the delivery and manual approval of paper documents). The processing process or review details of each collaborative transaction cannot be objectively and truly reflected online. Such a business processing model is also prone to lack of effective progress promotion and supervision, resulting in incomplete or erroneous information transmission, low efficiency, and affecting the development of subsequent work. Summary of the invention

[0004] The embodiments of the present application provide a business management method, system and related products for incorporating tasks in various links of the collaborative business processing process into online processing, thereby reducing the workload and error rate of offline processing.

[0005] A first aspect of an embodiment of the present application provides a service management method, including:

[0006] Obtain task flows constructed for various types of historical main businesses respectively; the task flows of the historical main businesses are composed of various template tasks required to complete the historical main businesses arranged by nodes, and the identity attributes of the executors of each template task are recorded; wherein, each preceding template task has at least one succeeding template task adjacent to it, and in an instance, when the task status of the preceding template task is completed and / or the actual value of the rule field of the succeeding template task meets a preset condition, the succeeding template task is determined as an applicable template that allows the creation of a corresponding instance task;

[0007] Determine the target task flow corresponding to the current main business from each group of the task flows, start from the first preceding template task in the target task flow, refer to the sample content of the preceding template task, extract the corresponding instance content from the instance document information of the current main business to create a preceding instance task; determine the applicable template from at least one subsequent template task based on the task status of the preceding instance task and / or the actual value of the rule field of at least one subsequent template task, and create a subsequent instance task with reference to the applicable template;

[0008] Based on the identity attribute corresponding to each selected template task, each instance task is assigned to an executor that meets the identity attribute for processing.

[0009] When the method described in the first aspect of the present application is implemented, the content described in the second aspect of the present application can be adopted to achieve it.

[0010] A second aspect of an embodiment of the present application provides a business management system, including: an acquisition unit and a processing unit;

[0011] The acquisition unit is used to obtain task flows constructed for various types of historical main businesses respectively; the task flow of the historical main business is composed of various template tasks required to complete the historical main business arranged by nodes, and the identity attributes of the executor of each template task are recorded; wherein, each preceding template task has at least one succeeding template task adjacent to it, and in an instance, when the task status of the preceding template task is completed and / or the actual value of the rule field of the succeeding template task meets the preset conditions, the succeeding template task is determined as an applicable template that allows the creation of a corresponding instance task;

[0012] The processing unit is used to determine the target task flow corresponding to the current main business from each group of the task flows, start from the first preceding template task in the target task flow, refer to the example content of the preceding template task, extract the corresponding instance content from the instance document information of the current main business to create a preceding instance task; based on the task status of the preceding instance task and / or the actual value of the rule field of at least one subsequent template task, determine the applicable template from at least one subsequent template task, and create a subsequent instance task with reference to the applicable template;

[0013] The processing unit is further configured to, based on the identity attribute corresponding to each selected template task, assign each instance task to an executor that meets the identity attribute for processing.

[0014] A third aspect of an embodiment of the present application provides an electronic device, including: a processor and a memory;

[0015] The processor is configured to communicate with the memory and execute instructions in the memory to implement the method described in the first aspect of the embodiment of the present application or any specific implementation of the first aspect.

[0016] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed by a processor, they implement the method described in the first aspect of the embodiment of the present application or any specific implementation of the first aspect.

[0017] A fifth aspect of an embodiment of the present application provides a computer program product, which includes computer instructions. When the computer instructions are executed by a processor, they implement the method described in the first aspect of the embodiment of the present application or any specific implementation of the first aspect.

[0018] It can be seen from the above technical solutions that the embodiments of the present application have at least the following advantages:

[0019] The embodiment of the present application abstracts the tasks of each link in the business processing process into a task flow, which can promote the inclusion of various collaborative tasks into the online processing process, reduce the traditional offline workload and delay, and promote business progress. In addition, the preset task flow can intuitively reflect the execution order and online processing content of each node task, which helps to efficiently record the details of each instance task online and effectively supervise the standardization of the task; and recording the identity attributes of the task executor can establish a "find a person for the task" collaboration mechanism to ensure that each task processing role can quickly and accurately receive and process tasks, thereby assisting in the completion of the main business online throughout the process, and meeting the requirements for online collaboration in human resources business scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0021] It should be noted that, although the steps in the process diagrams (if any) involved in the embodiments are drawn in sequence as indicated by the arrows, unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.

[0022] Figure 1 A schematic diagram of a system architecture of the business management method according to an embodiment of the present application;

[0023] Figure 2 A flowchart of the service management method according to an embodiment of the present application;

[0024] Figure 3.1 A schematic diagram of the onboarding business of the business management method of an embodiment of the present application;

[0025] Figure 3.2 This is a schematic diagram of the onboarding task flow of the business management method according to an embodiment of the present application;

[0026] Figure 4 It is a standard activity view of the service management method of the embodiment of the present application;

[0027] Figure 5 This is a business document view of the business management method of the embodiment of the present application;

[0028] Figure 6 A cross-domain view of the business management method of the embodiment of the present application;

[0029] Figure 7 Create a flowchart for the tasks of the business management method of the embodiment of the application;

[0030] Figure 8 This is a task processing diagram of the business management method according to an embodiment of the present application;

[0031] Fig. 9 A schematic diagram of task components of the business management method according to an embodiment of the present application;

[0032] Fig.10 A schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of this application.

[0034] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims and drawings of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0035] In the following description, similar expressions such as "a specific implementation" or "a specific example" are involved, which describe a subset of all possible embodiments, but it can be understood that "a specific implementation" or "a specific example" can be the same subset or different subsets of all possible embodiments, and can be combined with each other without conflict. In the following description, the term multiple refers to at least two. In some specific examples, the numerical value mentioned in this application reaches the threshold value (if any), which may include the case where the former is greater than the latter of the threshold value; if similar expressions such as "any" or "at least one" are mentioned, it can specifically refer to any one of the listed examples or any combination of these examples.

[0036] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0037] The method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 101 through the network, and the data storage system 100 can store the data that the server 101 needs to process or needs, such as the task flows constructed for various types of historical main businesses in the embodiments of the present application. The data storage system 100 can be integrated on the server 101, or it can be placed on the cloud or other network servers. The terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers and portable wearable devices. The portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server 101 can be implemented with an independent server or a server cluster consisting of multiple servers.

[0038] Terminal 102 can send the current main business (such as onboarding business) and its instance document (such as onboarding document) information to be processed to server 101. Server 101 can determine that the target task flow corresponding to the current main business is the onboarding task flow from each group of task flows, and start from the first pre-template task in the target task flow, refer to the example content of the pre-template task, and extract the corresponding instance content from the instance document information of the current main business to create a pre-instance task; based on the task status of the pre-instance task and / or the actual value of the rule field of at least one post-template task, determine the applicable template from at least one post-template task, and create a post-instance task with reference to the applicable template. Afterwards, server 101 can assign each instance task to an executor that meets the identity attributes for processing based on the identity attributes corresponding to each selected template task.

[0039] It should be noted that the method provided in the embodiment of the present application can be implemented by the terminal device and the server as described above, or can be implemented entirely on the server side, or can be implemented entirely on the terminal device side, which can be determined according to the actual application scenario and is not limited here. The method of the present application will be described in detail below.

[0040] See also Figure 2 In a first aspect, the present application provides a specific embodiment of a service management method, which includes the following steps:

[0041] Step S21, obtaining task flows constructed for various historical main businesses;

[0042] The task flow of the historical main business is composed of various template tasks required to complete the historical main business, which are arranged according to nodes, and the identity attributes of the executor of each template task are recorded; among them, each preceding template task has at least one succeeding template task adjacent to it. In the instance, when the task status of the preceding template task is completed and / or the actual value of the rule field of the succeeding template task meets the preset conditions, the succeeding template task is determined as an applicable template that allows the creation of the corresponding instance task.

[0043] The main business of the embodiment of this application can be onboarding, regularization, transfer, resignation, salary submission, probation management (requiring evaluation by mentors, managers, etc.), cross-store personnel support and other business scenarios that require multi-party collaboration. These collaborators are generally cross-domain, such as HR professional field, administrative field, attendance field, financial field, etc. For the convenience of explanation and understanding, the embodiment of this application mainly uses the onboarding business process as an example. Figure 3.1 As shown, the onboarding of corporate employees involves multiple collaborative links and multiple fields, and each link needs to handle different matters.

[0044] Specifically, based on a series of onboarding-related activities (or collaborative tasks) initiated in the history of different enterprises and the corresponding required information, the content of each node task required for the entire onboarding process (such as the information to be reviewed, the task executor or role responsible for reviewing the information) can be summarized, and the execution order (pre- or post-) between the node tasks can be arranged (such as Figure 3.2 As shown), a set of online onboarding task flows is preset, so that this onboarding task flow can be applied in the example scenario to quickly and accurately create example tasks of each link online. In other words, the onboarding task flow of the embodiment of the present application flexibly presets all possible related activities related to onboarding based on activity arrangement, defines the before and after creation logic or execution order of each node task, and also incorporates a rich set of process roles into the business processing process, which can provide online operation guidance for the handling of employee onboarding business in the example scenario, and realize cross-domain online integrated collaborative services.

[0045] like Figure 3.1 As shown, the above-mentioned node task can be at least one of the activities of initiating employment application, salary setting, employment reporting, contract signing, item collection, account activation, etc. The post-task adjacent to the "labor contract signing" task can be at least one of the following: reporting in, office supplies collection, account / authorization activation, dormitory confirmation, and work card processing. These post-tasks can be executed successively or simultaneously when they are at the same execution node, which can be set according to the actual situation and is not limited here; among them, activities involving the allocation or use of objects, such as office supplies collection tasks, can include details such as online submission of application information, online approval confirmation, online allocation and registration of object numbers, etc., which can be set according to the actual situation and are not limited here.

[0046] Step S22: Create corresponding instance tasks by referring to the examples of various template tasks in the target task flow corresponding to the current main business.

[0047] Specifically, the target task flow corresponding to the current main business can be determined from each group of task flows, starting from the first pre-template task in the target task flow, referring to the sample content of the pre-template task, extracting the corresponding instance content from the instance document information of the current main business to create the pre-instance task. This instance document can be an onboarding document for a new employee submitted online by HR, which records the name, job title, date of employment, department, and other instance content of the new employee. Afterwards, based on the task status of the pre-instance task and / or the actual value of the rule field of at least one post-template task, an applicable template can be determined from at least one post-template task, and a post-instance task can be created with reference to the applicable template.

[0048] It can be seen that the embodiment of the present application abstracts the business processing functions involved in each link of human resources business processing, and constructs a set of optional supporting workflows (or collaborative task models) as a reference for instance applications, which presets that every two template tasks have a mutually exclusive or parallel alternative relationship in the actual execution scenario, and whether the post-template task can be created in the instance is determined based on the task status of the pre-template task in the instance and / or the value of the post-template task in the instance, as well as the identity attributes of the executors of each task (such as the role of the reviewer, the department to which he belongs, etc.). Specifically, when there are multiple post-template tasks for the pre-instance task, the task status of the pre-instance task (completed or uncompleted) and the actual value of the rule field corresponding to each post-template task in the instance document information can be extracted, and the post-template task whose status is completed and / or the actual value of the rule field meets the preset conditions is used as the applicable template, that is, to determine which item listed in the task flow the post-template task is. Figure 3.1 As shown, after the online confirmation of the signing of the labor contract is completed (it can be an electronic contract), the post-template task can be at least one of dormitory confirmation and work card processing, and this rule field can be at least one information field of the party's rank, position, and academic qualifications in the main business.

[0049] Step S23: Based on the identity attribute corresponding to each selected template task, each instance task is assigned to an executor that meets the identity attribute for processing.

[0050] As explained above, for example, if the party has a higher education than a bachelor's degree, a "specialist talk" is required (this task can be assigned to a talk specialist after creation), parties with a job level of M3 or above need to sign a non-compete agreement (this task can be assigned to a contract preparation specialist after creation), and power safety officers need to be assigned a dormitory (this task can be assigned to a dormitory administrator after creation). In actual scenarios, the allocation time and execution time of each instance task can be in a sequential relationship, or can be performed simultaneously, which can be determined by the actual situation and is not limited here.

[0051] In summary, the embodiments of the present application abstract the tasks of each link in the business processing process into a task flow, which can promote the inclusion of various collaborative tasks in the online processing process, reduce the traditional offline workload and delay, and promote business progress. In addition, the preset task flow can intuitively reflect the execution order and online processing content of each node task, which helps to efficiently record the details of each instance task online and effectively supervise the standardization of the task; and recording the identity attributes of the task executor can establish a "find the person for the task" collaboration mechanism to ensure that each task processing role can quickly and accurately receive and process the task, so as to assist in completing the main business online throughout the process and meet the requirements of online collaboration in human resources business scenarios.

[0052] Based on the above example descriptions, the method of the present application will be further described in detail below, and some specific possible implementation examples will be provided. In actual applications, the implementation contents between these examples can be combined or implemented separately as needed according to the corresponding functional principles and application logic. If implemented in combination, the execution order between the combined examples can be determined according to their respective processing logics, which may be determined by the actual scenario.

[0053] In some examples, after S21, the method of the embodiment of the present application may further include (pre-setting inspection items): for template tasks whose executors are non-target specialists, rendering the inspection items in the template tasks to prompt that after the corresponding instance tasks are created from the template tasks, the instance contents belonging to the inspection items in the instance tasks are inspected; in the instance, if the inspection items require cooperation from collaborators other than the non-target specialists, sending a collaboration request to the collaborators.

[0054] Online inspection is important in the collaborative task processing process. The embodiment of the present application presets inspection items that are not available in the traditional online approval business system, which can realize online inspection of each task, ensure that the business processing process is traceable, effectively correct errors, and standardize the task content. Specifically, the inspection items can be set so that the front end renders the corresponding inspection item processing area, thereby completing the transaction inspection online. Figure 4 As shown, you can set the check of each related transaction to be completed one by one by checking (check if completed). This related transaction can be "whether the deposit has been paid, whether the attendance data synchronization has been completed". Of course, the check items can also be to check whether the required information is filled in, check whether the information filling format is incorrect, etc. In addition, the check items can be configured as automatic check items or collaborative check items. If it is an automatic check item that can be checked by itself, it can automatically check whether this related transaction is completed and automatically check it according to the configured check conditions. If it is a related transaction check that cannot be completed by itself (i.e. collaborative check item), such as issuing work cards, assigning dormitories and other transaction processing activities that are not handled by HR full-time (such as requiring collaborative processing by logistics specialists or dormitory managers), a service function of selecting collaborators and sending collaboration requests to collaborators can be provided to request the collaborators to cooperate in completing the transaction check; the way to send the collaboration request can be to send a collaboration request message or send the related transaction information that needs to be collaborated, that is, you can request or prompt the collaborator to participate in the transaction check online, supervise the task online and advance the task progress, and reduce the pressure of offline transaction docking.

[0055] In some examples, the task flow construction process includes: dividing the information of each template task according to different dimensions, so that the instance task information created corresponding to the template task of the same dimension is integrated and displayed in one type of view; the dimensions include information review class, the executor is the target specialist, and the executor is the non-target specialist.

[0056] In the enterprise resource management scenario, the above-mentioned target specialist may refer to a full-time HR staff member, and the non-target specialist may refer to a related affairs collaborator other than HR, such as dormitory managers, account managers, legal and other foreign affairs managers; this related affairs may refer to the related business that needs to be done while completing the main business (such as joining the company), such as dormitory allocation, resignation settlement, calling and re-signing contracts, etc. The embodiment of the present application configures views of corresponding dimensions for each template task based on different business configurations, so that the front-end page can be personalized according to the characteristics and functions of the task to meet different task processing requirements. The three types of views corresponding to the above three dimensions can be standard activity task view, business document view, and cross-domain view, respectively.

[0057] like Figure 4 As shown in the figure, the standard activity view mainly supports the initiation of transaction-related activities, such as issuing work cards, assigning dormitories, arranging tutors, handing over work, signing contracts and other related tasks, and provides basic business information (such as card name, card deposit) and employee personal information (such as entry date, entry position) that can be viewed by the current task handler. Generally, the background can obtain the page configuration table (or uipk) applicable to each applicable document - used to indicate which fields of the applicable document need to be configured and displayed, so as to render the standard activity view corresponding to the current applicable document. For example, the resignation document has a special page configuration table, which specifically configures the fields such as "resignation time, name" and needs to be configured for the task handler (i.e. the task executor or assignor); the entry document also has a dedicated page configuration table, which specifically configures the fields such as "entry time, name, entry position" and needs to be configured for the task handler. In actual situations, the page configuration table can be customized by need, and is not limited here.

[0058] like Figure 5 As shown in the figure, the business document view mainly faces or supports business information review activities, such as probationary period regularization, salary submission, job grade adjustment and other tasks that need to be reviewed. Based on the configuration of the business document view, it can provide functions such as review and modification of the main business information. Generally, the background can obtain all business document views adapted to the document type through the document type (such as entry document, resignation document) and the corresponding preset rules; in simple terms, the entry document corresponds to at least one style of business document view (or style map for short) for selection and display, and the resignation document also corresponds to at least one style of business document view for selection and display. These two parts of business document views are isolated from each other. For example, the entry document cannot use the style map of the resignation document for display, but must use the style map specifically corresponding to the entry document for display, because different types of documents have different subject information and / or different viewers. The reason why multiple styles of business document views are set for each type of document is that different processors have different permissions or want to see different information fields.

[0059] Cross-domain views are mainly oriented towards or support HR professional functional activities, such as onboarding information review, onboarding salary setting, resignation approval and other tasks that need to be handled by HR specialists. Similarly, the background can pre-define which specifically applicable cross-domain views are available for each task under each type of document for selection and display. For example, specific tasks such as onboarding with salary setting and newly signed labor contracts, and special tasks such as resignation without salary setting and newly signed labor contracts but possibly signed non-compete agreements. Furthermore, these tasks can each be equipped with some optional cross-domain view templates. Specifically, the cross-domain view template style dedicated to the onboarding salary setting task can be as follows Figure 6 As shown, it contains fields for information such as salary standard, fixed salary, and signing fee. This is just an example. The design of each view can be customized according to the actual situation, and there is no limit here.

[0060] On the other hand, the information displayed in the cross-domain view can come from the integrated functions of external systems or interfaces, which can be cross-domain, such as HR professional field, administrative field, attendance field, financial field, etc. In other words, the view of the embodiment of the present application, such as the cross-domain view, can integrate information from different fields or different platforms (such as salary standards), so that the required information can be quickly associated online without the need to retrieve information offline across fields or regions as traditionally. It can be seen that the embodiment of the present application can connect and interact with scattered information, reduce the complexity of collaborative tasks in the process of completion, and speed up the completion of tasks.

[0061] In summary, the three types of views, namely, the standard activity task view, the business document view, and the cross-domain view, respectively sort out and display the operational details of various collaborative tasks in a certain type of main business from three perspectives, that is, the combination of the three types of views fully reflects the entire process of handling the main business. Generally, these three types of views will not be displayed at the same time, and will not distinguish between priority relationships or importance. When setting activity tasks, business administrators can switch to view these three types of views, that is, they can choose which type of view to view.

[0062] Specifically, the standard activity task view mainly supports transactional processing activities, and its key tasks are: obtaining key information of the main business to carry out independent transactional work processing; supporting cross-system transaction processing information acquisition; supporting rapid expansion of transactional information, online inspection of offline transactions, and multi-role collaborative response. In some examples, the task handler can choose to initiate related documents (or initiate related business) in the standard activity task view, such as initiating a work card processing task, and can flexibly fill in the name of the party, card name, card deposit and other related transaction processing field information in the standard activity task view; generally, the related document table can be used to record which related documents can be initiated by a certain type of main business.

[0063] The business document task view mainly supports business information review activities. Its key tasks include: verifying and confirming the key business information; associating employee change records with file information; and supporting operations such as querying and modifying key business information.

[0064] The cross-domain business task view mainly supports professional activities of HR functions. Its key tasks include: obtaining key information of the main business to process professional business activities in this field; forming employee business records or business files according to the business logic of this field; supporting HR professional task processing based on main business triggers, including business initiation, information maintenance, etc.

[0065] In some examples, the task flow construction process includes: setting multiple triggering methods for each template task in the task flow to meet various opportunities for the template task to create corresponding instance tasks; based on the occurrence time of the template task in history and / or the task implementation logic, the time for each template task to create the corresponding instance task is divided into immediate creation or non-immediate creation.

[0066] In order to meet various implementation scenarios or creation conditions and ensure the smooth creation of tasks, you can set up the creation mechanism for each task. Figure 7 As shown, specifically, three triggering methods can be set: workflow triggering, background transaction triggering, and manual triggering, so that tasks can be created no matter which method is used to trigger them. The above workflow triggering means defining the task nodes in advance, and creating the corresponding tasks at which nodes; the background transaction triggering means defining what the post-tasks adjacent to each predecessor task are (that is, the relationship between tasks can be regarded as the task creation rule), and automatically creating the post-tasks once the predecessor tasks are completed; the manual triggering means manually clicking to trigger a task.

[0067] In addition, in order to avoid concurrently requiring the creation of multiple tasks, resulting in unreasonable resource allocation, long waiting time or process blockage, the historical occurrence time of the task and / or the task implementation logic can be obtained to determine whether the task is created immediately (or directly) or not (that is, delayed or advanced creation), so as to disperse the pressure of creating a large number of tasks and meet the actual business needs at the same time. For example, in the historical situation, the information review task was created 3 days before the employee reported to work, then the on-the-job information review task can be divided into a non-immediately created task, so that in the instance scenario, the on-the-job information review task for a certain employee can be designed to be created in advance (the advance time can be determined by the needs). Immediately created tasks can refer to tasks that can only be created after the task implementation logic (such as the need to click to confirm or the completion of the preceding task, etc.) is determined, such as the task of signing a new contract after joining the company. Of course, whether some tasks are created immediately or not can be determined based on their historical occurrence time and task implementation logic, etc., which will not be described in detail.

[0068] In some examples, after S21, the method of the embodiment of the present application may also include (asynchronous loading and rendering information): distinguishing the example content in the template task into key content and non-key content, and setting the key content as the first-screen loading content compared to the non-key content, so as to prompt the instance task created by the template task to first load and display the instance content corresponding to the first-screen loading content when displaying the instance content.

[0069] In actual applications, in order to improve the first screen loading speed of the page and ensure the user's reading experience, asynchronous loading and time-sharing information display can be designed. Specifically, factors such as cross-platform compatibility and performance optimization can be considered, as well as to ensure fast page loading speed, smooth animation, and natural interaction to improve the user experience. In the rendering of collaborative task processing pages, the task page can be divided into multiple layers through layered rendering according to the composition of the task page view (such as task information fields, controls, etc.), and the layer where the key content (such as the date of employment, inspection item content, party information and other key task information) is located is designed to be rendered and displayed in the view first, and the layer where the non-key content (such as progress information, processing records, operation instructions, etc.) is located is rendered and displayed in the view in a delayed manner; each layer can be rendered and synthesized independently to improve rendering performance. For complex collaborative task pages, such as pages containing cross-domain business views, task information views, task function views, and task processing process monitoring, the asynchronous processing method of loading and rendering key content first and then gradually loading other non-key content can effectively improve the first screen loading speed of the page and improve the user experience. At the same time, the application of caching and pre-rendering technology can be used to reduce user waiting time. In addition, the user's operating habits and changes in page content can be considered to intelligently adjust the rendering strategy to ensure the application experience of collaborative task processing users.

[0070] In some examples, a task allocation mechanism can be set up to determine the actual assignee (i.e., executor) of each task. Task allocation can include automatic allocation and manual allocation. The collaborative task allocation mechanism is implemented through a collaborative task allocation rule table and a collaborative task allocation rule detail table. The collaborative task allocation rule table is mainly used to record the basic information of key allocation rules, including key collaborative task processing objects such as users, roles, positions, employees, and the priority of this allocation rule. The collaborative task allocation rule detail table mainly records rule codes, rule fields, rule comparison operators, and rule values. After a collaborative task is created, the executor can be automatically assigned according to the allocation rules. Through the design of rule fields and conditional logic (i.e., whether the preset conditions are met), it is possible to dynamically take values ​​of rule fields and compare them with preset rule values, and then calculate the final actual assignee based on the relationship and priority, that is, determine who will handle the created task. The rule field can fully obtain the information required in the actual business processing process, including business information (such as employment form, department, rank and other information) and employee information (such as age, education and other personal background information not related to the position). Among them, employee information can be found from the corresponding employee file information through the designed structure configuration template (which can be regarded as a tool table for fully displaying and obtaining employee information). In some examples, the collaborative task allocation mechanism can simultaneously support the manual allocation of collaborative tasks to be assigned and assigned by business administrators. After the collaborative task is assigned, the collaborative task details table can be used to set or record the task status as in progress, and the task status can be set to completed after the task is completed; in some examples, this collaborative task details table can record attributes such as task status (in progress, completed, etc.), task code, task subject, task processing time, etc.; among them, if the task processing time is overdue, it can remind the executor to process or be used to analyze whether the processing time is set reasonably, and when it is unreasonable, it can be used to optimize the processing time to ensure the smooth completion of the task.

[0071] In some examples, after S23, the method of the embodiment of the present application may also include (information rewriting): writing back the unique information occupied by the instance task of completing the current main business to the information collection system, so that after the next main business of the same category creates an instance task with the same intention, the instance task of the next main business is completed through other information; other information refers to information in the information collection system other than the unique information.

[0072] Specifically, the data of the third-party system (such as the dormitory management system, asset management system, etc.) can be obtained by configuring the input and output integrated interface, and the task information that has been filled in and assigned can be written back to the third-party system to ensure that the data is updated synchronously and that the use does not conflict. For example, the dormitory management system can be called to inquire which dormitory has vacancies. After implementing the dormitory confirmation task to distribute a bed to the newcomer, the unique information such as a bed number can be written back to the dormitory management system to feedback to the dormitory management system that a bed is occupied by this newcomer, so as to avoid repeating the allocation of a bed to other newcomers next time. It can be seen that the embodiment of the present application supports simple configuration of task field information (such as financial arrears, office supplies, dormitories, etc.), and the task field can be integrated with an external system to realize the writing back and transmission of data between task processing information and external systems, and ensure the synchronous update of multi-party information.

[0073] As described above, the method of the embodiment of the present application solves the problems of offline and semi-offline processing of traditional human resources collaborative business; compared with the flexible use of document approval methods, the setting is simple, the task processing function is complete, and it meets the actual business application needs; the business scalability is good, and the applicable business, collaborative task information, and collaborative task functions can be flexibly expanded, reducing the high second-opening cost of traditional business processing; it provides a unified integration standard for rapid docking with external systems, providing a basis for the interaction between the HR system and external systems.

[0074] In some examples, a task processing mechanism can be set for each task in the embodiments of the present application. The task processing methods supported by this task processing mechanism may include completion, temporary storage, transfer, and return. Completion is the calling of the completion logic when the collaborative task handler receives the task and completes the online processing and clicks the completion button, including setting the collaborative task status to completed, and determining whether there is a post-task and after all the predecessor tasks of the post-task are completed, triggering the creation of the post-task. Temporary storage supports saving the processed task information at any time during the collaborative task processing (such as supplementing information in the middle), and the task status at this time does not change (still being processed). Transfer supports changing the executor of the current task, such as transferring it to other people for processing, and the task status does not change (still being processed). Return supports returning the task in the plan to the predecessor task, changing the current task status to returned, and re-creating the predecessor task. For example, re-create a to-do task "Onboarding Information Review".

[0075] In some examples, the task information of the embodiments of the present application can be rendered in a personalized manner. For example, the configured information can be further processed based on the existing field controls and using CSS style settings to render different style fields on the front end, such as string type, time type, numeric type, drop-down box type, and other styles.

[0076] In summary, the method of the embodiment of the present application can easily process all collaborative tasks in the human resources business management process of an enterprise online, with flexible configuration and low maintenance cost. On the basis of establishing a collaborative mechanism of "finding people for tasks", each task processing role receives tasks and completes the entire process of online processing. The task settings support one-stop settings for the allocation, creation, and processing mechanisms of collaborative tasks, as well as the settings of page views, task information, and task functions according to the task processing content of different collaborative activities. Figure 8 As shown, specifically including:

[0077] Support flexible configuration of page views required for processing tasks in each link of the online employee change service process;

[0078] Supports simple configuration of task field information, and task fields can be integrated with external systems to achieve data rewriting and transmission between task processing information and external systems;

[0079] Supports configuring operation instructions according to task nodes, guiding the current task processor to process tasks according to standard specifications;

[0080] Supports configuration of online inspection items, and pushes collaborative messages and sends collaborative activities based on inspection items;

[0081] Supports initiation settings based on associated documents. You can select the business document to be associated with the current task to achieve integrated processing of related businesses and avoid the trouble of decentralized processing of traditional businesses.

[0082] It can be seen that the method of the embodiment of the present application breaks through the single mode of traditional human resource management-related business processing that mainly relies on business documents for approval, and through the design of the human resource task collaboration model, includes building a complete collaborative task processing mechanism for HR business collaborative task creation, collaborative task allocation, and collaborative task processing; Fig. 9 As shown, it also supports the following multi-level and multi-dimensional task components or functions to be used individually or in combination: (1) independent task components, (2) cross-business task views, (3) personalized task services, and (4) third-party integration of task information; (5) abstract special components for online human resources processing, such as online inspection activities, online signing activities, and related document initiation activities, etc., breaking down the data isolation barriers inside and outside the HR system, realizing the full online processing of integrated collaborative tasks, improving the efficiency of enterprise human resources business processing, and accelerating the process of enterprise digital transformation.

[0083] A second aspect of the present application provides a specific embodiment of a business management system, the system comprising: an acquisition unit, a processing unit;

[0084] The acquisition unit is used to obtain task flows constructed for various types of historical main businesses respectively; the task flow of the historical main business is composed of various template tasks required to complete the historical main business arranged by nodes, and the identity attributes of the executor of each template task are recorded; wherein, each preceding template task has at least one subsequent template task adjacent to it, and in an instance, when the task status of the preceding template task is completed and / or the actual value of the rule field of the subsequent template task meets the preset conditions, the subsequent template task is determined as an applicable template that allows the creation of the corresponding instance task;

[0085] The processing unit is used to determine the target task flow corresponding to the current main business from each group of task flows, start from the first preceding template task in the target task flow, refer to the sample content of the preceding template task, extract the corresponding instance content from the instance document information of the current main business, so as to create the preceding instance task; based on the task status of the preceding instance task and / or the actual value of the rule field of at least one following template task, determine the applicable template from at least one following template task, and create the following instance task with reference to the applicable template;

[0086] The processing unit is also used to assign each instance task to an executor that meets the identity attributes for processing based on the identity attributes corresponding to each selected template task.

[0087] In some examples, the processing unit is also used to:

[0088] For template tasks where the executor is not a target specialist, the check items in the template task are rendered to prompt that after the corresponding instance task is created from the template task, the instance content belonging to the check items in the instance task is checked;

[0089] In the example, if the inspection item requires the cooperation of collaborators other than the non-target specialist, a collaboration request is sent to the collaborator.

[0090] In some examples, the acquisition unit is specifically used to:

[0091] The information of each template task is divided according to different dimensions, so that the instance task information created corresponding to the template task of the same dimension can be integrated and displayed in one type of view; the dimensions include information review category, executor as target specialist, and executor as non-target specialist.

[0092] In some examples, the acquisition unit is specifically used to:

[0093] Set multiple triggering methods for each template task in the task flow to meet the various opportunities for the template task to create corresponding instance tasks;

[0094] Based on the occurrence time of the template task in history and / or the task implementation logic, the time when each template task creates the corresponding instance task is divided into immediate creation or non-immediate creation.

[0095] In some examples, the processing unit is also used to:

[0096] The example content in the template task is divided into key content and non-key content, and the key content is set as the first-screen loading content compared to the non-key content, so as to prompt the instance task created by the template task to first load and display the instance content corresponding to the first-screen loading content when displaying the instance content.

[0097] In some examples, the processing unit is also used to:

[0098] The unique information used to complete the instance task of the current main business is written back to the information collection system, so that after the next main business of the same category creates an instance task with the same intention, the instance task of the next main business can be completed through other information; other information refers to information other than the unique information in the information collection system.

[0099] In the embodiment of the present application, the operations performed by each unit of the business management system are similar to the operations described in the first aspect or any specific method embodiment of the first aspect, and will not be described in detail here. Of course, the specific implementation process of each operation in the first aspect of the present application can also refer to the relevant description of the second aspect. Specifically, the business management system of the embodiment of the present application:

[0100] (1) Satisfy HR collaborative transaction processing needs and improve collaborative task processing functions

[0101] The HR collaborative task model is based on a full abstraction of collaborative activities in human resource business scenarios. In view of the characteristics and processing requirements of information review activities, cross-domain HR functional activities and transactional processing activities, it can provide various functions for each collaborative processing link, including professional business information review, cross-domain HR business processing (such as on-the-job salary setting, on-the-job contract signing, transfer and contract modification, etc.), transaction processing information maintenance (non-business information), online task checking, initiation of related collaborative activities, initiation of related business documents, viewing of operation instructions, task processing monitoring, etc., to meet the requirements of online collaborative task processing in human resource business scenarios.

[0102] (2) Simple setup and flexible configuration based on activity scheduling

[0103] The HR collaborative task model incorporates all aspects of the actual business of the enterprise into the human resources business processing process based on activity arrangement. Through activity settings, the online processing content of each collaborative task node can be intuitively defined, including task subject, creation requirements, allocation requirements, task processing view, task processing function requirements, etc. Through solution settings, the activities required for the business process can be selected and flexibly arranged as needed to achieve parallel and serial processing of various collaborative activities. The setting process is oriented to business personnel, simple and intuitive, and easy to operate.

[0104] (3) Collaborative task processing content supports flexible expansion in multiple dimensions

[0105] View extension: The collaborative task view supports standard document views, cross-domain professional views, and standard collaborative activity views. In addition, it can flexibly extend the personalized task views required for the current collaborative task.

[0106] Functional extension: The task processing function supports online checking, initiation of related business documents, initiation of related collaborative activities, etc., and supports flexible use according to the requirements of collaborative tasks.

[0107] Field extension: Task processing information is implemented through the task field setting function, which is used as a standard function to quickly implement the expansion of task processing information.

[0108] See also Fig.10 The electronic device of the embodiment of the present application may include one or more processors (such as central processing units (CPU)) and a memory, in which one or more applications or data are stored.

[0109] The memory may be a volatile memory or a persistent memory. The program stored in the memory may include one or more modules, each of which may include a series of instruction operations in the electronic device. Furthermore, the processor may be configured to communicate with the memory and execute a series of instruction operations in the memory on the electronic device.

[0110] The electronic device may also include one or more power supplies, one or more wired or wireless network interfaces, one or more input and output interfaces, and / or one or more operating systems, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc.

[0111] The processor can execute the operations performed by the aforementioned first aspect or any specific method embodiment of the first aspect, and the details will not be repeated here.

[0112] The present application provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enable the computer to execute the method described in the first aspect or any specific implementation of the first aspect.

[0113] The present application provides a computer program product comprising instructions or a computer program. When the computer program product is run on a computer, the computer is enabled to execute the method described in the first aspect or any specific implementation of the first aspect.

[0114] It is understood that in various embodiments of the present application, the sequence number of each step does not mean the order of execution, and the execution order of each step should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The operation content added or refined in each example scheme of the above method, system or device (if any) does not necessarily have to be executed in the specific implementation. If more than two operations are added, these operations can be implemented in combination or separately, depending on the actual scenario.

[0115] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system (if any) and device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0116] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system or device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0117] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0118] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0119] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product (or computer program product) is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a business server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A business management method, characterized in that: include: Obtain task flows constructed for each type of historical main business; The task flow of the historical main business is composed of various template tasks required to complete the historical main business, which are arranged in nodes, and the identity attributes of the executor of each template task are recorded; wherein, each preceding template task has at least one succeeding template task adjacent to it, and in an instance, when the task status of the preceding template task is completed and / or the actual value of the rule field of the succeeding template task meets the preset conditions, the succeeding template task is determined as an applicable template that allows the creation of a corresponding instance task; Determine the target task flow corresponding to the current main business from each group of the task flows, start from the first preceding template task in the target task flow, refer to the sample content of the preceding template task, extract the corresponding instance content from the instance document information of the current main business to create a preceding instance task; determine the applicable template from at least one subsequent template task based on the task status of the preceding instance task and / or the actual value of the rule field of at least one subsequent template task, and create a subsequent instance task with reference to the applicable template; Based on the identity attribute corresponding to each selected template task, each instance task is assigned to an executor that meets the identity attribute for processing.

2. The business management method according to claim 1, characterized in that: After obtaining the task flows respectively constructed for various historical main businesses, the method further includes: For the template task whose executor is a non-target specialist, the check items in the template task are rendered to prompt that after the corresponding instance task is created from the template task, the instance content belonging to the check items in the instance task is checked; In the example, if the inspection item requires the cooperation of a collaborator other than the non-target specialist, a collaboration request is sent to the collaborator.

3. The business management method according to claim 1, characterized in that: The construction process of the task flow includes: The information of each template task is divided according to different dimensions so that the instance task information created corresponding to the template task of the same dimension can be integrated and displayed in one type of view; the dimension includes information review category, the executor is a target specialist, and the executor is a non-target specialist.

4. The business management method according to claim 1, characterized in that: The construction process of the task flow includes: Setting a plurality of triggering modes for each of the template tasks in the task flow to meet a plurality of opportunities for the template task to create a corresponding instance task; Based on the occurrence time of the template task in history and / or the task implementation logic, the time when each template task creates a corresponding instance task is divided into immediate creation or non-immediate creation.

5. The business management method according to claim 1, characterized in that: After obtaining the task flows respectively constructed for various historical main businesses, the method further includes: The example content in the template task is divided into key content and non-key content, and the key content is set as the first-screen loading content compared to the non-key content, so as to prompt the instance task created by the template task to first load and display the instance content corresponding to the first-screen loading content when displaying the instance content.

6. The service management method according to any one of claims 1 to 5, characterized in that: After allocating each of the instance tasks to an executor that meets the identity attributes for processing, the method further includes: The unique information occupied by the instance task of completing the current main business is written back to the information collection system, so that after the next main business of the same category creates the instance task with the same intention, the instance task of the next main business is completed through other information; the other information refers to the information in the information collection system other than the unique information.

7. A business management system, characterized in that: include: Acquisition unit, processing unit; The acquisition unit is used to obtain task flows constructed for various types of historical main businesses respectively; the task flow of the historical main business is composed of various template tasks required to complete the historical main business arranged by nodes, and the identity attributes of the executor of each template task are recorded; wherein, each preceding template task has at least one succeeding template task adjacent to it, and in an instance, when the task status of the preceding template task is completed and / or the actual value of the rule field of the succeeding template task meets the preset conditions, the succeeding template task is determined as an applicable template that allows the creation of a corresponding instance task; The processing unit is used to determine the target task flow corresponding to the current main business from each group of the task flows, start from the first preceding template task in the target task flow, refer to the example content of the preceding template task, extract the corresponding instance content from the instance document information of the current main business, so as to create the preceding instance task; Based on the task status of the preceding instance task and / or the actual value of the rule field of at least one succeeding template task, determining the applicable template from at least one succeeding template task, and creating a succeeding instance task with reference to the applicable template; The processing unit is further configured to, based on the identity attribute corresponding to each selected template task, assign each instance task to an executor that meets the identity attribute for processing.

8. An electronic device, characterized in that: include: Processor and memory; The processor is configured to communicate with the memory and execute instructions in the memory to implement the method according to any one of claims 1 to 6.

9. A readable storage medium, characterized in that: The readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method according to any one of claims 1 to 6 is implemented.

10. A computer program product, characterized in that The computer program product comprises computer instructions, and when the computer instructions are executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images