Business data processing method and related device

Abstract

The application discloses a business data processing method and related equipment, and related embodiments can be applied to various scenes such as cloud technology, artificial intelligence, intelligent transportation and auxiliary driving; an application login request of a first object to a target application system can be acquired; a login credential of a terminal corresponding to the first object to the target application system is generated according to a first account; the terminal corresponding to the first object is triggered to log in to the target application system based on the login credential; when a calling request of the first object to a target component in the target application system is received, component data corresponding to the target component is filtered according to the login credential; and the filtered component data is sent to the terminal corresponding to the first object. The application can generate a login credential corresponding to the first object based on the first account, and limit the data access range of the first object based on the login credential, thereby realizing the function of processing business under the premise of ensuring the data security of the target application system, and reducing the risk of data leakage.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a business data processing method and related equipment. Background Technology

[0002] In business-to-business (B2B) operations, it is common to collaborate with external teams to drive the development of application systems. External teams often need to access internal data from the application system to fulfill business requirements during the business process.

[0003] In current technologies, application system interfaces without authentication or verification are directly provided to external collaboration teams for them to pull data for development. However, some internal data in the application system is highly sensitive. This approach directly exposes the system's internal data, allowing external personnel to freely access any data in the application system, which can easily lead to data leakage. Summary of the Invention

[0004] This application provides a business data processing method and related equipment. The related equipment may include a business data processing device, electronic equipment, computer-readable storage medium, and computer program product. It can realize the function of business processing while ensuring data security in the target application system and reduce the risk of data leakage.

[0005] This application provides a business data processing method, including:

[0006] Obtain an application login request from a first object for a target application system. The application login request includes a first account of the first object. The target application system includes a first account system and a second account system. The first account is an account in the first account system.

[0007] Generate login credentials for the target application system based on the first account for the terminal corresponding to the first object.

[0008] Based on the login credentials, the terminal corresponding to the first object is triggered to log in to the target application system;

[0009] When a request to invoke a target component in the target application system is received from the first object, the component data corresponding to the target component is filtered according to the login credentials;

[0010] Filtered component data is sent to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data.

[0011] Accordingly, embodiments of this application provide a business data processing apparatus, including:

[0012] The acquisition unit is used to acquire an application login request from a first object to a target application system. The application login request includes a first account of the first object. The target application system includes a first account system and a second account system. The first account is an account in the first account system.

[0013] The generation unit is configured to generate a login credential for the terminal corresponding to the first object to log in to the target application system based on the first account.

[0014] The login unit is used to trigger the terminal corresponding to the first object to log in to the target application system based on the login credentials;

[0015] The filtering unit is used to filter the component data corresponding to the target component based on the login credentials when the first object receives a call request for the target component in the target application system.

[0016] The sending unit is used to send filtered component data to the terminal corresponding to the first object, so as to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data.

[0017] Optionally, in some embodiments of this application, the generation unit may include an encryption subunit and a determination subunit, as follows:

[0018] The encryption subunit is used to encrypt the first account to obtain encrypted data.

[0019] The determination subunit is used to determine the login credentials for the terminal corresponding to the first object to log in to the target application system based on the encrypted data.

[0020] Optionally, in some embodiments of this application, the filtering unit may include a verification subunit and a first filtering subunit, as follows:

[0021] The verification subunit is used to verify the validity of the login credentials when it receives a call request from the first object to a target component in the target application system.

[0022] The first filtering subunit is used to filter the component data corresponding to the target component when the login credential passes the validity check.

[0023] Optionally, in some embodiments of this application, the invocation request includes the login credentials;

[0024] The filtering unit may include a parsing subunit and a second filtering subunit, as follows:

[0025] The parsing subunit is used to parse the login credentials in the call request when it receives a call request from the first object to a target component in the target application system, so as to obtain the first account of the first object.

[0026] The second filtering subunit is used to filter the component data corresponding to the target component based on the account permissions corresponding to the first account.

[0027] Optionally, in some embodiments of this application, the second account system is the account system of the target organizational structure in the target application system, the target organizational structure includes at least one organizational member; the components of the target application system include components corresponding to the organizational structure data.

[0028] Optionally, in some embodiments of this application, the filtered component data includes filtered target organizational structure data;

[0029] The transmitting unit may include an acquisition subunit, a transformation subunit, and a transmitting subunit, as follows:

[0030] The acquisition subunit is used to acquire the original organizational identification information of the target organizational structure data in the target application system;

[0031] The transformation subunit is used to transform the original organization identification information to obtain the target organization identification information of the target organizational structure data under the first account system.

[0032] The sending subunit is used to send the target organization identification information to the terminal corresponding to the first object.

[0033] Optionally, in some embodiments of this application, the transformation subunit may be specifically used to encode the original organization identification information based on the first account of the first object to obtain encoded organization identification information; and based on the encoded organization identification information, to determine the target organization identification information of the target organizational structure data under the first account system.

[0034] Optionally, in some embodiments of this application, the sending unit may further include a display subunit, as follows:

[0035] The display subunit is used to trigger the terminal corresponding to the first object to display the address book page corresponding to the target organizational structure data. The address book page includes the target organizational identification information of the target organizational structure data under the first account system.

[0036] Optionally, in some embodiments of this application, the filtering unit may include a search subunit and a third filtering subunit, as follows:

[0037] The search subunit is configured to perform a data search on the target component when it receives a search request from the first object for a target component in the target application system, and obtain the searched component data.

[0038] The third filtering subunit is used to filter the searched component data based on the login credentials.

[0039] An electronic device provided in this application includes a processor and a memory. The memory stores multiple instructions, and the processor loads the instructions to execute the steps in the business data processing method provided in this application.

[0040] This application also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps in the business data processing method provided in this application.

[0041] Furthermore, this application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the steps in the business data processing method provided in this application.

[0042] This application provides a business data processing method and related equipment. It can obtain an application login request from a first object for a target application system. The application login request includes a first account of the first object, and the target application system includes a first account system and a second account system. The first account is an account within the first account system. A login credential for the first object's corresponding terminal to log in to the target application system is generated based on the first account. The login credential triggers the first object's corresponding terminal to log in to the target application system. When a call request from the first object to a target component in the target application system is received, data filtering is performed on the component data corresponding to the target component based on the login credential. The filtered component data is sent to the terminal corresponding to the first object to trigger business processing based on the filtered component data. This application can generate a login credential for the first object based on the first account and restrict the data access scope of the first object based on the login credential, achieving business processing while ensuring data security in the target application system and reducing the risk of data leakage. Attached Figure Description

[0043] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0044] Figure 1a This is a schematic diagram of a scenario illustrating the business data processing method provided in the embodiments of this application;

[0045] Figure 1b This is a flowchart of the business data processing method provided in the embodiments of this application;

[0046] Figure 1c This is a schematic diagram of a page illustrating the business data processing method provided in an embodiment of this application;

[0047] Figure 1d This is another flowchart of the business data processing method provided in the embodiments of this application;

[0048] Figure 1e This is another flowchart of the business data processing method provided in the embodiments of this application;

[0049] Figure 1f This is another flowchart of the business data processing method provided in the embodiments of this application;

[0050] Figure 2 This is another flowchart of the business data processing method provided in the embodiments of this application;

[0051] Figure 3 This is a schematic diagram of the structure of the business data processing apparatus provided in the embodiments of this application;

[0052] Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0053] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0054] This application provides a business data processing method and related equipment. The related equipment may include a business data processing device, an electronic device, a computer-readable storage medium, and a computer program product. Specifically, the business data processing device may be integrated into an electronic device, which may be a terminal or a server, etc.

[0055] It is understood that the business data processing method of this embodiment can be executed on a terminal, on a server, or jointly by a terminal and a server. The above examples should not be construed as limiting this application.

[0056] like Figure 1a As shown, taking the joint execution of business data processing by a terminal and a server as an example, the business data processing system provided in this application embodiment includes a terminal 10 and a server 11, etc.; the terminal 10 and the server 11 are connected via a network, such as a wired or wireless network, etc., wherein the business data processing device can be integrated into the server.

[0057] Server 11 can be used to: obtain an application login request from a first object for a target application system, the application login request including a first account of the first object, the target application system including a first account system and a second account system, the first account being an account in the first account system; generate login credentials for the terminal 10 corresponding to the first object to log in to the target application system based on the first account; trigger the terminal 10 corresponding to the first object to log in to the target application system based on the login credentials; when receiving a call request from the first object for a target component in the target application system, filter the component data corresponding to the target component based on the login credentials; send the filtered component data to the terminal 10 corresponding to the first object to trigger the terminal 10 corresponding to the first object to perform business processing based on the filtered component data. Server 11 can be a single server, a server cluster composed of multiple servers, or a cloud server. In the business data processing method or apparatus disclosed in this application, multiple servers can form a blockchain, and the server is a node on the blockchain.

[0058] Terminal 10 can be used to: send an application login request for a target application system to server 11, the application login request including the first account of the first object; terminal 10 can also receive login credentials sent by server 11 and log in to the target application system based on the login credentials; furthermore, terminal 10 can send a call request to server 11 for a target component in the target application system, triggering server 11 to filter the component data corresponding to the target component based on the login credentials included in the call request; when terminal 10 receives the filtered component data sent by server 11, it can perform business processing based on the filtered component data. Terminal 10 can include a mobile phone, smart TV, tablet computer, laptop computer, or personal computer (PC), etc. A client can also be set on terminal 10, which can be an application client or a browser client, etc.

[0059] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the preferred order of the embodiments.

[0060] This embodiment will be described from the perspective of a business data processing device, which can be integrated into an electronic device, such as a server or a terminal.

[0061] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0062] The business data processing method of this application embodiment can be applied to various scenarios of collaborative development of application systems with external teams. This embodiment can be applied to various scenarios such as cloud technology, artificial intelligence, smart transportation, and assisted driving.

[0063] like Figure 1b As shown, the specific process of this business data processing method can be as follows:

[0064] 101. Obtain the application login request of the first object for the target application system. The application login request includes the first account of the first object. The target application system includes a first account system and a second account system. The first account is an account in the first account system.

[0065] Specifically, in this embodiment, the users of the target application system can be divided into internal users (i.e., internal personnel) and external users (i.e., external personnel). External users can specifically be personnel whose system access permissions are restricted. In specific scenarios, such as in business-to-business (B2B) operations, it is common to collaborate with external teams to drive the development of application systems. These external teams often need to access internal data from the application system to fulfill business requirements. However, some internal data within the application system is highly sensitive, such as contact list data. To ensure data security while providing external development teams with the ability to access application system data, this application provides a technical solution that allows external development teams to securely access the contact list data of the target application system.

[0066] For example, the target application system is a system developed by company A. Due to business needs, company B needs to use the data in the target application system in cooperation with company A. Therefore, company A needs to authorize company B to use the target application system. After authorization, the user corresponding to company B can be regarded as an external person of the target application system, and the user corresponding to company A can be regarded as an internal person of the target application system.

[0067] The first object can be an external user of the target application system, or a third-party user. An external user can be someone whose system access is restricted. A third party can refer to an external collaborative team other than the internal R&D team of the target application system, i.e., a development team that can only perform secondary development through the interfaces exposed by the target application system. The first account can be considered the object identification information of the first object. In a specific scenario, the first account can include the first object's enterprise ID (Identity document) and user ID. The enterprise ID identifies the enterprise to which the first object belongs, and the user ID identifies the individual identity of the first object.

[0068] The first account system can be the account system used by external personnel, while the second account system can be the account system used by internal personnel of the target application system. The data presented by the target application system can differ under different account systems.

[0069] The target application system can be a messaging system, and its type is not limited. For example, the target application system can be an instant messaging system, and this embodiment does not limit it.

[0070] In one specific embodiment, a QR code image for logging into the target application system can be obtained. The first object can send an application login request containing the first account to the server (specifically, the application system backend) by scanning the QR code image, so that the server can authorize the first account to log into the target application system based on the application login request.

[0071] 102. Generate login credentials for the terminal corresponding to the first object to log in to the target application system based on the first account.

[0072] Optionally, in this embodiment, the step "generating login credentials for the terminal corresponding to the first object to log in to the target application system based on the first account" may include:

[0073] The first account is encrypted to obtain encrypted data;

[0074] Based on the encrypted data, the login credentials for the terminal corresponding to the first object to log in to the target application system are determined.

[0075] The encryption process can take many forms, including symmetric and asymmetric encryption; this embodiment does not impose any restrictions. Symmetric encryption uses the same encryption and decryption keys, while asymmetric encryption uses different keys. Asymmetric encryption algorithms require two keys: a public key and a private key. The public and private keys are a pair; if data is encrypted with the public key, it can only be decrypted with the corresponding private key; conversely, if data is encrypted with the private key, it can only be decrypted with the corresponding public key.

[0076] The process of encrypting the first account may specifically include performing a hash operation on the first account to obtain its hash value; then, based on a key, encrypting the hash value of the first account to obtain encrypted data. This encrypted data is then used as the login credential for the terminal corresponding to the first object to log in to the target application system.

[0077] In this embodiment, encryption allows the login credentials to encrypt and store the first account of the first object. Specifically, if the first account includes the enterprise ID and user ID of the first object, then the login credentials will encrypt and store the enterprise ID and user ID of the first object. The login credentials can be considered as a ticket for the first object's first account to use the target application system.

[0078] In a specific scenario, after the application system backend receives the application login request sent by the terminal corresponding to the first object, it can parse the application login request to obtain the first account contained therein, generate login credentials based on the first account, and then send the login credentials to the terminal where the first object is located.

[0079] 103. Based on the login credentials, trigger the terminal corresponding to the first object to log in to the target application system.

[0080] In this embodiment, after generating the login credential, the login credential can be sent to the terminal corresponding to the first object. When the terminal corresponding to the first object receives the login credential, the terminal corresponding to the first object can log in to the target application system based on the login credential.

[0081] 104. When the first object receives a request to call a target component in the target application system, the component data corresponding to the target component is filtered according to the login credentials.

[0082] After logging into the target application system on the terminal corresponding to the first object, the terminal can display the application page corresponding to the target application system. The application page can include at least one component, which can specifically be a software component in the network application, also known as middleware. The component can provide some standard and simple application interfaces, allowing the setting and adjustment of parameters and properties.

[0083] Specifically, the first object can send a call request to the application system backend for the target component by triggering an operation on the target component in the application page, such as a click or swipe operation, in order to obtain component data related to the target component based on the call request. The target component can be any component in the application page. The component data can be relevant business information related to the business function corresponding to the component.

[0084] In this embodiment, the component can specifically be an iframe control embedded in the application page. An iframe is an HTML (Hypertext Markup Language) tag used to create an inline frame (i.e., an inline frame) that contains another document—essentially, a document within a document. When the first object accesses the application page with the embedded iframe control, if the iframe control is triggered, the application system backend can authenticate the first account's service permissions, obtain the data accessible to the first object under the first account's account permissions, and then transmit this data to the terminal corresponding to the first object.

[0085] In this embodiment, based on the provided iframe control, the third party (i.e., the first object) cannot directly call the component data; the target application system can provide related functional interactions through the displayed iframe control. The iframe control is a black box to the third party, which can isolate the component data from the third party, thus better ensuring data security and preventing data leakage.

[0086] In one specific embodiment, in the terminal where the first object resides, in response to the first object's triggering operation on the target component in the target application system, such as a click or swipe operation, a request to call the target component can be sent to the server (specifically, the application system backend). Furthermore, when a third party (i.e., the first object) calls component data, it needs to carry login credentials. The application system backend will verify the login credentials, and only if the verification is successful will the component data be returned to the terminal corresponding to the first object.

[0087] Optionally, in this embodiment, the invocation request includes the login credentials;

[0088] The step "When a request to invoke a target component in the target application system is received from the first object, data filtering is performed on the component data corresponding to the target component based on the login credentials" may include:

[0089] When a request to invoke a target component in the target application system is received from the first object, the login credentials in the request are parsed to obtain the first account of the first object;

[0090] Based on the account permissions corresponding to the first account, the component data corresponding to the target component is filtered.

[0091] The call request may carry login credentials, which are then parsed, specifically decrypted. The decryption algorithm used corresponds to the encryption algorithm used in step 102. Through decryption, the object identifier information of the first object, i.e., the first account, can be obtained, thereby determining the identity information of the first object. Based on this identity information, the data range of the target application system that the first object can access can be determined.

[0092] Specifically, based on the account permissions of the first account, the data content of the target application system that the first object corresponding to the first account cannot view can be determined. Then, based on this data content, data filtering is performed on the component data corresponding to the target component. Data filtering is also known as data screening. The filtered component data obtained by data filtering is the data content that the first object can access under the account permissions of the first account.

[0093] This embodiment can provide identity authentication to the application system backend by issuing login credentials to the terminal corresponding to the first object, and restrict the data range accessed by its call requests to the target application system. When the terminal corresponding to the first object has the correct login credentials and calls the target component in the target application system, the application system backend can decrypt the login credentials based on the call request to obtain the first object's first account (specifically, it may include the first object's enterprise ID and user ID). Using the trusted enterprise ID and user ID, the component data of the first object within the visible range of that enterprise can be returned to the terminal corresponding to the first object.

[0094] Optionally, in this embodiment, the step "when receiving a call request from the first object to a target component in the target application system, filtering the component data corresponding to the target component based on the login credentials" may include:

[0095] When a request to invoke a target component in the target application system is received from the first object, the login credentials are validated.

[0096] When the login credentials pass the validity verification, the component data corresponding to the target component is filtered.

[0097] Specifically, the login credentials issued by the application system backend to the terminal corresponding to the first object can have a certain validity period, which can be set according to the actual situation, for example, it can be set to 24 hours.

[0098] In some embodiments, the validity verification of login credentials may include time validity verification and identity validity verification. Only after the login credentials pass both time validity and identity validity verification is the component data corresponding to the target component filtered. Specifically, when the application system backend receives a call request from the terminal corresponding to the first object, it can perform identity validity verification on the login credentials in the call request. This can involve decrypting the login credentials to obtain the first account of the first object. If the first account is an authorized account capable of logging into the target application system, then the identity validity verification passes. Then, based on the issuance time of the login credentials, a time validity verification is performed. For example, if the validity period is 24 hours, it can be determined whether the issuance time is more than 24 hours from the current time. If it is not more than 24 hours, then the time validity verification passes.

[0099] In this embodiment, login credentials can be issued to the terminal corresponding to the first object to trigger the first object's login to the target application system. When the first object calls a component in the target application system, if there are no login credentials, the QR code scanning page will be restarted. The first object sends an application login request containing its first account to the application system backend by scanning the QR code, thereby triggering the application system backend to issue login credentials to the business party (i.e., the terminal corresponding to the first object). After receiving the login credentials, the business party can cache them to prevent the need to scan the QR code to log in to the target application system every time a component is called. Specifically, the login credentials have a validity period. When the validity period expires, the login credentials will become invalid. If the component is called at this time, it will fail, and a new login credentials need to be obtained by scanning the QR code again.

[0100] Optionally, in this embodiment, the step "when receiving a call request from the first object to a target component in the target application system, filtering the component data corresponding to the target component based on the login credentials" may include:

[0101] When a search request for a target component in the target application system is received from the first object, a data search is performed on the target component to obtain the searched component data;

[0102] Based on the login credentials, the searched component data is filtered.

[0103] The business data processing method provided in this application can support a search function. Specifically, the content to be searched can be selected on the application page corresponding to the target application system, and then the search control can be triggered to perform a data search on the content.

[0104] This application can fulfill the business requirement of a third-party team to display component data through an iframe control embedded in the application page of the target application system. This component data can specifically be contact list data (i.e., organizational structure data), and it also provides basic interactive functions, such as selecting and searching for organizational structure or members. Figure 1c As shown. Figure 1c The document displays the organizational structure data for "Company A," including the organizational structures for "Special List," "Interconnected Enterprises," "Service Accounts," "External List," and "Company A's Partners." Under the "Service Accounts" organizational structure, it also includes the organizational members of "Deprecated Service Accounts." The first object can obtain the corresponding component data by making a request to the component corresponding to the organizational structure data on the page.

[0105] In one specific embodiment, such as Figure 1d As shown, when the first object (i.e., a third party) searches for a target component in the target application system, that is, when it initiates a search call on the target component (specifically, an iframe control), it can pass through (i.e., transparently transmit) its search request through the target component. After receiving the search request, the application system backend can call the search service to perform a basic search. After the search service returns the search results to the application system backend, the application system backend can filter the search results according to the account permissions of the first account corresponding to the first object, obtain the filtered component data, and send the filtered component data to the terminal corresponding to the first object for display.

[0106] 105. Send filtered component data to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data.

[0107] Optionally, in this embodiment, the second account system is the account system of the target organizational structure in the target application system, and the target organizational structure includes at least one organizational member; the components of the target application system include components corresponding to the organizational structure data.

[0108] Specifically, the target organizational structure can be an organizational structure within the target application system. For example, a department within an enterprise can be considered an organizational structure, or the entire enterprise can also be considered an organizational structure. This embodiment does not impose strict limitations on this.

[0109] Organizational structure specifically refers to the overall structure of an organization. It serves as the fundamental structural basis for an organization's processes, departmental setup, and functional planning. Organizational structure data can include information about the various levels of organization within a company or organization, as well as the personnel belonging to each organization. Therefore, organizational structure data is relatively sensitive and requires enhanced security.

[0110] Specifically, the target organizational structure may include at least one organizational structure (which can also be regarded as an organizational unit), and each organizational structure includes at least one organizational member. The organizational members need to be arranged according to the organizational structure in the target application system. For example, if the target organizational structure is a certain enterprise, the organizational unit can be the various departments in the enterprise, and the organizational members in the organizational unit can be the employees in the corresponding departments.

[0111] Optionally, in this embodiment, organizational members within the organizational structure may possess account information under the target application system. Account information may include the corresponding organizational member's account in the target application system, as well as relevant information such as email addresses.

[0112] It should be noted that component data can include organizational structure data, i.e., contact list data. Organizational structure data can include the organizational structure itself and the corresponding organizational members. Specifically, the contact list refers to the tree structure of the enterprise's organizational structure and personnel structure within the target application system.

[0113] Optionally, in this embodiment, the filtered component data includes filtered target organizational structure data;

[0114] The step "send filtered component data to the terminal corresponding to the first object" may include:

[0115] Obtain the original organizational identification information of the target organizational structure data in the target application system;

[0116] The original organization identification information is transformed to obtain the target organization identification information of the target organizational structure data under the first account system;

[0117] The target organization identification information is sent to the terminal corresponding to the first object.

[0118] Specifically, the original organizational identification information can be the organizational identification information of the target organizational structure data under the second account system. The target organizational structure data can include the organizational structure itself and its members. Specifically, the organizational identification information can be the ID of the organizational structure data, or other identifying information such as an account or email address. If the target organizational structure data is a company, its organizational identification information is the company ID; if the target organizational structure data is a company member, its organizational identification information can be the member ID. The company ID is a unique number used to uniquely identify a company in the target application system; the member ID is a unique number used to uniquely identify a member of a company in the target application system.

[0119] This embodiment can transform the original organizational identification information of the target organizational structure data under the second account system into target organizational identification information under the first account system, and then send it to the terminal corresponding to the first object. The terminal then displays the transformed target organizational identification information instead of the original organizational identification information, thus hiding the original organizational identification information and improving the security of the organizational structure data. Here, the target organizational identification information refers to the first account system to which the first object's first account belongs, while the original organizational identification information is the organizational identification information under the native account system within the target application system.

[0120] Optionally, in this embodiment, the step "transforming the original organization identification information to obtain the target organization identification information of the target organizational structure data under the first account system" may include:

[0121] Based on the first account of the first object, the original organization identification information is encoded to obtain the encoded organization identification information;

[0122] Based on the encoded organization identification information, the target organization identification information of the target organizational structure data under the first account system is determined.

[0123] Specifically, in this embodiment, the first account of the first object can be encoded into the original organization identification information. The target organization identification information obtained in this way is for the first object, and the first account system can also be regarded as the account system corresponding to the first object. Based on the object identification information of the first object, different third-party development teams (i.e., external teams) can apply different account systems.

[0124] There are various ways to encode the original organizational identification information based on the first account of the first object, and this embodiment does not limit this. For example, the encoding method can be a fusion method such as addition. After encoding, the encoded organizational identification information can be determined as the target organizational identification information of the target organizational structure data under the first account system.

[0125] The target organization identification information can be denoted as OpenId. OpenId can be regarded as the account of the target organization's structure data in the external (i.e., to the first object) account system, which is different from the account in the target application system in the original internal account system. Specifically, the target organization identification information can be the member ID and enterprise ID obtained by encrypting and encoding the original organization identification information.

[0126] For example, in a specific scenario, the target organizational structure data may include the organizational structure (enterprise) and organizational members (enterprise members). The object identification information of the first object (i.e., the first account) is denoted as AppId. The original organizational identification information of the target organizational structure data in the target application system can be denoted as enterprise id and member id. The encoding process corresponding to the target organizational identification information can be represented by the following formula:

[0127] External Enterprise ID = Code (AppId, Enterprise ID)

[0128] External member ID = code(AppId, member ID)

[0129] Among them, the external enterprise ID represents the target organization identification information of the organizational structure (enterprise) under the first account system, and the external member ID represents the target organization identification information of the organizational member (enterprise member) under the first account system.

[0130] By encoding the Appid into the target organization's identification information, the account systems of different third-party teams accessing the target application systems can be made different, avoiding the risks of mixing accounts.

[0131] In this embodiment, for third-party development teams, the original organizational identification information of the organizational structure data can be encoded to avoid exposing the native account system within the target application system. Furthermore, different account systems can be used for different third-party development teams. This application can achieve the requirement of differentiated external account systems based on a unique and dedicated identity identifier (Appid) for authorized third-party development teams.

[0132] Optionally, in this embodiment, after the step "sending the target organization identification information to the terminal corresponding to the first object", the method may further include:

[0133] The terminal corresponding to the first object is triggered to display the address book page corresponding to the target organizational structure data. The address book page includes the target organizational identification information of the target organizational structure data under the first account system.

[0134] The business data processing method provided in this application can ensure the security of data accessed by third-party teams to the target application system during collaborative development, prevent the leakage of sensitive information such as contact list data, and adopt different account systems for different access teams to prevent different access teams from sharing a single account system. It also shields the original account system inside the target application system from the outside world, reducing the risk of being attacked.

[0135] In one specific embodiment, such as Figure 1e As shown, when the first object (third party) interacts with the target component in the target application system, that is, when it initiates a call request to the target component (specifically, an iframe control), it can pass through (i.e., transparently transmit) its call request through the target component. Based on the call request, the component data of the target component is filtered to obtain the filtered component data (interaction result). If the filtered component data contains target organizational structure data, since organizational structure data is relatively important information, the original organizational identification information of the target organizational structure data in the target application system can be encoded to obtain the target organizational identification information of the target organizational structure data under the first account system. The encoded target organizational identification information is then returned to the terminal corresponding to the first object as the final interaction result.

[0136] Specifically, such as Figure 1f The diagram illustrates the process of a first object accessing component data within a target application system. It's understandable that the first object (a third party) needs authorization to access data (such as contact information) within the target application system; it requires login credentials to correctly initiate control calls. The first object can send an application login request to the application system's backend by scanning the QR code used for login. The application system's backend can generate login credentials based on the first account contained in the login request. These credentials can be obtained by symmetric encryption of the first account, preventing third parties from cracking or modifying the information. The backend then distributes these login credentials to the terminal corresponding to the first object. When the first object calls the target component in the target application system, it needs to pass in the login credentials as a ticket. That is, the first object needs to send a call request carrying the login credentials and targeting the target component of the target application system to the application system backend. When the first object initiates the call request, it can pass through the target component (i.e., transparently transmit) the call request containing the ticket. After receiving the call request, the application system backend can determine the account permissions of the first account corresponding to the first object based on the ticket, so as to control the range of contact data that the first object can access. Based on the account permissions, the contact data is filtered and the filtered contact data is returned to the terminal corresponding to the first object for display.

[0137] As can be seen from the above, this embodiment can obtain an application login request from a first object for a target application system. The application login request includes a first account of the first object, and the target application system includes a first account system and a second account system. The first account is an account in the first account system. Login credentials for the first object's corresponding terminal to log in to the target application system are generated based on the first account. The login credentials trigger the first object's corresponding terminal to log in to the target application system. When a call request from the first object to a target component in the target application system is received, data filtering is performed on the component data corresponding to the target component based on the login credentials. The filtered component data is sent to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data. This application can generate login credentials for the first object based on the first account and restrict the data access scope of the first object based on the login credentials, realizing the function of performing business processing while ensuring data security in the target application system and reducing the risk of data leakage.

[0138] Based on the method described in the preceding embodiments, the following will provide a more detailed explanation by taking the specific integration of the business data processing device into a server as an example.

[0139] This application provides a business data processing method, such as... Figure 2 As shown, the specific process of this business data processing method can be as follows:

[0140] 201. The server obtains an application login request from a first object for a target application system. The application login request includes a first account of the first object. The target application system includes a first account system and a second account system. The first account is an account in the first account system.

[0141] Specifically, in this embodiment, the users of the target application system can be divided into internal users (i.e., internal personnel) and external users (i.e., external personnel). External users can specifically be personnel whose system access permissions are restricted. In specific scenarios, such as in business dealings with enterprise customers, it is common to collaborate with external teams to promote the development of application systems. External collaborating teams often need to obtain internal data from the application system to fulfill business requirements. However, some internal data in the application system is highly sensitive, such as contact list data. To ensure data security while providing external development teams with the ability to access application system data, this application provides a technical solution that allows external development teams to securely obtain contact list data from the target application system.

[0142] The first object can specifically be an external user of the target application system, or a third-party user. An external user can be someone whose system access is restricted, and a third party can refer to an external collaborative team other than the internal R&D team of the target application system—that is, a development team that can only perform secondary development through the interfaces exposed by the target application system. The first account can be considered the object identification information of the first object.

[0143] The first account system can be the account system used by external personnel, while the second account system can be the account system used by internal personnel of the target application system. The data presented by the target application system can differ under different account systems.

[0144] In one specific embodiment, a QR code image for logging into the target application system can be obtained. The first object can send an application login request containing the first account to the server (specifically, the application system backend) by scanning the QR code image, so that the server can authorize the first account to log into the target application system based on the application login request.

[0145] 202. The server generates login credentials for the terminal corresponding to the first object to log in to the target application system based on the first account.

[0146] Optionally, in this embodiment, the step "generating login credentials for the terminal corresponding to the first object to log in to the target application system based on the first account" may include:

[0147] The first account is encrypted to obtain encrypted data;

[0148] Based on the encrypted data, the login credentials for the terminal corresponding to the first object to log in to the target application system are determined.

[0149] There are various encryption methods, such as symmetric encryption or asymmetric encryption. This embodiment does not limit the methods.

[0150] The process of encrypting the first account may specifically include performing a hash operation on the first account to obtain its hash value; then, based on a key, encrypting the hash value of the first account to obtain encrypted data. This encrypted data is then used as the login credential for the terminal corresponding to the first object to log in to the target application system.

[0151] In a specific scenario, after the application system backend receives the application login request sent by the terminal corresponding to the first object, it can parse the application login request to obtain the first account contained therein, generate login credentials based on the first account, and then send the login credentials to the terminal where the first object is located.

[0152] 203. The server triggers the terminal corresponding to the first object to log in to the target application system based on the login credentials.

[0153] In this embodiment, after generating the login credential, the login credential can be sent to the terminal corresponding to the first object. When the terminal corresponding to the first object receives the login credential, the terminal corresponding to the first object can log in to the target application system based on the login credential.

[0154] 204. When the server receives the first object's request to call the target component in the target application system, it filters the component data corresponding to the target component based on the login credentials.

[0155] After logging into the target application system on the terminal corresponding to the first object, the terminal can display the application page corresponding to the target application system. The application page can include at least one component, which can specifically be a software component in the network application, also known as middleware. The component can provide some standard and simple application interfaces, allowing the setting and adjustment of parameters and properties.

[0156] In this embodiment, the component can specifically be an iframe control embedded in the application page. An iframe is an HTML (Hypertext Markup Language) tag used to create an inline frame (i.e., an inline frame) that contains another document—essentially, a document within a document. When the first object accesses the application page with the embedded iframe control, if the iframe control is triggered, the application system backend can authenticate the first account's service permissions, obtain the data accessible to the first object under the first account's account permissions, and then transmit this data to the terminal corresponding to the first object.

[0157] In this embodiment, based on the provided iframe control, the third party (i.e., the first object) cannot directly call the component data; the target application system can provide related functional interactions through the displayed iframe control. The iframe control is a black box to the third party, which can isolate the component data from the third party, thus better ensuring data security and preventing data leakage.

[0158] Optionally, in this embodiment, the invocation request includes the login credentials;

[0159] The step "When a request to invoke a target component in the target application system is received from the first object, data filtering is performed on the component data corresponding to the target component based on the login credentials" may include:

[0160] When a request to invoke a target component in the target application system is received from the first object, the login credentials in the request are parsed to obtain the first account of the first object;

[0161] Based on the account permissions corresponding to the first account, the component data corresponding to the target component is filtered.

[0162] Specifically, based on the account permissions of the first account, the data content of the target application system that the first object corresponding to the first account cannot view can be determined. Then, based on this data content, data filtering is performed on the component data corresponding to the target component. Data filtering is also known as data screening. The filtered component data obtained by data filtering is the data content that the first object can access under the account permissions of the first account.

[0163] Optionally, in this embodiment, the step "when receiving a call request from the first object to a target component in the target application system, filtering the component data corresponding to the target component based on the login credentials" may include:

[0164] When a request to invoke a target component in the target application system is received from the first object, the login credentials are validated.

[0165] When the login credentials pass the validity verification, the component data corresponding to the target component is filtered.

[0166] Specifically, the login credentials issued by the application system backend to the terminal corresponding to the first object can have a certain validity period, which can be set according to the actual situation, for example, it can be set to 24 hours.

[0167] 205. The server sends filtered component data to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data.

[0168] Optionally, in this embodiment, the second account system is the account system of the target organizational structure in the target application system, and the target organizational structure includes at least one organizational member; the components of the target application system include components corresponding to the organizational structure data.

[0169] Specifically, the target organizational structure can be an organizational structure within the target application system. For example, a department within an enterprise can be considered an organizational structure, or the entire enterprise can also be considered an organizational structure. This embodiment does not impose strict limitations on this.

[0170] It should be noted that component data can include organizational structure data, i.e., contact list data. Organizational structure data can include the organizational structure itself and the corresponding organizational members. Specifically, the contact list refers to the tree structure of the enterprise's organizational structure and personnel structure within the target application system.

[0171] Optionally, in this embodiment, the filtered component data includes filtered target organizational structure data;

[0172] The step "send filtered component data to the terminal corresponding to the first object" may include:

[0173] Obtain the original organizational identification information of the target organizational structure data in the target application system;

[0174] The original organization identification information is transformed to obtain the target organization identification information of the target organizational structure data under the first account system;

[0175] The target organization identification information is sent to the terminal corresponding to the first object.

[0176] This embodiment can transform the original organizational identification information of the target organizational structure data under the second account system into target organizational identification information under the first account system, and then send it to the terminal corresponding to the first object. The terminal then displays the transformed target organizational identification information instead of the original organizational identification information, thus hiding the original organizational identification information and improving the security of the organizational structure data. Here, the target organizational identification information refers to the first account system to which the first object's first account belongs, while the original organizational identification information is the organizational identification information under the native account system within the target application system.

[0177] Optionally, in this embodiment, the step "transforming the original organization identification information to obtain the target organization identification information of the target organizational structure data under the first account system" may include:

[0178] Based on the first account of the first object, the original organization identification information is encoded to obtain the encoded organization identification information;

[0179] Based on the encoded organization identification information, the target organization identification information of the target organizational structure data under the first account system is determined.

[0180] Specifically, in this embodiment, the first account of the first object can be encoded into the original organization identification information. The target organization identification information obtained in this way is for the first object, and the first account system can also be regarded as the account system corresponding to the first object. Based on the object identification information of the first object, different third-party development teams (i.e., external teams) can apply different account systems.

[0181] As can be seen from the above, this embodiment can obtain an application login request from a first object for a target application system through a server. The application login request includes a first account of the first object, and the target application system includes a first account system and a second account system. The first account is an account in the first account system. Login credentials for the terminal corresponding to the first object to log in to the target application system are generated based on the first account. The login credentials trigger the terminal corresponding to the first object to log in to the target application system. When a call request from the first object to a target component in the target application system is received, data filtering is performed on the component data corresponding to the target component based on the login credentials. The filtered component data is sent to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data. This application can generate login credentials for the first object based on the first account and restrict the data access scope of the first object based on the login credentials, realizing the function of performing business processing while ensuring data security in the target application system and reducing the risk of data leakage.

[0182] To better implement the above methods, embodiments of this application also provide a business data processing apparatus, such as... Figure 3 As shown, the business data processing device may include an acquisition unit 301, a generation unit 302, a login unit 303, a filtering unit 304, and a sending unit 305, as follows:

[0183] (1) Obtain unit 301;

[0184] The acquisition unit is used to acquire an application login request from a first object for a target application system. The application login request includes a first account of the first object. The target application system includes a first account system and a second account system. The first account is an account in the first account system.

[0185] (2) Generation unit 302;

[0186] The generation unit is used to generate login credentials for the terminal corresponding to the first object to log in to the target application system based on the first account.

[0187] Optionally, in some embodiments of this application, the generation unit may include an encryption subunit and a determination subunit, as follows:

[0188] The encryption subunit is used to encrypt the first account to obtain encrypted data.

[0189] The determination subunit is used to determine the login credentials for the terminal corresponding to the first object to log in to the target application system based on the encrypted data.

[0190] (3) Login unit 303;

[0191] The login unit is used to trigger the terminal corresponding to the first object to log in to the target application system based on the login credentials.

[0192] (4) Filter unit 304;

[0193] The filtering unit is used to filter the component data corresponding to the target component based on the login credentials when the first object receives a call request for the target component in the target application system.

[0194] Optionally, in some embodiments of this application, the filtering unit may include a verification subunit and a first filtering subunit, as follows:

[0195] The verification subunit is used to verify the validity of the login credentials when it receives a call request from the first object to a target component in the target application system.

[0196] The first filtering subunit is used to filter the component data corresponding to the target component when the login credential passes the validity check.

[0197] Optionally, in some embodiments of this application, the invocation request includes the login credentials;

[0198] The filtering unit may include a parsing subunit and a second filtering subunit, as follows:

[0199] The parsing subunit is used to parse the login credentials in the call request when it receives a call request from the first object to a target component in the target application system, so as to obtain the first account of the first object.

[0200] The second filtering subunit is used to filter the component data corresponding to the target component based on the account permissions corresponding to the first account.

[0201] Optionally, in some embodiments of this application, the filtering unit may include a search subunit and a third filtering subunit, as follows:

[0202] The search subunit is configured to perform a data search on the target component when it receives a search request from the first object for a target component in the target application system, and obtain the searched component data.

[0203] The third filtering subunit is used to filter the searched component data based on the login credentials.

[0204] (5) Transmitting unit 305;

[0205] The sending unit is used to send filtered component data to the terminal corresponding to the first object, so as to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data.

[0206] Optionally, in some embodiments of this application, the second account system is the account system of the target organizational structure in the target application system, the target organizational structure includes at least one organizational member; the components of the target application system include components corresponding to the organizational structure data.

[0207] Optionally, in some embodiments of this application, the filtered component data includes filtered target organizational structure data;

[0208] The transmitting unit may include an acquisition subunit, a transformation subunit, and a transmitting subunit, as follows:

[0209] The acquisition subunit is used to acquire the original organizational identification information of the target organizational structure data in the target application system;

[0210] The transformation subunit is used to transform the original organization identification information to obtain the target organization identification information of the target organizational structure data under the first account system.

[0211] The sending subunit is used to send the target organization identification information to the terminal corresponding to the first object.

[0212] Optionally, in some embodiments of this application, the transformation subunit may be specifically used to encode the original organization identification information based on the first account of the first object to obtain encoded organization identification information; and based on the encoded organization identification information, to determine the target organization identification information of the target organizational structure data under the first account system.

[0213] Optionally, in some embodiments of this application, the sending unit may further include a display subunit, as follows:

[0214] The display subunit is used to trigger the terminal corresponding to the first object to display the address book page corresponding to the target organizational structure data. The address book page includes the target organizational identification information of the target organizational structure data under the first account system.

[0215] As can be seen from the above, in this embodiment, the acquisition unit 301 can acquire the application login request of the first object for the target application system. The application login request includes the first account of the first object, and the target application system includes a first account system and a second account system. The first account is an account in the first account system. The generation unit 302 generates a login credential for the terminal corresponding to the first object to log in to the target application system based on the first account. The login unit 303 triggers the terminal corresponding to the first object to log in to the target application system based on the login credential. When a call request from the first object to a target component in the target application system is received, the filtering unit 304 filters the component data corresponding to the target component based on the login credential. The sending unit 305 sends the filtered component data to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data. This application can generate a login credential for the first object based on the first account and restrict the data access scope of the first object based on the login credential, realizing the function of performing business processing under the premise of ensuring data security in the target application system and reducing the risk of data leakage.

[0216] This application also provides an electronic device, such as... Figure 4 The diagram shows a structural schematic of an electronic device involved in an embodiment of this application. This electronic device can be a terminal or a server, specifically:

[0217] The electronic device may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will understand that... Figure 4 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0218] The processor 401 is the control center of the electronic device, connecting various parts of the device via various interfaces and lines. It executes various functions and processes data by running or executing software programs and / or modules stored in the memory 402, and by calling data stored in the memory 402. Optionally, the processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 401.

[0219] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.

[0220] The electronic device also includes a power supply 403 that supplies power to the various components. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 403 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0221] The electronic device may also include an input unit 404, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0222] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 401 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 402 according to the following instructions, and the processor 401 runs the applications stored in the memory 402 to realize various functions, as follows:

[0223] The system obtains an application login request from a first object for a target application system. The application login request includes a first account of the first object. The target application system includes a first account system and a second account system. The first account is an account within the first account system. A login credential for the terminal corresponding to the first object to log in to the target application system is generated based on the first account. The login credential triggers the terminal corresponding to the first object to log in to the target application system. When a call request from the first object to a target component in the target application system is received, data filtering is performed on the component data corresponding to the target component based on the login credential. The filtered component data is sent to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data.

[0224] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0225] As can be seen from the above, this embodiment can obtain an application login request from a first object for a target application system. The application login request includes a first account of the first object, and the target application system includes a first account system and a second account system. The first account is an account in the first account system. Login credentials for the first object's corresponding terminal to log in to the target application system are generated based on the first account. The login credentials trigger the first object's corresponding terminal to log in to the target application system. When a call request from the first object to a target component in the target application system is received, data filtering is performed on the component data corresponding to the target component based on the login credentials. The filtered component data is sent to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data. This application can generate login credentials for the first object based on the first account and restrict the data access scope of the first object based on the login credentials, realizing the function of performing business processing while ensuring data security in the target application system and reducing the risk of data leakage.

[0226] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0227] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute steps in any of the business data processing methods provided in embodiments of this application. For example, the instructions can execute the following steps:

[0228] The system obtains an application login request from a first object for a target application system. The application login request includes a first account of the first object. The target application system includes a first account system and a second account system. The first account is an account within the first account system. A login credential for the terminal corresponding to the first object to log in to the target application system is generated based on the first account. The login credential triggers the terminal corresponding to the first object to log in to the target application system. When a call request from the first object to a target component in the target application system is received, data filtering is performed on the component data corresponding to the target component based on the login credential. The filtered component data is sent to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data.

[0229] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0230] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0231] Since the instructions stored in the computer-readable storage medium can execute the steps of any of the business data processing methods provided in the embodiments of this application, the beneficial effects that any of the business data processing methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0232] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative implementations of the above-described business data processing aspects.

[0233] The above provides a detailed description of a business data processing method and related equipment provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A business data processing method, characterized in that, include: Obtain an application login request from a first object for a target application system. The application login request includes a first account of the first object. The target application system includes a first account system and a second account system. The first account is an account in the first account system. The first account system is the account system used by external personnel, and the second account system is the account system used by internal personnel of the target application system; Generate login credentials for the target application system based on the first account for the terminal corresponding to the first object. Based on the login credentials, the terminal corresponding to the first object is triggered to log in to the target application system; When a request to invoke a target component in the target application system is received from the first object, data filtering is performed on the component data corresponding to the target component based on the login credentials; the request to invoke the system includes the login credentials; the data filtering on the component data corresponding to the target component based on the login credentials includes: parsing the login credentials in the request to obtain the first account of the first object; and filtering the component data corresponding to the target component based on the account permissions corresponding to the first account. Sending filtered component data to the terminal corresponding to the first object to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data; the second account system is the account system of the target organizational structure in the target application system, and the target organizational structure includes at least one organizational member; the components of the target application system include components corresponding to the organizational structure data; the filtered component data includes filtered target organizational structure data; sending the filtered component data to the terminal corresponding to the first object includes: Obtain the original organization identification information of the target organizational structure data in the target application system; the original organization identification information is the organization identification information under the second account system; The original organization identification information is transformed to obtain the target organization identification information of the target organizational structure data under the first account system; The target organization identification information is sent to the terminal corresponding to the first object.

2. The method according to claim 1, characterized in that, The step of generating login credentials for the terminal corresponding to the first object to log in to the target application system based on the first account includes: The first account is encrypted to obtain encrypted data; Based on the encrypted data, the login credentials for the terminal corresponding to the first object to log in to the target application system are determined.

3. The method according to claim 1, characterized in that, When a request to invoke a target component in the target application system is received from the first object, data filtering is performed on the component data corresponding to the target component based on the login credentials, including: When a request to invoke a target component in the target application system is received from the first object, the login credentials are validated. When the login credentials pass the validity verification, the component data corresponding to the target component is filtered.

4. The method according to claim 1, characterized in that, The transformation process of the original organization identification information to obtain the target organization identification information of the target organizational structure data under the first account system includes: Based on the first account of the first object, the original organization identification information is encoded to obtain the encoded organization identification information; Based on the encoded organization identification information, the target organization identification information of the target organizational structure data under the first account system is determined.

5. The method according to claim 1, characterized in that, After sending the target organization identification information to the terminal corresponding to the first object, the method further includes: The terminal corresponding to the first object is triggered to display the address book page corresponding to the target organizational structure data. The address book page includes the target organizational identification information of the target organizational structure data under the first account system.

6. The method according to claim 1, characterized in that, When a request to invoke a target component in the target application system is received from the first object, data filtering is performed on the component data corresponding to the target component based on the login credentials, including: When a search request for a target component in the target application system is received from the first object, a data search is performed on the target component to obtain the searched component data; Based on the login credentials, the searched component data is filtered.

7. A business data processing device, characterized in that, include: The acquisition unit is used to acquire an application login request from a first object to a target application system. The application login request includes a first account of the first object. The target application system includes a first account system and a second account system. The first account is an account in the first account system. The first account system is the account system used by external personnel, and the second account system is the account system used by internal personnel of the target application system; The generation unit is configured to generate a login credential for the terminal corresponding to the first object to log in to the target application system based on the first account. The login unit is used to trigger the terminal corresponding to the first object to log in to the target application system based on the login credentials; A filtering unit is configured to, when receiving a call request from the first object to a target component in the target application system, filter the component data corresponding to the target component based on the login credentials; the call request includes the login credentials; the filtering unit is further configured to parse the login credentials in the call request to obtain the first account of the first object; and filter the component data corresponding to the target component based on the account permissions corresponding to the first account. The sending unit is used to send filtered component data to the terminal corresponding to the first object, so as to trigger the terminal corresponding to the first object to perform business processing based on the filtered component data; the second account system is the account system of the target organizational structure in the target application system, the target organizational structure includes at least one organizational member; the components of the target application system include the components corresponding to the organizational structure data; the filtered component data includes filtered target organizational structure data. The transmitting unit includes an acquisition subunit, a transformation subunit, and a transmitting subunit; The acquisition subunit is used to acquire the original organizational identification information of the target organizational structure data in the target application system; The original organization identification information is the organization identification information under the second account system; The transformation subunit is used to transform the original organization identification information to obtain the target organization identification information of the target organization structure data under the first account system. The sending subunit is used to send the target organization identification information to the terminal corresponding to the first object.

8. An electronic device, characterized in that, It includes a memory and a processor; the memory stores an application program, and the processor runs the application program within the memory to perform the operations in the business data processing method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to perform the steps of the business data processing method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the business data processing method according to any one of claims 1 to 6.

Images