WO2019047488A1 - 实现业务系统与多组件交互的方法、电子装置及存储介质 - Google Patents

实现业务系统与多组件交互的方法、电子装置及存储介质 Download PDF

Info

Publication number
WO2019047488A1
WO2019047488A1 PCT/CN2018/077420 CN2018077420W WO2019047488A1 WO 2019047488 A1 WO2019047488 A1 WO 2019047488A1 CN 2018077420 W CN2018077420 W CN 2018077420W WO 2019047488 A1 WO2019047488 A1 WO 2019047488A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
framework
service system
business
main
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/077420
Other languages
English (en)
French (fr)
Inventor
陆政
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Priority to US16/315,254 priority Critical patent/US20210334114A1/en
Priority to JP2018560950A priority patent/JP6751778B2/ja
Priority to SG11201810229WA priority patent/SG11201810229WA/en
Publication of WO2019047488A1 publication Critical patent/WO2019047488A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/41—User authentication where a single sign-on provides access to a plurality of computers
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04842—Selection of displayed objects or displayed text elements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/38—Creation or generation of source code for implementing user interfaces
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities

Definitions

  • the present invention relates to a method for constructing an intermediate platform, and in particular, to a method, an electronic device, and a storage medium for implementing a business system and interacting with multiple components.
  • the business system and the common components are put into the same framework to realize the interaction between the business system and the common components, but this way is too intrusive for the business system (such as It will change the domain name of the user accessing the business system, the user needs to apply for the framework permission, etc.), and many business systems are unwilling to accept it.
  • the technical problem to be solved by the present application is to overcome the problem that the intrusion of the business system is too high caused by the interaction between the business system and the common components in the prior art, and a method for realizing the interaction between the business system and the multi-component is proposed.
  • the electronic device and the storage medium embed the component into the business system in the form of a similar plug-in, so as to realize a quick connection between the business system and each component, and the development workload is small.
  • a method for implementing a business system and interacting with a plurality of components includes the following steps: S1: configuring at least one component in a framework system; S2, displaying a framework system configured with components on a front page of the main service system; S3, By clicking on the component displayed on the front-end web page of the main business system, the user jumps from the main business system and logs in to the front-end web page of another business system defined by the component being clicked.
  • An electronic device includes a memory and a processor, wherein the memory stores a system that can be executed by the processor to implement a business system and interact with multiple components, and the system for implementing a business system interacting with multiple components includes: a combination module For defining a component and managing the component; a front-end display module for displaying the combined component on the front-end page of the main service system; and detecting the access module for detecting the display on the front-end page of the main service system Once the component is clicked, it opens and logs into the front-end web page of another business system defined by the component being clicked.
  • a computer readable storage medium having stored therein a system for implementing a business system interacting with a plurality of components, the system implementing the business system interacting with the plurality of components being executable by at least one processor to enable
  • the at least one processor performs the following steps: S1, configuring at least one component in a framework system; S2, displaying a framework system configured with components on a front page of the main service system; S3, displaying the main service by clicking A component on the system front-end web page that the user jumps from the main business system and logs into the front-end web page of another business system defined by the component being clicked.
  • the positive progress of the present application is that the present application introduces a framework system to implement a docking interaction between a main service system and each component, and the framework system solves the standard problem, so that when the business system interacts with each component, it only needs to interface with the framework system. Once, you can quickly dock other components.
  • FIG. 1 is a schematic diagram showing the hardware architecture of an embodiment of an electronic device of the present application.
  • FIG. 2 is a schematic diagram of a program module of an embodiment of a system for implementing a business system and multi-component interaction in an electronic device of the present application.
  • FIG. 3 is a flow chart showing an embodiment of a method for implementing a business system interaction with a multi-component according to the present application
  • FIG. 4 is a flow chart showing still another embodiment of a method for implementing a business system interaction with a multi-component according to the present application
  • FIG. 5 is a flow chart showing a method for requesting a login to a network telephony tool from a main service system by implementing a method for interacting a business system with a multi-component using the present application;
  • FIG. 6 is a flow chart showing a method for requesting a business system to interact with a multi-component using the present application to request login to another service system from a primary service system.
  • the present application proposes an electronic device.
  • the electronic device 1 is an apparatus capable of automatically performing numerical calculation and/or information processing in accordance with an instruction set or stored in advance.
  • the electronic device 2 can be a smartphone, a tablet, a laptop, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including a stand-alone server, or a server cluster composed of multiple servers).
  • the electronic device 2 includes at least, but not limited to, a memory 21, a processor 22, a network interface 23, and a system 20 that enables a business system to interact with multiple components via a system bus. among them:
  • the memory 21 includes at least one type of computer readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (eg, SD or DX memory, etc.), a random access memory (RAM), Static Random Access Memory (SRAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, and the like.
  • the memory 21 may be an internal storage unit of the electronic device 2, such as a hard disk or a memory of the electronic device 2.
  • the memory 21 may also be an external storage device of the electronic device 2, such as a plug-in hard disk equipped on the electronic device 2, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, flash card, etc.
  • the memory 21 can also include both the internal storage unit of the electronic device 2 and its external storage device.
  • the memory 21 is generally used to store an operating system installed on the electronic device 2 and various types of application software, such as the program code of the system 20 for implementing the interaction between the business system and the multi-component. Further, the memory 21 can also be used to temporarily store various types of data that have been output or are to be output.
  • the processor 22 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments.
  • the processor 22 is typically used to control the overall operation of the electronic device 2, such as performing control and processing associated with data interaction or communication with the electronic device 2.
  • the processor 22 is configured to run program code or process data stored in the memory 21, such as running the system 20 for implementing a business system to interact with multiple components.
  • the network interface 23 may comprise a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the electronic device 2 and other electronic devices.
  • the network interface 23 is configured to connect the electronic device 2 to an external terminal through a network, establish a data transmission channel, a communication connection, and the like between the electronic device 2 and an external terminal.
  • the network may be an intranet, an Internet, a Global System of Mobile communication (GSM), a Wideband Code Division Multiple Access (WCDMA), a 4G network, or a 5G network.
  • Wireless or wired networks such as network, Bluetooth, Wi-Fi, etc.
  • Figure 1 only shows the electronic device 2 with the components 21-23, but it should be understood that not all illustrated components may be implemented and that more or fewer components may be implemented instead.
  • system 20 for implementing a business system interacting with multiple components stored in the memory 21 can be executed by at least one processor 22 to implement the following steps:
  • At least one component is configured in a framework system.
  • one or more components can be configured in a framework system as needed, depending on the needs of the business person.
  • a business person will need a common tool (the generic tool described here can also be understood as a business system, which is represented by another business system in the claims), such as VoIP tools and web chat tools, and may also need Use other business systems than the main business system.
  • the framework system is displayed as a visual design interface, and the at least one component is configured in a framework system, specifically, dragging various icons representing components into a visual design interface representing the framework system, And stay at a specific location in the visual design interface.
  • the framework system configured with components is displayed on the front page of the main business system.
  • the framework system configured with components is displayed on the front page of the main service system in the form of a floating toolbar, or can be displayed on the front page of the main service system in the form of a menu bar embedded in the main service system.
  • the floating toolbar When the floating toolbar is displayed, it is ensured that the floating toolbar is always located at the top of the current page, and the floating position may be the middle of the front page of the main business system on the right side, the left side or the bottom, ensuring that the information area does not It is blocked by the floating toolbar, so as not to affect the use of business personnel.
  • the floating toolbar can adjust the display position by the business personnel using the main business system, so that the display position of the floating toolbar is more convenient for the business person's own usage habits, and is more humanized. Adjusting the display position as described herein may be implemented by dragging the floating toolbar.
  • the system described in this embodiment realizes the combination of components on the framework system by dragging and dropping icons, and the operation is simple and convenient; in addition, the display position of the components on the front-end webpage is flexible and can meet the different needs of the business personnel.
  • the system 20 for implementing the interaction between the service system and the multi-component is executed by at least one processor 22, and the following steps are implemented:
  • the framework system configures the main service system information and the clicked component information
  • the front-end webpage of the main business system loads the framework system file umaplite.js provided by the framework system and the unified cross-domain file cross-domain.js through the HTTP protocol;
  • the main business system performs standard initialization on the framework system, and transmits the main service system authentication information and the required parameters of the clicked component to the framework system;
  • the framework system verifies whether the service login request is legal, and if the verification passes, returns the clicked component information configured by the framework system, and the framework system initializes components configured on the framework system;
  • the framework system requests the clicked component to perform the free authentication through the jsonp request. If the authentication is passed, the owner business system interacts with the clicked component through the unified cross-domain technology, so that the user jumps from the main service system and logs in to the user. The front-end web page of another business system defined by the component being clicked.
  • the exemption authentication described herein specifically means that the framework system directly obtains the account and password used by the service personnel to log in to the main service system as the account and password of another service system defined by the login component, that is, when When the service personnel jumps from the main service system to log in to other service systems, the service personnel do not need to re-enter the account and password for verification, but are automatically retrieved by the framework system.
  • the component described herein may be a general tool such as a network phone or a network chat, or may be another service system similar to the main service system; for the universal tool, the call may be performed without login authentication, but For other business systems, login authentication is required because it may involve permission issues.
  • the framework system configures the primary service system information and the network telephony component information
  • the front-end webpage of the main business system loads the framework system file umaplite.js provided by the framework system and the unified cross-domain file cross-domain.js through the HTTP protocol;
  • the main service system performs standard initialization on the framework system, and transmits the main service system authentication information and the required parameters of the network telephony component to the framework system;
  • the framework system verifies whether the service login request is legal, and returns the information of the clicked component configured by the framework system after the verification is passed;
  • the framework system initializes components including the network phone configured on the frame system;
  • the framework system requests the VoIP component to log in through jsonp;
  • the main service system interacts with the network telephony component through unified cross-domain technology, so that the user directly opens the network telephony window from the main service system.
  • the framework system configures the primary service system information and component information of the another service system
  • the front-end webpage of the main business system loads the framework system file umaplite.js provided by the framework system and the unified cross-domain file cross-domain.js through the HTTP protocol;
  • the main service system performs standard initialization on the framework system, and transmits the main service system authentication information and the required parameters of the other service system component to the framework system;
  • the framework system verifies whether the service login request is legal, and returns the component information of the another service system configured by the framework system after the verification is passed;
  • the framework system initializes components on the framework system including the other service system;
  • the framework system requests the other service system component to perform the free authentication by jsonp. If the authentication is passed, the next step is performed, otherwise the login failure information is returned;
  • the main service system interacts with the VoIP component through unified cross-domain technology, so that the user jumps from the main service system and logs in to the front-end webpage of another service system.
  • the calling step of accessing other components from the main service system is described in detail in this embodiment, and the cross-domain access object described herein may be a general-purpose tool system or another service system similar to the main service system. A wide range.
  • cross-domain access when cross-domain access is performed by the main business system for different business systems, it is determined whether the login authentication is required according to whether the component requires access rights, such as a universal tool such as a network telephone tool, and no login authentication is required, and if To cross-domain access is another business system, you need to log in to the authentication, and it is very convenient to use the free authentication, which avoids the trouble of the business personnel repeatedly inputting the account and password.
  • access rights such as a universal tool such as a network telephone tool
  • system 20 for implementing a business system interaction with multiple components may also be divided into one or more program modules, and the one or more program modules are stored in the memory 21 . And executed by one or more processors (the processor 22 in this embodiment) to complete the application.
  • the program module referred to in the present application refers to a series of computer program instruction segments capable of performing a specific function.
  • FIG. 2 shows a schematic diagram of a program module of an embodiment of the system 20 for implementing a service system interaction with multiple components.
  • the system 20 for implementing a service system interacting with multiple components may be divided into a combination module. 201.
  • the functions or operation steps implemented by the program modules 201-203 are similar to the above, and are not described in detail herein, exemplarily:
  • the combination module 201 is used to define a combination component and manage the component
  • the front-end display module 202 is configured to display the combined component on a front-end page of the main service system
  • the detecting access module 203 is configured to detect that the component displayed on the front end page of the main service system is clicked, open and log in to the front end webpage of another business system defined by the clicked component.
  • the present application proposes a method for implementing a business system interaction with multiple components.
  • the method for implementing a service system to interact with multiple components includes the following steps:
  • At least one component is configured in a framework system.
  • one or more components can be configured in a framework system as needed, depending on the needs of the business person.
  • a business person will need a common tool (the generic tool described here can also be understood as a business system, which is represented by another business system in the claims), such as VoIP tools and web chat tools, and may also need Use other business systems than the main business system.
  • the framework system is displayed as a visual design interface, and the at least one component is configured in a framework system, specifically, dragging various icons representing components into a visual design interface representing the framework system, And stay at a specific location in the visual design interface.
  • S2 Display the frame system configured with components on the front page of the main business system.
  • the framework system configured with components is displayed on the front page of the main service system in the form of a floating toolbar, or can be displayed on the front page of the main service system in the form of a menu bar embedded in the main service system.
  • the floating toolbar When the floating toolbar is displayed, it is ensured that the floating toolbar is always located at the top of the current page, and the floating position may be the front side of the main business system on the right side, the left side or the bottom side, ensuring that the information area does not It is blocked by the floating toolbar, so as not to affect the use of business personnel.
  • the floating toolbar can adjust the display position by the business personnel using the main business system, so that the display position of the floating toolbar is more convenient for the business person's own usage habits, and is more humanized. Adjusting the display position as described herein may be implemented by dragging the floating toolbar.
  • the components are standardized and packaged before use, and then the components are combined on the frame system by means of icon dragging, the operation is simple and convenient, and the workload of system development is greatly reduced;
  • the display position on the front-end webpage is flexible, and the display position can be determined by the business personnel in the later use process, which satisfies the different needs of the business personnel.
  • step 3 is provided with the following sub-steps:
  • the framework system configures the primary service system information and the clicked component information.
  • the front-end webpage of the main service system loads the framework system file umaplite.js provided by the framework system and the unified cross-domain file cross-domain.js through the HTTP protocol;
  • the main service system performs standard initialization on the framework system, and transmits the main service system authentication information and the required parameters of the clicked component to the framework system;
  • step S35 the framework system verifies that the service login request is legal, if the verification is passed, returns the clicked component information configured by the framework system, and then proceeds to step S36;
  • the framework system initializes components configured on the framework system
  • the exemption authentication in step S37 specifically means that the framework system directly obtains the account and password used by the service personnel to log in to the main service system as the account and password of another service system defined by the login component. That is, when the business personnel jumps from the main business system to log in to other business systems, the business personnel need not re-enter the account and password for verification, and the framework system automatically retrieves them.
  • the main service system interacts with the clicked component by using the unified cross-domain technology, so that the user jumps from the main service system and logs in to the front-end webpage of another service system defined by the clicked component.
  • the component described herein may be a general tool such as a network phone or a network chat, or may be another service system similar to the main service system; for the universal tool, the call may be performed without login authentication, but For other business systems, login authentication is required because it may involve permission issues.
  • the framework system configures the primary service system information and the network telephony component information
  • the front-end webpage of the main service system loads the framework system file umaplite.js provided by the framework system and the unified cross-domain file cross-domain.js through the HTTP protocol;
  • the main service system performs standard initialization on the framework system, and transmits the main service system authentication information and the required parameters of the network telephony component to the framework system;
  • the framework system verifies whether the service login request is legal, and returns the returned component information configured by the framework system after the verification is passed;
  • the framework system initializes components including the network phone configured on the framework system;
  • the framework system requests the VoIP component to log in through jsonp;
  • the main service system interacts with the network telephony component through the unified cross-domain technology, so that the user directly opens the network telephony window from the main service system.
  • the framework system configures the primary service system information and component information of the another service system
  • the front-end webpage of the main business system loads the framework system file umaplite.js provided by the framework system and the unified cross-domain file cross-domain.js through the HTTP protocol;
  • the main service system performs standard initialization on the framework system, and transmits the main service system authentication information and the required parameters of the another service system component to the framework system;
  • the framework system verifies whether the service login request is legal, and returns the component information of the another service system configured by the framework system after the verification is passed;
  • the framework system requests the other service system component to perform the certificate-free authentication through jsonp. If the authentication is passed, the next step is performed, otherwise the login failure information is returned;
  • the S38" and the main service system interact with the network telephony component through the unified cross-domain technology, so that the user jumps from the main service system and logs in to the front page of another service system.
  • the interaction method described in this embodiment elaborates the calling procedure of accessing other components from the main service system across domains, and the framework system formulates and reviews the access standard through configuration management and initialization components, so that each component accesses according to the standard;
  • the main service system realizes interaction with each component through unified cross-domain technology.
  • the cross-domain access object can be a general-purpose tool type system or other business system similar to the main business system, and has a wide application range.
  • the system of the universal tool class does not need to be directly authenticated by the login authentication, and the service system that needs to log in to the authentication system is freed from the authentication, thereby avoiding the business personnel repeatedly inputting the account and password.
  • the trouble has greatly simplified the operational steps of the business personnel.
  • the present application further provides a computer readable storage medium on which the system 20 for implementing a business system interacting with multiple components is stored, and the system 20 for implementing a business system interacting with multiple components is one or When the plurality of processors are executed, the above-described method of implementing the business system and multi-component interaction or the operation of the electronic device is implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)
  • Debugging And Monitoring (AREA)

Abstract

本申请公开了一种实现业务系统与多组件交互的方法，属于系统间的对接方法领域。一种实现业务系统与多组件交互的方法，包括如下步骤：S1、将至少一个组件配置在一个框架系统中；S2、将配置有组件的框架系统显示在主业务系统的前端网页上；S3、通过点击显示在主业务系统前端网页上的组件，用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。本方法引入框架系统来实现主业务系统与各组件之间的对接交互，由框架系统来解决标准问题，使得业务系统与各组件对接交互时，只要和框架系统对接一次，就可以快速对接其他各种组件，组件也只要对接一次框架系统，大大节省了开发工作量。

Description

实现业务系统与多组件交互的方法、电子装置及存储介质
本申请申明享有2017年9月11日递交的申请号为201710814312.X、名称为“实现业务系统与多组件交互的方法、电子装置及存储介质”的中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及一种中间平台的构建方法，特别涉及一种实现业务系统与多组件交互的方法、电子装置及存储介质。
背景技术
远程客户接触(销售、服务)领域，不同的业务场景(如产、寿、投、贷、银等)业务流程不一样，业务系统都大不一样，但是都会用到一些通用的组件，如软电话、视频、音频、客户画像、电子地图、知识库、机器人等组件。
最早，采用每个业务系统分别与这些组件对接的方法进行交互，但由于技术不一样、标准不一致，业务系统和组件都需要进行一些定制化开发，工作量大、沟通效率低、后期维护成本高。
为简化开发和后期维护的工作量，后来采用将业务系统和各通用组件放在同一个框架下来实现业务系统和各通用组件之间的交互，但这种方式对业务系统侵入性太高(如会改变用户访问业务系统的域名，用户需要申请框架权限等)，很多业务系统不愿意接受。
因此，如何方便业务系统与各种组件实现对接交互，同时又能降低开发和维护的工作量，成为亟待解决的技术问题。
发明内容
本申请要解决的技术问题是为了克服现有技术中实现业务系统和各通用组件之间的交互导致的对业务系统侵入性太高的问题，提出了一种实现业务系统与多组件交互的方法、电子装置及存储介质，将组件以类似插件的形式嵌入到业务系统中，以实现业务系统与各组件之间的快速对接，且开发工作量小。
本申请是通过下述技术方案来解决上述技术问题：
一种实现业务系统与多组件交互的方法，包括如下步骤：S1、将至少一个组件配置在一个框架系统中；S2、将配置有组件的框架系统显示在主业务系统的前端网页上；S3、通过点击显示在主业务系统前端网页上的组件，用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
一种电子装置，包括存储器和处理器，所述存储器上存储有可被所述处理器执行的实现业务系统与多组件交互的系统，所述实现业务系统与多组件交互的系统包括：组合模块，用于定义组合组件，并管理组件；前端展示模块，用于将组合后的组件显示在主业务系统的前端页面上；检测接入模块，用于检测到显示在主业务系统的前端页面上的组件被点击后，打开并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
一种计算机可读存储介质，所述计算机可读存储介质内存储有实现业务系统与多组件交互的系统，所述实现业务系统与多组件交互的系统可被至少一个处理器所执行，以使所述至少一个处理器执行以下步骤：S1、将至少一个组件配置在一个框架系统中；S2、将配置有组件的框架系统显示在主业务系统的前端网页上；S3、通过点击显示在主业务系统前端网页上的组件，用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
本申请的积极进步效果在于：本申请引入框架系统来实现主业务系统与 各组件之间的对接交互，由框架系统来解决标准问题，使得业务系统与各组件对接交互时，只要和框架系统对接一次，就可以快速对接其他各种组件。
附图说明
图1示出了本申请电子装置一实施例的硬件架构示意图；
图2示出了本申请电子装置中实现业务系统与多组件交互的系统一实施例的程序模块示意图。
图3示出了本申请实现业务系统与多组件交互的方法一实施例的流程图；
图4示出了本申请实现业务系统与多组件交互的方法又一实施例的流程图；
图5示出了采用本申请实现业务系统与多组件交互的方法从主业务系统请求登录网络电话工具的流程图；
图6示出了采用本申请实现业务系统与多组件交互的方法从主业务系统请求登录另一业务系统的流程图。
具体实施方式
下面通过实施例的方式进一步说明本申请，但并不因此将本申请限制在所述的实施例范围之中。
首先，本申请提出了一种电子装置。
参阅图1所示，是本申请电子装置一实施例的硬件架构示意图。本实施例中，所述电子装置1是一种能够按照事先设定或者存储的指令，自动进行数值计算和/或信息处理的设备。例如，可以是智能手机、平板电脑、笔记本电脑、台式计算机、机架式服务器、刀片式服务器、塔式服务器或机柜式服务器(包括独立的服务器，或者多个服务器所组成的服务器集群)等。如图所示，所述电子装置2至少包括，但不限于，可通过系统总线相互通信连接 存储器21、处理器22、网络接口23、以及实现业务系统与多组件交互的系统20。其中：
所述存储器21至少包括一种类型的计算机可读存储介质，所述可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中，所述存储器21可以是所述电子装置2的内部存储单元，例如该电子装置2的硬盘或内存。在另一些实施例中，所述存储器21也可以是所述电子装置2的外部存储设备，例如该电子装置2上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。当然，所述存储器21还可以既包括所述电子装置2的内部存储单元也包括其外部存储设备。本实施例中，所述存储器21通常用于存储安装于所述电子装置2的操作系统和各类应用软件，例如所述实现业务系统与多组件交互的系统20的程序代码等。此外，所述存储器21还可以用于暂时地存储已经输出或者将要输出的各类数据。
所述处理器22在一些实施例中可以是中央处理器(Central Processing Unit，CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。该处理器22通常用于控制所述电子装置2的总体操作，例如执行与所述电子装置2进行数据交互或者通信相关的控制和处理等。本实施例中，所述处理器22用于运行所述存储器21中存储的程序代码或者处理数据，例如运行所述的实现业务系统与多组件交互的系统20等。
所述网络接口23可包括无线网络接口或有线网络接口，该网络接口23通常用于在所述电子装置2与其他电子装置之间建立通信连接。例如，所述网络接口23用于通过网络将所述电子装置2与外部终端相连，在所述电子装置2与外部终端之间的建立数据传输通道和通信连接等。所述网络可以是 企业内部网(Intranet)、互联网(Internet)、全球移动通讯系统(Global System of Mobile communication，GSM)、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)、4G网络、5G网络、蓝牙(Bluetooth)、Wi-Fi等无线或有线网络。
需要指出的是，图1仅示出了具有部件21-23的电子装置2，但是应理解的是，并不要求实施所有示出的部件，可以替代的实施更多或者更少的部件。
在一实施例中，存储于存储器21中的实现业务系统与多组件交互的系统20可被至少一处理器22所执行，以实现如下步骤：
首先，将至少一个组件配置在一个框架系统中。
举例来说，根据需要可以在一个框架系统中配置一个或多个组件，具体由业务人员的需求而定。通常来说，一个业务人员会需要通用工具(这里所述通用工具也可理解为业务系统，在权利要求书中统一用另一业务系统表示)，比如网络电话工具和网络聊天工具，还可能需要使用除主业务系统以外的其他业务系统。
在配置之前，需要先将这些通用工具及业务系统封装成组件，封装后形成的组件以图标的形式进行显示，比如网络电话工具显示为电话机图形的图标。
所述框架系统显示为一种可视化的设计界面，所述将至少一个组件配置在一个框架系统中，具体而言，就是将代表组件的各种图标拖拽到代表框架系统的可视化设计界面中，并停留在该可视化设计界面的特定位置。
接着，将配置有组件的框架系统显示在主业务系统的前端网页上。
具体地，配置有组件的框架系统以悬浮工具栏的形式显示在主业务系统的前端网页上，也可以嵌入到主业务系统的菜单栏中的形式显示在主业务系统的前端网页上。
采用悬浮工具栏显示时，保证该悬浮工具栏始终位于当前页面并置顶， 所述悬浮的位置可以是主业务系统的前端网页靠右侧、靠左侧或靠底部的中间，保证信息区域不会被所述悬浮工具栏所遮挡，从而不影响业务人员的使用。
优选地，所述悬浮工具栏可由使用主业务系统的业务人员调整显示位置，以使悬浮工具栏的显示位置更方便业务人员自身的使用习惯，更加人性化。这里所述调整显示位置可以是通过拖拽所述悬浮工具栏的方式来实现。
最后，通过点击显示在主业务系统前端网页上的组件，用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
本实施例中所述的系统，通过拖拽图标的方式实现组件在框架系统上的组合，操作简单方便；另外，组件在前端网页上的显示位置灵活多变，可以满足业务人员的不同需求。
基于上述实施例，在又一实施例中，在实现所述通过点击显示在主业务系统前端网页上的组件，用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上的步骤时，所述实现业务系统与多组件交互的系统20被至少一处理器22所执行，具体实现如下步骤：
第一步，点击显示在主业务系统前端网页上的组件，以向框架系统发起登录所述组件所定义的另一业务系统的业务登录请求；
第二步，框架系统配置所述主业务系统信息和被点击的组件信息；
第三步，主业务系统的前端网页通过HTTP协议加载框架系统提供的框架系统文件umaplite.js和统一跨域文件cross-domain.js；
第四步，主业务系统对框架系统进行标准初始化，并向框架系统传入主业务系统认证信息和被点击的组件的所需参数；
第五步，框架系统验证业务登录请求是否合法，若验证通过，返回框架系统配置的所述被点击的组件信息，并且框架系统初始化配置在所述框架系统上的组件；
第六步，框架系统通过jsonp请求被点击的组件进行免登认证，若认证 通过则执主业务系统通过统一跨域技术与被点击的组件进行交互，实现用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
具体地，这里所述免登认证具体是指，框架系统直接获取业务人员登录所述主业务系统时使用的账号和密码作为登录被点击组件所定义的另一业务系统的账号和密码，即当业务人员从主业务系统跳转登录到其他业务系统时，无需该业务人员重新输入账号和密码进行验证，而由框架系统自动调取。
需要说明的是，这里所述组件可以是如网络电话、网络聊天等通用工具，也可以是类似于主业务系统的其他业务系统；针对所述通用工具，其调用可以无需登录认证，而针对所述其他业务系统，由于可能涉及权限问题，需要登录认证。
下面分别以从主业务系统跳转登录到网络电话工具和跳转登录到另一业务系统加以具体说明：
(一)从主业务系统请求登录网络电话工具的流程如下：
1、点击显示在主业务系统前端网页上的悬浮工具栏中的网络电话图标，向框架系统发起登录所述网络电话的业务登录请求；
2、框架系统配置所述主业务系统信息和所述网络电话组件信息；
3、主业务系统的前端网页通过HTTP协议加载框架系统提供的框架系统文件umaplite.js和统一跨域文件cross-domain.js；
4、主业务系统对框架系统进行标准初始化，并向框架系统传入主业务系统认证信息和网络电话组件的所需参数；
5、框架系统验证业务登录请求是否合法，验证通过后返回框架系统配置的所述被点击的组件信息；
6、框架系统初始化配置在所述框架系统上的包括网络电话在内的各组件；
7、框架系统通过jsonp请求网络电话组件进行登录；
8、主业务系统通过统一跨域技术与网络电话组件进行交互，实现用户从主业务系统直接打开网络电话窗口。
(二)从主业务系统请求登录到另一业务系统的流程如下：
1、点击显示在主业务系统前端网页上的悬浮工具栏中的代表另一业务系统的图标，向框架系统发起登录所述另一业务系统的业务登录请求；
2、框架系统配置所述主业务系统信息和所述另一业务系统的组件信息；
3、主业务系统的前端网页通过HTTP协议加载框架系统提供的框架系统文件umaplite.js和统一跨域文件cross-domain.js；
4、主业务系统对框架系统进行标准初始化，并向框架系统传入主业务系统认证信息和所述另一业务系统组件的所需参数；
5、框架系统验证业务登录请求是否合法，验证通过后返回框架系统配置的所述另一业务系统的组件信息；
6、框架系统初始化配置在所述框架系统上的包括所述另一业务系统在内的各组件；
7、框架系统通过jsonp请求所述另一业务系统组件进行免登认证，若认证通过，执行下一步，否则返回登录失败信息；
8、主业务系统通过统一跨域技术与网络电话组件进行交互，实现用户从主业务系统跳转并登录另一业务系统的前端网页上。
通过本实施例详细阐述了从主业务系统跨域访问其他组件的调用步骤，而且这里所述的跨域访问对象即可以是通用工具类系统，也可以是类似主业务系统的其他业务系统，适用范围很广。
而且，特别针对不同的业务系统被主业务系统进行跨域访问时，会根据组件是否需要访问权限而判断是否需要登录认证，比如像网络电话工具之类的通用工具，就无需登录认证，而如果要跨域访问的是另一业务系统，则需要登录认证，而且采用的是十分方便的免登认证，避免了业务人员反复输入账号和密码的麻烦。
需要说明的是，在其他的实施例中，所述实现业务系统与多组件交互的系统20还可以被分割为一个或者多个程序模块，所述一个或者多个程序模块被存储于存储器21中，并由一个或多个处理器(本实施例为处理器22)所执行，以完成本申请。其中，本申请所称的程序模块是指能够完成特定功能的一系列计算机程序指令段。
例如，图2示出了所述实现业务系统与多组件交互的系统20一实施例的程序模块示意图，该实施例中，所述实现业务系统与多组件交互的系统20可以被分割为组合模块201、前端展示模块202、检测接入模块203。其中，程序模块201-203所实现的功能或操作步骤均与上文类似，此处不再详述，示例性地：
组合模块201用于定义组合组件，并管理组件；
前端展示模块202用于将组合后的组件显示在主业务系统的前端页面上；
检测接入模块203用于检测到显示在主业务系统的前端页面上的组件被点击后，打开并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
其次，本申请提出一种实现业务系统与多组件交互的方法。
再一实施例中，如图3所示，所述的实现业务系统与多组件交互的方法，包括如下步骤：
S1、将至少一个组件配置在一个框架系统中。
举例来说，根据需要可以在一个框架系统中配置一个或多个组件，具体由业务人员的需求而定。通常来说，一个业务人员会需要通用工具(这里所述通用工具也可理解为业务系统，在权利要求书中统一用另一业务系统表示)，比如网络电话工具和网络聊天工具，还可能需要使用除主业务系统以外的其他业务系统。
在配置之前，需要先将这些通用工具及业务系统封装成组件，封装后形 成的组件以图标的形式进行显示，比如网络电话工具显示为电话机图形的图标。
所述框架系统显示为一种可视化的设计界面，所述将至少一个组件配置在一个框架系统中，具体而言，就是将代表组件的各种图标拖拽到代表框架系统的可视化设计界面中，并停留在该可视化设计界面的特定位置。
S2、将配置有组件的框架系统显示在主业务系统的前端网页上。
具体地，配置有组件的框架系统以悬浮工具栏的形式显示在主业务系统的前端网页上，也可以嵌入到主业务系统的菜单栏中的形式显示在主业务系统的前端网页上。
采用悬浮工具栏显示时，保证该悬浮工具栏始终位于当前页面并置顶，所述悬浮的位置可以是主业务系统的前端网页靠右侧、靠左侧或靠底部的中间，保证信息区域不会被所述悬浮工具栏所遮挡，从而不影响业务人员的使用。
优选地，所述悬浮工具栏可由使用主业务系统的业务人员调整显示位置，以使悬浮工具栏的显示位置更方便业务人员自身的使用习惯，更加人性化。这里所述调整显示位置可以是通过拖拽所述悬浮工具栏的方式来实现。
S3、通过点击显示在主业务系统前端网页上的组件，用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
本实施例中所述的方法，组件在使用前先进行了标准化封装，然后采用图标拖拽的方式实现组件在框架系统上的组合，操作简单方便，大大降低了系统开发的工作量；另外，组件组合后，在前端网页上的显示位置灵活多变，并可以在后期使用过程中，由业务人员自行确定显示的位置，满足了业务人员的不同需求。
基于上述实施例，在又一实施例中，如图4所示，所述步骤3具备包括以下分步骤：
S31、点击显示在主业务系统前端网页上的组件，以向框架系统发起登 录所述组件所定义的另一业务系统的业务登录请求；
S32、框架系统配置所述主业务系统信息和被点击的组件信息；
S33、主业务系统的前端网页通过HTTP协议加载框架系统提供的框架系统文件umaplite.js和统一跨域文件cross-domain.js；
S34、主业务系统对框架系统进行标准初始化，并向框架系统传入主业务系统认证信息和被点击的组件的所需参数；
S35、框架系统验证业务登录请求是否合法，若验证通过，返回框架系统配置的所述被点击的组件信息，并则执行步骤S36；
S36、框架系统初始化配置在所述框架系统上的组件；
S37、框架系统通过jsonp请求被点击的组件进行免登认证，若认证通过则执行S38；
具体地，步骤S37中所述免登认证具体是指，框架系统直接获取业务人员登录所述主业务系统时使用的账号和密码作为登录被点击组件所定义的另一业务系统的账号和密码，即当业务人员从主业务系统跳转登录到其他业务系统时，无需该业务人员重新输入账号和密码进行验证，而由框架系统自动调取。
S38、主业务系统通过统一跨域技术与被点击的组件进行交互，实现用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
需要说明的是，这里所述组件可以是如网络电话、网络聊天等通用工具，也可以是类似于主业务系统的其他业务系统；针对所述通用工具，其调用可以无需登录认证，而针对所述其他业务系统，由于可能涉及权限问题，需要登录认证。
下面分别以从主业务系统跳转登录到网络电话工具和跳转登录到另一业务系统加以具体说明：
(一)如图5所示，从主业务系统请求登录网络电话工具的步骤流程如 下：
S31’、点击显示在主业务系统前端网页上的悬浮工具栏中的网络电话图标，向框架系统发起登录所述网络电话的业务登录请求；
S32’、框架系统配置所述主业务系统信息和所述网络电话组件信息；
S33’、主业务系统的前端网页通过HTTP协议加载框架系统提供的框架系统文件umaplite.js和统一跨域文件cross-domain.js；
S34’、主业务系统对框架系统进行标准初始化，并向框架系统传入主业务系统认证信息和网络电话组件的所需参数；
S35’、框架系统验证业务登录请求是否合法，验证通过后返回框架系统配置的所述被点击的组件信息；
S36’、框架系统初始化配置在所述框架系统上的包括网络电话在内的各组件；
S37’、框架系统通过jsonp请求网络电话组件进行登录；
S38’、主业务系统通过统一跨域技术与网络电话组件进行交互，实现用户从主业务系统直接打开网络电话窗口。
(二)如图6所示，从主业务系统请求登录到另一业务系统的步骤流程如下：
S31”、点击显示在主业务系统前端网页上的悬浮工具栏中的代表另一业务系统的图标，向框架系统发起登录所述另一业务系统的业务登录请求；
S32”、框架系统配置所述主业务系统信息和所述另一业务系统的组件信息；
S33”、主业务系统的前端网页通过HTTP协议加载框架系统提供的框架系统文件umaplite.js和统一跨域文件cross-domain.js；
S34”、主业务系统对框架系统进行标准初始化，并向框架系统传入主业务系统认证信息和所述另一业务系统组件的所需参数；
S35”、框架系统验证业务登录请求是否合法，验证通过后返回框架系统 配置的所述另一业务系统的组件信息；
S36”、框架系统初始化配置在所述框架系统上的包括所述另一业务系统在内的各组件；
S37”、框架系统通过jsonp请求所述另一业务系统组件进行免登认证，若认证通过，执行下一步，否则返回登录失败信息；
S38”、主业务系统通过统一跨域技术与网络电话组件进行交互，实现用户从主业务系统跳转并登录另一业务系统的前端网页上。
本实施例中所述的交互方法详细阐述了从主业务系统跨域访问其他组件的调用步骤，框架系统通过配置化管理和初始化组件，制订和审核接入标准，使得各组件按照标准接入；此外，主业务系统通过统一跨域技术实现与各组件之间的交互，跨域访问对象即可以是通用工具类系统，也可以是类似主业务系统的其他业务系统，适用范围很广。
而且，对于主业务系统跨域访问不同的其他业务系统时，对于通用工具类的系统无需登录认证直接打开，而对于需要登录认证的业务系统进行免登认证，避免了业务人员反复输入账号和密码的麻烦，大大简化了业务人员的操作步骤。
此外，本申请还提出一种计算机可读存储介质，该计算机可读存储介质上存储有所述实现业务系统与多组件交互的系统20，该实现业务系统与多组件交互的系统20被一个或多个处理器执行时实现上述实现业务系统与多组件交互的方法或电子装置的操作。
虽然以上描述了本申请的具体实施方式，但是本领域的技术人员应当理解，这仅是举例说明，本申请的保护范围是由所附权利要求书限定的。本领域的技术人员在不背离本申请的原理和实质的前提下，可以对这些实施方式做出多种变更或修改，但这些变更和修改均落入本申请的保护范围。

Claims (14)

  1. 一种实现业务系统与多组件交互的方法，其特征在于，包括如下步骤：
    S1、将至少一个组件配置在一个框架系统中；
    S2、将配置有组件的框架系统显示在主业务系统的前端网页上；
    S3、通过点击显示在主业务系统前端网页上的组件，用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
  2. 根据权利要求1所述的实现业务系统与多组件交互的方法，其特征在于，步骤S1中所述的组件为封装后的除主业务系统以外的其他业务系统，封装后的其他业务系统以图标形式进行显示。
  3. 根据权利要求2所述的实现业务系统与多组件交互的方法，其特征在于，所述其他业务系统包括网络电话工具和网页聊天工具。
  4. 根据权利要求1所述的实现业务系统与多组件交互的方法，其特征在于，步骤S2中所述配置有组件的框架系统以悬浮工具栏的形式显示在主业务系统的前端网页上，或者以嵌入到主业务系统的菜单栏中的形式显示在主业务系统的前端网页上。
  5. 根据权利要求1-4任一项所述的实现业务系统与多组件交互的方法，其特征在于，步骤S3包括以下分步骤：
    S31、点击显示在主业务系统前端网页上的组件，以向框架系统发起登录所述组件所定义的另一业务系统的业务登录请求；
    S32、框架系统配置所述主业务系统信息和被点击的组件信息；
    S33、主业务系统的前端网页通过HTTP协议加载框架系统提供的框架系统文件umaplite.js和统一跨域文件cross-domain.js；
    S34、主业务系统对框架系统进行标准初始化，并向框架系统传入主业务系统认证信息和被点击的组件的所需参数；
    S35、框架系统验证业务登录请求是否合法，若验证通过，返回框架系统配置的所述被点击的组件信息，并则执行步骤S36；
    S36、框架系统初始化配置在所述框架系统上的组件；
    S37、框架系统通过jsonp请求被点击的组件进行免登认证，若认证通过则执行S38；
    S38、主业务系统通过统一跨域技术与被点击的组件进行交互，实现用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
  6. 一种电子装置，包括存储器和处理器，其特征在于，所述存储器上存储有可被所述处理器执行的实现业务系统与多组件交互的系统，所述实现业务系统与多组件交互的系统包括：
    组合模块，用于定义组合组件，并管理组件；
    前端展示模块，用于将组合后的组件显示在主业务系统的前端页面上；
    检测接入模块，用于检测到显示在主业务系统的前端页面上的组件被点击后，打开并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
  7. 根据权利要求6所述的电子装置，其特征在于，所述组件为封装后的除主业务系统以外的其他业务系统，并以图标形式进行显示；所述组合模块通过将表示组件的图标拖拽到特定位置的方式实现组件的定义组合。
  8. 根据权利要求7所述的电子装置，其特征在于，所述组件定义组合后，以悬浮工具栏或者嵌入到主业务系统的菜单栏中的形式显示在主业务系统的前端网页上。
  9. 根据权利要求6-8任一项所述的电子装置，其特征在于，所述其他业务系统包括网络电话工具和网页聊天工具。
  10. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质内存储有实现业务系统与多组件交互的系统，所述实现业务系统与多组件交 互的系统可被至少一个处理器所执行，以使所述至少一个处理器执行以下步骤：
    S1、将至少一个组件配置在一个框架系统中；
    S2、将配置有组件的框架系统显示在主业务系统的前端网页上；
    S3、通过点击显示在主业务系统前端网页上的组件，用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
  11. 根据权利要求10所述的计算机可读存储介质，其特征在于，步骤S1中所述的组件为封装后的除主业务系统以外的其他业务系统，封装后的其他业务系统以图标形式进行显示。
  12. 根据权利要求11所述的计算机可读存储介质，其特征在于，所述其他业务系统包括网络电话工具和网页聊天工具。
  13. 根据权利要求10所述的计算机可读存储介质，其特征在于，步骤S2中所述配置有组件的框架系统以悬浮工具栏的形式显示在主业务系统的前端网页上，或者以嵌入到主业务系统的菜单栏中的形式显示在主业务系统的前端网页上。
  14. 根据权利要求10-13中任一项所述的计算机可读存储介质，其特征在于，步骤S3包括以下分步骤：
    S31、点击显示在主业务系统前端网页上的组件，以向框架系统发起登录所述组件所定义的另一业务系统的业务登录请求；
    S32、框架系统配置所述主业务系统信息和被点击的组件信息；
    S33、主业务系统的前端网页通过HTTP协议加载框架系统提供的框架系统文件umaplite.js和统一跨域文件cross-domain.js；
    S34、主业务系统对框架系统进行标准初始化，并向框架系统传入主业务系统认证信息和被点击的组件的所需参数；
    S35、框架系统验证业务登录请求是否合法，若验证通过，返回框架系统配置的所述被点击的组件信息，并则执行步骤S36；
    S36、框架系统初始化配置在所述框架系统上的组件；
    S37、框架系统通过jsonp请求被点击的组件进行免登认证，若认证通过则执行S38；
    S38、主业务系统通过统一跨域技术与被点击的组件进行交互，实现用户从主业务系统跳转并登录到被点击的所述组件所定义的另一业务系统的前端网页上。
PCT/CN2018/077420 2017-09-11 2018-02-27 实现业务系统与多组件交互的方法、电子装置及存储介质 Ceased WO2019047488A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US16/315,254 US20210334114A1 (en) 2017-09-11 2018-02-27 Method And Storage Medium For Realizing Interaction Between Business Systems And At Least One Component
JP2018560950A JP6751778B2 (ja) 2017-09-11 2018-02-27 業務システムとマルチアセンブリーとのやりとりを実現する方法、電子装置及び記憶媒体
SG11201810229WA SG11201810229WA (en) 2017-09-11 2018-02-27 Method, electronic devices and storage medium for realizing interaction between business systems and multiple components

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710814312.X 2017-09-11
CN201710814312.XA CN108509190A (zh) 2017-09-11 2017-09-11 实现业务系统与多组件交互的方法、电子装置及存储介质

Publications (1)

Publication Number Publication Date
WO2019047488A1 true WO2019047488A1 (zh) 2019-03-14

Family

ID=63374495

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077420 Ceased WO2019047488A1 (zh) 2017-09-11 2018-02-27 实现业务系统与多组件交互的方法、电子装置及存储介质

Country Status (5)

Country Link
US (1) US20210334114A1 (zh)
JP (1) JP6751778B2 (zh)
CN (1) CN108509190A (zh)
SG (1) SG11201810229WA (zh)
WO (1) WO2019047488A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109992268A (zh) * 2019-03-29 2019-07-09 携程旅游信息技术（上海）有限公司 弹框实现方法、装置、电子设备、存储介质
CN112637113A (zh) * 2020-09-04 2021-04-09 山东英信计算机技术有限公司 集成系统跨平台认证方法及相关组件

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109379271B (zh) * 2018-10-16 2021-04-27 金瓜子科技发展（北京）有限公司 一种基于im的业务交互方法、设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102117203A (zh) * 2009-12-30 2011-07-06 上海杉达学院 一种基于Struts框架的信息管理系统
CN107015851A (zh) * 2016-01-28 2017-08-04 阿里巴巴集团控股有限公司 一种服务组件管理方法及系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006172195A (ja) * 2004-12-16 2006-06-29 Canon Inc アプリケーションプログラム管理装置、その制御方法および記憶媒体
US8234626B2 (en) * 2008-06-04 2012-07-31 Dell Products L.P. Modular ASL component
US9384101B2 (en) * 2011-07-26 2016-07-05 Apple Inc. Web application architecture
CN102819436B (zh) * 2012-08-01 2016-03-30 广州博冠信息科技有限公司 一种基于网页邮箱的用户界面交互方法和设备
JP5508498B2 (ja) * 2012-10-10 2014-05-28 Ｎｅｃインフロンティア株式会社 インストーリング方法、インストーラ装置及びインストーリング用プログラム
CN105516767B (zh) * 2015-12-01 2019-04-16 海信集团有限公司 智能电视及其应用切换方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102117203A (zh) * 2009-12-30 2011-07-06 上海杉达学院 一种基于Struts框架的信息管理系统
CN107015851A (zh) * 2016-01-28 2017-08-04 阿里巴巴集团控股有限公司 一种服务组件管理方法及系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109992268A (zh) * 2019-03-29 2019-07-09 携程旅游信息技术（上海）有限公司 弹框实现方法、装置、电子设备、存储介质
CN109992268B (zh) * 2019-03-29 2022-12-20 携程旅游信息技术（上海）有限公司 弹框实现方法、装置、电子设备、存储介质
CN112637113A (zh) * 2020-09-04 2021-04-09 山东英信计算机技术有限公司 集成系统跨平台认证方法及相关组件
CN112637113B (zh) * 2020-09-04 2022-08-12 山东英信计算机技术有限公司 集成系统跨平台认证方法及相关组件

Also Published As

Publication number Publication date
JP6751778B2 (ja) 2020-09-09
JP2020502598A (ja) 2020-01-23
US20210334114A1 (en) 2021-10-28
CN108509190A (zh) 2018-09-07
SG11201810229WA (en) 2019-04-29

Similar Documents

Publication Publication Date Title
US11159554B2 (en) Correlating threat information across sources of distributed computing systems
JP6310477B2 (ja) 複数のアプリケーションを表示するためのシステムおよび方法
US8181254B1 (en) Setting default security features for use with web applications and extensions
US20250184370A1 (en) System and method for comparative evaluation of security tools in isolated environments
US20120036498A1 (en) Mobile application performance management
US20170093828A1 (en) System and method for detecting whether automatic login to a website has succeeded
US9178746B2 (en) Browser-based fetch of external libraries
CN113706155A (zh) 网络金融反诈骗方法、装置、设备、介质和程序产品
US20180005152A1 (en) Technologies for correlation based data selection
CN113448578A (zh) 页面数据处理方法、处理系统、电子设备和可读存储介质
WO2019047488A1 (zh) 实现业务系统与多组件交互的方法、电子装置及存储介质
CN110795651A (zh) 用于保存前端数据的方法、装置及电子设备
CN112817831A (zh) 应用性能监测方法、装置、计算机系统和可读存储介质
US9436669B1 (en) Systems and methods for interfacing with dynamic web forms
US20160078350A1 (en) Contextual platform feature recommendations
CN108234391A (zh) 一种登录信息提示方法及装置
US11893199B2 (en) Systems and methods for viewing incompatible web pages via remote browser instances
US9049174B2 (en) Maintaining sessions in a smart thin client server
US20150100615A1 (en) Drag and drop of a uri to link resources
CN109981553A (zh) 访问控制方法及其系统、计算机系统和可读存储介质
US11467868B1 (en) Service relationship orchestration service
CN117176565A (zh) 业务请求的处理方法、系统、设备、介质及产品
CN116302561A (zh) 用于应用实例的状态控制方法、装置、设备及存储介质
CN116827604A (zh) 应用登录控制方法、系统、终端及存储介质
US10826978B1 (en) Systems and methods for server load control

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018560950

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18854838

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28.09.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18854838

Country of ref document: EP

Kind code of ref document: A1