Business management method, system and related products

Abstract

The embodiment of the application discloses a business management method, system and related products, which abstractly constructs tasks of each link in a business processing process into a task flow, can promote various collaborative tasks to be included in an online processing process, reduce traditional offline workload and delay, and promote business progress. In addition, the preset task flow can intuitively reflect the execution sequence and online processing content of each node task, which is helpful to efficiently online record the details of each instance task and effectively supervise the standard degree of the task. The identity attribute of the task execution party can establish a "task-finding-person" cooperation mechanism, so that each task processing role can quickly and accurately receive and process the task, thereby assisting in completing the main business in the whole process online, and meeting the online cooperation requirements in the human resource business scene.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of resource management, and in particular, to a business management method and system and related products. BACKGROUND

[0002] In the process of human resource (HR) business, there are a large number of collaborative transactions. For example, in the human resource management business scenarios, there are frequent main businesses such as "employment, regularization, transfer, and resignation". When an employee has a personnel change, in addition to the professional business (such as employment salary setting, social security registration, etc.) centered on HR that needs to be handled, there are also collaborative transactions involving different fields or links such as administration, attendance, information technology (IT), finance, etc. For example, dormitory arrangement at the time of employment, financial settlement and account recovery at the time of resignation, and other transactional work.

[0003] At present, although an online business processing system is provided, the online performance of the business processing system mainly provides single process approval and record services around the established bill information. Specifically, online can only support task officers of each node to enter their approval results (agreement or disagreement) and / or approval opinions, which is actually still dependent on offline manual processing methods (such as paper document delivery and manual reply). The processing process or review details of each collaborative transaction cannot be objectively and truly reflected online, and such a business processing mode is also prone to lack of effective progress promotion and supervision, resulting in incomplete or incorrect information transmission, low efficiency, and affecting the subsequent work. SUMMARY

[0004] Embodiments of the present application provide a business management method and system and related products for online processing of tasks in each link of the collaborative business processing process, reducing the offline processing workload and error rate.

[0005] A first aspect of embodiments of the present application provides a business management method, comprising:

[0006] obtaining a task flow constructed for each type of historical main business; the task flow of the historical main business is arranged by nodes according to each template task required to complete the historical main business, and records the identity attribute of the execution party of each template task; wherein at least one of the adjacent post-task of each pre-task has a post-task, in an instance, when the task status of the pre-task is completed and / or the actual value of the rule field of the post-task meets the preset condition, the post-task is determined as an applicable template allowing the creation of a corresponding instance task;

[0007] determine a target task flow corresponding to the current main business from each group of the task flows, create a preceding instance task from the first preceding template task in the target task flow by referring to example content of the preceding template task and extracting corresponding instance content from instance document information of the current main business, determine the applicable template from at least one subsequent template task based on a task state of the preceding instance task and / or a rule field actual value of at least one subsequent template task, and create a subsequent instance task by referring to the applicable template;

[0008] assign each instance task to an execution party that meets the identity attribute corresponding to each selected template task for processing.

[0009] The method in the first aspect of the application can be implemented by using the content in the second aspect of the application.

[0010] The second aspect of the embodiment of the application provides a business management system, which comprises an acquisition unit and a processing unit.

[0011] The acquisition unit is configured to obtain task flows constructed for various types of historical main businesses. The task flow of the historical main business is composed of each template task required to complete the historical main business and arranged according to nodes, and records an identity attribute of an execution party of each template task. In an instance, when a task state of a preceding template task is completed and / or a rule field actual value of a subsequent template task meets a preset condition, the subsequent template task is determined as an applicable template that allows creation of a corresponding instance task.

[0012] The processing unit is configured to determine a target task flow corresponding to the current main business from each group of the task flows, create a preceding instance task from the first preceding template task in the target task flow by referring to example content of the preceding template task and extracting corresponding instance content from instance document information of the current main business, determine the applicable template from at least one subsequent template task based on a task state of the preceding instance task and / or a rule field actual value of at least one subsequent template task, and create a subsequent instance task by referring to the applicable template.

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

[0014] The third aspect of the embodiment of the application provides an electronic device, which comprises 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 embodiments or any of the specific implementation manners of the first aspect.

[0016] The fourth aspect of the embodiments of the present application provides a computer readable storage medium, the readable storage medium stores computer instructions, and the computer instructions are executed by a processor to implement the method described in the first aspect of the embodiments or any of the specific implementation manners of the first aspect.

[0017] The fifth aspect of the embodiments of the present application provides a computer program product, the computer program product includes computer instructions, and the computer instructions are executed by a processor to implement the method described in the first aspect of the embodiments or any of the specific implementation manners of the first aspect.

[0018] From the above technical solutions, the embodiments of the present application have at least the following advantages:

[0019] The embodiments of the present application abstractly construct the tasks of each link in the business processing process into a task flow, which can promote the cooperation of each task into the online processing process, reduce the traditional offline workload and delay, and promote the business progress. In addition, the pre-set task flow can intuitively reflect the execution sequence and online processing content of each node task, which is helpful for efficiently recording the details of each instance task online, effectively supervising the standard degree of the task, and establishing a "task-finding-person" cooperation 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 in the whole process online, and meet the online cooperation requirements in the human resource business scenario. BRIEF DESCRIPTION OF DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiment description. Obviously, the drawings in the following description are only some embodiments described in the present application, and other drawings can also be obtained by those skilled in the art according to these drawings.

[0021] It should be noted that although each step in the flowchart (if any) involved in each embodiment is drawn in sequence according to the arrow, unless otherwise stated in this paper, the execution of these steps has no strict sequence limitation, and these steps can be executed in other order. Moreover, at least one part of the steps in the flowchart involved in each embodiment can include multiple steps or multiple stages, which do not necessarily be 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 rotation or alternation with other steps or steps or stages in other steps.

[0022] Figure 1 A system architecture diagram of the business management method of the embodiment of the present application;

[0023] Figure 2 A flow diagram of the business management method of the embodiment of the present application;

[0024] Figure 3.1 An on-boarding business diagram of the business management method of the embodiment of the present application;

[0025] Figure 3.2 An on-boarding task flow diagram of the business management method of the embodiment of the present application;

[0026] Figure 4 A standard activity view of the business management method of the embodiment of the present application;

[0027] Figure 5 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 A task creation flow diagram of the business management method of the embodiment of the present application;

[0030] Figure 8 A task processing diagram of the business management method of the embodiment of the present application;

[0031] Figure 9 A task component diagram of the business management method of the embodiment of the present application;

[0032] Figure 10 A structure diagram of the electronic device of the embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical scheme and advantages of the present application clearer, the present application will be described in further detail below with reference to the drawings, and the described embodiments should not be regarded as limiting the present application, and all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0034] The terms "first", "second", "third", "fourth" and the like in the description and in the claims of the present application, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the use of the terms so termed is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of orderly or chronological mundane operation, reverse order operation, based on circuitry availability, based on stated preference or the like, and that "default" or "first" and "second" order or the like are not necessarily in chronological or sequential order. It is to be understood that where the application is indicated to include a list of steps or a method, procedure, system, product or apparatus, the steps or elements need not be limited to those explicitly stated or included in the process, method, system, product, or apparatus, but are intended to cover any and all possible procedures, methods, systems, products, or apparatus that include those steps or elements which, alone or in combination, are equivalent to the steps or elements specified.

[0035] In the following description, reference is made to "one implementation" or "an implementation" or "the like" which describes a subset of all possible implementations, but it is to be understood that "one implementation" or "an implementation" can be a same subset or a different subset of all possible implementations, and can be combined with each other in non-contradictory manners. In the following description, the term "a plurality of" means at least two. In the present application, if a certain value reaches a threshold (if any), in some specific examples, it can include the case that the former is greater than the threshold; if referring to "any" or "at least one" or the like, it can specifically refer to any one of the listed examples or any combination between these examples.

[0036] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description herein is for describing particular embodiments only and is not intended to be limiting of the application.

[0037] The method provided by the embodiments of the present application can be applied to the application environment as shown in Figure 1 The data storage system 100 can store data required by the server 101 to process or required by the server 101, for example, the task flow constructed for each type of historical main service in the embodiments of the present application. The data storage system 100 can be integrated on the server 101, or placed on a cloud or other network server. The terminal 102 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers and portable wearable devices. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, etc. The server 101 can be implemented by an independent server or a server cluster composed of multiple servers.

[0038] The terminal 102 can send the current main service (such as an onboarding service) to be processed and instance document (such as an onboarding document) information thereof to the server 101. The server 101 can determine, from the groups of task flows, that a target task flow corresponding to the current main service is an onboarding task flow, and starting from a first preceding template task in the target task flow, refer to example content of the preceding template task to extract corresponding instance content from the instance document information of the current main service to create a preceding instance task; based on a task state of the preceding instance task and / or actual values of rule fields of at least one subsequent template task, determine an applicable template from the at least one subsequent template task, and refer to the applicable template to create a subsequent instance task. Subsequently, the server 101 can assign each instance task to an executor meeting an identity attribute corresponding to each template task selected based on the identity attribute for processing.

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

[0040] Please refer to Figure 2 The first aspect of the present application provides a specific embodiment of a business management method, which includes the following operation steps:

[0041] Step S21, obtaining task flows respectively constructed for various types of historical main services;

[0042] The task flow of the historical main service is arranged by each template task required to complete the historical main service according to nodes, and the identity attribute of the executor of each template task is recorded; wherein, at least one subsequent template task adjacent to each preceding template task, when the task state of the preceding template task is completed and / or the actual value of the rule field of the subsequent template task meets the preset condition, the subsequent template task is determined as an applicable template allowing the creation of a corresponding instance task.

[0043] The main service of the embodiments of the present application can be onboarding, regularization, transfer, resignation, salary reporting, probation management (requiring multi-role evaluation such as mentor, manager, etc.), personnel cross-store support, and other business scenarios requiring multi-party cooperation. These cooperating parties are generally cross-domain, such as HR professional domain, administrative domain, attendance domain, financial domain, etc. For ease of illustration and understanding, the embodiments of the present application mainly exemplify the onboarding service handling process, as shown in Figure 3.1 As shown in the figure, the onboarding service of an enterprise employee involves multiple cooperation links and multiple domains, and each link needs to handle different transactions.

[0044] Specifically, based on a series of onboarding association activities (or collaboration tasks) initiated by different enterprises in the past and the corresponding required information, the content of each node task required in the entire onboarding process (such as the required information to be audited, the task performer or role responsible for auditing the information) can be summarized, and the execution order (preceding or following) between each node task can be arranged (such as Figure 3.2 As shown in the figure, a set of online onboarding task flows can be preset for the example scenario to apply the onboarding task flow to create example tasks for each link online quickly and accurately. In other words, the onboarding task flow of the embodiments of the present application flexibly presets all possible association activities related to onboarding based on activity arrangement, defines the preceding and following creation logic or execution order of each node task, and also includes rich process roles in the business processing process, which can provide online operation guidance for the handling of employee onboarding business in the example scenario, and realize online integrated collaborative services across domains.

[0045] As shown in the figure, Figure 3.1 The above node task can be at least one of initiating an onboarding application, onboarding salary setting, onboarding reporting, contract signing, item taking, account opening, etc. The following tasks near the "labor contract signing" task can be at least one of onboarding reporting, office supplies taking, account / account permission opening, dormitory confirmation, and work card handling. These following tasks in the same execution node can be executed in sequence or simultaneously, which can be set by actual conditions and is not limited here. The activity involving object allocation or use, such as the office supplies taking task, can include online submission of application information, online approval confirmation, online allocation and registration of object identifier, etc. The details can be set by actual conditions and are not limited here.

[0046] Step S22, referring to the examples of each template task in the target task flow corresponding to the current main business, creating a corresponding example task.

[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 preceding template task in the target task flow, the example content of the preceding template task is referred to, and the corresponding example content is extracted from the example document information of the current main business to create a preceding example task. The example document can be an onboarding document of an onboarding employee submitted by HR online, which records the name, onboarding position, onboarding date, onboarding department, etc. of the onboarding employee. Then, based on the task state of the preceding example task and / or the actual value of the rule field of at least one following template task, a suitable template can be determined from the at least one following template task, and a following example task can be created by referring to the suitable template.

[0048] As can be seen, the embodiments of the present application abstract the business processing functions involved in each link of human resource business processing, and construct a set of selectable and matching work flows (or called collaborative task models) as reference for instance application, in which it is preset that each two template tasks have alternative relationship of mutual exclusion or parallel existence in actual execution scenario, whether the post template task can be created in the instance is determined based on the task state of the pre template task in the instance and / or the value of the post template task in the instance, and the identity attribute of the execution party of each task (such as the role of the auditor, the department to which the auditor belongs, etc.). Specifically, when there are multiple post template tasks of the pre instance task, the task state (completed or not completed) of the pre instance task 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 state is completed and / or whose actual value of the rule field meets the preset condition is regarded as the applicable template, that is, it is determined which item of the task flow the post template task is listed in. For example, as shown in Figure 3.1 , after the online confirmation of the signing of the labor contract (which can be signing an electronic contract) is completed, at least one of the post template tasks can be dormitory confirmation and work card handling, and the rule field can be at least one of the information fields of the rank, position and education level of the party in the main business.

[0049] Step S23: Based on the identity attribute corresponding to each selected template task, each instance task is correspondingly assigned to the execution party meeting the identity attribute for processing.

[0050] As explained above, for example, the party with an education level higher than a bachelor's degree needs "specialist talk" (this task can be assigned to a talk specialist for processing after being created), the party with a rank of M3 and above needs to sign a non-competition agreement (this task can be assigned to a contract preparation specialist for processing after being created), and the power safety officer needs to be assigned a dormitory (this task can be assigned to a dormitory administrator for processing after being created). In actual scenarios, the assignment time and execution time of each instance task can have a chronological relationship, or can be performed simultaneously, which can be determined by actual conditions, 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 to construct a task flow, which can promote the collaborative tasks to be included in the online processing process, reduce the traditional offline workload and delay, and promote the business progress. In addition, the preset task flow can intuitively reflect the execution sequence of each node task and the online processing content, which is helpful for efficiently recording the details of each instance task online, and effectively supervising the standard degree of the task; and recording the identity attribute of the task execution party can establish a "task-finding-person" collaboration mechanism, so as to ensure that each task processing role can quickly and accurately receive and process the task, thereby assisting the completion of the main business in the whole process online, and meeting the online collaboration requirements in the human resource business scenario.

[0052] ​​On the basis of the above example, the method of the present application will be further described in detail, and some specific possible implementation examples will be provided. In actual application, the implementation content between these examples can be combined or implemented individually according to the corresponding functional principle and application logic. If combined, the execution order of the combined examples can be determined according to the respective processing logic, and the specific implementation can be determined by the actual scene.

[0053] In some examples, after S21, the method of the embodiments of the present application can further include (presetting the check item): for the template task with the non-target specialist as the execution party, rendering the check item in the template task to prompt the checking of the instance content belonging to the check item in the instance task created by the template task; in the instance, if the check item needs the cooperation of the collaborators other than the target specialist, sending a collaboration request to the collaborators.

[0054] Online checking work is important in the process of collaboration task processing. The embodiments of the present application preset check items that the traditional online approval business system does not have, which can realize online checking of each item of the task, ensure traceability and effective error correction in the business processing process, and standardize the task content. Specifically, the check item setting can be performed to render the corresponding check item processing area in the front end, thereby completing the transaction checking online. As shown in Figure 4 , the checking of each associated transaction can be completed one by one by checking (e.g., checked if completed), and this associated transaction can be "whether the deposit has been paid, whether the attendance data synchronization is completed". Of course, the check item can also be whether the mandatory information is filled in, whether the information filling format is incorrect, etc. In addition, the check item can be configured as an automatic check item or a collaboration check item. If it is an automatic check item that can complete the check by itself, the associated transaction can be automatically checked according to the configured check condition whether it is completed and automatically checked. If it is an associated transaction check that cannot be completed by itself (i.e., a collaboration check item), for example, a non-HR full-time processing transaction such as issuing a work card, assigning a dormitory, etc. (such as needing the cooperation of a logistics specialist or dormitory manager), a service function of selecting a collaborator and sending a collaboration request to the collaborator can be provided to request the collaboration of the collaborator to complete the transaction checking; the sending of the collaboration request can be sending a collaboration request message or sending the associated transaction information that needs collaboration, that is, the collaboration party can be requested or prompted to participate in the transaction checking online, the task progress can be supervised and promoted online, and the offline transaction docking pressure can be reduced.

[0055] In some examples, the construction process of the task flow includes: dividing the information of each template task according to different dimensions, so that the template tasks of the same dimension correspond to the integrated instance task information displayed in a category view; the dimensions include information auditing, target specialist as the execution party, and non-target specialist as the execution party.

[0056] In the enterprise resource management scenario, the target agent can refer to an HR professional, and the non-target agent can refer to a related transaction collaborator such as a dormitory administrator, an account administrator, a legal officer, and the like. The related transaction can refer to a related business that is completed along with the main business (such as employment) such as dormitory allocation, settlement of resignation, calling and rescheduling of a contract, and the like. Embodiments of the present application configure views of each template task based on different business configurations of corresponding dimensions, so that the front-end page can be individually displayed according to the characteristics and functions of the task, to meet different task processing requirements. The three types of views corresponding to the three dimensions can be a standard activity task view, a business document view, and a cross-domain view.

[0057] As shown in Figure 4 , the standard activity view is mainly directed to or supports the initiation of transaction type handling activities such as the issuance of a work card, dormitory allocation, tutor arrangement, work handover, contract signing, and the like. The standard activity view provides basic business information (such as card name and card deposit) and employee personal information (such as date of employment and employment position) that can be viewed by a current task handler. Generally, the background can obtain a page configuration table (or referred to as uipk) applicable to each applicable document, which is used to indicate which fields of the applicable document need to be configured and displayed, 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 that the fields of "resignation time" and "name" need to be configured and displayed for the task handler (i.e., the task executor or the assignor) to see. The employment document also has a special page configuration table, which specifically configures that the fields of "employment time", "name", and "employment position" need to be configured and displayed for the task handler to see. In actual situations, the page configuration table can be self-defined, which is not limited here.

[0058] As shown in Figure 5 , the business document view is mainly directed to or supports the business information audit type activities such as probation conversion, salary reporting, and job level adjustment, which need to be audited. The configuration of the business document view can provide functions of auditing and modifying the main business information. Generally, the background can obtain all business document views adapted to the document type (such as the employment document and the resignation document) and the corresponding preset rules. In simple terms, the employment document corresponds to at least one style of business document view (or simply referred to as style diagram) for selection and display, and the resignation document also corresponds to at least one style of business document view for selection and display. The two parts of the business document view are isolated from each other, for example, the employment document cannot use the style diagram of the resignation document for display, but needs to use the special style diagram corresponding to the employment document for display, because the theme information and / or the viewer of the different types of documents are different. The business document view with multiple styles for each type of document is to consider that different handlers have different information fields that need to be seen or want to see.

[0059] The cross-domain view is mainly oriented to or supports HR professional function activities, such as onboarding information review, onboarding salary setting, and offboarding approval, which need to be handled by HR officers. Similarly, the background can define which cross-domain view is suitable for each task under each type of document for selection and display, such as onboarding salary setting, new labor contract signing, and other specific tasks. Further, these tasks can each be associated with some optional cross-domain view templates. Specifically, the cross-domain view template style for the onboarding salary setting task can be as shown in FIG. 14B, including salary standard, fixed salary, signing fee, and other information fields. Here, only an example is described, and the design of each view can be determined according to actual conditions, which is not limited here. Figure 6

[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 the HR professional domain, the administrative domain, the attendance domain, the financial domain, and the like. In other words, the view of the embodiments of the present application, such as the cross-domain view, can integrate information (such as salary standards) from different domains or different platforms, so that the required information can be quickly associated and found online without the need to retrieve information offline across domains or regions as in the traditional way. As can be seen, the embodiments of the present application can connect and interact with scattered information, reduce the complexity of collaboration tasks in the completion process, and speed up the task completion progress.

[0061] In summary, the three types of views, i.e., the standard activity task view, the business document view, and the cross-domain view, respectively, sort out and display the operation details of various collaboration tasks in a certain main business from three angles, i.e., the combination of the three types of views fully reflects the whole process of handling the main business. Generally, the three types of views are not displayed at the same time, and there is no priority relationship or importance level. The business administrator can switch to view the three types of views when setting the activity task, i.e., can choose to view which type of view.

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

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

[0064] The cross-domain business task view primarily supports HR professional activities, with key tasks including: acquiring key information from the main business to process professional business activities within that domain; creating employee business records or business files according to the business logic of that domain; and supporting HR professional task processing triggered by the main business, including business initiation and information maintenance.

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

[0066] To meet diverse implementation scenarios or creation conditions and ensure the smooth creation of tasks, creation mechanisms for various tasks can be set up. For example... Figure 7 As shown, specifically, three triggering methods can be set: workflow triggering, background transaction triggering, and manual triggering, ensuring that tasks are created regardless of the triggering method. Workflow triggering involves pre-defining task nodes, creating the corresponding task at each node; background transaction triggering involves defining the successor tasks adjacent to each preceding task (i.e., the sequence of tasks can be considered as task creation rules), automatically creating the successor task once a preceding task is completed; manual triggering involves manually clicking to trigger a task.

[0067] Furthermore, to avoid the problems of unreasonable resource allocation, excessive waiting time, or process blockage caused by concurrently creating multiple tasks, the historical occurrence time and / or task implementation logic of the task can be obtained to determine whether the task is created immediately (or directly) or not immediately (i.e., delayed or early creation). This distributes the pressure of creating a large number of tasks while meeting actual business needs. For example, if a document review task was created 3 days before the employee's onboarding, the onboarding information review task can be classified as a non-immediate creation task. This allows the scenario to design the creation of an onboarding information review task for a specific employee in advance (the advance time can be determined by the user). Immediately created tasks refer to tasks that can only be created after the task implementation logic (such as requiring confirmation or completion of prerequisite tasks) is determined, such as the task of signing a new contract upon onboarding. Of course, whether a task is created immediately or not can be determined by combining its historical occurrence time and task implementation logic, which will not be elaborated on in detail here.

[0068] In some examples, after S21, the method of the embodiments of the present application can further include (asynchronously loading and rendering information): distinguishing the example content in the template task into key content and non-key content, 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 load and display the instance content corresponding to the first-screen loading content first when displaying the instance content.

[0069] In actual applications, in order to improve the first-screen loading speed of the page and guarantee the reading experience of the user, the information can be designed to be asynchronously loaded and displayed in time. Specifically, considering the factors such as cross-platform compatibility and performance optimization, and in order to ensure fast page loading speed, smooth animation and natural interaction to improve the user experience, in the rendering of the collaborative task processing page, the task page can be divided into multiple layers through hierarchical rendering according to the composition of the task page view (such as task information fields, controls, etc.), the layer where the key content (such as task key information such as date of entry, inspection item content, party information, etc.) is located is preferentially rendered and displayed in the view, 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 time-delay manner; each layer can be independently rendered and synthesized to improve the rendering performance. For a complex collaborative task page, for example, a page containing cross-domain business view, task information view, task function view and task processing process monitoring content, through the asynchronous processing mode of loading and rendering the key content first and then gradually loading other non-key content, the first-screen loading speed of the page can be effectively improved and the user experience can be improved. At the same time, the application of cache and pre-rendering technology can reduce the waiting time of the user. In addition, the operation habits of the user and the change of the page content can be considered to intelligently adjust the rendering strategy to ensure the application experience of the collaborative task processing user.

[0070] In some examples, a task allocation mechanism can be configured to determine the actual person (i.e., the executor) who allocates each task, and the task allocation can include both 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, wherein the collaborative task allocation rule table is mainly used to record the basic information of key allocation rules, including users, roles, positions, employees, and other key collaborative task processing objects, as well as the priority of this allocation rule. The collaborative task allocation rule detail table mainly records rule codes, rule fields, rule comparison symbols, and rule values. After the collaborative task is created, the executor can be automatically allocated according to the allocation rules. Through the design of rule fields and conditional logic (i.e., whether the preset conditions are met), the rule fields can be dynamically valued and compared with the preset rule values, and the final actual allocation person can be calculated according to the relationship and priority, i.e., to determine who to handle the created task. The rule fields can comprehensively obtain the information required in the actual business processing process, including business information (such as employment form, department, position, and other employment information) and employee information (such as age, education, and other personal background information unrelated to employment), wherein the 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 support manual allocation of the collaborative tasks to be allocated and allocated by the business administrator. After the collaborative task allocation is completed, the task state can be set or recorded as processing in the collaborative task detail table, and the task state can be set as completed after the task is completed. In some examples, the collaborative task detail table can record task states (processing, completion, etc.), task codes, task topics, task processing times, and other attributes; wherein, if the task processing time is exceeded, the executor can be reminded to process or used to analyze whether the processing time is set reasonably, and used to optimize the processing time to ensure the smooth completion of the task.

[0071] In some examples, after S23, the method of the embodiments of the present application can further include (information rewriting): rewriting the unique information occupied by the instance task of the completed main business into the information collection system, so that the next main business of the same category creates an instance task with the same purpose, and 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.

[0072] Specifically, the data of a third-party system (such as a dormitory management system, an asset management system, etc.) can be obtained through the configuration input and output integrated interface, and the filled and allocated task information can be written back to the third-party system, so as to ensure data synchronization update and non-conflict use. For example, the dormitory management system can be called to query which dormitory has a vacancy, and after the implementation of the dormitory confirmation task divides a bed position to a new person, the unique information such as the a bed position number can be written back to the dormitory management system to feed back to the dormitory management system that the a bed position is occupied by the new person, so as to avoid the a bed position being allocated to other new persons next time. It can be seen that the embodiments of the present application support 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 the task processing information and the external system, and to ensure the synchronization update of multi-party information.

[0073] As described above, the method of the embodiments of the present application solves the problem of traditional human resource collaboration business offline and semi-offline processing; compared with the alternative use of a bill approval mode, the setting is simple, the task processing function is complete, and the actual business application requirements are met; the business expansion is good, and the applicable business, collaboration task information and collaboration task function can be flexibly expanded, the high secondary development cost of traditional business processing is reduced; and a unified integrated standard for rapid docking with an external system is provided, which provides a basis for the interaction between the HR system and the external system.

[0074] In some examples, a task processing mechanism can be set for each task of the embodiments of the present application. The task processing mode supported by the task processing mechanism can include completion, temporary storage, transfer, and return. Completion is to call completion logic when the collaboration task processor clicks the completion button after receiving the task and completing online processing, including setting the collaboration task state to completed, and triggering the creation of a post-task after judging whether there is a post-task and all the pre-tasks of the post-task are completed. Temporary storage supports saving the processed task information at any time during the collaboration task processing process (such as supplementing information halfway), and the task state does not change at this time (still in processing). Transfer supports changing the execution of the current task, such as transferring to others for processing, and the task state does not change (still in processing). Return supports returning the task in the scheme to the pre-task, the current task state is changed to returned, the pre-task is re-created, for example, a to-be-done task “entry information audit” is re-created.

[0075] In some examples, the task information of the embodiments of the present application can be personalized rendering. For example, the configured information can be deeply processed by relying on the existing field control and using CSS style settings to realize the rendering of different style fields such as string type, time type, numerical value type, and drop-down box type in the front end.

[0076] In summary, the method of this application embodiment can easily integrate various collaborative task stages of enterprise human resource business management into online processing. It offers flexible configuration and low maintenance costs. Based on a "task-find-person" collaborative mechanism, each task processing role receives tasks and completes the entire process online. The task settings support one-stop configuration of collaborative task allocation, creation, and processing mechanisms, as well as the ability to configure page views, task information, and task functions according to the task processing content of different collaborative activities. Figure 8 As shown, it specifically includes:

[0077] • Supports flexible configuration of page views required for each stage 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 realize the reverse writing and back transmission of data between task processing information and external systems;

[0079] • Supports configuring operation guidelines based on task nodes, instructing the current task handler to process the task according to standard specifications;

[0080] • Supports configuring online check items and sending collaborative messages and activities based on the check items;

[0081] It supports setting up based on associated documents, allowing users to select business documents that can be associated with the current task, thus enabling integrated processing of related business processes and avoiding the hassle of fragmented processing in traditional business processes.

[0082] As can be seen, the method in this application embodiment breaks through the traditional human resource management business processing that mainly relies on the approval of business documents. Through the design of a human resource task collaboration model, it includes constructing a complete collaborative task processing mechanism encompassing HR business collaboration task creation, task allocation, and task processing; such as... Figure 9 As shown, it also supports the use of the following task components or functions at multiple levels and dimensions individually or in combination: (1) independent task components, (2) cross-business task views, (3) personalized task services, (4) third-party integration of task information; (5) characteristic components for abstracting online human resources processing business, such as online inspection activities, online signing activities, and related document initiation activities, breaking down the data isolation barriers between the internal and external HR system, realizing the fully 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 this application provides a specific embodiment of a business management system, the system comprising: an acquisition unit and a processing unit;

[0084] The acquisition unit is configured to obtain task flows respectively constructed for each type of historical main business; the task flow of the historical main business is arranged by nodes according to each template task required to complete the historical main business, and the identity attribute of the execution party of each template task is recorded; wherein at least one adjacent post-template task of each pre-template task, in an instance, when the task state of the pre-template task is completed and / or the actual value of the rule field of the post-template task meets the preset condition, the post-template task is determined as an applicable template allowing the creation of a corresponding instance task;

[0085] The processing unit is configured to determine a target task flow corresponding to the current main business from each group of task flows, and create a pre-instance task from the first pre-template task in the target task flow by referring to the example content of the pre-template task and extracting the corresponding instance content from the instance document information of the current main business; determine an applicable template from at least one post-template task based on the task state of the pre-instance task and / or the actual value of the rule field of at least one post-template task, and create a post-instance task by referring to the applicable template;

[0086] The processing unit is further configured to assign each instance task to an execution party meeting the identity attribute based on the identity attribute corresponding to each template task selected by the execution party.

[0087] In some examples, the processing unit is further configured to:

[0088] For template tasks whose execution parties are non-target agents, the check items in the template tasks are rendered to prompt that after the corresponding instance tasks are created from the template tasks, the instance content belonging to the check items in the instance tasks is checked;

[0089] In an instance, if the check items require the cooperation of a collaborator other than the non-target agent, a collaboration request is sent to the collaborator.

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

[0091] The information of each template task is divided according to different dimensions, so that the information of the instance tasks created by the template tasks of the same dimension is integrated and displayed in a category view; the dimensions include information review, target agent as the execution party, and non-target agent as the execution party.

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

[0093] A plurality of trigger modes are set for each template task in the task flow to meet a plurality of opportunities for the template task to create corresponding instance tasks;

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

[0095] In some examples, the processing unit is further configured to:

[0096] In some examples, the processing unit is further configured to:

[0097] In some examples, the processing unit is further configured to:

[0098] In some examples, the processing unit is further configured to:

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

[0100] (1) Meet the HR collaboration transaction processing requirements, and perfect collaboration task processing functions

[0101] The HR collaboration task model is based on sufficient abstraction of collaboration activities in the human resource business scenario. For the characteristics and processing requirements of information review activities, cross-domain HR function activities, and transactional handling activities, various collaboration processing links can provide professional business information review, cross-domain HR business processing (such as job setting, job signing contract, transfer, and contract change), transactional processing information maintenance (non-business information), online task inspection, associated collaboration activity initiation, associated business document initiation, operation guide viewing, task handling monitoring, and other functions to meet the online collaboration task handling requirements in the human resource business scenario.

[0102] (2) Simple to set up, based on flexible configuration of activity arrangement

[0103] The HR collaboration task model based on activity arrangement includes each link in the actual business of the enterprise into the human resource business processing process. Through activity setting, the online processing content of each collaboration task node can be intuitively defined, including task theme, creation requirements, distribution requirements, task processing view, task processing function requirements, and other content. By selecting the activities required by the business process through scheme setting and flexibly arranging as needed, parallel and serial processing of various collaboration activities can be realized. The setting process is simple and intuitive for business personnel and convenient to operate.

[0104] (3) Collaboration task processing content supports multiple dimensions of flexible expansion

[0105] View expansion: The collaboration task view supports the standard view of the document, the cross-domain professional view, and the standard collaboration activity view, and in addition, the personalized task view required by the current collaboration task can be flexibly expanded.

[0106] Function expansion: The task processing function supports online inspection, associated business document initiation, associated collaboration activity initiation, and other functions, and supports flexible use according to the requirements of the collaboration task.

[0107] Field expansion: The task processing information is realized through the task field setting function, and the expansion of the task processing information is realized quickly as a standard function.

[0108] See Figure 10 The electronic device of the embodiment of the present application can include one or more processors (such as central processing units CPU) and a memory having one or more application programs or data stored therein.

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

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

[0111] The processor can perform the operations performed by the first aspect or any of the specific method embodiments of the first aspect, and the specific details are not repeated.

[0112] The present application provides a computer readable storage medium comprising instructions, when the instructions are run on a computer, the computer executes the method described in the first aspect or any of the specific implementation manners 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 executes the method described in the first aspect or any of the specific implementation manners of the first aspect.

[0114] It can be 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 according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The operation content added or refined by each example scheme of the above method, system or device (if any) does not necessarily have to be executed in specific implementation, such as more than two operations are added, which can be combined or implemented separately, and the specific implementation can be determined according to the actual scene.

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

[0116] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented by other ways. For example, the above-described apparatus embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system or apparatus, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, apparatus or unit, and can be electrical, mechanical or other forms.

[0117] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0118] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The above integrated unit can be realized in the form of hardware or in the form of software functional unit.

[0119] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, essentially or in other words, the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product (or computer program product) stored in a storage medium includes a plurality of instructions for causing a computer device (which can be a personal computer, a business server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, read-only memory), a random access memory (RAM, random access memory), a magnetic disk or an optical disk, and various media that can store program codes.

Claims

1. A service management method characterized by, The method comprises the following steps: obtaining task flows respectively constructed for various types of historical main businesses; the task flows of the historical main businesses are arranged by nodes according to various template tasks required for completing the historical main businesses, and the identity attributes of the execution parties of each template task are recorded; wherein, at least one of the template tasks adjacent to each preceding template task is a subsequent template task, in an instance, when the task state of the preceding template task is completed and / or the actual value of the rule field of the subsequent template task meets the preset condition, the subsequent template task is determined as an applicable template allowing the creation of a corresponding instance task; determining a target task flow corresponding to the current main business from each group of the task flows, starting from the first preceding template task in the target task flow, referring to the example content of the preceding template task, extracting the corresponding instance content from the instance document information of the current main business to create a preceding instance task; based on the task state of the preceding instance task and / or the actual value of the rule field of at least one subsequent template task, determining the applicable template from at least one subsequent template task, and creating a subsequent instance task according to the applicable template; based on the identity attribute corresponding to each template task selected, assigning each instance task to an execution party meeting the identity attribute for processing; the construction process of the task flow comprises: dividing the information of each template task according to different dimensions, so that the instance task information corresponding to the template tasks of the same dimension is integrated and displayed in a view.

2. The service management method according to claim 1, characterized by, After obtaining the task flows respectively constructed for various types of historical main businesses, the method further comprises: for the template tasks whose execution parties are non-target specialists, rendering the check items in the template tasks to prompt the checking of the instance content belonging to the check items in the instance task created according to the template task; in an instance, if the check items require the cooperation of a collaborator other than the non-target specialist, sending a collaboration request to the collaborator.

3. The service management method according to claim 1, characterized by, The dimensions include information review, target specialists, and non-target specialists.

4. The service management method according to claim 1, characterized by, The construction process of the task flow comprises: setting multiple trigger modes for each template task in the task flow to meet the multiple opportunities for the template task to create a corresponding instance task; based on the occurrence time and / or task implementation logic of the template task in history, the time for each template task to create a corresponding instance task is divided into immediate creation or non-immediate creation.

5. The service management method according to claim 1, characterized by, After obtaining the task flows respectively constructed for various types of historical main businesses, the method further comprises: distinguishing the example content in the template task into key content and non-key content, setting the key content as the first-screen loading content compared to the non-key content, to prompt the instance task created according to the template task to load and display the instance content corresponding to the first-screen loading content first when displaying the instance content.

6. The service management method according to any one of claims 1 to 5, characterized by, After assigning each instance task to an execution party meeting the identity attribute for processing, the method further comprises: The unique information occupied by the instance task of completing the current main business is written back to the information collection system, so that the next main business of the same category creates the instance task with the same purpose, and then the instance task of the next main business is completed by other information; the other information refers to information in the information collection system other than the unique information.

7. A service management system, characterized by Comprise: An acquisition unit and a processing unit; The acquisition unit is configured to obtain a task flow constructed for each type of historical main business; the task flow of the historical main business is arranged by nodes according to each template task required to complete the historical main business, and records the identity attribute of the execution party of each template task; wherein at least one of the adjacent post-task of each pre-task has a post-task, in an example, when the task state of the pre-task is completed and / or the actual value of the rule field of the post-task meets the preset condition, the post-task is determined as an applicable template allowing the creation of a corresponding instance task; The processing unit is configured to determine a target task flow corresponding to a current main business from each group of task flows, and starting from the first pre-task in the target task flow, refer to the example content of the pre-task, 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 state of the pre-instance task and / or the actual value of the rule field of at least one post-task, determine the applicable template from at least one post-task, and create a post-instance task by referring to the applicable template; The processing unit is further configured to assign each instance task to an execution party that meets the identity attribute based on the identity attribute corresponding to each template task selected; The processing unit is further configured to divide the information of each template task according to different dimensions, so that the instance task information corresponding to the template tasks of the same dimension is displayed in a view.

8. An electronic device, comprising: Comprise: A processor and a memory; The processor is configured to communicate with the memory and execute instructions in the memory to implement the method of any one of claims 1-6.

9. A readable storage medium, characterized by, The readable storage medium stores computer instructions, and the computer instructions are executed by the processor to implement the method of any one of claims 1-6.

10. A computer program product, characterised in that, The computer program product comprises computer instructions, and the computer instructions are executed by the processor to implement the method of any one of claims 1-6.

Images