CN112131192A - Request response method, device and system, storage medium and electronic device - Google Patents
Request response method, device and system, storage medium and electronic device Download PDFInfo
- Publication number
- CN112131192A CN112131192A CN202010976693.3A CN202010976693A CN112131192A CN 112131192 A CN112131192 A CN 112131192A CN 202010976693 A CN202010976693 A CN 202010976693A CN 112131192 A CN112131192 A CN 112131192A
- Authority
- CN
- China
- Prior art keywords
- account
- authority
- client
- data
- data object
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 230000004044 response Effects 0.000 title claims abstract description 28
- 230000015654 memory Effects 0.000 claims description 19
- 238000012423 maintenance Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 claims description 4
- 230000000694 effects Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 11
- 238000007726 management method Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000013523 data management Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/174—Redundancy elimination performed by the file system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/113—Details of archiving
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/01—Customer relationship services
- G06Q30/015—Providing customer assistance, e.g. assisting a customer within a business location or via helpdesk
- G06Q30/016—After-sales
Abstract
The application discloses a request response method, device and system, a storage medium and an electronic device. Wherein, the method comprises the following steps: receiving an operation request of a target account, wherein the operation request is used for requesting to execute data operation related to a client account, and data belonging to the same client account are stored in a database in a centralized manner; searching the operation authority configured for the target account from the authority configuration of the client account; and responding to the operation request according to the operation authority of the target account. The method and the device solve the technical problem that garbage files in a CRM system are too many in the related art.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a request response method, device, and system, a storage medium, and an electronic device.
Background
The CRM system is called Customer relationship management system, and is named as a Customer relationship management system in Chinese, and is used for establishing an information system for collecting, managing, analyzing and utilizing Customer information for enterprises by utilizing software, hardware and network technologies. The management of customer data is taken as a core, various interactive behaviors of an enterprise and customers in the marketing and sales process and states of various related activities are recorded, various data models are provided, and support is provided for later analysis and decision.
In the CRM system of the related art, each sales can only see the customer data in charge of itself, and can only add activity records, upload attachments, create sales opportunities, and the like to the customer in charge of itself. For the problem that a plurality of sales follow the same customer at the same time, the current solution in the CRM system is to create a plurality of customers with similar names, each customer has respective responsible sales, the data created for the sales of the customer can only be seen by the sales person, and the sales person responsible for the customer can not see any information of the customer, so that under the long-time operation of the system, a lot of junk data can be generated, thereby affecting the maintenance of the system.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the application provides a request response method, device and system, a storage medium and an electronic device, so as to at least solve the technical problem of excessive junk files in a CRM system in the related art.
According to an aspect of an embodiment of the present application, there is provided a request response method, including: receiving an operation request of a target account, wherein the operation request is used for requesting to execute data operation related to a client account, and data belonging to the same client account are stored in a database in a centralized manner; searching the operation authority configured for the target account from the authority configuration of the client account; and responding to the operation request according to the operation authority of the target account.
According to another aspect of the embodiments of the present application, there is also provided a request response apparatus, including: the receiving unit is used for receiving an operation request of a target account, the operation request is used for requesting to execute data operation related to a customer account, and data belonging to the same customer account are stored in a database in a centralized manner; the searching unit is used for searching the operation authority configured for the target account from the authority configuration of the client account; and the response unit is used for responding to the operation request according to the operation authority of the target account.
According to another aspect of the embodiments of the present application, there is also provided a request response system, including: the intelligent terminal is logged in with a target account and used for sending an operation request, and the operation request is used for requesting to execute data operation related to a client account; the server is used for searching the operation authority configured for the target account from the authority configuration of the client account under the condition of receiving the operation request, and responding to the operation request according to the operation authority of the target account; and the data of the same customer account is stored in the database in a centralized way.
According to another aspect of the embodiments of the present application, there is also provided a storage medium including a stored program which, when executed, performs the above-described method.
According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the above method through the computer program.
In the embodiment of the application, when an operation request of a target account is received, the operation authority configured for the target account is searched from the authority configuration of a client account; the operation request is responded according to the operation authority of the target account, and because the data belonging to the same customer account is stored in the database in a centralized manner instead of storing the data of the same customer in each sale, the same data is prevented from being stored in multiple copies, the technical problem of excessive junk files in a CRM system in the related technology can be solved, and the technical effect of preventing the generation of junk data is further achieved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a schematic diagram of a hardware environment for a method of responding to requests according to an embodiment of the present application;
FIG. 2 is a flow chart of an alternative method of responding to requests according to an embodiment of the present application;
FIG. 3 is a flow chart of an alternative method of responding to requests according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an alternative privilege configuration according to an embodiment of the present application;
FIG. 5 is a schematic diagram of an alternative privilege configuration according to an embodiment of the present application;
FIG. 6 is a schematic diagram of an alternative requested response device according to an embodiment of the present application;
and
fig. 7 is a block diagram of a terminal according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above 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 data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
First, partial nouns or terms appearing in the description of the embodiments of the present application are applicable to the following explanations:
sales opportunities: a purchasing-oriented customer having determined his purchasing intent, a sales opportunity for potential deal; moving: sales (herein referred to as sales accounts) records of the follow-up process after each follow-up of the customer; account number: a platform account number associated with the customer (i.e., a customer account number); contract: a purchase contract signed by the customer; accessories: selling attachments to related content uploaded down by the customer; history follows up with people: historically follow up with the customer's sales; operating the log: the operation log recorded when the customer account is edited each time; client team leader (denoted herein by administrator account): the client is mainly responsible for follow-up sales, and can add the group members and distribute the authority of the group members; checking and editing personal data: the sales has viewing and editing authority on the data created by the user; and (4) viewing all data: the sales has viewing authority on all data under the client and can edit the data created by the user; editing all data: sales have viewing and editing rights for all data under the customer.
According to an aspect of embodiments of the present application, there is provided an embodiment of a request response system. In the present embodiment, as shown in fig. 1, the system may be constituted by a terminal 101 and a server 103.
The server 103 is connected with the terminal 101 through a network, information interaction between the terminal and the terminal can be performed through the network, and through the interaction, the server provides CRM service for the terminal or a client (which can be a web client, an application client, or the like) installed on the terminal. The database 105 may be provided on the server or separately from the server, and is used for providing a data storage service for the server 103, storing data objects belonging to the same customer account in a separate database, or dividing an area in the database for storing in a centralized manner. Such networks include, but are not limited to: the terminal 101 is not limited to a PC, a mobile phone, a tablet computer, and the like.
As shown in fig. 1, the terminal is an intelligent terminal logged in a target account (the target account represents sales, and may be a sales manager or general sales) of a user, and when a request is required to perform a data operation related to a client account (the client account represents a client maintained by sales), an operation request is sent to a server; the server can search the operation authority configured for the target account from the authority configuration of the client account, and respond to the operation request according to the operation authority of the target account.
In a customer data management, CRM, system, customer data for multiple customers may be included, and a corresponding customer team may be created for each customer, with the team members in each customer team being able to perform a role division. For example, after the roles are divided, two types of members can be obtained, one type is a principal (i.e., an administrator), and the other type is a common member (or called a group member, i.e., a specific salesperson), the principal can manage the authority of the common member, the principal can also be provided with roles such as a general accountant, which number of roles are specifically divided, and the operation authority of each role in the system can be set according to requirements. Including but not limited to adding panelists, panel principals, viewing data, editing data, and the like.
The purposes of the interaction executed by the terminal and the server mainly comprise two purposes, one is that the administrator carries out related operations, for example, in an organization adopting a sales group, a client group leader can assign authorities to members, each data object can be specified, the authority of the members can be strictly controlled, the safety of client data is ensured, and different sales can carry out follow-up maintenance on the same client under the condition of not influencing each other; the other is data access operation of ordinary sales, such as data reading, modification, deletion, writing and the like, and when the operation is performed, the server can authenticate the ordinary sales according to the operation authority.
According to an aspect of embodiments of the present application, there is provided a method embodiment of a method for responding to a request. The request response method according to the embodiment of the present application may be executed by the server 103, or may be executed by both the server 103 and the terminal 101. Fig. 2 is a flowchart of an alternative request response method according to an embodiment of the present application, and as shown in fig. 2, the method may include the following steps:
in step S202, the server receives an operation request sent by a user on the terminal in the name of a target account to request to perform data operation related to a client account, where data belonging to the same client account is stored in a database in a centralized manner (e.g., the data is stored in the database in the form of a data object), that is, the data belonging to the same client account is stored in a centralized manner, rather than in a separate manner, for example, a storage area identified by the client account is established in the database, and all data of the client are stored in the area.
The data object is an object for defining a certain type of data in the customer data, and specific data objects include, but are not limited to, contacts, sales opportunity information, activity information, account information, contracts, attachments, operation logs, and the like, and may also refer to a more specific piece of information in the data object.
Step S204, the operation authority of each target account is recorded in the authority configuration of the client account, and the server can search the operation authority configured for the target account from the authority configuration of the client account.
And step S206, responding to the operation request according to the operation authority of the target account.
Through the steps, when the operation request of the target account is received, the operation authority configured for the target account is searched from the authority configuration of the client account; the operation request is responded according to the operation authority of the target account, and because the data belonging to the same customer account is stored in the database in a centralized manner instead of storing the data of the same customer in each sale, the same data is prevented from being stored in multiple copies, the technical problem of excessive junk files in a CRM system in the related technology can be solved, and the technical effect of preventing the generation of junk data is further achieved.
The technical scheme mainly comprises two parts, wherein one part is the authority management of an administrator in the client group on members, and the other part is the access management of the members in the client group. The following are described separately:
(1) and managing the authority of the members by the administrator in the client group.
And step 11, adding a sales account of a team member to the administrator account.
Each client can be used as a client group, a plurality of sales are carried out simultaneously, each client has a client responsible person, and the client responsible person has operation rights of adding group members, setting group member rights, moving out the group members, returning to the open sea, marking invalid and the like.
When a new group member is added, the server receives an adding instruction sent by an administrator, and the adding instruction indicates that a second account is added to be a sales account for maintaining a client account; and when the server responds to the adding instruction, adding the second account into a sales account for maintaining the client account, and configuring default operation permission or appointed operation permission for the second account.
If the client team member can view all data under the client by default, including data objects such as activities under the client, sales opportunities, follow-up records, operation logs, attachments and the like, the team member can only edit the data created by the team member. And a default authority is configured for sales of entering groups, so that the increment of the database can be reduced, and the pressure of a database server is relieved.
And step 12, if the default permission can not meet the requirement of the actual situation, the administrator individually configures the permissions of the group members.
In step 121, the server receives an operation request sent by the user on the terminal on the name of the target account.
In step 122, when the operation request indicates that it is requested to perform an authority configuration operation (i.e. the sales account configuration has an operation authority for operating the data object of the client account, which may be denoted as the first account), the operation authority configured for the target account is searched from the authority configuration of the client account.
Step 123, authenticate the user, that is, determine whether the target account is an administrator account.
When the target account does not belong to the administrator account, the server returns prompt information of request failure, and data security can be improved by verifying the account.
And step 124, executing the authority configuration operation under the condition that the operation authority of the target account indicates that the target account is the administrator account.
The above rights configuration operations include several types as follows:
1) the authority of the first account is configured to view all data, the first account is allowed to view all data objects of the customer account, and the data objects created by the first account are edited.
2) The authority of the first account is configured to view and edit the personal data, and the first account is allowed to view and edit the data objects created by the first account, such as viewing and editing the data objects created by the user, selling opportunities and the like.
3) The permissions of the first account are configured to edit all data, allowing the first account to view and edit all data objects of the customer account.
4) When the operation authority of each member in the group member is configured, the operation authority of the designated data object can be configured for the first account in a mode of data object by data object, which means that the first account is allowed to view the first data object or edit the first data object, and the first data object is the data object designated by the administrator account in all the data objects of the client account.
By independently authorizing each data object under each client, the selling authority can be clearly configured, so that the function that a sales person in charge who is not the client can check the client is realized, the selling authority under the client can be safely set, and the safety of client data is ensured.
5) And deleting the operation permission configured by the administrator account for the first account, wherein the operation permission can be deleting all permissions or deleting the permission of the specified data object.
6) And changing the authority configured by the administrator account for the first account from the current operation authority to another operation authority, such as changing the data of the user to be viewed and edited into all the data to be edited.
Step 13, the member exits.
And under the condition that the sales account is deleted from the client group, a third data object is delivered to the account maintenance of an administrator, and the third data object is a data object created or maintained by the sales account in all data objects of the client account. When the team member exits, member management can be performed through the unbinding process. I.e., when the panelist exits, the data under his or her responsibility is automatically assigned to the customer principal.
In the above customer data management scheme, the customer data is managed by the customer group, so that the members in the customer group can conveniently access and edit the customer data of the customer, the problem that the data cannot be shared among the members is avoided, the junk data generated by setting a plurality of similar customer accounts in the customer data management system is reduced, the pressure of a server is reduced, and the same customer adopts the corresponding customer group for management, so that the system is convenient to maintain.
(2) And (4) access management of members in the client team.
In step 21, the server receives an operation request sent by the team member on the terminal on the name of the sales account (i.e. the second account).
And step 22, under the condition that the operation request indicates that the client data operation is requested to be executed on the client account, searching the operation authority configured for the second account from the authority configuration of the client account, wherein the client data operation is the operation on the second data object of the client account.
Step 23, the second account is authenticated, that is, whether the second account has the authority to operate the second data object, such as the editing authority for checking, deleting, modifying, adding, etc.
The flow of determining the viewing permission is as follows:
step 231, determine whether the second account has the viewing right for the client account.
Step 232, under the condition that the second account has the viewing right to the client account, determining whether the second account has the viewing right to the second data object.
Step 233, allowing the second account to view the second data object under the condition that the second account has the view right for the second data object.
The process for determining the editing authority comprises the following steps:
step 231, determine whether the second account has the viewing right for the client account.
Step 232, under the condition that the second account has the viewing right to the client account, determining whether the second account has the viewing right to the second data object.
In step 233, in the case that the second account has the viewing right for the second data object, it is determined whether the second account has the editing right for the second data object.
Step 234, allowing the second account to edit the second data object under the condition that the second account is determined to have the editing authority for the second data object.
As an alternative embodiment, the technical solution of the present application is further detailed below with reference to the steps shown in fig. 3.
Step S301, adding team members of a client team, wherein one client can be followed by a plurality of team members simultaneously, and each client has a client responsible person.
Step S302, configuring the operation authority of each group member of the client group. The client principal has the operation rights of adding the group members, setting the group member rights, moving out the group members, exiting the open sea, marking invalid and the like.
By default, the client team member can view all data under the client, including data objects such as activity under the client, sales opportunities, follow-up records, operation logs, attachments, etc., but the team member can only edit the data created by the team member.
The client team leader can set the authority of the members, and the authority is divided into: checking and editing the personal data, checking all the data and editing all the data. The viewing and editing of the personal data represents that the group members can only view and edit data objects such as activities, sales opportunities and the like created by the persons; viewing all data shows that the team member can see all data of the specified data object under the client and can edit the data created by the team member; editing all data means that the team member can view and edit all data of the specified data object under the client.
For example: when the authority of the contact under the client is set to be the data of the user, the group member can only view and edit the data of the contact created by the user; if the authority of the contact person is set to view all the data, the sales can see the data of all the contact persons under the client, but only the data created by the user can be edited; if the authority of the contact is set to edit all data, all the contacts under the client can be viewed by the team members and can be edited.
The scheme for setting the authority for a single data object such as sales opportunities, activities, accounts, accessories, history followers, operation logs and the like refers to fig. 4, and fig. 4 is an interface schematic diagram of authority configuration.
Step S303, the terminal sends a client data viewing request, and the data viewing request carries a client identifier and an account identifier.
Step S304, judging whether the account contains the viewing authority corresponding to the client identification. When the viewing right is included, step S306 is executed, otherwise step S305 is executed.
In step S305, the terminal receives unauthorized prompt information returned by the server.
Step S306, the terminal receives the client data returned by the server.
Step S307, the terminal sends a data object viewing request, and the data object viewing request carries a target data object and an account.
Step S308, judging whether the account contains the viewing authority for viewing the data object. When included, step S310 is executed, otherwise step S309 is executed. After the client responsible person completes the authority configuration work, the team member can check the data of the client under the client team, and when checking the data objects such as sales opportunities, contacts, activities, attachments, history follow-up persons, operation logs and the like of the client, whether the sales has the checking authority (access authority) of the data objects needs to be judged.
In step S309, the terminal receives the non-viewable prompt information returned by the server.
In step S310, the terminal receives the data object returned by the server. When the authority of the team member is to view and edit the personal data, the team member can only view the data created by the person, such as: the team members can only see the sales opportunities created by themselves, but cannot see the sales opportunities created by others; when the team member's right is to view all data, the team member can view all data (i.e., data created by himself and other team members) of the specified data object under the current client, for example: the panelists may view the log of operations of the owner, the activity data created by the owner.
In step S311, the terminal sends a data editing request, which may carry an account and a data object.
Step S312, determine whether the account contains an editing right to edit the data object. When the editing right is included, step S314 is performed, and otherwise, step S313 is performed.
In step S313, the terminal receives the non-editable prompt message returned by the server.
In step S314, the data object is edited.
In an embodiment, referring to fig. 5, fig. 5 is an association diagram of a data table in a client data management method in an embodiment, and the association diagram includes a client table, an employee table, a client team member table, and a client team authority setting table, where the client table is used for storing client data, and the client table includes a client id and a client name. The employee table is used for storing employee information, and comprises an employee id, an employee name and the like. The client team member table is used for storing client team member information and comprises a client id and an employee id, and the client id and the employee id are associated through the client team member table, namely the client id and the employee id are bound. The client group authority setting table comprises a client id, an employee id, a data object type and a data object authority, and the incidence relation of the client id, the employee id, the data object type and the data object authority is established through the client group authority setting table.
In one embodiment, when a panelist needs to perform an operation on a data object, such as editing customer data, editing sales opportunities, setting activities to complete, downloading a delete attachment, etc., it needs to be verified whether the piece of data object was created by the panelist himself. If so, the team member can edit, if not, the team member needs to be verified whether the team member has an editing right for the type of data object, namely, the right to edit all data, if so, the team member can edit, and if not, the team member cannot edit.
According to the client data management method, each data object under each client is authorized independently, and the selling authority can be configured clearly, so that the function that a sales person in charge who is not the client can check the client is realized, the selling authority under the client can be set safely, and the safety of client data is ensured.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.
According to another aspect of the embodiment of the present application, there is also provided a request responding apparatus for implementing the above request responding method. Fig. 6 is a schematic diagram of an alternative request responding apparatus according to an embodiment of the present application, and as shown in fig. 6, the apparatus may include:
a receiving unit 61, configured to receive an operation request of a target account, where the operation request is used to request to perform data operation related to a client account, and data belonging to the same client account is centrally stored in a database;
the searching unit 63 is used for searching the operation authority configured for the target account from the authority configuration of the client account;
and the response unit 65 is configured to respond to the operation request according to the operation authority of the target account.
It should be noted that the receiving unit 61 in this embodiment may be configured to execute step S202 in this embodiment, the searching unit 63 in this embodiment may be configured to execute step S204 in this embodiment, and the responding unit 65 in this embodiment may be configured to execute step S206 in this embodiment.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the above embodiments. It should be noted that the modules described above as a part of the apparatus may operate in a hardware environment as shown in fig. 1, and may be implemented by software or hardware.
Through the module, when receiving an operation request of a target account, searching an operation authority configured for the target account from authority configuration of a client account; the operation request is responded according to the operation authority of the target account, and because the data belonging to the same customer account is stored in the database in a centralized manner instead of storing the data of the same customer in each sale, the technical problem of excessive junk files in a CRM system in the related technology can be solved, and the technical effect of avoiding generating junk data is further achieved.
Optionally, the target account includes an administrator account, wherein the lookup unit is further configured to: under the condition that the operation request indicates that the permission configuration operation is requested to be executed, searching an operation permission configured for a target account from permission configuration of the client account, wherein the permission configuration operation is used for indicating that the target account configures the operation permission of a data object of the client account for a first account, and the first account is a sales account for maintaining the client account; the response unit may be further operable to: and executing authority configuration operation under the condition that the operation authority of the target account indicates that the target account is the administrator account.
Optionally, the response unit may be further configured to: configuring the authority of the first account into a first operation authority, wherein the first operation authority represents that the first account is allowed to view the data object of the client account and edit the data object created by the first account; configuring the authority of the first account into a second operation authority, wherein the second operation authority represents that the first account is allowed to view and edit the data object created by the first account; and configuring the authority of the first account as a third operation authority, wherein the third operation authority represents that the first account is allowed to view and edit all data objects of the client account.
Optionally, the response unit may be further configured to: and configuring the authority of the first account as a fourth operation authority, wherein the fourth operation authority represents that the first account is allowed to view or edit the first data object, and the first data object is a data object specified by an administrator account in all data objects of the client account.
Optionally, the response unit may be further configured to: deleting the operation authority configured by the administrator account for the first account; and changing the authority configured by the administrator account for the first account from the current operation authority to another operation authority.
Optionally, the target account includes a second account that is a sales account, wherein the lookup unit is further configured to: under the condition that the operation request indicates that the client data operation is requested to be performed on the client account, searching an operation authority configured for a second account from authority configuration of the client account, wherein the client data operation is an operation on a second data object of the client account; the response unit may be further operable to: and executing the client data operation under the condition that the operation authority of the second account indicates that the second account is allowed to operate the second data object.
Optionally, the client data operation comprises an operation of viewing the second data object, and the response unit is further operable to: determining whether the second account has the viewing permission for the client account; under the condition that the second account has the viewing permission for the client account, determining whether the second account has the viewing permission for the second data object; and allowing the second account to view the second data object under the condition that the second account has the view permission of the second data object.
Optionally, the client data operation comprises an operation of editing the second data object, and the response unit is further operable to: determining whether the second account has the viewing permission for the client account; under the condition that the second account has the viewing permission for the client account, determining whether the second account has the viewing permission for the second data object; under the condition that the second account has the viewing permission of the second data object, determining whether the second account has the editing permission of the second data object; and allowing the second account to edit the second data object under the condition that the second account is determined to have the editing authority of the second data object.
Optionally, the apparatus of the present application may further include a configuration unit, configured to receive an addition instruction before receiving the operation request of the target account, where the addition instruction is used to instruct to add the second account as a sales account for maintaining the customer account; and responding to the adding instruction, adding the second account into a sales account for maintaining the customer account, and configuring default operation authority or appointed operation authority for the second account.
Optionally, the configuration unit of the present application may be further configured to: and after responding to the operation request according to the operation permission of the target account, under the condition that the second account is deleted from the sales account for maintaining the client account, handing a third data object to the administrator account for maintenance, wherein the third data object is a data object created or maintained by the second account in all data objects of the client account.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the above embodiments. It should be noted that the modules described above as a part of the apparatus may be operated in a hardware environment as shown in fig. 1, and may be implemented by software, or may be implemented by hardware, where the hardware environment includes a network environment.
According to another aspect of the embodiment of the present application, there is also provided a server or a terminal for implementing the response method of the request.
Fig. 7 is a block diagram of a terminal according to an embodiment of the present application, and as shown in fig. 7, the terminal may include: one or more processors 701 (only one of which is shown in fig. 7), a memory 703, and a transmission means 705. as shown in fig. 7, the terminal may further include an input-output device 707.
The memory 703 may be used to store software programs and modules, such as program instructions/modules corresponding to the request response method and apparatus in the embodiment of the present application, and the processor 701 executes various functional applications and data processing by running the software programs and modules stored in the memory 703, that is, implements the request response method described above. The memory 703 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory 703 may further include memory located remotely from the processor 701, which may be connected to the terminal through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 705 is used for receiving or transmitting data via a network, and may also be used for data transmission between a processor and a memory. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 705 includes a Network adapter (NIC) that can be connected to a router via a Network cable and other Network devices to communicate with the internet or a local area Network. In one example, the transmission device 705 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
Among other things, the memory 703 is used to store application programs.
The processor 701 may call the application program stored in the memory 703 through the transmission means 705 to perform the following steps:
receiving an operation request of a target account, wherein the operation request is used for requesting to execute data operation related to a customer account, and data belonging to the same customer account are stored in a database in a centralized manner;
searching the operation authority configured for the target account from the authority configuration of the client account;
and responding to the operation request according to the operation authority of the target account.
The processor 701 is further configured to perform the following steps:
determining whether the second account has the viewing permission for the client account;
under the condition that the second account has the viewing permission for the client account, determining whether the second account has the viewing permission for the second data object;
under the condition that the second account has the viewing permission of the second data object, determining whether the second account has the editing permission of the second data object;
and allowing the second account to edit the second data object under the condition that the second account is determined to have the editing authority of the second data object.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment is not described herein again.
It can be understood by those skilled in the art that the structure shown in fig. 7 is only an illustration, and the terminal may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, and a Mobile Internet Device (MID), a PAD, etc. Fig. 7 is a diagram illustrating a structure of the electronic device. For example, the terminal may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 7, or have a different configuration than shown in FIG. 7.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
Embodiments of the present application also provide a storage medium. Alternatively, in this embodiment, the storage medium may be used to execute a program code of a request response method.
Optionally, in this embodiment, the storage medium may be located on at least one of a plurality of network devices in a network shown in the above embodiment.
Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:
receiving an operation request of a target account, wherein the operation request is used for requesting to execute data operation related to a customer account, and objects belonging to the same customer account are centrally stored in a database;
searching the operation authority configured for the target account from the authority configuration of the client account;
and responding to the operation request according to the operation authority of the target account.
Optionally, the storage medium is further arranged to store program code for performing the steps of:
determining whether the second account has a view right to the client account;
determining whether the second account has the viewing permission for the second data object or not under the condition that the second account has the viewing permission for the client account;
determining whether the second account has the editing authority on the second data object under the condition that the second account has the viewing authority on the second data object;
and allowing the second account to edit the second data object under the condition that the second account is determined to have the editing authority of the second data object.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment is not described herein again.
Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including instructions for causing one or more computer devices (which may be personal computers, servers, network devices, or the like) to execute all or part of the steps of the method described in the embodiments of the present application.
In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (14)
1. A method for responding to a request, comprising:
receiving an operation request of a target account, wherein the operation request is used for requesting to execute data operation related to a customer account, and data belonging to the same customer account are stored in a database in a centralized manner;
searching the operation authority configured for the target account from the authority configuration of the client account;
and responding to the operation request according to the operation authority of the target account.
2. The method of claim 1, wherein the target account number comprises an administrator account number, wherein,
the step of searching the operation permission configured for the target account from the permission configuration of the client account comprises the following steps: under the condition that the operation request represents a request for executing authority configuration operation, searching an operation authority configured for the target account from authority configuration of the client account, wherein the authority configuration operation is used for representing that the target account configures operation authority for a first account on a data object of the client account, and the first account is a sales account for maintaining the client account;
responding to the operation request according to the operation permission of the target account comprises the following steps: and executing the authority configuration operation under the condition that the operation authority of the target account indicates that the target account is an administrator account.
3. The method of claim 2, wherein performing the permission configuration operation comprises one of:
configuring the authority of the first account as a first operation authority, wherein the first operation authority represents that the first account is allowed to view the data object of the client account and edit the data object created by the first account;
configuring the authority of the first account as a second operation authority, wherein the second operation authority represents that the first account is allowed to view and edit the data object created by the first account;
and configuring the authority of the first account as a third operation authority, wherein the third operation authority represents that all data objects of the client account are allowed to be viewed and edited by the first account.
4. The method of claim 2, wherein performing the permission configuration operation comprises:
configuring the authority of the first account as a fourth operation authority, wherein the fourth operation authority represents that the first account is allowed to view or edit a first data object, and the first data object is a data object specified by the administrator account in all data objects of the customer account.
5. The method of claim 2, wherein performing the permission configuration operation comprises one of:
deleting the operation authority configured by the administrator account for the first account;
and changing the authority configured by the administrator account for the first account from the current operation authority to another operation authority.
6. The method of claim 1, wherein the target account number comprises a second account number that is a sales account number, wherein,
the step of searching the operation permission configured for the target account from the permission configuration of the client account comprises the following steps: under the condition that the operation request indicates that a client data operation is requested to be performed on the client account, searching an operation authority configured for the second account from authority configuration of the client account, wherein the client data operation is an operation on a second data object of the client account;
responding to the operation request according to the operation permission of the target account comprises the following steps: and executing the client data operation under the condition that the operation authority of the second account indicates that the second account is allowed to operate the second data object.
7. The method of claim 6, wherein the client data operation comprises an operation to view the second data object, and wherein, in the case that the operating permissions of the second account indicate that the second account is allowed to view the second data object, performing the client data operation comprises:
determining whether the second account has a view right to the client account;
determining whether the second account has the viewing permission for the second data object or not under the condition that the second account has the viewing permission for the client account;
and allowing the second account to view the second data object under the condition that the second account has the view permission of the second data object.
8. The method of claim 6, wherein the client data operation comprises an operation of editing the second data object, and wherein, in the case that the operation permission of the second account indicates that the second account is allowed to edit the second data object, performing the client data operation comprises:
determining whether the second account has a view right to the client account;
determining whether the second account has the viewing permission for the second data object or not under the condition that the second account has the viewing permission for the client account;
determining whether the second account has the editing authority on the second data object under the condition that the second account has the viewing authority on the second data object;
and allowing the second account to edit the second data object under the condition that the second account is determined to have the editing authority of the second data object.
9. The method of claim 6, wherein prior to receiving the operation request of the target account, the method further comprises:
receiving an adding instruction, wherein the adding instruction is used for instructing to add the second account as a sales account for maintaining the customer account;
and responding to the adding instruction, adding the second account into a sales account for maintaining the customer account, and configuring default operation authority or appointed operation authority for the second account.
10. The method of claim 6, wherein after responding to the operation request according to the operation permission of the target account, the method further comprises:
and under the condition that the second account is deleted from the sales account for maintaining the customer account, a third data object is delivered to an administrator account for maintenance, wherein the third data object is a data object created or maintained by the second account in all data objects of the customer account.
11. A request response apparatus, comprising:
the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving an operation request of a target account, the operation request is used for requesting to execute data operation related to a customer account, and data belonging to the same customer account are centrally stored in a database;
the searching unit is used for searching the operation authority configured for the target account from the authority configuration of the client account;
and the response unit is used for responding to the operation request according to the operation authority of the target account.
12. A request response system, comprising:
the intelligent terminal is logged in with a target account and used for sending an operation request, wherein the operation request is used for requesting to execute data operation related to a client account;
the server is used for searching the operation authority configured for the target account from the authority configuration of the client account under the condition of receiving the operation request, and responding to the operation request according to the operation authority of the target account;
and the data objects belonging to the same customer account are stored in the database in a centralized manner.
13. A storage medium, characterized in that the storage medium comprises a stored program, wherein the program when executed performs the method of any of the preceding claims 1 to 10.
14. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor executes the method of any of claims 1 to 10 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010976693.3A CN112131192A (en) | 2020-09-16 | 2020-09-16 | Request response method, device and system, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010976693.3A CN112131192A (en) | 2020-09-16 | 2020-09-16 | Request response method, device and system, storage medium and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112131192A true CN112131192A (en) | 2020-12-25 |
Family
ID=73845932
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010976693.3A Pending CN112131192A (en) | 2020-09-16 | 2020-09-16 | Request response method, device and system, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112131192A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101996348A (en) * | 2009-08-20 | 2011-03-30 | 上海杉达学院 | Control system and method of customer information |
| CN104202306A (en) * | 2014-08-15 | 2014-12-10 | 小米科技有限责任公司 | Method, device and system of access authentication |
| CN109510849A (en) * | 2017-09-14 | 2019-03-22 | 腾讯科技（深圳）有限公司 | The account number method for authenticating and device of cloud storage |
-
2020
- 2020-09-16 CN CN202010976693.3A patent/CN112131192A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101996348A (en) * | 2009-08-20 | 2011-03-30 | 上海杉达学院 | Control system and method of customer information |
| CN104202306A (en) * | 2014-08-15 | 2014-12-10 | 小米科技有限责任公司 | Method, device and system of access authentication |
| CN109510849A (en) * | 2017-09-14 | 2019-03-22 | 腾讯科技（深圳）有限公司 | The account number method for authenticating and device of cloud storage |
Non-Patent Citations (1)
| Title |
|---|
| FENGCHENXI007: "CRM客户关系用友TCRM使用手册", 《网络资源》, 15 April 2020 (2020-04-15), pages 1 - 8 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103020541B (en) | Personal space (data) in contrast to company space (data) | |
| CN103023993A (en) | Enterprise information system based on cloud computing | |
| CN101901315A (en) | Security isolation and monitoring management method of USB mobile storage media | |
| CN103795745A (en) | Monitoring method and monitoring system of intelligent mobile terminal | |
| CN103366122B (en) | For realizing the method and system of scan service | |
| US20120290545A1 (en) | Collection of intranet activity data | |
| CN111935110B (en) | Method and device for controlling permission of tenant to access container instance | |
| CN104704506A (en) | System control | |
| CN107302586A (en) | A kind of Webshell detection methods and device, computer installation, readable storage medium storing program for executing | |
| CN115081001A (en) | Data asset active management system, computing equipment and storage medium | |
| CN115130124A (en) | Data asset management method and data asset active management system | |
| US11019065B2 (en) | Digital consent system and associated methods | |
| CN111510428B (en) | Security resource operation and maintenance platform system and control method | |
| CN111897768A (en) | Method and device for configuring object access policy | |
| CN107294959A (en) | The method of inside and outside Network Communication, apparatus and system | |
| CN112131192A (en) | Request response method, device and system, storage medium and electronic device | |
| CN109087006B (en) | Method and device for processing power equipment monitoring information | |
| CN108965317B (en) | Network data protection system | |
| CN111178971A (en) | Advertisement putting control method and device, electronic equipment and storage medium | |
| CN115643068A (en) | Media information fusion system | |
| CN113190200B (en) | Exhibition data security protection method and device | |
| Peras et al. | Influence of GDPR on social networks used by omnichannel contact center | |
| AU2022205250A1 (en) | Systems, devices & methods for accountable identification for data protection, authority, welfare, health and economic participation including potentially multiple different sovereign identification protocols in multiple jurisdictions, enabling better management of diverse economic assets, information and environments (sovereign, personal, professional, cloud based) using advanced technologies including block chain. A framework for authenticating agreed international transactions that might not otherwise be practicable and extensions that may help pay for the infrastructure are included. | |
| CN116756711A (en) | Data processing method, device, equipment and medium | |
| Aljanabi et al. | Cloud Computing Issues, Challenges, and Needs: A Survey |
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 |