Method for realizing enterprise customization demand in business travel service system
By setting expansion points and providing multiple implementation options in the travel service system, combined with the plug-in configuration interface, the problem that existing systems are difficult to achieve enterprise customization needs is solved, and convenient customized development and efficient system iteration are achieved.
Patent Information
- Application Number
- CN202411336738.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-24
- Publication Date
- 2025-02-25
AI Technical Summary
When facing the personalized needs of multiple enterprises, existing travel service systems are difficult to achieve convenient customized development, resulting in high costs, complex development and difficult to iterate quickly.
By setting extension points in the travel control process and providing multiple implementation options for each extension point, a plug-in configuration interface is provided, allowing enterprises to select and configure extension points to implement according to their own needs, forming customized plug-ins.
It realizes that in a travel service system for multiple enterprises, it can easily meet the personalized needs of enterprises, reduce development costs and complexity, and improve the flexibility and iterative capabilities of the system.
Smart Images
Figure CN119515281A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a business travel service computer software system, and more particularly to a method for realizing enterprise customization requirements in the business travel service system. Background Art
[0002] Computer software systems that serve enterprises (TO B) are oriented to the enterprise (B) end market. In their development and maintenance process, the topic of enterprise personalized needs and customized development cannot be avoided. Different enterprises always put forward various personalized needs according to their actual situations, which require targeted customized development.
[0003] The business travel service system is such a system for multiple companies. The business travel rules within each company are different, and there are various personalized needs. There are many customized needs, which require customized development accordingly. For example, some companies require same-sex cohabitation when traveling on business; some companies may allow employees to use corporate payments when visiting relatives, etc.
[0004] In order to achieve these personalized needs of enterprises, they need to be addressed accordingly during the development and maintenance of the service system.
[0005] At present, different versions are used for development and maintenance for different corporate customers, which requires an independent operating environment and is costly.
[0006] Moreover, this will result in more than a dozen or even dozens of pre-release environment development branches, each of which requires complete development and maintenance operations.
[0007] On the other hand, some requirements, even if they seem to be small requirements, such as the requirements involving hotel reservation links, require the coordinated development of multiple links, such as the hotel reservation link and the management and control link, which further increases the difficulty of system development and maintenance.
[0008] Therefore, there is still a need for a method that can more conveniently realize corporate customization needs in a travel service system for multiple enterprises. Summary of the invention
[0009] A technical problem to be solved by the present disclosure is to provide a method that can more conveniently realize the customization needs of enterprises in a travel service system for multiple enterprises.
[0010] According to a first aspect of the present disclosure, a method for realizing customized needs of enterprises in a travel service system for multiple enterprises is provided, comprising: presenting a plug-in configuration interface, the plug-in configuration interface being used to configure a plug-in for the enterprise to realize the customized needs of the enterprise in the travel management process; presenting an extension point list in the plug-in configuration interface, the extension point list including identification information of multiple extension points, the extension point being a node that can add functions set in the travel management process; presenting identification information of one or more extension point implementations provided respectively for the multiple extension points, the extension point implementations being respectively designed to realize functions that can be executed at the extension points; and saving a collection of extension point implementations selected for the multiple extension points based on the customized needs of the enterprise as a plug-in for realizing the customized needs of the enterprise.
[0011] Optionally, the step of presenting the plug-in configuration interface includes: creating a new plug-in, and presenting a plug-in configuration interface for the new plug-in.
[0012] Optionally, the step of presenting the plug-in configuration interface includes: selecting an existing plug-in that has been configured in the plug-in library, and presenting a plug-in configuration interface for the existing plug-in.
[0013] Optionally, the method further includes: adding the new plug-in created for the enterprise to the plug-in library so that it can be selected and used by other enterprises as an existing plug-in.
[0014] Optionally, the method further comprises: adjusting the extension point selection and / or extension point implementation selection of an existing plug-in selected from the plug-in library.
[0015] Optionally, the enterprise data is stored in a database, and the extension point implementation is designed to read the enterprise data from the database.
[0016] Optionally, the functions corresponding to the extension points are functions designed to be executed at the corresponding extension points in order to realize the customized requirements of the enterprise.
[0017] Optionally, when multiple extension point implementations are provided for one extension point, the multiple extension point implementations correspond to different customization requirements respectively.
[0018] Optionally, for new plugins, default all extension point implementations to be unselected.
[0019] Optionally, in the case that only one extension point implementation is provided for an extension point, in response to the one extension point being selected, the one extension point implementation provided for it is set to be selected.
[0020] Optionally, in response to identification information of an extension point implementation being clicked, it is determined that the extension point implementation is selected.
[0021] Optionally, in response to the identification information of an extension point implementation being clicked, a configuration interface of the extension point implementation is presented, and a selection of the extension point implementation is received on the configuration interface.
[0022] Optionally, in response to clicking on identification information of an extension point implementation, a configuration interface for the extension point implementation is presented, and a parameter configuration control is provided on the configuration interface for receiving parameter values of parameter configuration involved in the extension point implementation for the enterprise, and the parameter values are stored in a database in association with the enterprise as enterprise data.
[0023] Optionally, the business travel management and control process includes multiple process nodes, and one or more extension points are respectively set at multiple customizable process nodes among the multiple process nodes that can be customized according to the customization requirements of the enterprise.
[0024] Optionally, the enterprise customization requirements include budget control customization requirements, and the multiple customizable process nodes include multiple process nodes involving budget control in the travel control process.
[0025] Optionally, the enterprise customization requirements include same-sex rooming in a business trip scenario, and the multiple customizable process nodes include multiple process nodes involving hotel room occupant information in the order-related process stages in the business travel management and control process.
[0026] Optionally, the enterprise customization requirement includes allowing corporate payment for family visits, and the multiple customizable process nodes include process nodes involving payment in the process stages related to transaction ordering in the travel management and control process.
[0027] Optionally, the method also includes: determining information of a plug-in configured for the enterprise during execution of the travel management process for the enterprise; determining multiple extension point implementations selected for the enterprise to be added to multiple extension points based on the information of the plug-in configured for the enterprise; and adding corresponding extension point implementations to the multiple extension points in the travel management process.
[0028] Optionally, the method further comprises: when one or more plug-ins configured for the enterprise include multiple extension point implementations selected for the same extension point, integrating the multiple extension point implementations selected for the same extension point according to preset rules.
[0029] Optionally, the step of integrating the multiple extension point implementations selected for the same extension point according to a preset rule includes at least one of the following: when the same extension point implementation is selected for the same extension point in multiple plug-ins configured for the enterprise, the same extension point implementation is added to the same extension point only once; two or more different extension point implementations that do not conflict with each other among the multiple extension point implementations selected for the same extension point are added to the same extension point; for two or more different extension point implementations that conflict with each other among the multiple extension point implementations selected for the same extension point, selecting the extension point implementation with the highest priority according to a preset priority rule and adding it to the same extension point.
[0030] According to a second aspect of the present disclosure, a computing device is provided, comprising: a processor; and a memory on which executable codes are stored, and when the executable codes are executed by the processor, the processor executes the method described in the first aspect above.
[0031] According to a third aspect of the present disclosure, a computer program product is provided, comprising an executable code, and when the executable code is executed by a processor of an electronic device, the processor is caused to execute the method as described in the first aspect above.
[0032] According to a fourth aspect of the present disclosure, a non-transitory machine-readable storage medium is provided, on which executable code is stored. When the executable code is executed by a processor of an electronic device, the processor executes the method described in the first aspect above.
[0033] As a result, a method is provided to more conveniently realize the customized needs of enterprises in the travel service system for multiple enterprises, so as to enable more efficient and stable delivery, release greater productivity by utilizing limited resources, and quickly support the iterative development of the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, wherein like reference numerals generally represent like components in the exemplary embodiments of the present disclosure.
[0035] Figure 1 It is a schematic diagram of an interface for presenting extension point information in an open architecture platform.
[0036] Figure 2 This is a diagram of the plugin management interface that presents the configured plugins.
[0037] Figure 3 This is a schematic diagram of the starting interface for enterprise plug-in configuration.
[0038] Figure 4 It is a schematic flowchart of a method for realizing enterprise customization requirements according to an embodiment of the present disclosure.
[0039] Figure 5 This is a schematic diagram of the interface for plug-in configuration for enterprises.
[0040] Figure 6 It is a schematic flowchart of the processing of extension points involved in executing the travel control process.
[0041] Figure 7 This is a schematic diagram of an exemplary plug-in configuration using budget control as an example.
[0042] Figure 8 A schematic diagram of the structure of a computing device that can be used to implement the above-mentioned method for realizing enterprise customization requirements in a travel service system according to an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0043] The preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the preferred embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.
[0044] The present disclosure proposes a method for realizing enterprise customization requirements in a business travel service system for multiple enterprises. The method can be applied to the development and maintenance of a business travel service system such as a business travel reservation management system.
[0045] In an embodiment of the present disclosure, extension points are set at some customizable process nodes among the multiple process nodes included in the travel management and control process, and one or more extension point implementations that can be selected according to the personalized needs of the enterprise are prepared for each extension point, so that according to the personalized needs of the enterprise, the extension point implementation that meets the personalized needs is selected at the corresponding extension point to realize the desired functions, thereby achieving the purpose of customized development.
[0046] Extension points are points that can be added or modified in the process logic. Through extension points, new functions can be easily added or existing functions can be modified without modifying the process logic itself, which makes process extension simpler and more flexible.
[0047] The basic information of the extension point definition is the basic information that needs to be provided in the extension point definition, which may include the name, type, parameters, etc. of the extension point. This basic information can be used to help the system identify and process extension point requests.
[0048] Extension point implementation is used to implement corresponding functions at the extension point in order to meet the customized needs of the enterprise.
[0049] The basic information of the extension point implementation is the basic information that needs to be provided in the extension point implementation, for example, the extension point code, dependency, etc. This basic information can be used to help the system compile and run the extension point.
[0050] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0051] The method can be executed on an open architecture platform, for example, to present pre-prepared extension points and extension point implementation information to users, and to receive selections and / or configuration inputs from platform staff or enterprise staff for customized development.
[0052] On the interface of the configuration management system of an open architecture platform, for example, an "extension point management" interface for presenting extension point information, a "plugin management" interface for presenting configured plug-ins, and a "plugin configuration" interface for performing plug-in configuration can be provided.
[0053] Figure 1 It is a schematic diagram of an interface for presenting extension point information in an open architecture platform.
[0054] like Figure 1 As shown, when you click the "Extension Point Management" tab in the left column, the "Extension Point Management" interface appears on the right.
[0055] The left side of the "Extension Point Management" interface (the middle column of the entire screen) presents a list of extension points that can be configured. Extension points are nodes that can be set in the travel control process to add functions. The extension point list includes identification information of multiple extension points, such as "hotel", "order page rendering", "payment information", etc.
[0056] The extension point may have a tree structure, for example, and each node (extension point) may have one or more child nodes (sub-extension points). For example, "order page rendering" is a child node of "hotel", and "payment information" is a child node of "order page rendering".
[0057] The right side of the "Extension Point Management" interface (the right column of the entire screen) displays the information of the extension point, such as the basic information such as the name of the extension point and the extension point parameter information such as the class name, method name, version number, input parameter, output parameter, push record, etc. The detailed information of the input parameter, output parameter, push record, etc. parameters can be hidden, and the hidden detailed information can be displayed by clicking.
[0058] Figure 1 The interface shown is used to provide information about the extension points that can be configured to the platform staff or enterprise staff who perform customization operations. The specific configuration of each extension point is in Figure 3 and Figure 5 Execute in the "Plug-in Configuration" interface shown.
[0059] After appropriately configuring the corresponding extension points that need to be configured according to the personalized needs of the enterprise, a customized plug-in for realizing the personalized prelude of the enterprise can be formed.
[0060] After creating a plug-in for the personalized needs of an enterprise, you can put the created plug-in into the plug-in library. When you customize other enterprises in the future, you can choose the created plug-in according to the situation, and make appropriate modifications or adjustments based on the created plug-in when necessary to meet the personalized needs of the corresponding enterprise.
[0061] Figure 2 This is a diagram of the plugin management interface that presents the configured plugins.
[0062] like Figure 2 As shown, when you click the "Plugin Management" tab in the left column, the "Plugin Management" interface appears on the right.
[0063] In "Plug-in Management", for example, multiple already created plug-ins contained in the plug-in library are listed in the form of cards. In addition, you can click the "+ Add Plug-in" card to create a new plug-in to put it in the plug-in library for subsequent selection.
[0064] exist Figure 2 In the interface shown, by clicking on the listed plug-in card, some detailed information of the corresponding plug-in can be further presented, such as the usage of the plug-in, the extension point configuration information contained in the plug-in, etc. In addition, the maintainer of the plug-in can also maintain it, such as modifying or adjusting the plug-in.
[0065] Figure 3 This is a schematic diagram of the starting interface for enterprise plug-in configuration.
[0066] like Figure 3 As shown, when you click the "Plugin Configuration" tab in the left column, the starting interface of the "Plugin Configuration" interface appears on the right.
[0067] The start interface may have an input or selection control for inputting or selecting identification information of the enterprise that needs to be customized and developed, such as an enterprise ID, to determine the currently targeted enterprise.
[0068] If no plug-in has been configured for the determined enterprise, "No plug-in data, please add a plug-in" may be displayed. Click the "Add a plug-in" control to enter the plug-in specific configuration interface to add a plug-in for the enterprise.
[0069] If one or more plug-ins have been configured for the determined enterprise, the configured plug-ins can be presented, for example, in the form of cards, and a "new plug-in" control is also provided to add new plug-ins. When a configured plug-in card is clicked, the configuration interface of the plug-in can also be entered to modify or adjust the plug-in.
[0070] The present disclosure can realize enterprise customization requirements by configuring the plug-in.
[0071] Figure 4 It is a schematic flowchart of a method for realizing enterprise customization requirements according to an embodiment of the present disclosure.
[0072] In step S410, a plug-in configuration interface is presented. As described above, the plug-in configuration interface is used to configure a plug-in for the enterprise to realize the customized needs of the enterprise in the travel management process.
[0073] As described above, here, you can create a new plug-in and present a plug-in configuration interface for the new plug-in; or you can select an existing plug-in that has been configured in the plug-in library and present a plug-in configuration interface for the existing plug-in.
[0074] Figure 5 This is a schematic diagram of the interface for plug-in configuration for enterprises.
[0075] exist Figure 5 In the right column of the plug-in configuration interface shown, information about the plug-in currently being configured for the enterprise is presented in the form of a card, for example, the name is "plugin", the type is "general", and the description is "business travel general plug-in". In addition, a delete control can also be provided in association with the plug-in, for deleting the plug-in in the customization of the enterprise.
[0076] In step S420, in the plug-in configuration interface, for example Figure 5 A list of extension points is displayed at the bottom right of the interface.
[0077] The travel control process includes multiple process nodes. These process nodes can also be divided into multiple process stages, such as the search list stage, the search details stage, the order rendering stage, and the transaction order stage. Each process stage can include one or more process nodes.
[0078] One or more extension points are respectively arranged at a plurality of customizable process nodes among the plurality of process nodes that can be customized according to the customization requirements of the enterprise.
[0079] For example, when the enterprise customization requirements include budget control customization requirements, the multiple customizable process nodes may include multiple process nodes involving budget control in the travel control process.
[0080] For another example, when the enterprise customization requirements include same-sex rooming in business trip scenarios, multiple customizable process nodes may include multiple process nodes involving hotel room occupancy information in the order-related process stages of the travel management process.
[0081] For another example, when the enterprise customization requirements include allowing family visits to be made using enterprise payments, multiple customizable process nodes may include process nodes involving payment in the process stages related to transaction ordering in the travel management and control process.
[0082] As described above, the extension point list includes identification information of multiple extension points, and the extension point is a node that can add functions set in the travel management and control process.
[0083] For example, Figure 5 The identification information of three extension points is shown in FIG. 1 , “obtaining user role”, “obtaining user difference”, and “obtaining whether a shared flight is required”.
[0084] In step S430, if Figure 5 As shown, in association with the identification information of each extension point, identification information of one or more extension point implementations respectively provided for the plurality of extension points is presented.
[0085] Extension point implementations are each designed to implement the functionality that can be performed at the extension point.
[0086] Furthermore, the functions corresponding to the extension points are designed to be executed at the corresponding extension points in order to realize the customized requirements of the enterprise.
[0087] When multiple extension point implementations are provided for one extension point, the multiple extension point implementations correspond to different customization requirements respectively.
[0088] like Figure 5 As shown, two extension point implementations "A1 implementation" and "A2 implementation" are provided for the extension point "Get user role", one extension point implementation "B implementation" is provided for the extension point "Get user difference", and three extension point implementations "C1 implementation", "C2 implementation" and "C3 implementation" are provided for the extension point "Get whether to share the flight".
[0089] For example, in the extension point involving budget management, a strict management extension point implementation can be provided, and the process cannot continue if the budget is exceeded; or a loose management extension point implementation can be provided, which only provides a pop-up window prompt when the budget is exceeded, and the process can still continue if the user confirms. According to the personalized needs of the enterprise, appropriate extension point implementations can be selected for multiple extension points.
[0090] More specifically, from the perspective of implementation logic, taking the difference standard (travel standard) management as an example, at the extension point of judging whether the difference standard limit is exceeded, three exemplary extension points can be provided for implementation depending on whether there are different difference standard limits for different identities of the travelers.
[0091] Extension point implementation 1 does not distinguish between identities. The implementation logic is as follows: obtain the limit that does not distinguish between identities from the database; determine whether the product price exceeds the limit.
[0092] The extension point implements 2 to distinguish identities and sets different difference limits for travelers with different identities. The implementation logic is as follows: determine the identity of the traveler; obtain the limit corresponding to the identity from the database; and determine whether the limit is exceeded.
[0093] Extension point implementation 3 can include the above two situations, and the implementation logic is as follows: first, determine whether to set different difference limits for different identities; if the identities are not distinguished, obtain the limits from the database and determine whether the limits are exceeded; if the identities are distinguished, determine the identity of the traveler, obtain the limits corresponding to the identity from the database, and determine whether the limits are exceeded.
[0094] In the plug-in configuration interface, you can select and configure extension points for multiple extension points according to the personalized needs of the enterprise, thereby completing the configuration of the customized plug-in.
[0095] For new plug-ins, it can be assumed that all extension point implementations are not selected, like a blank sheet of paper, waiting for the extension point implementation to be selected for configuration.
[0096] In some embodiments, the extension point to be configured may be selected first, and then the corresponding extension point implementation may be configured for the extension point. In other embodiments, the extension point implementation corresponding to the extension point may be directly selected without the need to select the extension point.
[0097] In the case of selecting an extension point first, when only one extension point implementation is provided for an extension point, in response to the extension point being selected, the extension point implementation provided for it can be directly set as selected without further selecting and configuring the extension point implementation.
[0098] In some embodiments, the extension point implementation is selected when it is clicked. In response to the identification information of an extension point implementation being clicked, it is determined that the extension point implementation is selected.
[0099] In some embodiments, after clicking on an extension point implementation, a corresponding configuration interface is presented, wherein a control for selecting to enable the extension point implementation is provided. In response to the identification information of an extension point implementation being clicked, a configuration interface for the extension point implementation is presented, and a selection of the extension point implementation is received on the configuration interface.
[0100] For example, for the extension point "Get User Role", click the extension point implementation "A1 Implementation", and the detailed information of the extension point implementation will be presented on the right side of the extension point list, such as the implementation name, implementation description, implementation scenario, etc. When the "Enable Configuration" opening control is configured to "Open", the extension point implementation "A1 Implementation" is selected for the extension point "Get User Role".
[0101] After selecting and configuring the corresponding extension point implementation for all extension points that need to be configured, the plug-in used to implement the personalized needs of the enterprise is configured.
[0102] It should be understood that not every extension point needs to be configured with an extension point implementation. For example, there may be some extension points that are not related to the personalized needs currently customized for the enterprise and do not need to be selected and configured with extension point implementations.
[0103] In step S440, a set of extension point implementations selected for a plurality of extension points based on the customization requirements of the enterprise is saved as a plug-in for implementing the customization requirements of the enterprise.
[0104] Further, the new plug-in created for the enterprise can also be added to the plug-in library so as to be selected and used by other enterprises as an existing plug-in. That is, when customizing for other enterprises, in step S410, the plug-in added to the plug-in library can be selected and saved here.
[0105] When an existing plug-in is selected from the plug-in library, the existing plug-in has already selected and configured extension point implementations for several extension points. In the case where the needs of the current enterprise are different from the enterprise for which the plug-in was previously configured, the extension point selection and / or extension point implementation selection of the existing plug-in selected from the plug-in library can also be adjusted. For example, the extension point that was originally configured with an extension point implementation can be adjusted to no longer be configured with an extension point implementation; the extension point that was originally not configured with an extension point implementation can be adjusted to be configured with an extension point implementation; different extension point implementations can be configured for the extension point selection, or extension point implementations can be added (in the case where multiple extension point implementations can be selected for one extension point).
[0106] The method described above is used to customize the travel control process according to the user's personalized needs. The enterprise data used in this process, such as user roles, budgets, and travel standards, can be managed by the enterprise management background.
[0107] These enterprise data can be stored in a database. If the corresponding enterprise data needs to be called, such as determining whether the budget is exceeded or whether the difference requirement is met, the corresponding extension point implementation can be designed to read the corresponding enterprise data from the database.
[0108] Alternatively, in some embodiments, a parameter configuration control may be added to the configuration interface of the extension point implementation to configure the parameters involved in the extension point implementation. In this way, in response to the identification information of an extension point implementation being clicked, the configuration interface of the extension point implementation is presented, and a parameter configuration control is provided in the configuration interface to receive parameter values configured for the parameters involved in the extension point implementation for the enterprise, and the parameter values are stored in the database in association with the enterprise as enterprise data. When the extension point implementation is subsequently executed, the enterprise data may be read from the database.
[0109] Figure 6 It is a schematic flowchart of the processing of extension points involved in executing the travel control process.
[0110] like Figure 6 As shown, in the process of executing the travel control process for an enterprise, in step S610, information of the plug-in configured for the enterprise is determined.
[0111] In step S620, multiple extension point implementations to be added to multiple extension points selected for the enterprise are determined according to the information of the plug-in configured for the enterprise.
[0112] Then, in step S630, corresponding extension points are added to the multiple extension points of the travel control process, thereby realizing a travel control process customized for the personalized needs of the enterprise.
[0113] One or more plug-ins can be configured for an enterprise according to one or more personalized needs of the enterprise. In some cases, in a plug-in configured for an enterprise, multiple extension point implementations may be selected for one extension point. In some cases, when multiple plug-ins are configured for an enterprise, corresponding extension point implementations may be configured for the same extension point in more than one plug-in.
[0114] In this way, when one or more plug-ins configured for an enterprise include multiple extension point implementations selected for the same extension point, the multiple extension point implementations selected for the same extension point are integrated according to preset rules.
[0115] In some embodiments, when the same extension point implementation is respectively selected for the same extension point in multiple plug-ins configured for an enterprise, the same extension point implementation is added to the same extension point only once.
[0116] In some embodiments, two or more different extension point implementations that do not conflict with each other among multiple extension point implementations selected for the same extension point may be added to the same extension point.
[0117] In some embodiments, for two or more different extension point implementations that conflict with each other among multiple extension point implementations selected for the same extension point, the extension point implementation with the highest priority may be selected according to a preset priority rule and added to the same extension point.
[0118] For example, you can set the priority order for multiple extension point implementations designed for the same extension point when designing the extension point implementation. Alternatively, you can set the priority order according to the time when you choose to configure the extension point implementation or the time when you configure the plug-in containing the extension point implementation. The later one has a higher priority than the earlier one.
[0119] The method for implementing enterprise customization requirements in a travel service system according to the present disclosure has been described in detail above.
[0120] Through this method, the provided extension points can be utilized to configure these extension points according to the unique needs of the enterprise, and the corresponding extension point implementation can be selected and configured for it.
[0121] In this way, different companies can route different service processes to different customized extension points for operation in the same travel service (booking management system).
[0122] This provides a flexible and customized solution that allows each company to adjust and expand the functions of the travel service system (booking control system) according to its own specific needs.
[0123] By pre-setting multiple extension points and selecting corresponding extension point implementations for enterprises at multiple extension points, different enterprises perform extension point routing according to the information of the plug-ins configured for them and parse the corresponding extension point implementations, thereby achieving the effect of meeting multiple customized needs in a set of operating environments.
[0124] Figure 7 This is a schematic diagram of an exemplary plug-in configuration using budget control as an example.
[0125] Figure 7 The straight line with an arrow in the upper middle shows the direction of the entire travel control process. The first half involves basic shopping guide business capabilities, and the second half involves basic transaction business capabilities.
[0126] The first half includes two process stages, the "search list" stage and the "search details" stage. The second half includes two process stages, the "order rendering" stage and the "trading order" stage.
[0127] Figure 7 The key process nodes included in each process stage are schematically shown below the aforementioned straight line with arrows.
[0128] For example, the "Search List" stage includes process nodes such as "Product Search", "Budget Control" and "Difference Control". The "Search Details" stage includes process nodes such as "Product Information", "Product Filtering", "Difference Control", "Budget Control", and "Page Rendering". The "Order Rendering" stage includes "Product Information", "Price Calculation", "Budget Control", "Page Rendering", etc. The "Transaction Order" stage includes "Order Information", "Budget Verification", "Difference Verification", "Resource Deduction", and "Budget Freeze".
[0129] For multiple process nodes, for example, the "Budget Control" process node in the "Search List" stage, you can set multiple extension points, such as "Budget Query", "Budget Amount", "Custom Budget Component", and "List Card Rendering".
[0130] Figure 7 Two example plug-ins are shown below, one plug-in ("Approval Form, Cost Center Budget Plug-in") uses a stricter standard for control, and the other plug-in ("Weak Control Budget Plug-in") uses a looser standard for control. The two plug-ins include the extension point implementation selected for each extension point.
[0131] As an example, in the "weakly controlled budget plug-in", only a few extension point implementations that are different from the "approval form, cost center budget plug-in" are schematically shown.
[0132] Taking the "Custom Reservation Button" extension point set in the "Budget Control" process node of the "Search Details" process stage as an example, in the "Approval Form, Cost Center Budget Plug-in", select the "Over budget, button disabled and prompt" extension point implementation. When the budget is exceeded, the button is disabled, the process cannot continue, and a prompt is given; in the "Weak Control Budget Plug-in", select the "Over budget, button available, pop-up prompt" extension point implementation. When the budget is exceeded, the button is still available, the process can still continue, but a pop-up prompt is given.
[0133] In this way, when the user's personalized demand for budget control is strong control, the extension point that realizes the expected strong control function can be selected in the relevant extension points of each process node involved in budget control, just like the "Approval Form, Cost Center Budget Plug-in". If the user's personalized demand for budget control is weak, the extension point that realizes the expected weak control function can be selected in the relevant extension points of each process node involved in budget control, just like the "Weak Control Budget Plug-in".
[0134] As a result, corporate customization needs can be easily and conveniently realized in the travel service system.
[0135] Figure 8 A schematic diagram of the structure of a computing device that can be used to implement the above-mentioned method for realizing enterprise customization requirements in a travel service system according to an embodiment of the present invention is shown.
[0136] See also Figure 8 , the computing device 800 includes a memory 810 and a processor 820 .
[0137] The processor 820 may be a multi-core processor or may include multiple processors. In some embodiments, the processor 820 may include a general-purpose main processor and one or more special coprocessors, such as a graphics processing unit (GPU), a digital signal processor (DSP), etc. In some embodiments, the processor 820 may be implemented using a customized circuit, such as an application-specific integrated circuit (ASIC) or a field programmable gate array (FPGA).
[0138] The memory 810 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. Among them, ROM can store static data or instructions required by the processor 820 or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that does not lose the stored instructions and data even after the computer is powered off. In some embodiments, the permanent storage device uses a large-capacity storage device (such as a magnetic or optical disk, flash memory) as a permanent storage device. In some other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, optical drive). The system memory may be a readable and writable storage device or a volatile readable and writable storage device, such as a dynamic random access memory. The system memory may store some or all instructions and data required by the processor at run time. In addition, the memory 810 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks may also be used. In some embodiments, the memory 810 may include a readable and / or writable removable storage device, such as a laser disc (CD), a read-only digital versatile disc (e.g., DVD-ROM, double-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (e.g., SD card, mini SD card, Micro-SD card, etc.), a magnetic floppy disk, etc. The computer-readable storage medium does not include carrier waves and transient electronic signals transmitted wirelessly or wired.
[0139] The memory 810 stores executable codes. When the executable codes are processed by the processor 820, the processor 820 can execute the method mentioned above for realizing enterprise customization requirements in the travel service system.
[0140] The method for realizing enterprise customization requirements in a business travel service system according to the present invention has been described in detail above with reference to the accompanying drawings.
[0141] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0142] In addition, the method according to the present invention may also be implemented as a computer program or a computer program product, which includes computer program code instructions for executing the above steps defined in the above method of the present invention.
[0143] Alternatively, the present invention may also be implemented as a non-temporary machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) on which executable code (or computer program, or computer instruction code) is stored. When the executable code (or computer program, or computer instruction code) is executed by a processor of an electronic device (or computing device, server, etc.), the processor executes the various steps of the above-mentioned method according to the present invention.
[0144] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or a combination of both.
[0145] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system and method according to multiple embodiments of the present invention. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or code, and the part of the module, program segment or code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0146] The embodiments of the present invention have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein are selected to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.
Claims
1. A method for realizing enterprise customization requirements in a travel service system for multiple enterprises, comprising: Presenting a plug-in configuration interface, wherein the plug-in configuration interface is used to configure a plug-in for the enterprise to implement the customized needs of the enterprise in the travel management and control process; Presenting an extension point list in the plug-in configuration interface, the extension point list including identification information of a plurality of extension points, the extension points being nodes set in the travel management and control process to which functions can be added; Presenting identification information of one or more extension point implementations respectively provided for the plurality of extension points, wherein the extension point implementations are respectively designed to implement functions that can be executed at the extension points; as well as A set of extension point implementations selected for a plurality of extension points based on the customization requirements of the enterprise is saved as a plug-in for implementing the customization requirements of the enterprise.
2. The method according to claim 1, wherein: The step of presenting the plug-in configuration interface includes: Creating a new plug-in and presenting a plug-in configuration interface for the new plug-in; and / or Select an existing plug-in that has been configured in the plug-in library, and a plug-in configuration interface for the existing plug-in is presented.
3. The method according to claim 2, further comprising: Adding the new plug-in created for the enterprise to the plug-in library so that it can be selected and used by other enterprises as an existing plug-in; and / or The extension point selection and / or extension point implementation selection of an existing plug-in selected from the plug-in library is adjusted.
4. The method according to claim 1, wherein: The enterprise data is stored in a database, and the extension point implementation is designed to read the enterprise data from the database; and / or The functions corresponding to the extension points are designed to be executed at the corresponding extension points in order to meet the customized needs of the enterprise; and / or In the case where multiple extension point implementations are provided for one extension point, the multiple extension point implementations correspond to different customization requirements respectively; and / or For new plugins, default all extension point implementations to be unselected; and / or In the case where only one extension point implementation is provided for an extension point, in response to the one extension point being selected, setting the one extension point implementation provided for it to be selected; and / or In response to identification information of an extension point implementation being clicked, determining that the extension point implementation is selected; and / or In response to the identification information of an extension point implementation being clicked, presenting a configuration interface for the extension point implementation, and receiving a selection of the extension point implementation on the configuration interface; and / or In response to identification information of an extension point implementation being clicked, a configuration interface of the extension point implementation is presented, a parameter configuration control is provided on the configuration interface, and a parameter value of a parameter configuration involved in the extension point implementation for the enterprise is received, and the parameter value is stored in a database in association with the enterprise as enterprise data.
5. The method according to claim 1, wherein: The business travel management and control process includes multiple process nodes, and one or more extension points are respectively set at multiple customizable process nodes in the multiple process nodes that can be customized according to the customization requirements of the enterprise.
6. The method according to claim 5, wherein: The enterprise customization requirements include budget control customization requirements, and the multiple customizable process nodes include multiple process nodes related to budget control in the travel control process; and / or The enterprise customization requirements include same-sex sharing in a business trip scenario, and the multiple customizable process nodes include multiple process nodes involving hotel room occupant information in the order-related process stage in the business travel management and control process; and / or The enterprise customization requirements include allowing corporate payment for family visits, and the multiple customizable process nodes include process nodes involving payment in the process stages related to transaction ordering in the travel management and control process.
7. The method according to claim 1, further comprising: In the process of executing the travel control process for the enterprise, determining information of the plug-in configured for the enterprise; Determining, according to information of the plug-in configured for the enterprise, a plurality of extension point implementations selected for the enterprise to be added to the plurality of extension points; Add corresponding extension points to the multiple extension points in the travel management and control process.
8. The method according to claim 7, further comprising: In the case that one or more plug-ins configured for the enterprise include multiple extension point implementations selected for the same extension point, the multiple extension point implementations selected for the same extension point are integrated according to preset rules.
9. The method according to claim 8, wherein: The step of integrating the multiple extension point implementations selected for the same extension point according to a preset rule comprises at least one of the following: When the same extension point implementation is selected for the same extension point in the multiple plug-ins configured for the enterprise, the same extension point implementation is added only once to the same extension point; Adding two or more different extension point implementations that do not conflict with each other from the multiple extension point implementations selected for the same extension point to the same extension point; For two or more different extension point implementations that conflict with each other among the multiple extension point implementations selected for the same extension point, the extension point implementation with the highest priority is selected according to a preset priority rule and added to the same extension point.
10. A computer program product, comprising executable codes, which, when executed by a processor of an electronic device, cause the processor to perform the method according to any one of claims 1 to 9.