Team data interaction method, device, equipment and storage medium

Abstract

The present invention relates to the field of team management technology, and in particular to a team data interaction method, device, equipment and storage medium. The method includes: when a target team creation request is received, obtaining first requester information corresponding to the target team creation request, verifying the first requester information, and responding to the target team creation request according to the verification result; when the verification result is passed, presenting a team creation interface corresponding to the target team, obtaining and storing the team information filled in the team creation interface, and creating the target team; when any one of a data viewing request, a member change request, a team change request and a permission change request is received, responding according to the corresponding requester information and the team work mode or the corresponding request type; in the method disclosed in the present application, the creation of the target team can be realized according to the needs of merchant customers, which facilitates team management, data viewing and data sharing, and improves the user experience of merchant customers.

Description

Technical Field

[0001] The present invention relates to the field of team management technology, and in particular to a team data interaction method, device, equipment and storage medium. Background Art

[0002] Merchant customers of a certain scale generally include multiple employees. Since data between employees cannot be shared, when arranging orders and invoice processing for employees, the employees need to open an electronic waybill account before they can conduct work inquiries. For employees who are not familiar with mobile phone operations, they cannot respond to work in a timely manner, which affects work progress and reduces work efficiency. In addition, due to the large number of electronic waybill accounts, there is a problem of difficult management. When merchant customers need to view the work data of each employee, there are problems of difficulty in viewing and low viewing efficiency.

[0003] It can be seen that the existing technology still needs to be improved and enhanced. Summary of the Invention

[0004] In order to overcome the shortcomings of the existing technology, the purpose of the present invention is to provide a team data interaction method, device, equipment and storage medium, which can realize the creation of teams according to the needs of merchant customers, facilitate team management, data sharing and data viewing, and improve the user experience.

[0005] A first aspect of the present invention provides a team data interaction method, including: when a target team creation request is received, obtaining first requester information corresponding to the target team creation request, verifying the first requester information, and responding to the target team creation request according to the verification result, wherein the verification result includes pass and fail; when the verification result is pass, presenting a team creation interface corresponding to the target team, obtaining and storing the team information filled in the team creation interface, and creating the target team; when a data viewing request is received, obtaining second requester information corresponding to the data viewing request and the working mode of the target team, and responding to the data viewing request according to the second requester information and the working mode of the target team; when a member change request is received, obtaining third requester information corresponding to the member change request and the first request type, and responding to the member change request according to the third requester information and the first request type; when a team change request is received, obtaining fourth requester information corresponding to the team change request and the second request type, and responding to the team change request according to the fourth requester information and the second request type; when a permission change request is received, obtaining fifth requester information corresponding to the permission change request and the permission change content, and responding to the permission change request according to the fifth requester information and the permission change content.

[0006] Optionally, in a first embodiment of the first aspect of the present invention, when a request to create a new target team is received, the first requester information corresponding to the request to create a new target team is obtained, the first requester information is verified, and the request to create a new target team is responded to according to the verification result. The verification result includes pass and fail, specifically including: when a request to create a new target team is received, the first requester information corresponding to the request to create a new target team is obtained, and the first requester information includes a user face order account; when the content of the user face order account is empty, the verification fails, and a verification failure instruction is returned; when the content of the user face order account is not empty, it is determined whether the user face order account has an established team. If so, the verification fails, and the team interface of the established team is returned.

[0007] Optionally, in a second embodiment of the first aspect of the present invention, when the verification result is passed, the team creation interface corresponding to the target team is presented, the team information filled in the team creation interface is obtained and stored, and the target team is created, specifically including: when the verification result is passed, the team creation interface corresponding to the target team is presented, the team creation interface is used to input team member information and change team members, and the team creation interface includes a member submission button; when the submit button is clicked, the team information filled in the team creation interface is obtained, and the team information is stored in a pre-selected database, and the pre-selected database includes multiple data channels; according to the first requester information and the obtained team information, the target team is created.

[0008] Optionally, in a third embodiment of the first aspect of the present invention, when a data viewing request is received, the second requester information corresponding to the data viewing request and the working mode of the target team are obtained, and the data viewing request is responded to according to the second requester information and the working mode of the target team, specifically including: when a data viewing request is received, the corresponding second requester information is obtained, the second requester information includes the requester identity, and the requester identity includes the team leader and team member; when the requester identity is a team member, the team's working mode is obtained, and the team's working mode includes team mode and personal mode; when the team's working mode is personal mode, a viewing failure instruction is returned; when the team's working mode is team mode, the request content of the data viewing request is obtained, and the request viewing result is fed back according to the request content.

[0009] Optionally, in a fourth embodiment of the first aspect of the present invention, when a member change request is received, third requester information and the first request type corresponding to the member change request are obtained, and the member change request is responded to according to the third requester information and the first request type, specifically including: when a member change request is received, the corresponding first request type is obtained, and the first request type includes a request to join the group instruction and an internal change instruction; when the first request type is a request to join the group instruction, review information is generated according to the joining request information; when the first request type is an internal change instruction, the corresponding third requester information is obtained, and the third requester information includes the requester identity, and the requester identity includes the group leader and the group member; when the requester identity is the group leader, the member change content corresponding to the internal change instruction is obtained, and the member information in the team information is changed according to the member change content.

[0010] Optionally, in a fifth embodiment of the first aspect of the present invention, when a team change request is received, fourth requester information and a second request type corresponding to the team change request are obtained, and the team change request is responded to according to the fourth requester information and the second request type, specifically including: when a team change request is received, the corresponding fourth requester information is obtained, the fourth requester information includes the requester identity, and the requester identity includes the team leader and team members; when the requester identity is the team leader, the corresponding second request type is obtained, and the second request type includes a name modification instruction and a team disbanding instruction; when the second request type is a name modification instruction, a modification pop-up window is generated, and the modification pop-up window includes a team name input box; when the second request type is a team disbanding instruction, an information storage path is obtained, and the team information is stored in the obtained information storage path.

[0011] Optionally, in a sixth embodiment of the first aspect of the present invention, when a permission change request is received, the fifth requester information corresponding to the permission change request and the permission change content are obtained, and the permission change request is responded to according to the fifth requester information and the permission change content, specifically including: when a permission change request is received, the corresponding fifth requester information is obtained, the fifth requester information includes the requester identity, and the requester identity includes the team leader and the team member; when the requester identity is the team leader, the permission change content corresponding to the permission change instruction is obtained to modify the permissions of the team members in the target team, and the permission change content includes the team member information and the permission change information; when the requester identity is a team member, a permission change request failure instruction is returned.

[0012] The second aspect of the present invention provides a team data interaction device, including: a first request module, which is used to obtain the first requester information corresponding to the target team creation request when receiving the target team creation request, verify the first requester information, and respond to the target team creation request according to the verification result, and the verification result includes pass and fail; a creation module, which is used to present the team creation interface corresponding to the target team when the verification result is pass, obtain and store the team information filled in the team creation interface, and create the target team; a second request module, which is used to obtain the second requester information corresponding to the data viewing request and the working mode of the target team when receiving the data viewing request, and respond to the target team creation request according to the second requester information. and the working mode of the target team to respond to the data viewing request; the third request module is used to obtain the third requester information and the first request type corresponding to the member change request when a member change request is received, and respond to the member change request according to the third requester information and the first request type; the fourth request module is used to obtain the fourth requester information and the second request type corresponding to the team change request when a team change request is received, and respond to the team change request according to the fourth requester information and the second request type; the fifth request module is used to obtain the fifth requester information and the permission change content corresponding to the permission change request when a permission change request is received, and respond to the permission change request according to the fifth requester information and the permission change content.

[0013] Optionally, in a first implementation method of the second aspect of the present invention, the first request module includes: a first request unit, used to obtain first requester information corresponding to the target team creation request when receiving the target team creation request, the first requester information including the user face order account; a first verification unit, used to fail the verification when the content of the user face order account is empty, and return a verification failure instruction; a second verification unit, used to determine whether the user face order account has an established team when the content of the user face order account is not empty, and if so, fail the verification and return the team interface of the established team.

[0014] Optionally, in a second implementation method of the second aspect of the present invention, the creation module includes: a presentation unit, which is used to present a team creation interface corresponding to the target team when the verification result is passed, and the team creation interface is used to input team member information and change team members, and the team creation interface includes a member submission button; a storage unit, which is used to obtain the team information filled in the team creation interface when the submit button is clicked, and store the team information in a pre-selected database, and the pre-selected database includes multiple data channels; a creation unit, which is used to create the target team based on the first requester information and the obtained team information.

[0015] Optionally, in a third implementation of the second aspect of the present invention, the second request module includes: a first acquisition unit, used to obtain the corresponding second requester information when receiving a data viewing request, the second requester information including the requester identity, the requester identity including the team leader and the team member; a second acquisition unit, used to obtain the team's working mode when the requester identity is a team member, the team's working mode including the team mode and the individual mode; a second request unit, used to return a viewing failure instruction when the team's working mode is the individual mode; a third request unit, used to obtain the request content of the data viewing request when the team's working mode is the team mode, and to feedback the request viewing result according to the request content.

[0016] Optionally, in a fourth implementation of the second aspect of the present invention, the third request module includes: a third acquisition unit, for acquiring the corresponding first request type when a member change request is received, the first request type including a request to join the group and an internal change instruction; an audit unit, for generating audit information based on the group joining request information when the first request type is a request to join the group; a fourth acquisition unit, for acquiring the corresponding third requester information when the first request type is an internal change instruction, the third requester information including the requester identity, the requester identity including the group leader and the group member; a change unit, for acquiring the member change content corresponding to the internal change instruction when the requester identity is the group leader, and changing the member information in the team information according to the member change content.

[0017] Optionally, in a fifth implementation of the second aspect of the present invention, the fourth request module includes: a fifth acquisition unit, for acquiring corresponding fourth requester information when a team change request is received, the fourth requester information including the requester identity, and the requester identity including the team leader and team member; a sixth acquisition unit, for acquiring the corresponding second request type when the requester identity is the team leader, the second request type including a name modification instruction and a team disbanding instruction; a fourth request unit, for generating a modification pop-up window when the second request type is a name modification instruction, the modification pop-up window including a team name input box; a fifth request unit, for acquiring an information storage path when the second request type is a team disbanding instruction, and storing the team information in the acquired information storage path.

[0018] Optionally, in a sixth implementation of the second aspect of the present invention, the fifth request module further includes: a seventh acquisition unit, for acquiring corresponding fifth requester information when receiving a permission change request, the fifth requester information including the requester identity, the requester identity including the team leader and the team member; a sixth request unit, for acquiring permission change content corresponding to the permission change instruction when the requester identity is the team leader, so as to modify the permissions of the team members in the target team, the permission change content including the team member information and permission change information; a seventh request unit, for returning a permission change request failure instruction when the requester identity is a team member.

[0019] The third aspect of the present invention provides a team data interaction device, which includes: a memory and at least one processor, wherein the memory stores instructions; at least one processor calls the instructions in the memory to enable the team data interaction device to execute each step of the team data interaction method described in any one of the above items.

[0020] A fourth aspect of the present invention provides a computer-readable storage medium having instructions stored thereon, which, when executed by a processor, implement the various steps of any of the above-mentioned team data interaction methods.

[0021] In the technical solution of the present invention, when a request for the creation of a target team is received, the first requester information corresponding to the request for the creation of the target team is obtained, the first requester information is verified and processed, and the request for the creation of the target team is responded to according to the verification result; when the verification result is passed, the team creation interface corresponding to the target team is presented, the team information filled in the team creation interface is obtained and stored, and the target team is created; when any request among data viewing request, member change request, team change request and authority change request is received, a response is made according to the corresponding requester information and the team work mode or the corresponding request type; in the method disclosed in the present application, the creation of the target team can be realized according to the needs of merchant customers, which facilitates team management, data viewing and data sharing, and improves the user experience of merchant customers. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 A first flow chart of the team data interaction method provided by an embodiment of the present invention;

[0023] Figure 2 A second flow chart of the team data interaction method provided by an embodiment of the present invention;

[0024] Figure 3 A third flow chart of the team data interaction method provided in an embodiment of the present invention;

[0025] Figure 4A fourth flow chart of the team data interaction method provided by an embodiment of the present invention;

[0026] Figure 5 A fifth flow chart of the team data interaction method provided in an embodiment of the present invention;

[0027] Figure 6 A sixth flow chart of the team data interaction method provided by an embodiment of the present invention;

[0028] Figure 7 A seventh flow chart of the team data interaction method provided in an embodiment of the present invention;

[0029] Figure 8 A schematic diagram of the structure of a team data interaction device provided by an embodiment of the present invention;

[0030] Figure 9 Another structural diagram of the team data interaction device provided by an embodiment of the present invention;

[0031] Figure 10 A schematic diagram of the structure of a team data interaction device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0032] The present invention provides a team data interaction method, device, equipment and storage medium. In the technical solution disclosed in the present invention, when a target team creation request is received, the first requester information corresponding to the target team creation request is obtained, the first requester information is verified and processed, and the target team creation request is responded to according to the verification result; when the verification result is passed, the team creation interface corresponding to the target team is presented, the team information filled in the team creation interface is obtained and stored, and the target team is created; when any request among data viewing request, member change request, team change request and authority change request is received, a response is made according to the corresponding requester information and the team work mode or the corresponding request type; in the method disclosed in the present application, the creation of the target team can be realized according to the needs of merchant customers, which facilitates team management, data viewing and data sharing, and improves the user experience of merchant customers.

[0033] The terms "first," "second," "third," "fourth," and the like (if any) in the description and claims of the present invention and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" or "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or apparatus.

[0034] For ease of understanding, the specific process of the embodiment of the present invention is described below. Figure 1 An embodiment of the team data interaction method in an embodiment of the present invention includes:

[0035] 101. When receiving a target team creation request, obtain first requester information corresponding to the target team creation request, verify the first requester information, and respond to the target team creation request based on the verification result, wherein the verification result includes pass or fail.

[0036] In this embodiment, the first requester information is the information of the initiator of the target team creation request, that is, when a merchant customer needs to create a team, he needs to fill in personal information first to verify the first requester information and confirm whether the merchant customer can create a new target team; the first requester information can be entered through a first filling pop-up window, and the first filling pop-up window includes one or more option boxes or one or more text input boxes.

[0037] 102. When the verification result is passed, presenting a team creation interface corresponding to the target team, obtaining and storing the team information filled in the team creation interface, and creating the target team;

[0038] In this embodiment, the team creation interface presented is used to realize the addition of new members, the filling of member information and the allocation of member permissions. An invitation button is provided in the team creation interface, and merchant users can add new members through the invitation button; when the invitation button is clicked, a second filling pop-up window is generated for filling in the invited member information. The second filling pop-up window includes one or more option boxes or one or more text input boxes. The member information includes at least the member name, member face sheet account number and member data; after the member information is entered into the team creation interface, a check box is set in front of each member name to facilitate merchant customers to adjust the member's permissions.

[0039] 103. When a data viewing request is received, obtain the second requester information and the work mode of the target team corresponding to the data viewing request, and respond to the data viewing request according to the second requester information and the work mode of the target team;

[0040] In this embodiment, the second requester information is the information of the initiator of the data viewing request. The team leader and team members can click on the team member data of a certain team member in the team interface of the target team to send a data viewing request.

[0041] 104. When a member change request is received, obtain third requester information and the first request type corresponding to the member change request, and respond to the member change request according to the third requester information and the first request type;

[0042] In this embodiment, the third requester information is the information of the initiator of the member change request. The team interface of the target team is provided with an invite button and a delete button. The merchant user, that is, the team leader, can invite and delete team members in the team interface of the target team to realize the change of existing team members, that is, to realize the sending of member change requests; external members can also send applications to join the team, that is, send member change requests.

[0043] 105. When a team change request is received, obtain fourth requester information and a second request type corresponding to the team change request, and respond to the team change request according to the fourth requester information and the second request type;

[0044] In this embodiment, the fourth requester information is the information of the initiator of the team change request. The team interface of the target team is provided with one or more team change buttons related to the team change request. When the team change button is clicked, the team change request is sent.

[0045] 106. When receiving a permission change request, obtain the fifth requester information and permission change content corresponding to the permission change request, and respond to the permission change request based on the fifth requester information and permission change content;

[0046] In this embodiment, in the team interface of the target team, a check box is set in front of each team member's name. When the merchant user clicks the check box, it indicates that a permission change request is sent.

[0047] The present application discloses a team data interaction method, which comprises the following steps: when a request for creating a new target team is received, first requester information corresponding to the request for creating a new target team is obtained, the first requester information is verified, and the request for creating a new target team is responded to according to the verification result; when the verification result is passed, a team creation interface corresponding to the target team is presented, the team information filled in the team creation interface is obtained and stored, and the target team is created; when any of a data viewing request, a member change request, a team change request, and a permission change request is received, a response is made according to the corresponding requester information and the team work mode or the corresponding request type; in the method disclosed in the present application, the creation of a target team can be realized according to the needs of merchant customers, which facilitates merchant customers to manage teams and view data, and improves the user experience of merchant customers; data sharing can be realized between members of the team according to corresponding permissions, which can improve work efficiency and ensure that all tasks are carried out on time.

[0048] See also Figure 2 The second embodiment of the team data interaction method in the embodiment of the present invention includes:

[0049] 201. When a target team creation request is received, obtain first requester information corresponding to the target team creation request, where the first requester information includes a user face order account number;

[0050] In this embodiment, the first requester information also includes the requester's personal information and merchant information, the personal information includes at least the name and contact number, and the merchant information includes at least the store name; the first requester information defaults to the group leader information, that is, the initiator of the new request for the target team is the group leader by default, and the group leader can also select the corresponding manager as the group leader in the team interface of the target team.

[0051] 202. When the content of the user's face order account is empty, the verification fails and a verification failure instruction is returned;

[0052] In this embodiment, for the initiator who does not have a user face order account, creating a new target team is not supported.

[0053] 203. When the content of the user's face order account is not empty, determine whether the user's face order account has an established team. If so, the verification fails and returns to the team interface of the established team.

[0054] In this embodiment, when the first requester information includes a user face order account, the user face order account is input into a pre-established team list for judgment processing. The team list includes multiple established team information, and each established team information corresponds to a user face order account; it is judged whether the user face order account of any team in the team list is consistent with the user face order account in the first requester information. If there is a consistency, the team meeting of the established team is directly displayed. If not, the team creation interface corresponding to the target team is displayed.

[0055] See also Figure 3 A third embodiment of the team data interaction method in the embodiment of the present invention includes:

[0056] 301. When the verification result is passed, a team creation interface corresponding to the target team is presented. The team creation interface is used to input team member information and change team members. The team creation interface includes a member submission button.

[0057] In this embodiment, an invitation button is provided in the team creation interface, and merchant users can use the invitation button to add new members; when the invitation button is clicked, a second filling pop-up window is generated for filling in the information of the invited members. After completing the filling of the member information of a member, the member information of the member is displayed in the team creation interface, and a check box is set in front of each member's name to facilitate merchant customers to adjust the permissions of the members; a member submission button is provided at the bottom of the team creation interface. After completing the addition of new members, click the member submission button to create the target team.

[0058] 302. When the submit button is clicked, the team information entered in the team creation interface is obtained and stored in a pre-selected database, wherein the pre-selected database includes multiple data channels;

[0059] In this embodiment, the pre-selected database is the Redis database. Redis is completely open source, complies with the BSD protocol, and is a high-performance key-value database. Redis and other key-value cache products have the following three characteristics: First, Redis supports data persistence, and can save data in memory to disk, which can be loaded again for use when restarted; second, Redis not only supports simple key-value type data, but also provides storage of data structures such as list, set, zset, and hash; third, Redis supports data backup, that is, data backup in master-slave mode; data viewing and sharing are achieved through multiple data channels of the Redis database.

[0060] 303. Create the target team according to the first requester information and the obtained team information;

[0061] In this embodiment, the first requester information is the group leader information, the team information includes group member information corresponding to multiple members, the group member information includes group member personal information, group member face sheet account number and group member authority information, and the group member personal information includes group member name and group member contact number.

[0062] See also Figure 4 The fourth embodiment of the team data interaction method in the embodiment of the present invention includes:

[0063] 401. When a data viewing request is received, obtain the corresponding second requester information, where the second requester information includes the requester identity, which includes the group leader and group members.

[0064] 402. When the requester is a team member, obtain the team's work mode, which includes a team mode and an individual mode.

[0065] 403. When the team's working mode is individual mode, return to view the failed instructions;

[0066] In this embodiment, the viewing failure instruction is a viewing failure pop-up window, and the viewing failure pop-up window displays a preset text, and the preset text is "the working mode is personal mode, and data sharing is not supported."

[0067] 404. When the team's working mode is team mode, obtain the request content of the data viewing request and feedback the request viewing result based on the request content;

[0068] In this embodiment, the request content includes the request object and the data requested to be viewed. Each member information corresponds to a view button, and the request object is the member information corresponding to the view button clicked by the initiator of the data viewing request; when the view button is clicked, a view pop-up window is generated, and the view pop-up window includes multiple view options, and the view options include at least order quantity, order quantity, order work arrangement and order work arrangement. The view option selected by the initiator of the data viewing request is the data requested to be viewed.

[0069] In this embodiment, when the team's working mode is team mode, team members with viewing permissions are allowed to view the order data of other team members, and the order data includes order quantity, order processing quantity, order placement work schedule and order processing work schedule; when the team's working mode is individual mode, regardless of whether the team member has viewing permissions, he cannot perform the viewing work, that is, in individual mode, data is not shared, and only the team leader can view the order data of each team member.

[0070] See also Figure 5 The fifth embodiment of the team data interaction method in the embodiment of the present invention includes:

[0071] 501. When a member change request is received, obtain a corresponding first request type, where the first request type includes a group joining request instruction and an internal change instruction;

[0072] 502. When the first request type is a request to join a group, generate review information according to the group joining request information;

[0073] In this embodiment, the generated review information is fed back to the message management system of the team leader, who reviews it. If the review is approved, the member information included in the team joining request information is filled in the team interface of the target team.

[0074] 503. When the first request type is an internal change instruction, obtain corresponding third requester information, where the third requester information includes the requester identity, including the group leader and group members.

[0075] In this embodiment, when the identity of the requester in the third requester information is a team member, an internal change request failure instruction is returned. The internal change request failure instruction is an internal change request failure pop-up window. The internal change request failure pop-up window displays a preset text, and the preset text is "Does not have operation authority", that is, only the team leader has the authority to change internal team members.

[0076] 504. When the requester is a team leader, obtain the member change content corresponding to the internal change instruction, and change the team member information in the team information according to the member change content;

[0077] In this embodiment, the internal change instruction can be an internal addition instruction and an internal deletion instruction. When the invite button in the team interface of the target team is clicked, it indicates that the internal addition instruction is triggered, and the filled-in new member information is displayed in the team interface to realize the addition of internal members; when the delete button in the team interface of the target team is clicked, a check box is generated at the end of each member information. When the check box is clicked, it indicates that the member information corresponding to the check box is to be deleted. When the delete button is clicked again, all clicked check boxes are obtained to realize the deletion of internal members.

[0078] See also Figure 6 The sixth embodiment of the team data interaction method in the embodiment of the present invention includes:

[0079] 601. When a team change request is received, obtain corresponding fourth requester information, where the fourth requester information includes the requester identity, which includes the team leader and team members.

[0080] In this embodiment, when the requester identity in the fourth requester information is a team member, a team change request failure instruction is returned. The team change request failure instruction is a team change request failure pop-up window. The team change request failure pop-up window displays a preset text, and the preset text is "Does not have operation authority", that is, only the team leader has the authority to change the team.

[0081] 602. When the requester is a team leader, obtain a corresponding second request type, which includes a name modification instruction and a team disbanding instruction;

[0082] 603. When the second request type is a name modification instruction, a modification pop-up window is generated, wherein the modification pop-up window includes a team name input box;

[0083] In this embodiment, a setting button is provided in the team interface of the target team. When the setting button is clicked, a modification pop-up window is generated; the text content in the team name input box is obtained to modify the team name.

[0084] 604. When the second request type is a team disbanding instruction, obtain an information storage path, and store the team information in the obtained information storage path;

[0085] In this embodiment, a disband button is provided in the team interface of the target team. When the disband button is clicked, the team disband instruction is fed back; the information storage path is a personal database pre-set by the team leader. When the team is disbanded, the order data of each member during the team period is stored in the personal database to achieve data retention.

[0086] See also Figure 7 The seventh embodiment of the team data interaction method in the embodiment of the present invention includes:

[0087] 701. When receiving a permission change request, obtain corresponding fifth requester information, where the fifth requester information includes the requester identity, including the identity of the group leader and group member.

[0088] 702. When the requester is a team leader, obtain permission change content corresponding to the permission change instruction to modify the permissions of team members in the target team. The permission change content includes team member information and permission change information.

[0089] In this embodiment, in the team interface of the target team, a check box is set at the front end of each member's information. The check box is not checked by default, and each member in the team has the authority to view the order data of others, thereby realizing comprehensive data sharing; when the team leader clicks the check box at the front end of a member's information, the member's data viewing permission is closed. After closing, the member can only see his or her own order data and cannot see the order data of others, thereby realizing the change of member permissions; the member information is the member information corresponding to the checked check box, and the permission change information is that the check box is in a checked state.

[0090] 703. When the requester is a member of the group, the permission change request fails.

[0091] In this embodiment, the permission change request failure instruction is a permission change request failure pop-up window, and the permission change request failure pop-up window displays a preset text, which is "no operation authority", that is, only the team leader has the authority to change the permissions of team members.

[0092] The team data interaction method according to the embodiment of the present invention is described above. The team data interaction device according to the embodiment of the present invention is described below. Figure 8 , an embodiment of the team data interaction device in an embodiment of the present invention includes: a first request module 801, which is used to obtain the first requester information corresponding to the target team creation request when a target team creation request is received, verify the first requester information, and respond to the target team creation request according to the verification result, and the verification result includes pass and fail; a creation module 802 is used to present the team creation interface corresponding to the target team when the verification result is pass, obtain and store the team information filled in the team creation interface, and create the target team; a second request module 803 is used to obtain the second requester information corresponding to the data viewing request and the working mode of the target team when a data viewing request is received, and respond to the target team creation request according to the second requester information. and the working mode of the target team responds to the data viewing request; the third request module 804 is used to obtain the third requester information and the first request type corresponding to the member change request when a member change request is received, and respond to the member change request according to the third requester information and the first request type; the fourth request module 805 is used to obtain the fourth requester information and the second request type corresponding to the team change request when a team change request is received, and respond to the team change request according to the fourth requester information and the second request type; the fifth request module 806 is used to obtain the fifth requester information and the permission change content corresponding to the permission change request when a permission change request is received, and respond to the permission change request according to the fifth requester information and the permission change content.

[0093] See also Figure 9Another embodiment of the team data interaction device in this embodiment includes:

[0094] The first request module 801 is configured to, upon receiving a target team creation request, obtain first requester information corresponding to the target team creation request, verify the first requester information, and respond to the target team creation request based on the verification result, which may include a pass or fail result.

[0095] The creation module 802 is used to present a team creation interface corresponding to the target team when the verification result is passed, obtain and store the team information filled in the team creation interface, and create the target team;

[0096] The second request module 803 is configured to, upon receiving a data viewing request, obtain information about a second requester and a target team's work mode corresponding to the data viewing request, and respond to the data viewing request according to the information about the second requester and the target team's work mode;

[0097] The third request module 804 is configured to, upon receiving a member change request, obtain third requester information and the first request type corresponding to the member change request, and respond to the member change request according to the third requester information and the first request type;

[0098] The fourth request module 805 is configured to, upon receiving a team change request, obtain fourth requester information and a second request type corresponding to the team change request, and respond to the team change request according to the fourth requester information and the second request type;

[0099] The fifth request module 806 is configured to, upon receiving a permission change request, obtain information about a fifth requester and permission change content corresponding to the permission change request, and respond to the permission change request based on the information about the fifth requester and permission change content;

[0100] In this embodiment, the first request module 801 includes: a first request unit 8011, which is used to obtain the first requester information corresponding to the target team creation request when a target team creation request is received, and the first requester information includes the user face order account; a first verification unit 8012, which is used to fail the verification when the content of the user face order account is empty, and return a verification failure instruction; a second verification unit 8013, which is used to determine whether the user face order account has an established team when the content of the user face order account is not empty, and if so, fail the verification and return to the team interface of the established team.

[0101] In this embodiment, the creation module 802 includes: a presentation unit 8021, which is used to present the team creation interface corresponding to the target team when the verification result is passed, and the team creation interface is used to input team member information and change team members, and the team creation interface includes a member submission button; a storage unit 8022, which is used to obtain the team information filled in the team creation interface when the submit button is clicked, and store the team information in a pre-selected database, and the pre-selected database includes multiple data channels; a creation unit 8023, which is used to create the target team based on the first requester information and the obtained team information.

[0102] In this embodiment, the second request module 803 includes: a first acquisition unit 8031, which is used to obtain the corresponding second requester information when a data viewing request is received, and the second requester information includes the requester identity, and the requester identity includes the team leader and the team member; a second acquisition unit 8032, which is used to obtain the team's working mode when the requester identity is a team member, and the team's working mode includes the team mode and the individual mode; a second request unit 8033, which is used to return a viewing failure instruction when the team's working mode is the individual mode; a third request unit 8034, which is used to obtain the request content of the data viewing request when the team's working mode is the team mode, and to feedback the request viewing result according to the request content.

[0103] In this embodiment, the third request module 804 includes: a third acquisition unit 8041, which is used to obtain the corresponding first request type when a member change request is received, and the first request type includes a request to join the group and an internal change instruction; an audit unit 8042, which is used to generate audit information based on the group joining request information when the first request type is a request to join the group; a fourth acquisition unit 8043, which is used to obtain the corresponding third requester information when the first request type is an internal change instruction, and the third requester information includes the requester identity, and the requester identity includes the group leader and the group member; a change unit 8044, which is used to obtain the member change content corresponding to the internal change instruction when the requester identity is the group leader, and change the member information in the team information according to the member change content.

[0104] In this embodiment, the fourth request module 805 includes: a fifth acquisition unit 8051, which is used to obtain the corresponding fourth requester information when a team change request is received, and the fourth requester information includes the requester identity, and the requester identity includes the team leader and the team member; a sixth acquisition unit 8052, which is used to obtain the corresponding second request type when the requester identity is the team leader, and the second request type includes a name modification instruction and a team disbanding instruction; a fourth request unit 8053, which is used to generate a modification pop-up window when the second request type is a name modification instruction, and the modification pop-up window includes a team name input box; a fifth request unit 8054, which is used to obtain the information storage path when the second request type is a team disbanding instruction, and store the team information in the obtained information storage path.

[0105] In this embodiment, the fifth request module 806 also includes: a seventh acquisition unit 8061, which is used to obtain the corresponding fifth requester information when receiving a permission change request, and the fifth requester information includes the requester identity, and the requester identity includes the team leader and the team member; a sixth request unit 8062, which is used to obtain the permission change content corresponding to the permission change instruction when the requester identity is the team leader, so as to modify the permissions of the team members in the target team, and the permission change content includes the team member information and the permission change information; a seventh request unit 8063, which is used to return a permission change request failure instruction when the requester identity is a team member.

[0106] above Figure 8 and Figure 9 The team data interaction apparatus in the embodiment of the present invention is described in detail from the perspective of modular functional entities. The team data interaction device in the embodiment of the present invention is described in detail from the perspective of hardware processing.

[0107] Figure 10It is a structural diagram of a team data interaction device provided by an embodiment of the present invention. The team data interaction device 900 may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) 910 (for example, one or more processors) and memory 920, and one or more storage media 930 (for example, one or more massive storage devices) for storing application programs 933 or data 932. Among them, the memory 920 and the storage medium 930 can be short-term storage or persistent storage. The program stored in the storage medium 930 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the team data interaction device 900. Furthermore, the processor 910 may be configured to communicate with the storage medium 930, and execute a series of instruction operations in the storage medium 930 on the team data interaction device 900 to implement the steps of the team data interaction method provided by the above-mentioned method embodiments.

[0108] The team data interaction device 900 may also include one or more power supplies 940, one or more wired or wireless network interfaces 950, one or more input and output interfaces 960, and / or one or more operating systems 931, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. It will be understood by those skilled in the art that Figure 10 The team data interaction device structure shown does not constitute a limitation on the team data interaction device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0109] The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores instructions, which, when executed on a computer, cause the computer to execute the steps of the team data interaction method.

[0110] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0111] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc., various media that can store program code.

[0112] Finally, it should be noted that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art will be able to modify the technical solutions described in the aforementioned embodiments or substitute equivalents for some of the technical features. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. A team data interaction method, characterized in that: include: When receiving a target team creation request, obtaining the first requester information corresponding to the target team creation request, verifying the first requester information, and responding to the target team creation request based on the verification result, wherein the verification result includes pass or fail; When the verification result is passed, the team creation interface corresponding to the target team is presented, the team information filled in the team creation interface is obtained and stored, and the target team is created; specifically, when the verification result is passed, the team creation interface corresponding to the target team is presented, the team creation interface is used to input and change team member information, and the team creation interface includes a member submission button; when the submit button is clicked, the team information filled in the team creation interface is obtained, and the team information is stored in a pre-selected database, the pre-selected database includes multiple data channels; according to the first requester information and the obtained team information, the target team is created; the pre-selected database is a redis database, and data viewing and sharing are achieved through multiple data channels of the redis database; When a data viewing request is received, the second requester information corresponding to the data viewing request and the working mode of the target team are obtained, and the data viewing request is responded to according to the second requester information and the working mode of the target team; specifically, when a data viewing request is received, the corresponding second requester information is obtained, the second requester information includes the identity of the requester, and the identity of the requester includes the team leader and the team member; when the identity of the requester is a team member, the working mode of the team is obtained, and the working mode of the team includes the team mode and the individual mode; when the working mode of the team is the individual mode, a viewing failure instruction is returned; when the working mode of the team is the team mode, the request content of the data viewing request is obtained, and the request viewing result is fed back according to the request content; the request content includes the request object and the data requested to be viewed, each team member information corresponds to a view button, and the request object is the team member information corresponding to the view button clicked by the initiator of the data viewing request; When the View button is clicked, a pop-up window is generated. The pop-up window includes multiple viewing options, including at least order quantity, order processing quantity, order placement work schedule, and order processing work schedule. The viewing option selected by the initiator of the data viewing request is the data requested for viewing; When a member change request is received, obtaining third requester information and the first request type corresponding to the member change request, and responding to the member change request according to the third requester information and the first request type; When a team change request is received, obtaining fourth requester information and a second request type corresponding to the team change request, and responding to the team change request according to the fourth requester information and the second request type; When a permission change request is received, the fifth requester information and permission change content corresponding to the permission change request are obtained, and the permission change request is responded to according to the fifth requester information and permission change content.

2. A team data interaction method according to claim 1, characterized in that: When receiving a target team creation request, obtaining the first requester information corresponding to the target team creation request, verifying the first requester information, and responding to the target team creation request based on the verification result, wherein the verification result includes pass or fail, and specifically includes: When a target team creation request is received, first requester information corresponding to the target team creation request is obtained, where the first requester information includes a user's face order account number; If the user's face order account number is empty, the verification fails and a verification failure instruction is returned; When the content of the user's face order account is not empty, determine whether there is an established team for the user's face order account. If so, the verification fails and returns to the team interface of the established team.

3. A team data interaction method according to claim 1, characterized in that: When a member change request is received, obtaining third requester information and the first request type corresponding to the member change request, and responding to the member change request according to the third requester information and the first request type, specifically includes: When a member change request is received, a corresponding first request type is obtained, wherein the first request type includes a request to join a group and an internal change instruction; When the first request type is a request to join a group, generating review information according to the group joining request information; When the first request type is an internal change instruction, obtaining corresponding third requester information, the third requester information including the requester identity, the requester identity including the group leader and group member; When the requester is a team leader, obtain the member change content corresponding to the internal change instruction, and change the team member information in the team information according to the member change content.

4. A team data interaction method according to claim 1, characterized in that: When receiving the team change request, obtaining fourth requester information and the second request type corresponding to the team change request, and responding to the team change request according to the fourth requester information and the second request type, specifically includes: When a team change request is received, the corresponding fourth requester information is obtained, where the fourth requester information includes the requester identity, which includes the team leader and team members. When the requester is a team leader, the corresponding second request type is obtained, which includes a name modification instruction and a team disbanding instruction; When the second request type is a name modification instruction, a modification pop-up window is generated, wherein the modification pop-up window includes a team name input box; When the second request type is a team disbanding instruction, an information storage path is obtained, and the team information is stored in the obtained information storage path.

5. A team data interaction method according to claim 1, characterized in that: When receiving the permission change request, obtaining the fifth requester information and permission change content corresponding to the permission change request, and responding to the permission change request according to the fifth requester information and permission change content, specifically including: When receiving a permission change request, obtaining corresponding fifth requester information, the fifth requester information including the requester identity, the requester identity including the group leader and group member; When the requester is a team leader, obtain the permission change content corresponding to the permission change instruction to modify the permissions of team members in the target team. The permission change content includes team member information and permission change information; If the requester is a group member, a permission change request failure message will be returned.

6. A team data interaction device, characterized in that: include: A first request module is configured to, upon receiving a target team creation request, obtain first requester information corresponding to the target team creation request, verify the first requester information, and respond to the target team creation request based on a verification result, wherein the verification result includes a pass or fail. A creation module is used to present a team creation interface corresponding to the target team when the verification result is passed, obtain and store the team information filled in the team creation interface, and create the target team; specifically, when the verification result is passed, present a team creation interface corresponding to the target team, the team creation interface is used to input and change team member information, and the team creation interface includes a member submission button; when the submit button is clicked, obtain the team information filled in the team creation interface, and store the team information in a pre-selected database, the pre-selected database includes multiple data channels; create the target team according to the first requester information and the obtained team information; the pre-selected database is a redis database, and data viewing and sharing are achieved through the multiple data channels of the redis database; The second request module is used to obtain the second requester information corresponding to the data viewing request and the working mode of the target team when a data viewing request is received, and respond to the data viewing request according to the second requester information and the working mode of the target team; specifically, when a data viewing request is received, the corresponding second requester information is obtained, the second requester information includes the identity of the requester, and the identity of the requester includes the team leader and the team member; when the identity of the requester is a team member, the working mode of the team is obtained, and the working mode of the team includes the team mode and the individual mode; when the working mode of the team is the individual mode, a viewing failure instruction is returned; when the working mode of the team is the team mode, the request content of the data viewing request is obtained, and the viewing result of the request is fed back according to the request content; the request content includes the request object and the data requested to be viewed, each team member information corresponds to a view button, and the request object is the team member information corresponding to the view button clicked by the initiator of the data viewing request; When the View button is clicked, a pop-up window is generated. The pop-up window includes multiple viewing options, including at least order quantity, order processing quantity, order placement work schedule, and order processing work schedule. The viewing option selected by the initiator of the data viewing request is the data requested for viewing; a third request module configured to, upon receiving a member change request, obtain third requester information and the first request type corresponding to the member change request, and respond to the member change request according to the third requester information and the first request type; a fourth request module configured to, upon receiving a team change request, obtain fourth requester information and a second request type corresponding to the team change request, and respond to the team change request according to the fourth requester information and the second request type; The fifth request module is used to obtain the fifth requester information and permission change content corresponding to the permission change request when receiving the permission change request, and respond to the permission change request according to the fifth requester information and permission change content.

7. A team data interaction device, characterized in that: The team data interaction device includes: a memory and at least one processor, wherein the memory stores instructions; At least one of the processors calls the instructions in the memory to enable the team data interaction device to execute each step of the team data interaction method as described in any one of claims 1-5.

8. A computer-readable storage medium having instructions stored thereon, characterized in that: When the instructions are executed by the processor, the various steps of the team data interaction method as described in any one of claims 1 to 5 are implemented.

Images