CN116562831A

CN116562831A - Personnel synchronous consistency method for multiple office systems

Info

Publication number: CN116562831A
Application number: CN202310539915.9A
Authority: CN
Inventors: 李程; 叶宇峰
Original assignee: Shenzhen Fengyi Technology Co ltd
Current assignee: Shenzhen Fengyi Technology Co ltd
Priority date: 2023-05-12
Filing date: 2023-05-12
Publication date: 2023-08-08
Anticipated expiration: 2043-05-12
Also published as: CN116562831B

Abstract

The invention provides a multi-office system personnel synchronization consistency method, which comprises the following steps: creating a data table in a local database, wherein the data table is used for storing personnel information, and the personnel information comprises personnel data and personnel relationship data; establishing an event processor as a unified processing inlet of personnel abnormal events, wherein the event processor comprises a plurality of atomic event processors, and according to the event type, the events are processed by different atomic event processors, and finally personnel information is stored in a data table corresponding to a local database; and (3) compensating personnel information, finishing data in a local database, and realizing consistency synchronization of the personnel information. According to the invention, personnel transaction is captured from different business scenes, and different personnel transaction events are uniformly processed by adopting an event processor; and synchronously updating personnel information to a local database, so as to realize consistency synchronization of multi-platform data.

Description

Personnel synchronous consistency method for multiple office systems

Technical Field

The invention relates to the technical field of office informatization, in particular to a multi-office system personnel synchronous consistency method.

Background

With the continuous development of enterprises, the number of enterprise staff and enterprise clients is gradually increased; the enterprise needs to manage the entering and leaving of the staff in the enterprise and also needs to maintain the relationship of the enterprise clients; the method comprises the following steps of attributing relation between a client and staff, and keeping relation between the client and an enterprise; with the development of science and technology, enterprises sequentially introduce different personnel management platforms in the process; such as a Northsen talent management platform (Northsen platform), an enterprise WeChat platform; along with the increasingly vigorous competition of retail industry, more and more enterprises finish personalized marketing to clients through a self-research system, and maintain and manage client relations; the development of the system becomes a necessary way for many enterprises; for the self-grinding system, personnel data of a personnel management platform used by an enterprise needs to be synchronized to the self-grinding platform; the management of a plurality of enterprise staff and enterprise clients exists in a plurality of staff management platforms, staff among the platforms can be crossed to a certain extent, and the staff is data which changes at any time; the self-research system firstly faces to clean personnel data of each personnel management platform, and simultaneously monitors and processes the change data in time; therefore, when people on different platforms are synchronized to the self-polishing system, how to ensure the integrity and consistency of data, how to make corresponding processing by the self-polishing system after the personnel on each platform are changed, and how to ensure the accuracy of the data are all the problems to be solved.

Therefore, there is a need to provide a new method to achieve synchronization of multi-platform data.

Disclosure of Invention

Aiming at the problems existing in the prior art, the invention provides a multi-office system personnel synchronous consistency method.

In order to achieve the above object, the present invention is specifically as follows:

the invention provides a multi-office system personnel synchronization consistency method, which comprises the following steps:

s1, creating a data table in a local database, wherein the data table is used for storing personnel information, and the personnel information comprises personnel data and personnel relation data;

s2, establishing an event processor as a unified processing inlet of personnel transaction events, wherein the event processor comprises a plurality of atomic event processors, and according to the event type, the events are processed by different atomic event processors, and finally personnel information is stored in a data table corresponding to a local database;

s3, a timing task is established to collect personnel information from the Northsen platform, the collected personnel information is transmitted to an event processor, and the collected personnel information is uniformly processed by the event processor; the synchronization of personnel information follows the same set of logic, so that the error rate of data is reduced, the personnel information of other platforms is accessed, and the personnel information is uniformly processed by an event processor;

s4, collecting client information and friend relation information of clients and enterprise staff through enterprise WeChat staff abnormal monitoring callback, and delivering the client information and the friend relation information to an event processor for unified processing; adding, editing and deleting clients by enterprise staff, and deleting enterprise staff by clients;

and S5, personnel information compensation is carried out, data in a local database are finished, and consistency synchronization of personnel information is realized.

Further, the step S1 specifically includes the following steps:

s101, creating a Northson platform user table to store personnel information acquired from the Northson platform;

s102, creating a user main table to store basic information of enterprise staff and clients; the method comprises the steps of enterprise WeChat personnel numbering, name, mobile phone number, job position, enterprise and remarks;

s103, creating a user affiliated list to store friend relations of enterprise staff and clients and remarks of staff to clients; the method comprises the steps of numbering enterprise staff, numbering clients, remarks of staff on the clients and mobile phone numbers.

Further, in step S2, the processing procedure of the event handler includes the following steps:

s201, adding a lock to the event processing process, and when a plurality of events need to be processed at the same time, queuing and waiting are needed, and the event processor always processes the first event; thus avoiding the local database from generating dirty data when synchronizing personnel data; different enterprise staff are prevented from operating the same client at the same time, dirty data are generated, only one event is processed at the same time, and other events are placed into a queue to be queued for processing;

s202, selecting a corresponding atomic event processor according to the event type; by designing different atomic event processors, each processing logic is not interfered with each other, and a single responsibility principle is followed;

s203, event types include: the staff joins the enterprise, the staff exits the enterprise, the staff adds the client as the friend, the staff and the client release the friend relationship, and the staff is updated.

Further, the step S3 specifically includes:

s301, setting 7-day timing tasks in the morning and evening, and storing the changed enterprise personnel information in a time range from the previous morning to the current timing task execution time point of the Northsen platform to a Northsen platform user table of a local database; the starting time of the timing task is set in the early morning, so that a fault tolerance effect can be realized, and errors can be prevented when data of a certain person are synchronized; if someone is data synchronized more than three times wrong, then human intervention is done;

s302, calling an enterprise WeChat API through an enterprise employee mailbox or a mobile phone number, finding the number of the enterprise employee in the enterprise WeChat, supplementing the number to a local database, and enabling the personnel acquired from the Northsen platform to correspond to the personnel in the enterprise WeChat one by one; if the corresponding number cannot be found in the enterprise WeChat, the account is indicated not to belong to enterprise staff and is regarded as invalid data;

s303, respectively acquiring a local database Northsen platform user staff data set and a local database user main staff data set, and respectively eliminating the reported white list users from the local database user main staff data set; traversing the personnel data set of the Northsen platform user table, comparing the personnel data set with a local database, setting event content and event type, giving the event to an event processor for unified processing, and storing personnel information to the local database by the event processor;

s304, deleting the non-white list user and the employee away from the local database user master table.

Further, the step S5 specifically includes:

s501, enterprise personnel information compensation;

s502, compensating friend relation information of enterprise staff and clients.

Further, step S501 specifically includes:

s5011, when enterprise personnel use enterprise WeChat to open customer operation and maintenance application, automatically detecting whether the enterprise personnel information is synchronized to a local database;

s5012, if the staff of the enterprise is not synchronized to the local database, using the staff to join an atomic event processor corresponding to the enterprise, and automatically compensating the staff information of the enterprise to the local database;

s5013, if the enterprise employee has been synchronized to the local database, updating the enterprise employee key data, including: handset number, mailbox, name.

Further, step S502 specifically includes:

s5021, when an enterprise employee opens a friend dialog box with a client in an enterprise WeChat and clicks a client information column in the dialog box, if the client information is not returned normally, the client displays a repair button;

s5022, when an enterprise employee clicks a repair button, an employee atomic event processor is triggered to be updated, and enterprise personnel information is compensated;

s5023, triggering an event processor for adding the client friend relation atoms to compensate the friend relation information of the enterprise staff and the client;

and S5024, returning the client information to the client information column in the dialog box.

The technical scheme of the invention has the following beneficial effects:

according to the invention, personnel transaction is captured from different business scenes, and different personnel transaction events are uniformly processed by adopting an event processor; after the staff of the enterprise takes part in from the North forest platform, if the staff uses the customer operation and maintenance application of the enterprise WeChat, the staff data is synchronized to a local database through a staff compensation mechanism; if the personnel enter the office and do not use the customer operation and maintenance of the enterprise WeChat, the personnel data are synchronized to the local database through the timing task; similarly, when the enterprise personnel information is changed on the Northsen platform, the enterprise personnel information is synchronously updated to a local database through the two approaches; when the relationship between the enterprise staff and the clients is changed, personnel transaction is captured through enterprise WeChat callback events, and personnel information is synchronously updated to a local database, so that consistency synchronization of multi-platform data is realized.

Drawings

FIG. 1 is an overall flow chart of the present invention;

FIG. 2 is a specific flowchart of step S1 of the present invention;

FIG. 3 is a flowchart showing the step S2 of the present invention;

FIG. 4 is a flowchart showing the step S3 of the present invention;

FIG. 5 is a flowchart showing the step S5 of the present invention;

fig. 6 is a specific flowchart of step S501 of the present invention;

fig. 7 is a specific flowchart of step S502 of the present invention.

Detailed Description

The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.

In the description of the present invention, unless explicitly stated and limited otherwise, the terms "connected," "connected," and "fixed" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally formed; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communicated with the inside of two elements or the interaction relationship of the two elements. The specific meaning of the above terms in the present invention will be understood in specific cases by those of ordinary skill in the art.

In the present invention, unless expressly stated or limited otherwise, a first feature "above" or "below" a second feature may include both the first and second features being in direct contact, as well as the first and second features not being in direct contact but being in contact with each other through additional features therebetween. Moreover, a first feature being "above," "over" and "on" a second feature includes the first feature being directly above and obliquely above the second feature, or simply indicating that the first feature is higher in level than the second feature. The first feature being "under", "below" and "beneath" the second feature includes the first feature being directly under and obliquely below the second feature, or simply means that the first feature is less level than the second feature.

In the description of the present embodiment, the terms "upper", "lower", "front", "rear", "left", "right", and the like are orientation or positional relationships based on those shown in the drawings, and are merely for convenience of description and simplicity of operation, and do not indicate or imply that the apparatus or elements referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and the like, are used merely for distinguishing between descriptions and not for distinguishing between them.

As shown in fig. 1-7, the present invention provides a multi-office system personnel synchronization consistency method comprising the steps of:

The step S1 specifically comprises the following steps:

In step S2, the processing procedure of the event handler includes the steps of:

In the step S203 of the process of the present invention,

employee joining enterprise process:

acquiring personnel information of the Northsen platform, covering the personnel information in the event details by using the personnel information, and storing the personnel information into a local database;

employee exit enterprise process:

inquiring personnel information to be deleted, and deleting the personnel information and friend relation information of the personnel and clients from a local database;

and updating the personnel information of the enterprise, acquiring the personnel information in the personnel information coverage event content from the Northsen platform, and updating the personnel information to a local database.

Staff edit customer information:

acquiring client details and a friend relation set of a client and staff through an enterprise WeChat API;

storing the client information into a local database, and modifying mobile phone number remarks of other staff to the client through an enterprise WeChat API (application program interface), wherein the mobile phone number remarks are consistent with the latest remarks;

storing the friend relation between the staff and the client into a local database, and if the client has deleted the staff, disregarding;

the method comprises the steps of removing friend relation processing between staff and clients:

the employee's friend relationship with the customer is deleted from the local database,

if the client is deleted by the staff, judging whether other staff also add the client as friends, and if the client is not added by other staff, deleting the client information from the local database.

The step S3 specifically comprises the following steps:

s301, setting 7-day timing tasks in the morning and evening, and storing the changed enterprise personnel information in a time range from the previous morning to the current timing task execution time point of the Northsen platform to a local database Northsen platform user table; the starting time of the timing task is set in the early morning, so that a fault tolerance effect can be realized, and errors can be prevented when data of a certain person are synchronized; if someone is data synchronized more than three times wrong, then human intervention is done;

s304, deleting non-white list users and employee away from the local database user master list;

because the enterprise WeChat API has access frequency and error frequency limit in unit time, after exceeding the frequency limit, the API can be shielded from access in the same unit time; if the access of the interface A exceeds the number of times in one hour, the interface A is shielded from being accessed for one hour; in order to avoid the influence of the enterprise WeChat shielding API on the Northsen platform side service and other monitoring callback synchronization, the timing task time is set to 7 points in the morning and evening every day, and personnel information in the enterprise WeChat is preferentially searched through the mailbox in the step S302.

The step S5 specifically comprises the following steps:

s501, enterprise personnel information compensation;

s502, compensating friend relation information of enterprise staff and clients.

The step S501 specifically includes:

The step S502 specifically includes:

s5024, returning the client information to the client information column in the dialog box;

in the whole process, the client is not perceived at the enterprise WeChat client.

The enterprise personnel data of the invention can be circulated as follows:

1.1, triggering a personnel compensation mechanism in the step S501, and inputting the personnel information of the enterprise into a local database based on the information of the enterprise WeChat;

1.2, deleting the enterprise personnel information from a local database when the step S3 is executed on the same day to synchronize the Northson platform personnel information;

2. when the enterprise staff is the white list account number which is reported to open the customer operation and maintenance, the enterprise staff data can generate the following circulation:

2.1, triggering the personnel compensation mechanism in the step S501, and inputting the enterprise personnel information into a local database based on the enterprise WeChat information;

2.2, when the step S3 is executed to synchronize the Northsen platform personnel information on the same day, the synchronization of the white list user is eliminated from the Northsen platform personnel set and the local user main list personnel set. So the timing task does not process any of the enterprise personnel information in the local database;

3. when an enterprise employee opens a customer operation, the enterprise personnel data may be circulated as follows:

3.1, triggering the personnel compensation mechanism in the step S501, and inputting the enterprise personnel information into a local database based on the enterprise WeChat information;

and 3.2, when the step S3 is executed on the same day to synchronize the information of the staff on the Northson platform, the name, the mobile phone number and the sex of the staff in the Northson are used for covering the name, the mobile phone and the sex information of the staff in the local database.

4. When the enterprise personnel information is changed on the Northsen platform, the enterprise personnel data can be circulated as follows:

4.1, when the timing task is executed on the same day, acquiring employee change information of the enterprise from a Northsen platform;

4.2, the event processor processes the enterprise personnel information change event and processes the event for the event processor of the updated enterprise personnel;

and 4.3, in the processor, covering the personnel information acquired from the enterprise micro-letter server by using personnel key information (name, sex and mobile phone number) recorded by the Northsen platform, and storing the covered personnel information into a local database of the self-research system.

5. When a client deletes an enterprise employee from a buddy list, the client data may be streamed as follows:

step S4, triggering enterprise WeChat personnel abnormal monitoring, and delivering the friend relation information of the clients and the enterprise staff to an event processor for processing;

and 5.2, the event processor distributes the event to an atomic event processor for processing the friend relationship between staff and clients.

6. When an enterprise employee deletes a client from the buddy list, the client data may be streamed as follows:

step 6.1, triggering step 4 enterprise WeChat personnel abnormal monitoring, and delivering the friend relation information of the clients and the enterprise staff to an event processor for processing;

and 6.2, the event processor distributes the event to an atomic event processor for processing the friend relationship between staff and clients.

7. Suppose client a has a friendship only with enterprise employee a. When the enterprise employee A deletes the client A and the enterprise employee B adds the client A, the expected result is that the local database stores the information of the client A and the friend relation information of the client A and the enterprise employee B, and the friend relation between the client A and the enterprise employee A is deleted; the actual data flow is as follows:

7.1, deleting the client A by the enterprise employee A, adding the client A by the employee B, and triggering an event processor;

7.2, because the event processor is internally provided with a fair lock, two events of deleting the client A by the enterprise staff A and adding the client A by the staff B compete for the fair lock;

7.3, assuming that the enterprise employee A deletes the fair lock of the event handler that the client A robs, then the employee B adds the client A and waits in a queue;

7.4, the event processor transmits the enterprise employee A deletion client A to the atom event processor for releasing the friend relation between the employee and the client, deletes the information of the client A from the local database and deletes the friend relation information of the enterprise employee A and the client A;

7.5, the staff B adds the client A to acquire the fair lock of the event processor, and the event processor gives the event to the staff editing client atomic event processor. Storing the information of the client A, the staff B and the information of the client A into a local database;

7.6, assuming that the enterprise employee B adds the fair lock of the event handler to which the client A robs, the employee A deletes the client A and waits in a queue;

7.7, the staff B adds the client A to acquire the fair lock of the event processor, and the event processor gives the event to the staff editing client processor. Storing friend relation information of staff B and client A into a local database, and updating information of client A in the local database;

and 7.5, the event processor transmits the deletion of the client A by the enterprise employee A to the atom event processor for releasing the friend relationship between the employee and the client, and deletes the friend relationship information of the enterprise employee A and the client A from the local database, and the client A has added the employee B, so that the information of the client A in the user master table is reserved.

In the above steps, whichever event first acquired the lock, we can get the result consistent with expectations. If the processor is not provided with the built-in public-flat lock, the event that the staff and the client release the friend relationship and the event that the staff edits the client are performed simultaneously. Then the following may occur:

1. in the employee edit customer event, customer A information is found.

2. In the event that the friend relationship between the staff and the client is released, the client A information is deleted because the friend relationship between the client A and the staff B is not stored in the last step.

3. Only the friend relation information of the client A and the enterprise employee B is saved.

4. This will result in an error in the local database saving of customer a's information.

In the invention, the fair lock in the event processor perfectly solves the dirty data problem possibly caused by the concurrency problem.

As described above, the invention processes different business scenes by performing differential processing on the personnel data of different platforms, so as to obtain a piece of personnel data which is consistent with the personnel data of multiple platforms and meets the business requirements, and the personnel data is stored in the local database of the self-research system.

At present, the system is online for 9 months, 100% synchronization of enterprise staff to a local database is realized, after the system is formally online, a time point is randomly selected, the synchronization rate of the enterprise staff in the Northsen platform to the local database and the synchronization rate of the enterprise staff and white list staff in the enterprise WeChat to the local database are calculated, and the observation and realization effects are shown in the following table:

platform	Personnel synchronization rate of enterprises	White list synchronization rate
			North forest platform	100％
Enterprise WeChat	100％	100％

The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the invention, and all equivalent structural changes made by the description of the present invention and the accompanying drawings or direct/indirect application in other related technical fields are included in the scope of the present invention.

Claims

1. The multi-office system personnel synchronous consistency method is characterized by comprising the following steps of:

2. The multi-office system personnel synchronization consistency method according to claim 1, wherein the step S1 specifically comprises the steps of:

3. The multi-office system personnel synchronization consistency method according to claim 1, wherein in step S2, the processing procedure of the event handler comprises the steps of:

4. The multi-office system personnel synchronization consistency method according to claim 1, wherein the step S3 specifically comprises:

5. The multi-office system personnel synchronization consistency method according to claim 1, wherein step S5 specifically comprises:

s501, enterprise personnel information compensation;

s502, compensating friend relation information of enterprise staff and clients.

6. The multi-office system personnel synchronization consistency method according to claim 5, wherein the step S501 specifically comprises:

7. The method for synchronizing and conforming multiple office system personnel according to claim 5 wherein step S502 comprises:

s5022, when the enterprise staff clicks the repair button, the staff atomic event processor is triggered to be updated, and the enterprise staff information is compensated;

friend relationship information of a user;