CN116485341A - Multi-account front-end feedback method and system based on shared user number - Google Patents
Multi-account front-end feedback method and system based on shared user number Download PDFInfo
- Publication number
- CN116485341A CN116485341A CN202310461716.0A CN202310461716A CN116485341A CN 116485341 A CN116485341 A CN 116485341A CN 202310461716 A CN202310461716 A CN 202310461716A CN 116485341 A CN116485341 A CN 116485341A
- Authority
- CN
- China
- Prior art keywords
- user
- account
- identity
- request
- accounts
- 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 41
- 238000004590 computer program Methods 0.000 claims description 16
- 230000008520 organization Effects 0.000 claims description 13
- 238000003860 storage Methods 0.000 claims description 10
- 238000012423 maintenance Methods 0.000 claims description 3
- 238000002372 labelling Methods 0.000 abstract 1
- 230000006870 function Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 230000006872 improvement Effects 0.000 description 3
- 239000000872 buffer Substances 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- RWSOTUBLDIXVET-UHFFFAOYSA-N Dihydrogen sulfide Chemical compound S RWSOTUBLDIXVET-UHFFFAOYSA-N 0.000 description 1
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Data Mining & Analysis (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Software Systems (AREA)
- Marketing (AREA)
- Economics (AREA)
- Computational Linguistics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a multi-account front-end feedback method and a system based on shared user numbers, which are used for establishing a unique user number corresponding to a user and an account identity and a user role identity which are matched with each other and are used for specifically labeling a specific account for calling.
Description
Technical Field
The invention relates to the technical field of business flow operation and automatic processing, in particular to a multi-account front-end feedback method and system based on shared user numbers.
Background
In the existing mechanism composition, the situation of one person sharing and counting is often caused, and a plurality of different mechanism departments may need to be respectively dealt with to work, and in the digital office process, a user is required to respectively use a plurality of different account identities to deal with the work operations of the different mechanism departments and the roles. The management process of the personnel account is substantially equivalent to copying the original primary account on the basis of the information of the personnel table, and reinserting the personnel table after only changing the corresponding limited appointed information such as the user number, the user job authority, the affiliated institution, the affiliated department and the like, thereby creating additional virtual accounts for the existing personnel account.
For more complex functional business transaction systems, which include a large number of business workflow transaction operations of various types, users often rely heavily on the front-end system to retrieve feedback work arrangements, such as work to be done, lists to be done, etc., to properly perform business workflow operations, and query-like request transactions using the system to perform business data. In the prior art, various operations of the front-end system are executed by calling corresponding information such as the user number, the user job authority, the affiliated mechanism, the affiliated department and the like matched in the personnel list based on the account identity of the user so as to determine the specific execution range of the business operation and judge the execution limit.
For the common realization problem of single user and multiple accounts, the prior art generally adopts a newly added account, adds a piece of personnel data corresponding to a personnel list of the system, and uses a brand new user number. The processing method is not essentially different from the actual newly added users, each user account is essentially an independent individual, and the business operation is completely independent. The limited improvement comprises the steps of additionally establishing a relation table among user accounts outside an original personnel table, supporting a user to acquire other related accounts in any account login state, manually selecting to switch login accounts, wherein the substantial business operation still depends on the authority and range corresponding to the login accounts, the business operation process of different accounts does not have any correlation, and in actual use, a plurality of limits and invariants for the user operation still exist.
Another improvement is still based on different user accounts (different user numbers), and aiming at specific query type requests, interfaces and menu lists (front-end feedback) which can be seen by users are displayed in a mode of front-end feedback union based on different account rights of the users; after the user sends out the operation request, the system background traverses the user account list with the authority under the corresponding menu, and integrates and outputs the query results under all the account authorities as the request response.
It can be seen that when a person has multiple accounts, the front-end feedback (e.g., service menu view) that is typically required to be obtained under different account identities is also different; in addition, in the actual business handling process of the user in the system, because the workflow handling operation is often dependent on some third-party open source workflow engine components (e.g. activity), the tool components often record user number information for distinguishing the information of the attribution person to be handled in the process, the user is inevitably caused to obtain feedback such as workflow to be handled and handled information limited by the currently logged-in unique account only in the front-end system, and only the business flow handling operation under the current account can be correspondingly operated, i.e. the scope of the business module data is limited to the currently logged-in account only. When the user needs to transact the business operation under another account, the login operation must be repeated to switch the user account, so as to ensure that the data feedback and the business operation are not confused.
It is naturally desirable for users as a single natural person to minimize the cumbersome problem of multiple different user account operations, particularly to avoid the need to repeatedly switch between different user accounts to complete different business operations, and to avoid missing the backlog under a particular account. While in the prior art, the improvement of information aggregation display is tried, although the designs can realize some global queries through traversing and aggregating the query results of the business form data, because of the dependence of third party components such as a workflow engine and the like, a plurality of specific business operation functions are directly bound by user accounts (user numbers), the function of processing business corresponding to other related accounts together under the condition of logging in a single user account cannot be realized, and the system background obviously greatly increases the system resource consumption and influences the system execution efficiency by correspondingly searching a plurality of user accounts with an indefinite number according to each request.
Obviously, how to realize that the specific contents such as various business data, work to-do and the like under all the related account identities can be checked according to the needs under the condition of not switching the user account in the actual work, and meanwhile, the business operation can still be submitted based on the corresponding correct user account identity is a technical problem to be solved continuously.
Disclosure of Invention
In order to solve the defects of the prior art, the invention provides a multi-account front-end feedback method and a system based on shared user numbers, which improve the coupling between different user accounts of the same user by sharing the same user numbers for different user accounts, solve the problem that the content of a multi-user account cannot be integrally displayed due to the fact that a third party workflow component is bound with the user numbers in the prior art, and ensure the determination of the identity of the account to which a service request operation belongs by adding corresponding account identifiers to service data.
In order to achieve the above object, the present invention adopts the technical scheme that:
the multi-account front-end feedback method based on the shared user number is characterized by comprising the following steps of:
s1, establishing a personnel list, wherein the personnel list comprises unique user numbers corresponding to specific users;
s2, judging whether a specific user has a plurality of different user accounts, and when judging that the specific user does not have the plurality of different user accounts, using a user number as an account identity and a user role identity;
s3, when judging that a specific user has a plurality of different user accounts, further judging whether the plurality of user accounts belong to the same service organization, and when judging that the plurality of user accounts belong to the same service organization, using a user number as an account identity;
s4, when judging that the plurality of user accounts do not belong to the same service organization, respectively configuring the account identity identifiers to which the corresponding service organizations belong, and establishing a first association relation label of the account identity identifiers and the corresponding user numbers;
s5, judging whether a plurality of user accounts belong to the same account identity, and when judging that the plurality of user accounts do not belong to the same account identity, using the account identity as a user role identity;
s6, when judging that a plurality of user accounts belong to the same account identity, respectively configuring the user role identities corresponding to the user accounts, and establishing a second association relation label of the user role identities and the corresponding account identity;
s7, acquiring a user request, and identifying the belonged user number according to the user request, wherein the user request comprises any one or more of a user number, an account identity and a user role identity;
s8, calling and feeding back front-end feedback content corresponding to all user accounts according to the user numbers.
Further, the method further comprises:
s9, acquiring an operation request for the front-end feedback content, identifying a user account to which the operation request corresponds to the front-end feedback content, and executing the operation request according to the identified user account.
Further, the identifying the user account to which the operation request corresponds to the front-end feedback content includes:
identifying the account identity corresponding to the front-end feedback content;
and identifying the user role identifier corresponding to the front-end feedback content.
Further, the executing the operation request according to the identified user account includes:
verifying whether the operation request meets the permission requirement according to the user role identification;
and selecting the execution range of the operation request according to the account identity.
Further, the identifying the user number according to the user request includes:
judging whether the user request comprises a user number, and when the user request comprises the user number, using the user number contained in the user request as the affiliated user number;
when the user request does not include the user number, further judging whether the user request includes the account identity, and when the user request includes the account identity, identifying the affiliated user number according to the account identity;
when the user request does not include the account identity, the user number is identified according to the user role identity.
Further, the step S8 includes:
acquiring all corresponding user accounts according to the user numbers;
and classifying and calling the corresponding front-end feedback content according to the account identity identification and/or the user role identification of the user account.
The invention also relates to a multi-account front-end feedback system based on shared user numbers, which is characterized by comprising the following steps:
the personnel list maintenance module is used for establishing a personnel list and maintaining user numbers, account identity identifiers and user role identifier data in the personnel list;
the request identification module is used for identifying the number of the user according to the user request;
the request feedback module is used for calling and feeding back front-end feedback contents corresponding to all user accounts according to the user numbers;
and the operation feedback module is used for identifying the user account to which the front-end feedback content corresponding to the operation request belongs and executing the operation request according to the identified user account.
The invention also relates to a computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when executed by a processor, implements the method described above.
The invention also relates to an electronic device, which is characterized by comprising a processor and a memory;
the memory is used for storing a user number, an account identity and a user role identity;
the processor is used for executing the method by calling the user number, the account identity and the user role identity.
The invention also relates to a computer program product comprising a computer program and/or instructions, characterized in that the computer program and/or instructions, when executed by a processor, implement the steps of the above-mentioned method.
The beneficial effects of the invention are as follows:
by adopting the multi-account front-end feedback method and system based on the shared user number, the coupling between different user accounts of the same user is improved by sharing the same user number with different user accounts, the problem that the multi-user account content cannot be integrally displayed due to the fact that a third party workflow component is bound with the user number in the prior art is solved, after a user logs in the system by any account, when a panoramic view mode is selected, page function menus which can be used under all account identities can be displayed in the system, and the authority of each page function menu can be identified and controlled in account authority, so that the system use experience of the user with the multi-account identity is greatly facilitated, and the working efficiency is improved; meanwhile, the shared user number can still be used as a unique identifier required by interaction among multiple systems, and interaction requests of the cross systems are not affected. By adding the corresponding account identifier to the service data, the front end stores the corresponding relation between each menu under the display authority possessed by the user and the current user account identity information corresponding to each menu, thereby ensuring the determination of the account identity to which the service request operation belongs.
Drawings
Fig. 1 is a flow chart of a multi-account front-end feedback method based on shared user numbers.
Fig. 2 is a schematic diagram of a multi-account front-end feedback system structure based on shared user numbers according to the present invention.
Detailed Description
For a clearer understanding of the present invention, reference will be made to the following detailed description taken in conjunction with the accompanying drawings and examples.
The first aspect of the present invention relates to a multi-account front-end feedback method based on shared user numbers, which is shown in fig. 1, and includes:
s1, establishing a personnel list, wherein the personnel list comprises unique user numbers corresponding to specific users.
In the prior art, the system personnel table stores all the registrant information in the system. Typically, the personnel list must have a user number (userNo) as the unique identification for each data record. The newly added account in the personnel list correspondingly generates a new user number, so that the problem that the user number cannot be directly corresponding to a real user is caused.
In the technical scheme of the invention, the user number peels off the unique identification function of the data record, and is used as the unique identification of the user, and the same user number is used for any newly added account of the same user.
S2, judging whether the specific user has a plurality of different user accounts, and when judging that the specific user has no plurality of different user accounts, using the user number as an account identity and a user role identity.
Typically, for users with only a single responsibility in the system, there is typically only one actual user account, so their user number can still be used as a unique identification of the corresponding data record in the user account without adding additional system burden or verification steps.
S3, when judging that a specific user has a plurality of different user accounts, further judging whether the plurality of user accounts belong to the same service organization, and when judging that the plurality of user accounts belong to the same service organization, using the user number as an account identity.
And S4, when judging that the plurality of user accounts do not belong to the same service organization, configuring the account identity identifiers corresponding to the service organizations respectively, and establishing a first association relation label of the account identity identifiers and the corresponding user numbers.
For the situation that the same user is both personally and personally counted, the fact that different responsibilities of the user can correspond to different business institutions needs to be considered, and therefore the correspondence needs to be identified. When multiple accounts belong to the same business organization, the user number can be simply used as an account identity (useraccounflag).
When judging that a plurality of different service institutions exist, the user needs to reestablish the account identity identifier to be different from the user number, and meanwhile needs to establish a corresponding relation between the account identity identifier and the user number, namely a first association relation label, so that the user can freely select the user number or the account identity identifier as login credentials according to the situation in the use process, and meanwhile, the user can ensure that all feedback information can be correspondingly acquired by any selection.
S5, judging whether a plurality of user accounts belong to the same account identity, and when judging that the plurality of user accounts do not belong to the same account identity, using the account identity as a user role identity.
Typically, a user in the system can see which menus are determined by the roles that the user has, since the visibility of the page menu is typically controlled by the various roles defined in the system. Thus, the range of page menus that a user of a system can see can be indirectly controlled by giving the user various roles. Similar to the step S3, for the application situation that multiple roles are not needed, the account identity identifier can still be selected to be directly used as the user role identifier (rollno), so that the technical effect that multiple different user accounts have the same front-end feedback is achieved, the method is particularly suitable for specific scene applications such as multi-user testing, and extra system overhead is not caused.
And S6, when judging that a plurality of user accounts belong to the same account identity, respectively configuring the corresponding user role identities for the user accounts, and establishing a second association relation label of the user role identities and the corresponding account identity.
Similar to the step S4, in the case that there are a plurality of different user roles, it is necessary to reestablish the user role identifier different from the original user number and account identifier, and establish a second association relationship label between the user role identifier and the corresponding account identifier.
S7, acquiring a user request, and identifying the belonged user number according to the user request, wherein the user request comprises any one or more of a user number, an account identity and a user role identity.
Wherein identifying the user number may preferably include sequentially performing: judging whether the user request comprises a user number, and when the user request comprises the user number, using the user number contained in the user request as the affiliated user number; when the user request does not include the user number, further judging whether the user request includes the account identity, and when the user request includes the account identity, identifying the affiliated user number according to the account identity; when the user request does not include the account identity, the user number is identified according to the user role identity.
S8, calling and feeding back front-end feedback content corresponding to all user accounts according to the user numbers. Specifically, based on acquiring all corresponding user accounts according to the user numbers, the corresponding front-end feedback content can be preferably classified and called according to the account identity and/or the user role identity of the user account.
When a user logs into the system, the system will initialize a menu of pages that the user can display and present the user with a page view accordingly. Because the menu has a corresponding relation with the roles, and the roles have a corresponding relation with the user numbers and the user account identity information. The system may calculate account identification information for the corresponding user under each menu. And synchronously returning account identification information corresponding to each menu to the front end when the system initializes the page menu displayed by the user.
S9, acquiring an operation request for the front-end feedback content, identifying a user account to which the operation request corresponds to the front-end feedback content, and executing the operation request according to the identified user account.
Specifically, identifying the user account to which the front-end feedback content corresponding to the operation request belongs includes: and identifying the account identity corresponding to the front-end feedback content and identifying the user role identity corresponding to the front-end feedback content. Then, whether the operation request meets the authority requirement is preferably verified according to the user role identification, and the execution range of the operation request is selected according to the account identity identification. Therefore, the method can accurately define the query range of the related list and the account identity applicable to each service form based on the menus cached at the front end and the account identification information to which the service form belongs.
In actual execution, when the system initializes the page menu when the user logs in, the system returns the account identity information of each menu, and the front end stores the information as a dynamic page cache of the user. And then, each time a user initiates a query class or other service requests under a certain page menu, the account identity information is transmitted to the back end as an additional parameter, and the back end defines the range of the data list query result related to the request according to the additional parameter. Each record of the queried business list contains the account identity applicable to the record. When a user clicks each business sheet to process specific data, the account identity information is transmitted to the back end as an additional parameter, and after the back end receives the information, the back end responds to correct processing according to the received account identity information.
For example, the account identity to which each specific service request belongs is USER1, and the account organization to which this account identity USER1 corresponds is a first. When the user needs to perform some business countersign operations and sends a business request to other departments of the same organization, the background can know that the department under the organization A needs to be sent. And not to the department under institution B. Thus, the account identity applicable to each service request is accurately defined, and the correct processing of the service operation is ensured.
Another aspect of the present invention further relates to a multi-account front-end feedback system based on shared user numbers, where the structure of the multi-account front-end feedback system is shown in fig. 2, and the multi-account front-end feedback system includes:
the personnel list maintenance module is used for establishing a personnel list and maintaining user numbers, account identity identifiers and user role identifier data in the personnel list;
the request identification module is used for identifying the number of the user according to the user request;
the request feedback module is used for calling and feeding back front-end feedback contents corresponding to all user accounts according to the user numbers;
and the operation feedback module is used for identifying the user account to which the front-end feedback content corresponding to the operation request belongs and executing the operation request according to the identified user account.
By using the system, the above-mentioned operation processing method can be executed and the corresponding technical effects can be achieved.
The embodiments of the present invention also provide a computer-readable storage medium capable of implementing all the steps of the method in the above embodiments, the computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements all the steps of the method in the above embodiments.
The embodiment of the invention also provides electronic equipment for executing the method, which is used as an implementation device of the method, and at least comprises a processor and a memory, wherein the memory is particularly used for storing data required by executing the method and related computer programs, such as user numbers, account identities, user role identities and the like, and all the steps of the implementation method are executed by calling the data and the programs in the memory by the processor, so that corresponding technical effects are obtained.
Preferably, the electronic device may comprise a bus architecture, and the bus may comprise any number of interconnected buses and bridges, the buses linking together various circuits, including the one or more processors and memory. The bus may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., as are well known in the art and, therefore, will not be further described herein. The bus interface provides an interface between the bus and the receiver and transmitter. The receiver and the transmitter may be the same element, i.e. a transceiver, providing a unit for communicating with various other systems over a transmission medium. The processor is responsible for managing the bus and general processing, while the memory may be used to store data used by the processor in performing operations.
Additionally, the electronic device may further include a communication module, an input unit, an audio processor, a display, a power supply, and the like. The processor (or controllers, operational controls) employed may comprise a microprocessor or other processor device and/or logic devices that receives inputs and controls the operation of the various components of the electronic device; the memory may be one or more of a buffer, a flash memory, a hard drive, a removable medium, a volatile memory, a nonvolatile memory, or other suitable means, may store the above-mentioned related data information, may further store a program for executing the related information, and the processor may execute the program stored in the memory to realize information storage or processing, etc.; the input unit is used for providing input to the processor, and can be a key or a touch input device; the power supply is used for providing power for the electronic equipment; the display is used for displaying display objects such as images and characters, and may be, for example, an LCD display. The communication module is a transmitter/receiver that transmits and receives signals via an antenna. The communication module (transmitter/receiver) is coupled to the processor to provide an input signal and to receive an output signal, which may be the same as in the case of a conventional mobile communication terminal. Based on different communication technologies, a plurality of communication modules, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, etc., may be provided in the same electronic device. The communication module (transmitter/receiver) is also coupled to the speaker and microphone via the audio processor to provide audio output via the speaker and to receive audio input from the microphone to implement the usual telecommunications functions. The audio processor may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor is also coupled to the central processor so that sound can be recorded on the host through the microphone and sound stored on the host can be played through the speaker.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a system for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
The foregoing is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions easily contemplated by those skilled in the art within the scope of the present invention should be included in the scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.
Claims (10)
1. The multi-account front-end feedback method based on the shared user number is characterized by comprising the following steps of:
s1, establishing a personnel list, wherein the personnel list comprises unique user numbers corresponding to specific users;
s2, judging whether a specific user has a plurality of different user accounts, and when judging that the specific user does not have the plurality of different user accounts, using a user number as an account identity and a user role identity;
s3, when judging that a specific user has a plurality of different user accounts, further judging whether the plurality of user accounts belong to the same service organization, and when judging that the plurality of user accounts belong to the same service organization, using a user number as an account identity;
s4, when judging that the plurality of user accounts do not belong to the same service organization, respectively configuring the account identity identifiers to which the corresponding service organizations belong, and establishing a first association relation label of the account identity identifiers and the corresponding user numbers;
s5, judging whether a plurality of user accounts belong to the same account identity, and when judging that the plurality of user accounts do not belong to the same account identity, using the account identity as a user role identity;
s6, when judging that a plurality of user accounts belong to the same account identity, respectively configuring the user role identities corresponding to the user accounts, and establishing a second association relation label of the user role identities and the corresponding account identity;
s7, acquiring a user request, and identifying the belonged user number according to the user request, wherein the user request comprises any one or more of a user number, an account identity and a user role identity;
s8, calling and feeding back front-end feedback content corresponding to all user accounts according to the user numbers.
2. The method of claim 1, wherein the method further comprises:
s9, acquiring an operation request for the front-end feedback content, identifying a user account to which the operation request corresponds to the front-end feedback content, and executing the operation request according to the identified user account.
3. The method of claim 2, wherein the identifying the user account to which the operation request corresponds to the front-end feedback content belongs comprises:
identifying the account identity corresponding to the front-end feedback content;
and identifying the user role identifier corresponding to the front-end feedback content.
4. The method of claim 3, wherein the performing the operation request in accordance with the identified user account comprises:
verifying whether the operation request meets the permission requirement according to the user role identification;
and selecting the execution range of the operation request according to the account identity.
5. The method of claim 1, wherein said identifying the belonging user number in accordance with the user request comprises:
judging whether the user request comprises a user number, and when the user request comprises the user number, using the user number contained in the user request as the affiliated user number;
when the user request does not include the user number, further judging whether the user request includes the account identity, and when the user request includes the account identity, identifying the affiliated user number according to the account identity;
when the user request does not include the account identity, the user number is identified according to the user role identity.
6. The method according to claim 1, wherein the step S8 includes:
acquiring all corresponding user accounts according to the user numbers;
and classifying and calling the corresponding front-end feedback content according to the account identity identification and/or the user role identification of the user account.
7. A multi-account front-end feedback system based on shared user numbering, comprising:
the personnel list maintenance module is used for establishing a personnel list and maintaining user numbers, account identity identifiers and user role identifier data in the personnel list;
the request identification module is used for identifying the number of the user according to the user request;
the request feedback module is used for calling and feeding back front-end feedback contents corresponding to all user accounts according to the user numbers;
and the operation feedback module is used for identifying the user account to which the front-end feedback content corresponding to the operation request belongs and executing the operation request according to the identified user account.
8. A computer readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when executed by a processor, implements the method of any of claims 1 to 6.
9. An electronic device comprising a processor and a memory;
the memory is used for storing a user number, an account identity and a user role identity;
the processor is configured to perform the method of any one of claims 1 to 6 by invoking a user number, an account identity and a user role identity.
10. A computer program product comprising a computer program and/or instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310461716.0A CN116485341A (en) | 2023-04-26 | 2023-04-26 | Multi-account front-end feedback method and system based on shared user number |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310461716.0A CN116485341A (en) | 2023-04-26 | 2023-04-26 | Multi-account front-end feedback method and system based on shared user number |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116485341A true CN116485341A (en) | 2023-07-25 |
Family
ID=87219052
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310461716.0A Pending CN116485341A (en) | 2023-04-26 | 2023-04-26 | Multi-account front-end feedback method and system based on shared user number |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116485341A (en) |
-
2023
- 2023-04-26 CN CN202310461716.0A patent/CN116485341A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107798038B (en) | Data response method and data response equipment | |
| US8229962B1 (en) | Location-aware task management systems and methods | |
| CN109447820B (en) | Data processing method, device, computer equipment and storage medium | |
| US20200286100A1 (en) | Payment complaint method, device, server and readable storage medium | |
| CN110163739B (en) | Payment complaint method, device, server and readable storage medium | |
| CN105207881B (en) | A kind of message method and equipment | |
| CN110659206A (en) | Simulation architecture establishing method, device, medium and electronic equipment based on microservice | |
| US20170132001A1 (en) | Code based configuration of mobile devices | |
| CN110647827A (en) | Comment information processing method and device, electronic equipment and storage medium | |
| CN112150030A (en) | Account management method based on multiple units and multiple identities, terminal equipment and storage medium | |
| CN115391356A (en) | Data processing method, device, equipment, medium and computer program product | |
| CN110706117A (en) | Business processing method, device, computer device and storage medium | |
| KR101614890B1 (en) | Method of creating multi tenancy history, server performing the same and storage media storing the same | |
| CN110336872B (en) | Method, device and system for acquiring third-party data | |
| CN106569408B (en) | Processing system, method and device for personalized information of intelligent equipment | |
| CN110866229B (en) | Multi-platform account authority unified management method and system | |
| CN116485341A (en) | Multi-account front-end feedback method and system based on shared user number | |
| CN105512208A (en) | Information issuing method, device and system | |
| CN106533718A (en) | Data processing method and device | |
| CN112260933B (en) | Communication method, communication device, electronic equipment and medium | |
| WO2018200167A1 (en) | Managing asynchronous analytics operation based on communication exchange | |
| CN111652580B (en) | Method and device for processing data of nodes | |
| CN112019364B (en) | Information management method and device | |
| US20210349903A1 (en) | Row secure table plan generation | |
| CN114205329A (en) | Equipment coding method and device |
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 |