CN107547609B - Method and device for realizing flow collaborative management among different clients - Google Patents
Method and device for realizing flow collaborative management among different clients Download PDFInfo
- Publication number
- CN107547609B CN107547609B CN201610496058.9A CN201610496058A CN107547609B CN 107547609 B CN107547609 B CN 107547609B CN 201610496058 A CN201610496058 A CN 201610496058A CN 107547609 B CN107547609 B CN 107547609B
- Authority
- CN
- China
- Prior art keywords
- client
- account
- management
- same platform
- mapping
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a device for realizing flow collaborative management among different clients. Wherein the method comprises the following steps: acquiring a first account of a first client and a second account of a second client; respectively mapping the first account of the first client and the second account of the second client to a third account under the same platform according to a preset mapping rule; binding incidence relation information aiming at a third account under the same platform, and setting corresponding authority; and realizing flow cooperative management between the first client and the second client according to a preset service flow. According to the invention, two user accounts with different properties are mapped into the same type of user account, the same type of user account is integrated on the same platform, and the association relation information and the authority are bound, so that flow collaborative management can be realized among different clients.
Description
Technical Field
The present invention relates to the field of process collaborative management, and in particular, to a method and an apparatus for implementing process collaborative management between different clients.
Background
At present, all users served by the collaboration tool are registered users in the same platform system, namely all users collaborate on the same platform, such as nailing, open road, WeChat enterprise number and the like. All process approval is completed in the same platform (client), for example, process initiation, approval and collaboration of the nailing user are all completed on the nailing client. The transportation capacity center needs to realize the cooperation among users of different platform systems, a direct-operated driver is a user of a driver account platform system, an internal driving management system and a vehicle captain are users of an employee account platform system, the two users are users with different properties, the driver initiates a service flow (such as asking for leave) at a driver client, the driving management system passes approval at the transportation capacity center client and cooperates with a city manager, and the management and the cooperation of the users need to be realized in different platforms.
However, in the prior art, the cooperative management of the process cannot be realized among users of different platforms, and none of the products on the market can meet the requirement.
Disclosure of Invention
Aiming at the defects of the prior art, the invention provides a method for realizing flow collaborative management among different clients, which can realize flow collaborative management among different clients by mapping two user accounts with different properties into user accounts of the same type, integrating the user accounts of the same type into the same platform and compiling an organization and authority.
According to a first aspect of the present invention, a method for implementing flow collaborative management between different clients is provided, where the method includes:
acquiring a first account of a first client and a second account of a second client;
respectively mapping the first account of the first client and the second account of the second client to a third account under the same platform according to a preset mapping rule;
binding incidence relation information aiming at a third account under the same platform, and setting corresponding authority;
and realizing flow cooperative management between the first client and the second client according to a preset service flow.
Optionally, the mapping, according to a preset mapping rule, the first account of the first client and the second account of the second client to a third account under the same platform respectively includes:
mapping the first account of the first client and the second account of the second client into third accounts with the same length and format by using an MD5 algorithm;
storing the third account number, the corresponding relation between the third account number and the first account number and the corresponding relation between the third account number and the second account number on the same platform,
the same platform is a server side independent of the first client side and the second client side.
Optionally, the first client is a driver client.
Optionally, the second client is a capacity center client.
Optionally, the preset business process includes a leave-asking approval process or a job task process.
According to a second aspect of the present invention, an apparatus for implementing collaborative flow management between different clients is provided, the apparatus comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a first account of a first client and a second account of a second client;
the mapping unit is used for mapping the first account of the first client and the second account of the second client to a third account under the same platform according to a preset mapping rule;
the binding unit is used for binding the association relation information aiming at the third account under the same platform and setting corresponding authority;
and the cooperative management unit is used for realizing flow cooperative management between the first client and the second client according to a preset service flow.
Optionally, the mapping unit is specifically configured to:
mapping the first account of the first client and the second account of the second client into third accounts with the same length and format by using an MD5 algorithm;
storing the third account number, the corresponding relation between the third account number and the first account number and the corresponding relation between the third account number and the second account number on the same platform,
the same platform is a server side independent of the first client side and the second client side.
Optionally, the first client is a driver client.
Optionally, the second client is a capacity center client.
Optionally, the preset business process includes a leave-asking approval process or a job task process.
According to the technical scheme, a first account of a first client and a second account of a second client are obtained; respectively mapping the first account of the first client and the second account of the second client to a third account under the same platform according to a preset mapping rule; binding incidence relation information aiming at a third account under the same platform, and setting corresponding authority; and realizing flow cooperative management between the first client and the second client according to a preset business flow, so that the flow cooperative management can be realized between different clients.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a method for implementing process collaborative management between different clients according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of an apparatus for implementing flow collaborative management between different clients according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
Some words mentioned in the embodiments of the present disclosure are exemplified below.
The User Equipment (UE) mentioned in the embodiments of the present disclosure is a device such as a mobile terminal or a Personal Computer (PC). Such as a smart phone, a Personal Digital Assistant (PDA), a tablet computer, a laptop computer, a car computer (carputer), a handheld game console, smart glasses, a smart watch, a wearable device, a virtual display device or a display enhancement device (e.g., Google Glass, Oculus Rift, Hololens, Gear VR), etc.
Fig. 1 is a flowchart of a method for implementing process collaborative management between different clients according to an embodiment of the present disclosure. As shown in fig. 1, a method for implementing flow collaborative management between different clients according to an embodiment of the present disclosure includes:
in step S101, a first account of a first client and a second account of a second client are acquired.
The first client is a driver client, and is loaded on user equipment, the user equipment can be a mobile terminal or a PC terminal and the like, the terminal is a mobile terminal or a PA terminal and the like which are held by the user equipment and used for providing operation service, the second client is a capacity center client and can be loaded on an internal tool of an enterprise, and the first account and the second account are a pure number combination, a pure letter combination, a combination of mixed numbers and letters, a pure Chinese character combination, a combination of mixed numbers and Chinese characters or a combination of mixed letters and Chinese characters.
Next, in step S102, the first account of the first client and the second account of the second client are mapped to a third account of the same platform according to a preset mapping rule.
Specifically, the steps include: mapping the first account of the first client and the second account of the second client into third accounts with the same length and format by using an MD5 algorithm; and storing the third account number, the corresponding relation between the third account number and the first account number and the corresponding relation between the third account number and the second account number on the same platform.
More specifically, account numbers of different clients are mapped into uniform 16-bit length MD5 values by using an MD5 algorithm, and the corresponding relation between each user account number and the MD5 value is recorded. Since the MD5 value is unique, mapping the user account to the MD5 value does not duplicate. For example, a1 is the user account of the driver client, and after mapping to MD5 value, the account X1 is obtained, and B1 is the user account of the driver client, and after mapping to MD5 value, the account X2 is obtained. Originally, A1 and B1 are account numbers of different clients, which are not known to each other, and now belong to a series of account numbers on the same platform. The mapped account numbers are all account numbers with uniform length and format, are managed and stored on the same platform, and simultaneously store the corresponding relation between the new account number and the original account number, so that the restoration is ensured.
The same platform is a server independent from the first client and the second client, and particularly relates to a set of user management system. For example, a user originally belongs to a first client, now belongs to the first client and the user management system, and a user originally belongs to a second client, now belongs to the second client and the user management system. The specific storage mode adopts a user information database, and fields include user id (account corresponding to the client and account corresponding to the user management system), user name, user group, user authority and the like.
Next, in step S103, binding association relationship information for a third account under the same platform, and setting a corresponding right.
For the driver client user account A1, it is subordinate to the capacity center client's fleet management account B1, while fleet management account B1 is subordinate to the capacity center client's fleet manager account C1, while fleet manager account C1 is subordinate to the capacity center client's city manager account D1, and city manager account D1 is subordinate to the capacity center client's region manager account E1. Similarly, according to the account number under the same platform, the association relation information is bound on the platform, and corresponding authority is set.
Finally, in step S104, a flow coordination management is implemented between the first client and the second client according to a preset service flow.
The preset business process comprises a leave-asking approval process or a job task process. The procedure of the leave approval will be described as an example. When a driver applies for vacation on a driver client, the driver needs to fill in a vacation examination and approval worksheet on the driver client. After the leave approval work order is filled, the leave approval work order is sent to a third party platform (the same platform). And the platform forwards the request for the fake examination and approval work order to the client of the transport center according to the bound organization and the post so as to manage the driving management of the driver for examination and approval. If the driving management approval passes, the information that the work order approval passes can be sent to the platform, the platform can collaboratively or copy the information to the leader of the driving management according to the bound organization and post to know, and the information can be forwarded to the driver client side to enable the corresponding driver to know that the work order applying for vacation has been approved by the superior (driving management) of the driver. If the driving management approves and rejects, the information of the approval rejection of the worksheet is transmitted to the leader of the driving management cooperatively or copied in the similar process, and is transmitted to the driver client side to enable the corresponding driver to know that the worksheet applying for vacation is approved and rejected by the superior (driving management) of the driver.
Specifically, the third-party platform (the same platform) is a server independent of two different clients, the user cannot log in the third-party platform, and a login mode of the user at the client is unchanged compared with the prior art. The user to which the work order flows and various flow logics are realized by separate flow configuration logics, although the flow logic has a certain relation with the application, the flow logic is realized by another set of separate logics and systems, and the flow logic is the prior art. It should be noted that there is a separate process configuration third-party platform, and this third-party platform may create a process, and configure a template of a work order (leave-asking template, maintenance approval template, payment application template, etc.) during creation, a node of the process, a creation and closing rule of the process, and a flow rule between nodes (the flow to the leader, to the specific user, to a certain post, and the flow after approval and rejection may all be configured). In particular embodiments, the request flow configures an API of the third party platform to obtain instructions on how to flow. As to why the work order is automatically sent from the client to the platform, two different clients share one server (third party platform) when implementing a specific service.
In the embodiment, a first account of a first client and a second account of a second client are obtained; respectively mapping the first account of the first client and the second account of the second client to a third account under the same platform according to a preset mapping rule; binding incidence relation information aiming at a third account under the same platform, and setting corresponding authority; and realizing flow cooperative management between the first client and the second client according to a preset business flow, so that the flow cooperative management can be realized between different clients.
Method embodiments are described as a series of acts or combinations for simplicity of explanation, but it should be understood by those skilled in the art that the disclosed embodiments are not limited by the order of acts or acts described, as some steps may occur in other orders or concurrently with other steps in accordance with the disclosed embodiments. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the disclosed embodiments.
Fig. 2 is a schematic structural diagram of an apparatus for implementing flow collaborative management between different clients according to an embodiment of the present disclosure. As shown in fig. 2, an apparatus for implementing flow coordination management between different clients according to an embodiment of the present disclosure includes:
an obtaining unit 201, configured to obtain a first account of a first client and a second account of a second client;
a mapping unit 202, configured to map, according to a preset mapping rule, a first account of the first client and a second account of the second client to third accounts of the same platform respectively;
a binding unit 203, configured to bind, for a third account under the same platform, association relationship information, and set a corresponding right;
a cooperative management unit 204, configured to implement flow cooperative management between the first client and the second client according to a preset service flow.
In an optional embodiment of the present disclosure, the mapping unit 202 is specifically configured to:
mapping the first account of the first client and the second account of the second client into third accounts with the same length and format by using an MD5 algorithm;
and storing the third account number, the corresponding relation between the third account number and the first account number and the corresponding relation between the third account number and the second account number on the same platform.
In an optional embodiment of the disclosure, the first client is a driver client.
In an optional embodiment of the present disclosure, the second client is a capacity center client.
In an optional embodiment of the present disclosure, the preset business process includes a leave examination and approval process or a job task process.
It should be noted that, specific details related to the apparatus for implementing flow collaborative management between different clients provided by the present disclosure have been described in detail in the method for implementing flow collaborative management between different clients provided by the present disclosure, and are not described herein again.
It should be noted that, in the respective components of the system of the present disclosure, the components therein are logically divided according to the functions to be implemented, but the present disclosure is not limited thereto, and the respective components may be re-divided or combined as needed, for example, some components may be combined into a single component, or some components may be further decomposed into more sub-components.
Various component embodiments of the disclosure may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components in a system according to embodiments of the present disclosure. The present disclosure may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present disclosure may be stored on a computer-readable medium or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the disclosure, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The disclosure may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
The above embodiments are only suitable for illustrating the present disclosure, and not limiting the present disclosure, and those skilled in the relevant art can make various changes and modifications without departing from the spirit and scope of the present disclosure, so that all equivalent technical solutions also belong to the scope of the present disclosure, and the scope of the present disclosure should be defined by the claims.
Claims (10)
1. A method for implementing flow collaborative management between different clients is characterized in that the method comprises the following steps:
acquiring a first account of a first client and a second account of a second client, wherein the first client and the second client are clients of different platforms;
respectively mapping a first account of the first client and a second account of the second client to different third accounts on the same platform according to a preset mapping rule, wherein the same platform is independent of the server of two different clients;
binding incidence relation information aiming at a third account under the same platform, and setting corresponding authority;
and realizing flow cooperative management between the first client and the second client according to a preset service flow.
2. The method of claim 1, wherein the mapping the first account of the first client and the second account of the second client to different third accounts on the same platform according to a preset mapping rule comprises:
mapping the first account of the first client and the second account of the second client into third accounts with the same length and format by using an MD5 algorithm;
storing the third account number, the corresponding relation between the third account number and the first account number and the corresponding relation between the third account number and the second account number on the same platform,
the same platform is a server side independent of the first client side and the second client side.
3. The method for implementing collaborative management of processes between different clients according to claim 1, wherein the first client is a driver client.
4. The method of claim 1, wherein the second client is a transportation center client.
5. The method of claim 1, wherein the preset business process comprises a leave-on examination and approval process or a job task process.
6. An apparatus for implementing collaborative management of processes between different clients, the apparatus comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a first account of a first client and a second account of a second client, and the first client and the second client are clients of different platforms;
the mapping unit is used for mapping the first account of the first client and the second account of the second client into different third accounts on the same platform according to a preset mapping rule, wherein the same platform is a server independent of two different clients;
the binding unit is used for binding the association relation information aiming at the third account under the same platform and setting corresponding authority;
and the cooperative management unit is used for realizing flow cooperative management between the first client and the second client according to a preset service flow.
7. The apparatus for implementing collaborative flow management between different clients as recited in claim 6, wherein the mapping unit is specifically configured to:
mapping the first account of the first client and the second account of the second client into third accounts with the same length and format by using an MD5 algorithm;
storing the third account number, the corresponding relation between the third account number and the first account number and the corresponding relation between the third account number and the second account number on the same platform,
the same platform is a server side independent of the first client side and the second client side.
8. The apparatus for implementing collaborative management of processes between different clients according to claim 6, wherein the first client is a driver client.
9. The apparatus for implementing collaborative management of processes between different clients as recited in claim 6, wherein the second client is a capacity center client.
10. The apparatus for implementing collaborative flow management between different clients as recited in claim 6, wherein the preset business process includes a leave approval process or a job task process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610496058.9A CN107547609B (en) | 2016-06-28 | 2016-06-28 | Method and device for realizing flow collaborative management among different clients |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610496058.9A CN107547609B (en) | 2016-06-28 | 2016-06-28 | Method and device for realizing flow collaborative management among different clients |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107547609A CN107547609A (en) | 2018-01-05 |
| CN107547609B true CN107547609B (en) | 2021-04-09 |
Family
ID=60965898
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610496058.9A Active CN107547609B (en) | 2016-06-28 | 2016-06-28 | Method and device for realizing flow collaborative management among different clients |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107547609B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109413195B (en) * | 2018-11-12 | 2021-06-22 | 北京云狐时代科技有限公司 | Service processing method and device |
| CN112035275A (en) * | 2020-07-30 | 2020-12-04 | 长沙市到家悠享网络科技有限公司 | Data processing method and server side equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103248661A (en) * | 2012-02-13 | 2013-08-14 | 宇龙计算机通信科技(深圳)有限公司 | Account number binding method and system |
| CN104539422A (en) * | 2014-12-01 | 2015-04-22 | 魅族科技（中国）有限公司 | Authentication control method for application client, server and terminals |
| CN104867044A (en) * | 2015-04-28 | 2015-08-26 | 广西智通节能环保科技有限公司 | Method for sharing electronic shopping cart |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11042946B2 (en) * | 2014-09-30 | 2021-06-22 | Walmart Apollo, Llc | Identity mapping between commerce customers and social media users |
-
2016
- 2016-06-28 CN CN201610496058.9A patent/CN107547609B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103248661A (en) * | 2012-02-13 | 2013-08-14 | 宇龙计算机通信科技(深圳)有限公司 | Account number binding method and system |
| CN104539422A (en) * | 2014-12-01 | 2015-04-22 | 魅族科技（中国）有限公司 | Authentication control method for application client, server and terminals |
| CN104867044A (en) * | 2015-04-28 | 2015-08-26 | 广西智通节能环保科技有限公司 | Method for sharing electronic shopping cart |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107547609A (en) | 2018-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11347889B2 (en) | Data processing systems for generating and populating a data inventory | |
| US10997671B2 (en) | Methods, systems and computer program products for collaborative tax return preparation | |
| CN107516191B (en) | System, method and tool for collaborative approval of "multi-planning" and "one-picture" project | |
| CN112150107B (en) | Order task processing and travel service providing method and device | |
| US20180349640A1 (en) | Data processing systems for generating and populating a data inventory | |
| US9786017B1 (en) | Systems and methods for generating and sending electronic messages related to a tax return | |
| US10318116B2 (en) | Dynamic presentations management | |
| US20130218829A1 (en) | Document management system and method | |
| US9704139B2 (en) | Techniques for requesting web conference recordings automatically via a conference invitation response | |
| US9608987B2 (en) | Systems and methods for the secure sharing of data | |
| US20180322571A1 (en) | System and method for facilitating electronic transactions | |
| CN107644318A (en) | A kind of bid evaluation system for the integrated management that calls for bid | |
| CN107547609B (en) | Method and device for realizing flow collaborative management among different clients | |
| US11222309B2 (en) | Data processing systems for generating and populating a data inventory | |
| US20160275454A1 (en) | Populating Forms for Electronic Signature on a Mobile Device | |
| CN110046233A (en) | Problem distributing method and device | |
| US20140207706A1 (en) | Computer Implemented System and Method for Aggregating, Analyzing and Distributing Information Corresponding to Retirement Plans | |
| US20220129837A1 (en) | Data processing systems for generating and populating a data inventory | |
| US20140143349A1 (en) | Distributed Architecture Data Transfer System | |
| US20120215718A1 (en) | Computer Implemented System and Method for Aggregating, Analyzing and Distributing Information Corresponding to Retirement Plans | |
| US20240177119A1 (en) | Artificial intelligence agent | |
| US20250131383A1 (en) | System and method for matching job applicants to job openings | |
| WO2019023538A1 (en) | Data processing systems for generating and populating a data inventory | |
| AU2017101041A4 (en) | The invention provides a cloud-based via electronic device networking method and system that connects businesses (employers) with individuals (employees/job seekers) utilizing a system of date and time availability, predetermined skill requirements, geographical location and real time technology. | |
| Tuomey | Arlington County Vendor Permit Application and Guidelines |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201202 Address after: 100193, No. 34, building No. 8, West flourishing road, Haidian District, Beijing Applicant after: BEIJING DIDI INFINITY TECHNOLOGY AND DEVELOPMENT Co.,Ltd. Address before: Office building D comprehensive service district Nangang Industrial Zone 300480 in Tianjin Binhai Economic and Technological Development Zone of Tianjin City 2 219-23 room Applicant before: Didi (China) Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |