CN112337099A

CN112337099A - Service management method and device

Info

Publication number: CN112337099A
Application number: CN202011162366.0A
Authority: CN
Inventors: 马达
Original assignee: Tencent Technology Beijing Co Ltd
Current assignee: Tencent Technology Beijing Co Ltd
Priority date: 2020-10-27
Filing date: 2020-10-27
Publication date: 2021-02-09
Anticipated expiration: 2040-10-27
Also published as: CN112337099B

Abstract

The embodiment of the application provides a business management method and a business management device, the method is characterized in that after a data source is established based on business requirements, selection operation is executed on a business composition selection interface to generate business composition data and business components, and corresponding business is generated by executing triggering operation, configuration operation, associated path adding operation and setting operation on a business configuration interface, so that an operator can quickly generate a new operation application through direct operation on the interface. In addition, by setting the association option in the service association area, the operator can set the service association relation between the service components according to the requirement, thereby meeting the personalized requirement of operation.

Description

Service management method and device

Technical Field

The present application relates to the field of computers, and in particular, to a method and an apparatus for service management.

Background

The game development personnel carries out requirement evaluation on the characteristics included in the related requirement documents, then returns evaluation results to the operation, writes further requirement documents according to the evaluation results and sends the further requirement documents to the game development personnel, and the game development personnel and the system development personnel assist the work to complete the requirements and finally deliver the operation after the test is successful. In the process, due to the assistance of game and system developers, both sides need to repeatedly develop some same or similar modules, and the communication cost is higher due to more involved persons, so that the time from the requirement determination to the system landing delivery is longer.

In addition, if the operation needs to be completed incompletely, the whole process needs to be repeated, and the workload is increased in multiples. That is, the process of constructing the game operation application in the prior art is complicated and the period is long.

Content of application

The embodiment of the application provides a service management method and device, which can solve the problems of complicated operation and application process and long period.

In one aspect, the present application provides a service management method, including:

acquiring a service demand, and creating a data source based on the service demand;

displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, and generating a corresponding service component for the service composition data;

displaying a service configuration interface, wherein the service configuration interface comprises a component display area, a service configuration area and a service association area;

receiving a triggering operation through the component display area, and displaying a candidate service component of a service corresponding to the triggering operation in the component display area;

receiving configuration operation through the service configuration area, and adding a service component corresponding to the configuration operation to the service configuration area;

receiving an association path adding operation through the service configuration area, wherein the association path adding operation comprises adding an association path between corresponding service components, determining a direction for the association path, and displaying association options between a source service component and a downstream service component corresponding to the association path in the service association area according to the association path adding operation;

and receiving the setting operation of the association option through the service association area, and adding the service association relationship generated according to the setting operation to the source service component and the downstream service component corresponding to the association path to generate the service corresponding to the triggering operation.

In one aspect, the present application provides a service management apparatus, including:

the system comprises a creating module, a data source creating module and a data source sending module, wherein the creating module is used for acquiring service requirements and creating the data source based on the service requirements;

the generating module is used for displaying a business composition selection interface, receiving selection operation through the business composition selection interface, generating business composition data according to the data source and a business composition template corresponding to the selection operation, and generating a corresponding business component for the business composition data;

the first display module is used for displaying a service configuration interface, and the service configuration interface comprises an assembly display area, a service configuration area and a service association area;

the second display module is used for receiving the triggering operation through the component display area and displaying the candidate service components of the service corresponding to the triggering operation in the component display area;

a first adding module, configured to receive configuration operation through the service configuration area, and add a service component corresponding to the configuration operation to the service configuration area;

a third display module, configured to receive, through the service configuration area, an association path addition operation, where the association path addition operation includes adding an association path between corresponding service components, determining a direction for the association path, and displaying, according to the association path addition operation, an association option between a source service component and a downstream service component corresponding to the association path in the service association area;

and the second adding module is used for receiving the setting operation of the association option through the service association area and adding the service association relationship generated according to the setting operation to the source service component and the downstream service component corresponding to the association path so as to generate the service corresponding to the triggering operation.

In one embodiment, the third display module comprises:

a determining unit, configured to determine, according to the associated path adding operation, a service component corresponding to the associated path starting point as a source service component, and a service component corresponding to the associated path directing point as a downstream service component;

and the display unit is used for displaying the association options between the source service component and the downstream service component in the service association area, wherein the association options comprise an option of whether to establish a service association relationship, an option of triggering types of the downstream service component and an option of filling positions of the downstream service component.

In an embodiment, the service management apparatus further includes a receiving module, where the receiving module is configured to receive, through the service configuration area, an association identifier adding operation, where the association identifier adding operation includes adding, based on a downstream service component pointed by the association path, an association identifier corresponding to the downstream service component on the association path.

In one embodiment, the creation module comprises:

the first acquisition unit is used for acquiring the storage type of the service data based on the service requirement;

a second obtaining unit, configured to receive a connection identifier selection operation through a service data selection interface, determine a connection identifier corresponding to the storage type according to the connection identifier selection operation, and obtain the service data from a storage address corresponding to the connection identifier;

and the creating unit is used for determining a display field according to the field selection operation of the service data and creating a data source according to the display field.

In one embodiment, the generating module comprises:

the system comprises a first generation unit, a second generation unit and a front-end service component generation unit, wherein the first generation unit is used for receiving front-end page selection operation through a front-end page selection interface, generating front-end page data according to a front-end page template corresponding to the front-end page selection operation and the data source, and generating a corresponding front-end service component for the front-end page data;

the second generation unit is used for receiving background process selection operation through a background process selection interface, generating background process data according to a background process template corresponding to the background process selection operation and the data source, and generating a corresponding background service component for the background process data.

In one embodiment, the first generation unit includes:

the first receiving unit is used for receiving a first preset template selection operation through a front-end page selection interface;

the second receiving unit is used for displaying a preset front-end page template selection interface corresponding to the first preset template selection operation, receiving the first template selection operation through the preset front-end page template selection interface, and determining a target preset front-end page template according to the first template selection operation;

and the first association unit is used for associating the data source with the target preset front-end page template to generate front-end page data.

In one embodiment, the first generation unit further includes:

the third receiving unit is used for receiving the selection operation of the first self-defined template through the front-end page selection interface;

a fourth receiving unit, configured to display a custom front-end page template generation interface corresponding to the first custom template selection operation, receive a layout selection operation and a control selection operation through the custom front-end page template generation interface, determine a required layout according to the layout selection operation, determine a required control according to the control selection operation, and generate a custom front-end page template according to the layout and the control;

and the second association unit is used for associating the data source with the self-defined front-end page template to generate front-end page data.

In one embodiment, the second generating unit includes:

the fifth receiving unit is used for receiving second preset template selection operation through the background process selection interface;

a sixth receiving unit, configured to display a preset background process template selection interface corresponding to the second preset template selection operation, receive the second template selection operation through the preset background process template selection interface, and determine a target preset background process template according to the second template selection operation;

and the third association unit is used for associating the data source with the target preset background process template to generate background process data.

In one embodiment, the second generating unit further comprises:

the seventh receiving unit is used for receiving the selection operation of the second custom template through the background process selection interface;

an eighth receiving unit, configured to display a custom background flow template generation interface corresponding to the second custom template selection operation, receive a processor configuration operation and a processor connection operation through the custom background flow template generation interface, determine a configuration parameter of a processor according to the processor configuration operation, and generate a custom background flow template according to the processor connection operation;

and the fourth association unit is used for associating the data source with the user-defined background flow template to generate background flow data.

In one aspect, embodiments of the present application provide a server, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method as described above.

In one aspect, the present application provides a computer-readable storage medium having stored thereon a plurality of instructions adapted to be loaded by a processor to perform the steps of the above-described method.

The embodiment of the application provides a business management method and a business management device, based on the method, business requirements are obtained, and a data source is established based on the business requirements; displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, and generating a corresponding service component for the service composition data; displaying a service configuration interface, wherein the service configuration interface comprises a component display area, a service configuration area and a service association area; receiving a triggering operation through the component display area, and displaying a candidate service component of a service corresponding to the triggering operation in the component display area; receiving configuration operation through the service configuration area, and adding a service component corresponding to the configuration operation to the service configuration area; receiving an association path adding operation through the service configuration area, wherein the association path adding operation comprises adding an association path between corresponding service components, determining a direction for the association path, and displaying association options between a source service component and a downstream service component corresponding to the association path in the service association area according to the association path adding operation; and receiving the setting operation of the association option through the service association area, and adding the service association relationship generated according to the setting operation to the source service component and the downstream service component corresponding to the association path to generate the service corresponding to the triggering operation. According to the method and the device, after the data source is established based on the business requirement, the business composition data and the business components are generated by executing the selection operation on the business composition selection interface, the corresponding business is generated by executing the trigger operation, the configuration operation, the associated path adding operation and the setting operation on the business configuration interface, so that the operator can quickly generate a new operation application by directly operating on the interface, the operator can directly and independently operate in the whole process of constructing the operation application without communicating with game development and system developers back and forth, the labor cost is greatly reduced, the steps for constructing the operation application are reduced, the whole process period is short, and the operation is simple and easy. In addition, by setting the association option in the service association area, an operator can set the service association relation among the service components according to needs, and various operations such as independently increasing or decreasing front end pages, independently changing switching actions among the front end pages, independently establishing and disconnecting the connection between the front end pages and the background process and the like can be realized when the operator is not communicated with a developer, so that the personalized requirements of operation are met.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic view of a scenario of a service management system provided in an embodiment of the present application;

fig. 2 is a first flowchart of a service management method provided in an embodiment of the present application;

fig. 3 is a logic block diagram of creating a data source in a service management method provided in an embodiment of the present application;

fig. 4 is a logic block diagram of generating front-end page data in a service management method provided in an embodiment of the present application;

fig. 5 is a schematic diagram of a custom front-end page template in the service management method provided in the embodiment of the present application;

fig. 6 is a logic block diagram of generating background process data in a service management method provided in an embodiment of the present application;

fig. 7 is a first schematic diagram of a service configuration interface in a service management method according to an embodiment of the present application;

fig. 8 is a second schematic view of a service configuration interface in a service management method provided in an embodiment of the present application;

fig. 9 is a third schematic view of a service configuration interface in the service management method according to the embodiment of the present application;

fig. 10 is a schematic front-end page of a service in a service management method provided in an embodiment of the present application;

fig. 11 is a schematic overall flow chart of constructing an operation application in the service management method provided in the embodiment of the present application;

fig. 12 is a second flowchart of a service management method provided in an embodiment of the present application;

FIG. 13 is a schematic diagram of a game interface adding activity in the service management method according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a service management apparatus according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The embodiment of the application provides a service management method and device, a server and a computer readable storage medium. The service management device may be integrated in a server, and the server may be a terminal or the like.

The business management method provided by the embodiment of the application relates to the construction of game operation application. After a service requirement is acquired, a data source is established based on the service requirement, then a selection operation is received through a service composition selection interface, service composition data is generated according to a service composition template corresponding to the data source and the selection operation, a corresponding service component is generated for the service composition data, then a trigger operation is received through a component display area on a service configuration interface comprising a component display area and a service configuration area, a candidate service component corresponding to the trigger operation is displayed in the component display area, a configuration operation is received through the service configuration area, the service component corresponding to the configuration operation is added to the service configuration area, an association path adding operation is received through the service configuration area, and an association option between a source service component corresponding to the association path and a downstream service component is displayed in the service association area according to the association path adding operation; and finally, receiving the setting operation of the association option through the service association area, and adding the service association relationship generated according to the setting operation to the source service component and the downstream service component corresponding to the association path to generate the service corresponding to the triggering operation, thereby completing the construction of the game operation application.

Referring to fig. 1, fig. 1 is a schematic view of an office view of a service management system according to an embodiment of the present application, where the system may include terminals and servers, and the terminals, the servers, and the terminals and the servers are connected and communicated through internet formed by various gateways, and the like, where the application office view includes a user terminal 11 and a server 12; wherein:

the user terminal 11 includes, but is not limited to, a tablet Computer, a notebook Computer, a Personal Computer (PC), a micro processing box, or other devices;

the server 12 includes a local server and/or a remote server, etc.

The user terminal 11 and the server 12 are located in a wireless network or a wired network for data interaction.

The method comprises the steps that a server 12 creates a data source after acquiring a service requirement, a user terminal 11 executes selection operation on a service composition selection interface, the server 12 receives the selection operation through the service composition selection interface, generates service composition data according to a service composition template corresponding to the data source and the selection operation, and generates a corresponding service component for the service composition data, then the user terminal 11 executes trigger operation on a service configuration interface comprising a component display area and a service configuration area, the server 12 receives the trigger operation through the component display area and displays a candidate service component corresponding to the service of the trigger operation on the component display area, the user terminal 11 executes configuration operation again, the server 12 receives configuration operation through the service configuration area and adds the service component corresponding to the configuration operation to the service configuration area, the user terminal 11 executes associated path adding operation again, the server 12 receives the associated path adding operation through the service configuration area, and according to the associated path adding operation, displaying an associated option between a source service component and a downstream service component corresponding to the associated path in the service associated region, finally executing a setting operation on the associated option by the user terminal 11, receiving the setting operation by the server 12 through the service associated region, and adding a service association relation generated according to the setting operation to the source service component and the downstream service component corresponding to the associated path to generate a service corresponding to the triggering operation, thereby completing the construction of the game operation application.

It should be noted that the schematic diagram of the office view of the system shown in fig. 1 is only an example, the server and the office view described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and as a person having ordinary skill in the art knows, with the evolution of the system and the emergence of a new office view, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems. The following are detailed below. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.

Referring to fig. 2, fig. 2 is a first flowchart of a service management method according to an embodiment of the present application, and is applied to the server, where the service management method includes:

201: and acquiring a service demand, and creating a data source based on the service demand.

In the application, the service refers to an operation application which the game operator wants to construct according to operation requirements, and after the game is released, the operator operates the game through the constructed operation application so as to monitor, manage and maintain the whole life cycle of the game. The service requirement means what kind of operation application needs to be constructed to operate the game to achieve a certain operation objective, such as increasing player payment rate, increasing player number, increasing player game duration, and the like, and the constructed operation application is different based on different operation requirements, so that the service requirement needs to be acquired before the operation application is constructed. A plurality of operation applications can be constructed on the SAAS platform according to different operation requirements, each operation application is an independent application on the SAAS platform after being constructed, and the operation applications can be used after being unpacked, namely the operation applications can be directly opened to see operation data related to the game, and operation operations such as adding recharging and rebate activities and the like can be executed in the operation applications, so that the activities corresponding to the operation operations can be displayed in the game. A plurality of operation applications can be constructed on the SAAS platform according to different business requirements, each operation application is a single application, the operation applications can be presented on the SAAS platform in a list form, and an operator selects one operation application to operate the game according to needs.

SAAS is an abbreviation of Software As A Service, meaning Software is a Service, SAAS platform is a Software application platform providing Software Service based on Internet, SAAS provider builds all network infrastructure and Software and hardware operation platform required by informatization for enterprise, and takes charge of a series of services such As all early implementation, later maintenance and the like, enterprise can rent Software Service to SAAS provider according to actual need without purchasing Software and hardware, building machine room and recruiting IT personnel, and information system is used through Internet. In the application, the game enterprise sends a requirement for constructing the operation application to the SAAS provider, and the SAAS provider adds a corresponding construction function on the SAAS platform according to the requirement, so that a user can autonomously generate a service corresponding to the service requirement on the SAAS platform.

The game comprises game characteristics, the game characteristics comprise parameters such as game playing methods, game incentive mechanisms, game activities and the like, game developers or game operators can adjust the game characteristics according to the feedback of the players after the game is released, that is, the game characteristics will be different at different time intervals after the game is released, when the operator needs to construct a service, the current game characteristics are obtained from the game first, and then determining the service requirement according to the current game characteristics, if obtaining that an incentive mechanism in the current game characteristics is that a player logs in continuously for multiple days to receive a certain gift package, the player reaches a certain level to receive a high-value gift package and the like, and if the activity is that the player wants to buy certain props and needs to recharge and the like, finding that an incentive mechanism capable of improving the player payment rate is lacked, determining the service requirement to construct a service capable of improving the player payment rate.

After acquiring a service requirement, an operator needs to acquire service data related to the service first, and create a data source according to the service data, where the service data includes account data, game data, data of game activities, data of data storage nodes, and other data related to the operation, and the required service data is different based on different service requirements, and if it is desired to improve a player payment rate, it is necessary to acquire service data such as the current number of players to be recharged, the amount of money to be recharged, and if it is desired to increase the online duration of a player, it is necessary to acquire service data such as the number of players online, the current online duration, and the like. The step of creating a data source comprises: acquiring a storage type of service data based on service requirements; receiving a connection identifier selection operation through a service data selection interface, determining a connection identifier corresponding to a storage type according to the connection identifier selection operation, and acquiring service data from a storage address corresponding to the connection identifier; and determining a display field according to field selection operation on the service data, and creating a data source according to the display field.

As shown in fig. 3, the user 100 is a game operator, and the user 100 first obtains the type 21 of the service data storage based on the service requirement. During the operation of the game, game data is generated, and operation-related service data in the game data, such as data of a player, data of game activities, data of data storage nodes, and the like, may be stored in different types of locations, such as a mysql database or a rediss database, which may be stored in a database of a system where the SAAS platform is located, and may also be stored in other systems, so that, after obtaining the type 21 of service data storage, it is determined, based on the type 21, whether to remotely call the service data from other systems, or to directly obtain the service data from the database of the system, then a connection identifier selection operation is performed on a service data selection interface, a connection identifier corresponding to the storage type is selected, the service data is obtained from a storage address corresponding to the connection identifier, specifically, if the connection identifier is remotely called, the connection identifier selected on the service data selection interface is in an interface form 22, and further selects the communication protocol 23 of the target system; if it is obtained directly from the database, the connection selected on the service data selection interface is identified as database form 24 and further the database address 25 of the target database is selected or entered on this interface. After the above steps are completed, the service data corresponding to the connection identifier may be associated with the operation application, that is, the service data is obtained, because the data volume of the service data in other systems or databases is large, an operator does not need to show all the service data, after the service data is obtained, a field selection operation is performed on the service data on a service data selection interface, a field picking display 26 is selected, part of data is selected from the service data to be shown as a display field, and the display effect is made to be intuitive by showing in the form of a field, where the field may be an account number of a player, a role of the player, game start time and end time, and the like. After the field is extracted, field configuration 27 is needed, where the field configuration refers to defining parameters such as the field, the field length, and the field type, so as to ensure that the extracted field is displayed in a specified format and facilitate subsequent verification of the validity of the field. After all operations are performed on the service data selection interface, the selection operations and configuration operations are configured and stored 20, and then a data source is created on the SAAS platform. In actual operation, the operation requires more service data, so the above steps need to be repeated to create a plurality of data sources. The operator may generate data source identifiers for the created multiple data sources, specifically, names or numbers of the data sources, and may quickly find the corresponding data sources according to the data source identifiers when searching and selecting are subsequently required.

Through the step, an operator can directly perform selection operation and configuration operation on the service data selection interface to obtain the data source, and the whole process is simple and easy to implement.

202: and displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to a service composition template and a data source corresponding to the selection operation, and generating a corresponding service component for the service composition data.

For a complete service, the service composition includes a front-end page and a background flow, the front-end page is required to be generated at the front end to display service data required by an operator, the background flow is required to be generated at the background to provide relevant logic for the display of the front-end page data and the interaction between the operator and the front-end page, wherein the background flow refers to operations such as adding, deleting, modifying, checking, condition judging, calculating, file uploading and the like of the service data corresponding to the triggering operation performed by the operator after the triggering operation is performed on a control or data in the front-end page, the background flow is started based on the triggering of an associated event, the associated event refers to an action or operation required to be performed by the triggering background flow, such as clicking, pointer suspension and the like, for example, the clicking is set as an associated event of the background flow, when the operator clicks an "inquiry" button on the front-end page, the background process is started in response to the trigger operation, and the business data to be displayed is inquired, so that the front-end page displays the inquired business data. The method comprises the steps that a front-end page and a background process need to be associated to realize normal operation of a service, wherein the association refers to selection of two objects of the front-end page and the background process on an interface of an SAAS platform, a mapping relation is established between the two selected objects at the rear end of the SAAS platform, and after the mapping relation is established, relevant logics corresponding to the front-end page are provided by the background process associated with the front-end page.

After the data source is created, displaying a service composition interface, selecting operation on a service composition selection interface of the SAAS platform by a game operator, and selecting a service composition template, wherein the service composition selection interface comprises a front-end page selection interface and a background process selection interface, and the service composition template comprises a front-end page template and a background process template.

In an embodiment, the step of generating the service component specifically includes: receiving front-end page selection operation through a front-end page selection interface, generating front-end page data according to a front-end page template and a data source corresponding to the front-end page selection operation, and generating a corresponding front-end service component for the front-end page data; the background process selection operation is received through the background process selection interface, background process data are generated according to the background process template and the data source corresponding to the background process selection operation, and corresponding background business components are generated for the background process data.

Selecting a front-end page template on a front-end page selection interface, associating the front-end page template with a data source, namely selecting two objects of the front-end page template and the data source on the front-end page selection interface of the SAAS platform, establishing a mapping relation between the two selected objects at the rear end of the SAAS platform so that the data sources can be displayed in the front-end page template to generate front-end page data capable of displaying the data sources, and then generating a front-end service component corresponding to the front-end page data. There are two ways to generate front-end page data.

In one embodiment, the step of generating front-end page data comprises: receiving a first preset template selection operation through a front-end page selection interface; displaying a preset front-end page template selection interface corresponding to the first preset template selection operation, receiving the first template selection operation through the preset front-end page template selection interface, and determining a target preset front-end page template according to the first template selection operation; and associating the data source with the target preset front-end page template to generate front-end page data. As shown in fig. 4, the user 100 is a game operator, and the user 100 selects the creation type 31 of the front-end page template based on the business requirement. Before constructing an operation application, summarizing the layout and the format of front-end pages in all operation modes in the industry to form a plurality of standard page templates, wherein each standard page template has a specific layout and a specific control, adding the standard page templates into a system where an SAAS platform is located to serve as a preset front-end page template, when a user 100 executes a first preset template selection operation, namely selecting a creation type 31 as a standard, the SAAS platform displays a preset front-end page template selection interface corresponding to the first preset template selection operation, an operator can directly select a required target preset front-end page template from all the standard page templates 32 of the preset front-end page template selection interface, specifically, a data source 110 which is desired to be displayed on the front-end page is selected on the front-end page selection interface, and then the first template selection operation is executed in the standard page templates 32 of the preset front-end page template selection interface, that is, the page template selection 33 is performed, and the required target preset front-end page template is selected, the data source 110 is associated with the selected target preset front-end page template, and front-end page data 36 is generated in the SAAS platform according to the association result, where the front-end page data includes the layout of the front-end page, the setting positions of the controls, the data sources shown in the controls, and the like. After the above operations are performed, the configuration storage 30 is performed, so that the generation and storage of the front-end page data are completed, and subsequently, when the operation application is constructed, the target preset front-end page template selected this time is displayed on the front-end page, and the control in the target preset front-end page template displays the data source selected this time.

In one embodiment, the step of generating front-end page data comprises: receiving a first self-defined template selection operation through a front-end page selection interface; displaying a custom front-end page template generation interface corresponding to the first custom template selection operation, receiving layout selection operation and control selection operation through the custom front-end page template generation interface, determining a required layout according to the layout selection operation, determining a required control according to the control selection operation, and generating a custom front-end page template according to the layout and the control; and associating the data source with the self-defined front-end page template to generate front-end page data. As shown in fig. 4, when the user 100 does not find a desired template in the existing standard page templates, a first custom template selecting operation is performed, that is, the creation type 31 is selected as custom, specifically, the first custom template selecting operation is performed on the front-end page selection interface to select custom, then the SAAS platform displays a custom front-end page template generating interface corresponding to the first custom template selecting operation, the operator performs a layout selecting operation and a widget selecting operation in the custom front-end page template generating interface, that is, performs a dragging layout 34 to form a desired layout, performs dragging of a widget 35 to form a desired widget in the desired layout, generates a custom front-end page template, and then binds the data sources 110 for each widget in the custom front-end page template, so that the widget can display the content of the data source 100, then the data sources 110 are associated with the selected custom front-end page template, and generating front-end page data 36 in the SAAS platform according to the association result, wherein the front-end page data comprises the layout of the front-end page, the setting positions of the controls, the data sources shown in the controls and the like. After the above operations are executed, the configuration storage 30 is performed, so that the generation and storage of the front-end page data are completed, and subsequently, when the operation application is constructed, the self-defined front-end page template selected this time is displayed on the front-end page, and the control in the self-defined front-end page template displays the data source selected this time.

As shown in fig. 5, in order to generate the custom front-end page template generating interface when generating the custom front-end page template, the custom front-end page template generating interface in fig. 5 includes a first function area 51, a display area 52, an attribute area 53, and a second function area 54. The first functional area 51 is provided with a layout container and basic field options, and a plurality of controls are displayed under each option, for example, the controls of the layout container options include a grid layout, horizontal dividing lines, dynamic tables, tab Tabs, and the like, and the controls of the basic field options include a navigation menu, an input box, a text box, and the like. The display area 52 and the attribute area 53 are blank areas in the initial state, and the second function area 54 is provided with a return list button, a reset button, and a save button, and is further configured to display an identifier of the generated custom front-end page template, where the identifier includes a name and a number of the template, such as [ CFM weekly warfare ] query page- (186).

When the custom front-end page template is generated, one of the controls is selected from the layout container options in the first functional area 51, and then the selected control is dragged to the display area 52, at this time, the layout corresponding to the control is displayed in the display area 52, for example, when a grid layout control is selected, the layout presented in the display area 52 is a grid layout, and a required control can be added in each grid in the grid layout. If the initial blank layout is adopted by default if no relevant layout is selected in the layout container, then if the dynamic form control is selected and dragged to the display area 52, a dynamic form control is displayed in the display area 52. Based on the business requirements, a plurality of controls are selected in the layout container and dragged to the display area 52, and accordingly, a plurality of controls are displayed in the display area 52, and the positions of the controls in the display area 52 can be adjusted to generate the required customized front-end page template. The initial stage of the control in the display area 52 is represented as a blank control 522, when the user 100 generates the customized front-end page template based on the business requirement, the blank control 522 is added with fields according to its own requirement, so that the customized front-end page template becomes a function control 521 with a specific function, for example, when the customized front-end page template to be generated is an inquiry page, fields such as a start date selection box, an end date selection box, an inquiry button and the like are added to a certain blank control 522, and the specific operation is to select a corresponding field from basic field options in the first function area 51 and drag the corresponding field into the blank control 522, so that the corresponding field becomes the function control 521. In addition, after selecting a control, some basic properties of the control, such as the size of the table, the frame of the table, etc., are displayed in the property area 53, and the user 100 may set in the property area 53 to adjust the property of the corresponding control. A field & data option is further provided in the attribute area 53, when a data source is to be displayed in a certain blank control 522, if the option is triggered, a list of the data source is displayed, and then a required data source is selected from the data source, the data sources are displayed in the blank control 522 in the display area 52, and the control is bound to the displayed data source, at this time, the blank control 522 becomes a display control 523, in this embodiment, the display control 523 is formed by dragging a dynamic form control at an initial stage, and after the data source is bound, the display control 523 is used for displaying dynamic form data.

After the required layout and the required controls are determined, a custom front-end page template is generated, fields or data sources are associated with the controls in the custom front-end page template to generate corresponding function controls and display controls, then identifiers are added to the custom front-end page template, the identifiers comprise names and numbers of the templates, for example, a [ CFM Weekly warfare ] inquiry page- (186), and the specific addition mode can be directly input in the second functional area 54. After all the above operations are performed, the save button in the second functional area 54 is clicked, and the custom front-end page template generated this time is saved in the system where the SAAS platform is located. When the front-end page template is selected next time, the template generated this time can be used as a preset front-end page template for selection, namely, each time a self-defined front-end page template is generated, the template can be stored and used as a newly-added standard page template, so that the quantity of the standard page templates can be continuously increased, the selectable range is larger when the front-end page template is selected, the condition needing self-definition can be gradually reduced, and the time for generating the front-end page data is shortened.

In actual operation, the front end needs to display more than one front end page, so the above steps need to be repeated to create a plurality of front end page data. The operator may generate page identifiers, specifically, names, numbers, and the like of the pages, for the created plurality of front-end page data, and may quickly find the corresponding front-end page data according to the page identifiers when the front-end page data needs to be subsequently found. After generating the front-end page data, a corresponding front-end page component is generated for each front-end page data, and the page component identifier of the front-end page component may be the same as the page identifier.

After the front-end page data is generated, a game operator selects a background flow template on a background flow selection interface of the SAAS platform and associates the background flow template with a data source, namely selects two objects of the background flow template and the data source on the background flow selection interface of the SAAS platform, establishes a mapping relation between the two selected objects at the rear end of the SAAS platform to generate background flow data for realizing application functions of operation and application, and then generates a background service component corresponding to the background flow data. There are two ways to generate background process data.

In one embodiment, the step of generating background process data comprises: receiving a second preset template selection operation through a background process selection interface; displaying a preset background process template selection interface corresponding to the second preset template selection operation, receiving the second template selection operation through the preset background process template selection interface, and determining a target preset background process template according to the second template selection operation; and associating the data source with the target preset background process template to generate background process data. As shown in fig. 6, the user 100 is a game operator, and the user 100 first selects a creation type 41 of the background process template based on the business requirement. Before constructing an operation application, summarizing background processes in all operation modes in the industry to form a plurality of standard process templates, adding the standard process templates into a system where an SAAS platform is located to serve as a preset background process template, when a user 100 executes a second preset template selection operation, namely, selects a creation type 41 as a standard, a preset background process template selection interface corresponding to the second preset template selection operation is displayed on the SAAS platform, an operator can directly select a required target preset background process template from all standard process templates 42 of the preset background process template selection interface, specifically, a data source 110 is selected on the background process template selection interface, then the second template selection operation is executed in the standard process templates 42 of the preset background process template selection interface, namely, a process template selection 43 is performed, if the required target preset background process template is selected, the data source 110 is associated with the selected target preset background process template, the background process after association can realize transparent transmission of the data source 110 and packaging and issuing of the data source 110, and then the corresponding associated event 47 is selected for the process in the target preset background process template after association of the data source. In the present application, a background process refers to relevant logic that needs to be implemented by an operation application, such as adding, deleting, modifying, checking, and the like, and a related event refers to an action or operation that needs to be performed by triggering the background process, such as an action event that needs to process data before and after adding data, and the like. After the above operations are executed, background process data is generated in the SAAS platform, where the background process data includes configuration of middle processes of the background process, events related to the background process, and the like, then configuration storage 40 is performed to complete generation and storage of the background process data, and subsequently when an operating application is built, a corresponding background process is started according to the trigger of the related event.

In one embodiment, the step of generating background process data comprises: receiving a second custom template selection operation through a background process selection interface; displaying a user-defined background flow template generation interface corresponding to the second user-defined template selection operation, receiving processor configuration operation and processor connection operation through the user-defined background flow template generation interface, determining configuration parameters of a processor according to the processor configuration operation, and generating a user-defined background flow template according to the processor connection operation; and associating the data source with the user-defined background flow template to generate background flow data. As shown in fig. 6, when the user 100 does not find a desired template in the existing standard flow templates, a second custom template selection operation is performed, that is, the creation type 41 is selected as a custom, specifically, the second custom template selection operation is performed on the background flow selection interface to select a custom, then the SAAS platform displays a custom background flow template generation interface corresponding to the second custom template selection operation, the operator performs a processor configuration operation and a processor connection operation in the custom background flow template generation interface, the processor configuration operation refers to selecting the background processor 44 to perform background flow configuration 45, so that the SAAS platform has a capability of processing data according to preset logic and steps after acquiring the data, and the configuration process specifically includes basic information configuration, input field configuration, related parameter configuration, output field configuration, and the like, after configuration, each processor has corresponding configuration parameters, which can be used for performing specific operations such as updating, querying, calculating and the like, usually, a plurality of flow processors 46 need to be generated, each flow processor 46 is used for performing one operation, the processor connection operation includes connecting the plurality of flow processors 46 in series according to a preset sequence, specifically, after configuration of each flow processor 46 is completed, generating corresponding flow components for each flow processor 46, then arranging the flow components in the preset sequence in a custom background flow template generation interface, and adding flow association paths between adjacent components, namely adding associated lines with arrows, wherein an arrow is pointed to a next flow by a previous flow, and after an upper flow association path is added between each flow component, storing the arrangement operations and the path addition operations, so that processing logics of each flow processor 46 are combined with each other, a complete set of processing logic is formed to generate a custom background flow template, and then the data source 110 is associated with the custom background flow template, and a corresponding associated event 47 is selected for the flow in the custom background flow template after the data source is associated. After the above operations are executed, background process data is generated in the SAAS platform, then configuration storage 40 is performed to complete generation and storage of the background process data, and subsequently, when the running application is constructed, the background starts the corresponding background process according to the trigger of the associated event.

In actual operation, there are many interactions between the user and the operating application on the front-end page, and there are also many corresponding background processes, so that the above steps need to be repeated to create multiple background process data. The operator may generate a process identifier for the created plurality of background process data, specifically, the process identifier may be a name, a number, and the like of the process, and may quickly find the corresponding background process data according to the process identifier when needing to find the corresponding background process data in the subsequent process. After the background process data is generated, a corresponding background business component is generated for each background process data, and the process component identifier of the background business component may be the same as the process identifier.

Through the steps, the operator can directly select the service composition template and the data source on the service composition interface and associate the service composition template and the data source, front-end page data and background process data can be generated simply and intuitively, the data do not need to be generated by repeatedly communicating and communicating with developers, compiling codes and the like, and the professional requirements on the operator are greatly reduced. And after the user-defined front-end page template and the user-defined background flow template are generated each time, the user-defined front-end page template and the user-defined background flow template can be stored as a new preset front-end page template and a new preset background flow template, and the selectable template range can be gradually increased when other services are constructed subsequently, namely, the more times the services are constructed on the SAAS platform, the larger the selectable template range is, the fewer and fewer conditions need to be defined, and therefore, the efficiency of constructing the services can be gradually improved.

203: and displaying a service configuration interface, wherein the service configuration interface comprises a component display area, a service configuration area and a service association area.

The service configuration interface comprises a component display area, a service configuration area and a service association area, when the service configuration interface initially enters the service display interface, a list of each service is displayed in the component display area, each service in the list displays a respective service identifier, specifically, a service name and/or a service number, and the like, and the service configuration area and the service association area are blank areas. The front-end service components and the background service components generated in the above steps are visual components corresponding to front-end service data and background process data, and are all stored in the SAAS platform, and the front-end service components and the background service components belonging to the same service all have the same service identifier, when entering a service configuration interface, all the front-end service components and all the background service components belonging to the same service are all located in a sub-list of the service, and jointly form candidate service components of the service.

204: and receiving the triggering operation through the component display area, and displaying the candidate service components of the service corresponding to the triggering operation in the component display area.

And each service in the service list has a corresponding sub-list, when a trigger operation is received, the service corresponding to the trigger operation shows the corresponding sub-list, and other services still only display the service identifier. And displaying candidate service components corresponding to the service in the sub-list, wherein the candidate service components comprise a front-end service component and a background service component corresponding to the service. Because the operator needs to see the operation data, needs the front-end page to display the data source, and meanwhile, the operator has an operation requirement on the front-end page and needs the background process to provide processing logic for each operation, the front-end page data and the background process data are necessary components for forming a complete service, and the candidate service component in the application needs to include a front-end service component and a background service component.

205: and receiving configuration operation through the service configuration area, and adding the service component corresponding to the configuration operation to the service configuration area.

The game operator performs configuration operation in the service configuration area, specifically, a candidate service component in the component display area is selected and dragged to the service configuration area, or an insertion component is selected in the service configuration area, and then a candidate service component is selected in the component display area, and the server receives configuration operation through the service configuration area.

The service configuration area is blank in the initial state, when configuration operation is received, candidate service components corresponding to the configuration operation in the component display area are added to the service configuration area, the service components can be placed at any position in the service configuration area, or grid layout is set in advance in the service configuration area, and then the service components can be placed at certain preset positions.

In one embodiment, this step includes: and adding the front-end service component and the background service component corresponding to the configuration operation to the service configuration area. For the same service, a front-end service component and a background service component are displayed in a sub-list of the service, templates corresponding to the two components are both associated with a data source, but the front end and the background are still independent, so that when configuration operation is performed, a front-end service component corresponding to the service requirement is selected from the sub-list displayed by the service and is added to a service configuration area, then the background service component corresponding to each front-end service component is determined according to the corresponding relation between a front-end page corresponding to each added front-end service component and a background process, and the background service component is also added to the service configuration area.

As shown in fig. 7, the service configuration interface includes a component display area 71 and a service configuration area 72, a service list is displayed in the component display area 71, the service may include a white list task, a video relay, CFM weekly warfare report management, multimedia management, and the like, and when a certain service is triggered, candidate service components corresponding to the service, including a front-end service component and a background service component, are displayed. Taking a white list task as an example, when the white list task is triggered, a front-end service component and a background service component corresponding to the white list task are displayed in the component display area 71, wherein the front-end service component may include a [ on-demand ] general white list home page 711, a [ on-demand ] white list 712, an [ on-demand ] service configuration table 713, an [ on-demand ] import white list 714, an [ on-demand ] newly-added edit configuration 715 and an [ on-demand ] callback configuration 716, and the background service component may include a setting service COOKIE721, an [ on-demand ] query redisk list 723, an [ on-demand ] added white list task 724, an [ on-demand ] configuration list 725 and an [ on-demand ] configuration adding edit 726.

The user 100 executes configuration operation on the service configuration interface, where the configuration operation may specifically be dragging, and sequentially adds the front-end service component and the background service component corresponding to the white list task to the service configuration area 72. Each front-end service component is sequentially arranged in the service configuration area 72 from top to bottom, between two front-end service components adjacent to each other from top to bottom, the front-end page corresponding to the front-end service component below is a sub-page of the front-end service component above, that is, after entering the operation application, the front-end page corresponding to the front-end service component above is displayed first, and after the user 100 performs the selection operation on the page, the front-end page corresponding to the front-end service component below, that is, the sub-page, is displayed. For example, there are two options, namely a white list and a service configuration list, on the first page of the general white list, when the white list is selected, a front-end page corresponding to the front-end service component of the [ on-demand ] white list 712 is displayed, and on the front-end page corresponding to the front-end service component of the [ on-demand ] white list 714 is displayed when the white list is selected to be imported, and so on. Each background service component is determined according to the position of a front-end service component when being added, when a front-end page corresponding to a certain front-end service component needs to use a flow corresponding to a certain back-end service component, the back-end service component is added above or below the front-end service component, for example, after a triggering event for introducing a white list is received in a front-end page corresponding to a white list 714, a background flow is needed to perform the processing of adding the white list task, so that a white list adding task 724 in the background service component is added below the white list 714 in the front-end service component.

When the service configuration interface does not find the required service components, a plug-in mode can be used firstly, namely, the required service components are written and generated by manually using a plug-in self-writing program or an interface provided by a system, the plug-in self-writing program or the interface is embedded into the current SAAS platform for completion, and then the newly added service components are associated with the original service components through triggering operation, configuration operation and association operation continuously on the service configuration interface to generate corresponding services. As shown in fig. 7, a component area 73 is further disposed on the right side of the service configuration area, and when a plug-in option is selected in the component area 73, an element corresponding to the plug-in can be selected and a corresponding code can be written therein, so as to generate a new service component. By adopting the plug-in mode, the selection range of operators is increased, the operation application is more flexible and changeable, and more operation requirements are met.

206: and receiving an associated path adding operation through the service configuration area, wherein the associated path adding operation comprises adding an associated path between corresponding service components, determining a direction for the associated path, and displaying an associated option between a source service component and a downstream service component corresponding to the associated path in the service associated area according to the associated path adding operation.

The game operator executes an associated path adding operation in the service configuration area, wherein the associated path adding operation is specifically to add a line with an arrow between an upper service component and a lower service component which are associated with each other, the line represents an associated path between the two service components, and the direction of the arrow represents the direction of the associated path. After adding the associated path, the component area 73 of the interface in the previous step becomes a service associated area 75, and the associated option between the source service component and the downstream service component corresponding to the associated path is displayed in the service associated area 75.

In one embodiment, the steps specifically include: determining a service component corresponding to the initial point of the associated path as a source service component and determining a service component corresponding to the point pointed by the associated path as a downstream service component according to the associated path adding operation; and displaying association options between the source service component and the downstream service component in the service association area, wherein the association options comprise a downstream service component triggering type option, a service association relation establishment option and a downstream service component filling position option. The association path is a line with an arrow, the line comprises a starting point and a pointing point, after the association path is added between the two service components, the service component connected with the starting point of the line is used as a source service component, and the service component connected with the pointing point of the line is used as a downstream service component. Each time an association path is added in the service configuration area, association options between the source service component and the downstream service component corresponding to the association path are displayed in the service association area 75, where the association options include an option of whether to establish a service association relationship, an option of a trigger type of the downstream service component, and an option of a filling position of the downstream service component. The association path may be added between two front-end service components, or between one front-end service component and one back-end service component. For different association path adding modes, the contents of the association options correspondingly displayed in the service association area 75 are also different.

When the association path is added between the two front-end service components, the source service component and the downstream service component are both front-end service components, whether to establish a service association option in the association option includes whether to enter a front-end page corresponding to the downstream service component through a triggering operation on the front-end page corresponding to the source service component, the downstream service component triggering type option includes what type of triggering operation is executed on the front-end page corresponding to the source service component to enter the front-end page corresponding to the downstream service component, and the downstream service component filling selection includes what type of front-end page corresponding to the downstream service component appears on the front-end page corresponding to the source service component. As shown in fig. 8, the service components in the service configuration area 72 are arranged in order, at this time, the user 100 executes an associated path adding operation in the service configuration area 72, adds a line between two front-end service components associated with each other, and an arrow points to a next front-end service component from a front-end service component in the previous stage, if an associated path is added between the first page 711 of the universal white list and the service configuration table 713 of "on demand", then the associated options displayed in the service association area 75 include menu items, trigger types, downstream component loading, and downstream component filling to the same, and the service component identifier "service configuration" corresponding to the service configuration table 713 of "on demand" is displayed in the menu items by default, the trigger types include none, loading, single-click, double-click, change, hover, and self-definition, the downstream component loading includes yes and no, and the downstream component filling to the same includes none, zero, and, A popup window, a source component, and a process entry.

When the association path is added between a front-end service component and a background service component, the source service component is the front-end service component, the downstream service component is the background service component, whether the service association relationship option is established in the association option comprises whether the background process corresponding to the downstream service component can provide the relevant logic for the front-end page corresponding to the source service component, the downstream service component triggering type option comprises what type of triggering operation is executed on the front-end page corresponding to the source service component to start the background process corresponding to the downstream service component, and the downstream service component filling position option comprises what position of the front-end page corresponding to the source service component to trigger to start the background process corresponding to the downstream service component. As shown in fig. 9, the service components in the service configuration area 72 are arranged in order, at this time, the user 100 performs an associated path adding operation in the service configuration area 72, adds a line with an arrow between the front-end service component and the corresponding back-end service component, where the arrow points to the back-end service component from the front-end service component, and if an associated path is added between the [ on-demand ] service configuration table 713 and the [ on-demand ] configuration list 725, the associated options displayed in the service association area 75 include a trigger element, a trigger type, a downstream component loading, a downstream component padding to and the like, the trigger type includes none, loading, single-click, double-click, change, hover, and custom, the downstream component loading includes yes and no, and the downstream component padding to include none, a source component, and a flow entry.

In one embodiment, after the step of receiving the associated path adding operation through the service configuration area, the method further includes: and receiving association identifier adding operation through the service configuration area, wherein the association identifier adding operation comprises adding an association identifier corresponding to a downstream service component on an association path based on the downstream service component pointed by the association path. The associated identifier adding operation is specifically to add a text description on the added line, where the content of the text description is based on the function of the downstream service component to which the associated path points, for example, if the identifier content added on the line between the [ on-demand ] import white list 714 and the [ on-demand ] add white list task 724 is the [ on-demand ] add white list task, the function of the background flow corresponding to the background service component, which represents the [ on-demand ] add white list task 724, is used to execute the white list add task, and the identifier content of the associated identifier in the present application is the same as the name of the downstream service component, but not limited thereto, and may not be the same as the name of the service component, or may be other characters added by the operator based on own habits and understanding. After each service component and the associated path are added to the service configuration area 72, a tree structure is formed in the service configuration area 72, and when the operation application desired to be constructed is complex, the tree structure is also complex and huge, and at this time, because the associated path is added with the associated identifier, an operator using the service configuration interface can visually see what logic is based on which association between each service component in the tree structure.

207: and receiving the setting operation of the association option through the service association area, and adding the service association relationship generated according to the setting operation to the source service component and the downstream service component corresponding to the association path so as to generate the service corresponding to the trigger operation.

After the association options are displayed in the service association area 75, setting operation is performed on each association option, service association relations generated by different setting operations are different, according to the setting operation, a service association relation is established between corresponding service components, when two service components associated with each other are front-end service components, it is indicated that a front-end page corresponding to a next front-end service component is a sub-page of a previous front-end service component, that is, the previous front-end page is displayed first after the operation application is entered, and a back front-end page corresponding to a control, that is, a sub-page, is displayed only after the control is triggered on the front-end page. When one of the two service components which are associated with each other is a front-end service component, and the other is a background service component, it indicates that the flow corresponding to the background service component is used for starting after the front-end page corresponding to the front-end service component receives the trigger of the associated event, so as to perform corresponding data processing.

As shown in fig. 8, an association path is added between the [ on-demand ] universal white list home page 711 and the [ on-demand ] service configuration table 713, then the association options displayed in the service association area 75 include menu items, trigger types, downstream component loading, downstream component filling and other options, a setting operation is performed on these association options, a downstream component loading operation is set to "yes", which indicates that a service association relationship is to be added between the [ on-demand ] universal white list home page 711 and the [ on-demand ] service configuration table 713, a page of the service configuration table can be entered after the white list home page is subjected to the trigger operation, the trigger type is set to "single click", which indicates that the page of the service configuration table can be entered after the white list home page is subjected to the single click trigger operation, the downstream component filling operation is set to "source component", a secondary association option will appear, which includes a filling type, the filling type is set to "position selection", then, three levels of association options including a position and a filling mode are presented, the position is selected and the filling mode is set to be 'covered', which means that a triggering operation is performed on the white list home page according to the selected position, a page of the service configuration table is directly displayed on the white list home page, and the page of the service configuration table is directly displayed on the white list home page in a covered manner. When the setting operation is different, the correspondingly generated business association relations are also different, for example, when the downstream component is set to be loaded to be "no", it indicates that although an association path is added between the two business components, the business association relation is not actually established between the two business components, and the page of the business configuration table is not displayed after the white list first page is displayed, that is, the number of the front-end pages is increased or decreased autonomously by setting the "yes" and "no" loaded by the downstream component. For example, if the trigger type is changed from "single-click" to "hover", it means that the trigger operation when the white list top page is switched to the service configuration table page is changed from single-click to hover on the white list top page, that is, by setting different trigger types, the switching action between the front end pages is changed autonomously.

As shown in fig. 9, an association path is added between the [ on demand ] service configuration table 713 and the [ on demand ] configuration list 725, and then the association options displayed in the service association area 75 include options such as a trigger element, a trigger type, a downstream component loading, and a downstream component filling. Setting the loading of the downstream component as "yes", which means that a service association relation is to be added between the [ on-demand ] service configuration table 713 and the [ on-demand ] configuration list 725, when a trigger operation is performed on a front end page of the service configuration table, a configuration list background process is started, a trigger element is set as "search", a trigger type is set as "loading", which means that when a loading operation is performed in a search box of the front end page of the service configuration table, the corresponding configuration list background process is started, the downstream component is set to be filled as "source component", a secondary association option including a filling type and a filling type as "position selection" appears, a tertiary association option including a position and a filling manner is generated, the position is selected and the filling manner is set as "overlay", which means that a trigger operation is performed on the front end page of the service configuration table according to the selected position, the background process of the configuration list is directly triggered, and the background process of the configuration list contacts with a front-end page of the service configuration list in an overlay mode. When the setting operation is different, the correspondingly generated service association relations are also different, for example, when the downstream component is set to be loaded to be 'no', the association path is added between the two service components, but the service association relation is not actually established between the two service components, the background process of the configuration list does not provide logic for the front-end page of the service configuration list, namely, the connection between the front-end page and the background process is automatically established and disconnected by setting the 'yes' and 'no' of the downstream component loading, certain unnecessary connections can be selectively disconnected according to needs in some use scenes, and the effect of simplifying operation application is achieved.

After adding the business association relationship to all the corresponding business components, clicking and storing on a business configuration interface, associating the front-end page corresponding to the business components with the background process according to the business association relationship, forming an organic whole for each part, generating a business, namely an operation application, corresponding to the triggering operation on the SAAS platform according to the stored configurations, and allowing game operators to automatically allocate operation permission in the operation application and determine the usable range and the use range of the personnel. By setting the association option in the service association area, the operator can set the service association relationship among the service components as required, and can realize various operations such as independently increasing or decreasing the front-end pages, independently changing the switching action among the front-end pages, and independently establishing and disconnecting the connection between the front-end pages and the background process when not communicating with the developer, namely, different operation applications can be generated according to the difference of the setting operation of the association option on the premise that only one tree structure is established in the service configuration area, so that the autonomy and flexibility of constructing the operation applications are greatly improved, and the individual requirements of operation are met.

Before the SAAS platform builds the operation application, the SAAS platform provides an SDK (software development kit) for the game, game developers import the SDK into game engineering, the game pulls up the SDK after the game is initialized, the SDK is displayed in a presentation mode temporarily covering a game panel and can interact with game data in a game bottom layer through an interface or interact with game data stored in other systems in a separately written communication mode. After the operation application is constructed, some configurations performed by the game operator in the operation application are slid down to the SDK and an interface is rendered in the game by the SDK, so that the association between the operation application and the game is realized.

As shown in fig. 10, after a service is generated on the SAAS platform, the service is directly entered, the displayed data source can be seen on the front-end page of the display, taking selecting a white list page after entering the first page of the general white list as an example, when one or some data sources in the page need to be viewed, a selection operation is performed in the query area 81, such as selecting an application, an application type, an application state, a large area to which a game belongs, a platform to which the game belongs, a small area to which the game belongs, and the like, and then a search is clicked, a background process corresponding to the white list page is started based on the click operation, a search of the data source is performed based on the selected conditions, and then a data source list meeting the selected conditions is displayed in the data source display area 82, each piece of information in the data source list includes a task ID, an application name, a type, a size, creation information, a state, an update information, and, the operator can then select the data source that he needs himself and click on this data source to obtain further information.

Through the seven steps, after a data source is established based on business requirements, the selection operation is executed on the business composition selection interface to generate business composition data and business components, the triggering operation, the configuration operation, the associated path adding operation and the setting operation are executed on the business configuration interface to generate corresponding business, so that an operator can quickly generate a new operation application through direct operation on the interface, the operator can directly and independently operate in the whole process of constructing the operation application without communicating with game development and system development personnel back and forth, the labor cost is greatly reduced, the steps of constructing the operation application are reduced, and the whole process period is short, simple and easy to operate. In addition, by setting the association option in the service association area, an operator can set the service association relation among the service components according to needs, and various operations such as independently increasing or decreasing front end pages, independently changing switching actions among the front end pages, independently establishing and disconnecting the connection between the front end pages and the background process and the like can be realized when the operator is not communicated with a developer, so that the personalized requirements of operation are met.

As shown in fig. 11, in the service management method of the present application, an operator first sends a request for refining characteristics to a game, the game returns all characteristics, then the operator generates an operation requirement according to the characteristics, sends a request for arranging a data source to an SAAS platform based on the requirement, then sequentially performs data source configuration, front-end page configuration, and background flow configuration on the SAAS platform, constructs an operation application after associating the front-end page with the background flow, and submits the operation application to a tester, and the tester returns a test result to the operator after testing, and if the test result is passed, the operator can normally use the operation system. Compared with the prior art, operators can directly carry out association between the front-end page and the background process on the SAAS platform in a dragging mode after operation requirements exist, the required operation application is quickly built, the requirement document does not need to be written first to be repeatedly communicated and developed by game developers and system developers, and the operators who do not know development can also quickly generate the required operation application.

Fig. 12 is a second flowchart of a service management method according to an embodiment of the present application, please refer to fig. 12, where the service management method includes the following steps:

901: the first user terminal arranges the template.

The first user terminal is any terminal used by a worker who can have SAAS platform access authority, the worker is usually a game operator, the operator arranges all front-end pages and background processes in the current industry on the first user terminal to generate a preset front-end page template and a preset background process template, and uploads the preset front-end page template and the preset background process template to the server.

902: the server stores the template.

The server stores all the templates uploaded by the first user terminal in a system where the SAAS platform is located, and when other authorized users access the SAAS platform, the templates can be obtained from the SAAS platform.

903: the second user terminal obtains game characteristics from the game.

The second user terminal is a terminal used by a game operator, and may be the same as or different from the first user terminal, and when the game operator wants to construct an operation application, the game operator needs to first acquire the current game characteristics of the game, where the game characteristics include parameters such as a game playing method, a game incentive mechanism, and game activities.

904: the second user terminal refines the service requirements.

And the operator of the second user terminal compares and analyzes the current game characteristic with an expected target to extract a service requirement, wherein the service requirement refers to what kind of operation application needs to be constructed to achieve a certain operation target, such as improving the payment rate of players, increasing the number of the players, increasing the game duration of the players and the like, under the current game characteristic.

905: and the second user terminal displays the service data selection interface.

When it is determined what service is to be constructed, the second user terminal needs to acquire service data related to the service first, and the service data is selected on a service data selection interface displayed by the second user terminal.

906: the second user terminal receives a connection identity selection operation.

The service data is stored in different types of locations, for example, the service data may be stored in a database of a system where the SAAS platform is located, such as a mysql database or a redis database, or may be stored in other systems, so that it is necessary to select a connection identifier corresponding to the storage type first, then obtain the service data from a storage address corresponding to the connection identifier, and after selecting the corresponding connection identifier, an operator selects different data call forms according to the difference of the connection identifier, and further selects or inputs a communication protocol or a database address corresponding to the connection identifier.

907: the second user terminal obtains the service data from the server.

And the second user terminal sends the selected content to the server, so that the service data corresponding to the connection identifier can be acquired from the server.

908: the second user terminal receives a field selection operation.

The acquired business data is large in data volume, and the business data does not need to be displayed completely, so that after the business data is acquired, operators receive field selection operation on a business data selection interface, select partial data from the business data to be displayed as display fields, and display in the form of the fields enables the display effect to be visual.

909: the second user terminal sends a data source creation request to the server.

And after the display field is obtained, the second user terminal sends a data source creating request to the server to request for creating the data source.

910: the server creates a data source.

And the server creates a data source corresponding to the service according to the request sent by the second user terminal and each item of selection content on the service data selection interface.

911: and the second user terminal displays the service composition selection interface.

And after the data source is created, displaying a service composition interface, and selecting a service composition template by an operator on a service composition selection interface of the SAAS platform, wherein the service composition selection interface comprises a front-end page selection interface and a background process selection interface, and the service composition template comprises a front-end page template and a background process template.

912: the second user terminal receives the selection operation.

The second user terminal receives the selection operation, which may specifically include a front-end page selection operation and a background process selection operation. An operator firstly selects a front-end page template on a front-end page selection interface of the SAAS platform, when the preset front-end page template in the SAAS platform can meet the requirement, the required front-end page template is directly determined from the preset front-end page template, and when the requirement cannot be met, the user-defined front-end page template is generated in a dragging layout and control mode. Then, an operator selects a background flow template on a background flow selection interface of the SAAS platform, when the background flow template preset in the SAAS platform can meet the requirement, the operator directly determines the required background flow template from the preset background flow template, and when the requirement cannot be met, the operator generates a user-defined background flow template in a mode of configuring and connecting a processor.

913: the second user terminal obtains the data source from the server.

After the front-end page template is determined, the data source needs to be displayed in the corresponding front-end page, and after the background flow template is determined, the corresponding data source needing to be processed needs to be selected, so that the second user terminal obtains the data source created in the previous step from the server.

914: the second user terminal associates the data source with the service composition template.

The method comprises the steps that an operator selects a front-end page template and a data source to be displayed on a front-end page selection interface displayed by a second user terminal, associates the front-end page template and the data source to be displayed, selects a background process template and the data source to be processed on a background process selection interface, associates the background process template and the data source to be processed, and after the operator performs association operation on the interface, a background of the SAAS platform establishes a mapping relation for the selected front-end page template and the selected data source, so that the front-end page can display the selected data source, the background process can process the selected data source, and generates front-end page data and background process data according to an association result after the association.

915: the second user terminal sends a request for generating a service component to the server.

After the front-end page data and the background process data are generated, the second user terminal sends a request for generating a service component to the server to request for generating a front-end service component corresponding to the front-end page data and a background service component corresponding to the background process data.

916: the server generates a business component.

After receiving the request, the server generates a corresponding front-end page component for each piece of front-end page data, the page component identifier of the front-end page component can be the same as the page identifier, the server generates a corresponding background business component for each piece of background process data, the page component identifier of the background business component can be the same as the process identifier, and each business component is a visual component which can be displayed on a second user terminal interface.

917: and the second user terminal displays the service configuration interface.

The second user terminal displays a service configuration interface, the service configuration interface comprises a component display area, a service configuration area and a service association area, when the second user terminal initially enters the service configuration interface, a list of each service is displayed in the component display area, each service in the list displays a respective service identifier, specifically, a service name and/or a service number, and the service configuration area and the service association area are blank areas.

918: and the second user terminal receives the trigger operation and displays the candidate service components.

The sub-list corresponding to each service in the service list is provided, and the operator executes a triggering operation in the component display area, specifically, the operator may click or touch a service identifier of a certain service in the service list, the service corresponding to the triggering operation shows the sub-list corresponding to the triggering operation, and other services still only display the service identifier. And displaying candidate service components corresponding to the service in the sub-list, wherein the candidate service components comprise a front-end service component and a background service component corresponding to the service.

919: and the second user terminal executes configuration operation and adds the service component to the service configuration area.

The configuration operation is executed by the operator in the service configuration area, specifically, a candidate service component in the component display area is selected and dragged to the service configuration area, or a component is selected and inserted in the service configuration area, and then a candidate service component is selected in the component display area, and the server receives the configuration operation through the service configuration area. And in the initial state, the service configuration area is blank, and when the server receives configuration operation, candidate service components corresponding to the configuration operation in the component display area are added to the service configuration area. For the same service, a front-end service component and a background service component are displayed in a sub-list of the service, templates corresponding to the two components are both associated with a data source, but the front end and the background are still independent, so when configuration operation is received, the front-end service component corresponding to the sub-list displayed by the service needs to be added to a service configuration area, then the background service component corresponding to each front-end service component is determined according to the corresponding relation between the front-end page corresponding to each added front-end service component and the background process, and the background service component is also added to the service configuration area.

920: and the second user terminal executes the associated path adding operation and displays the associated options.

An operator executes an associated path adding operation in a service configuration area, wherein the associated path adding operation is specifically to add a line with an arrow between an upper service component and a lower service component which are associated with each other, the line represents an associated path between the two service components, the direction of the arrow represents the direction of the associated path, the service component corresponding to a starting point of the associated path is a source service component, the service component corresponding to the direction point is a downstream service component, and after the associated path is added, an associated option between the source service component corresponding to the associated path and the downstream service component is displayed in the service associated area.

921: the second user terminal receives a setting operation.

After the association options are displayed in the service association area, the operator sets each association option, and service association relations generated by different setting operations are different.

922: and the second user terminal sends a service association relation adding request to the server.

And after the setting is finished, the second user terminal sends a service association relation adding request to the server, and the request is to add the association relation between the source service component and the downstream service component corresponding to the association path.

923: and adding business association relation among the business components by the server.

And the server establishes an association relationship between the corresponding service components according to the association path and the specific setting content of the association option, and then establishes a mapping relationship between the front-end pages or the background processes corresponding to the two service components with the service association relationship. When two related service components are front-end service components, the front-end page corresponding to the next front-end service component is a sub-page of the previous front-end service component, namely the previous front-end page is displayed first after the operation application is started, and the back front-end page corresponding to a control, namely the sub-page, is displayed after the control is triggered on the front-end page. When one of the two service components which are associated with each other is a front-end service component, and the other is a background service component, it indicates that the flow corresponding to the background service component is used for starting after the front-end page corresponding to the front-end service component receives the trigger of the associated event, so as to perform corresponding data processing.

924: the server generates the traffic.

After adding the association relationship to all the corresponding business components, clicking and storing on a business configuration interface, associating the front-end page corresponding to the business components with the background process according to the association relationship, forming an organic whole for each part, then generating a business, namely an operation application, on the SAAS platform by the server according to the stored configuration, and enabling game operators to automatically distribute operation permissions in the operation application and determine which personnel can use and the use range.

The application takes the second user terminal to construct the operation application as an example, and shows that the application can enable the operator to generate a new operation application quickly through selection operation, trigger operation, configuration operation, associated path adding operation and setting operation without communicating with game development and system developers back and forth, so that the labor cost is greatly reduced, the steps for constructing the operation application are reduced, and the whole process is short in period, simple and easy to operate.

Taking the service requirement as an example for constructing a service capable of improving the player's payment rate, after the construction of the operation application is completed, the operation application is entered, a front-end page for displaying the user's recharging data is selected, data sources such as the current number of recharging people, recharging amount, payment rate and the like of the player can be obtained, then a front-end page for displaying prop purchasing data is selected, data sources such as the occupation ratio of each prop purchased by the player with the recharging amount and the like can be obtained, after the analysis, a large proportion of players can select to purchase one or a plurality of props after recharging, which shows that if a certain number of hot props are returned to the player after the player is recharged, the player's payment rate can be improved to a certain extent, so that the operator can add a recharging and rewarding activity on the operation platform, the activity slides down to the SDK interface of the X game and the SDK renders an activity interface in the game, as shown in fig. 13, when the player enters the X game or clicks the "activity" icon after entering the game, the game interface 131 of the game or pops up the activity interface 132 to show the daily recharging and rebate activity, where the recharging and rebate activities at different gears are set in the activity, such as the recharging of 20 to XX prop X1, the recharging of 100 to XX prop X6, the recharging of 300 to XX prop X25, the recharging of 500 to XX prop X50, etc., and a "immediate recharging" button is shown in each gear recharging activity, and the player can perform the recharging activity at the corresponding gear and obtain the XX prop at the gear by clicking the button. Through the process, after obtaining game characteristics, an operator determines that a service requirement is a service which can improve the player payment rate, based on the service requirement, obtains service data related to the player payment rate, creates a data source according to the service data, displays the service data on a corresponding front-end page under the processing of a background process after the operation application is built, analyzes the data, determines that a recharging and rewarding activity needs to be added, adds the activity on an operation platform and slides down to the game, and finally enables the player to enter the activity in the game to carry out corresponding recharging operation so as to improve the player payment rate.

On the basis of the method in the foregoing embodiment, the present embodiment will be further described from the perspective of a service management device, please refer to fig. 14, where fig. 14 specifically describes the service management device provided in the embodiment of the present application, which may include:

a creating module 101, configured to acquire a service requirement, and create a data source based on the service requirement;

a generating module 102, configured to display a service composition selection interface, receive a selection operation through the service composition selection interface, generate service composition data according to the data source and a service composition template corresponding to the selection operation, and generate a corresponding service component for the service composition data;

the first display module 103 is configured to display a service configuration interface, where the service configuration interface includes a component display area, a service configuration area, and a service association area;

a second display module 104, configured to receive a trigger operation through the component display area, and display a candidate service component of a service corresponding to the trigger operation in the component display area;

a first adding module 105, configured to receive a configuration operation through the service configuration area, and add a service component corresponding to the configuration operation to the service configuration area;

a third display module 106, configured to receive, through the service configuration area, an association path adding operation, where the association path adding operation includes adding an association path between corresponding service components, determining a direction for the association path, and displaying, according to the association path adding operation, an association option between a source service component and a downstream service component corresponding to the association path in the service association area;

a second adding module 107, configured to receive, through the service association area, a setting operation on the association option, and add a service association relationship generated according to the setting operation to a source service component and a downstream service component corresponding to the association path, so as to generate a service corresponding to the trigger operation.

In one embodiment, the third display module 106 comprises:

In one embodiment, the creation module 101 includes:

In one embodiment, the generation module 102 includes:

In one embodiment, the first generation unit includes:

In one embodiment, the first generation unit further includes:

In one embodiment, the second generating unit includes:

In one embodiment, the second generating unit further comprises:

and the fourth association unit is used for associating the data source with the user-defined background flow template to generate background flow number.

Different from the prior art, the message management device provided by the application generates service composition data and service components by executing selection operation on the service composition selection interface after a data source is created based on service requirements, and generates corresponding services by executing triggering operation, configuration operation, associated path adding operation and setting operation on the service configuration interface, so that an operator can quickly generate a new operation application by directly operating on the interface. In addition, by setting the association option in the service association area, an operator can set the service association relation among the service components according to needs, and various operations such as independently increasing or decreasing front end pages, independently changing switching actions among the front end pages, independently establishing and disconnecting the connection between the front end pages and the background process and the like can be realized when the operator is not communicated with a developer, so that the personalized requirements of operation are met.

Accordingly, an embodiment of the present application further provides a server, as shown in fig. 15, which shows a schematic structural diagram of the server according to the embodiment of the present application, and specifically:

the server may include components such as a processor 1101 of one or more processing cores, memory 1102 of one or more computer-readable storage media, a power supply 1103, and an input sub-module 1104. Those skilled in the art will appreciate that the server architecture shown in FIG. 15 is not meant to be limiting, and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:

the processor 1101 is a control center of the server, connects various parts of the entire server using various interfaces and lines, and performs various functions of the server and processes data by running or executing software programs and/or modules stored in the memory 1102 and calling data stored in the memory 1102, thereby performing overall monitoring of the server. Optionally, processor 1101 may include one or more processing cores; preferably, the processor 1101 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 1101.

The memory 1102 may be used to store software programs and modules, and the processor 1101 executes various functional applications and data processing by operating the software programs and modules stored in the memory 1102. The memory 1102 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to the use of the server, and the like. Further, the memory 1102 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 1102 may also include a memory controller to provide the processor 1101 with access to the memory 1102.

The server further includes a power supply 1103 for supplying power to the various components, and preferably, the power supply 1103 is logically connected to the processor 1101 through a power management system, so that the power management system can manage charging, discharging, and power consumption. The power supply 1103 may also include any component, such as one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.

The server may also include an input sub-module 1104, the input sub-module 1104 being operable to receive entered numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

Although not shown, the server may further include a display sub-module and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 1101 in the server loads the executable file corresponding to the process of one or more application programs into the memory 1102 according to the following instructions, and the processor 1101 runs the application programs stored in the memory 1102, so as to implement various functions as follows:

acquiring a service demand, and creating a data source based on the service demand; displaying a service composition selection interface, receiving selection operation through the service composition selection interface, generating service composition data according to the data source and a service composition template corresponding to the selection operation, and generating a corresponding service component for the service composition data; displaying a service configuration interface, wherein the service configuration interface comprises a component display area, a service configuration area and a service association area; receiving a triggering operation through the component display area, and displaying a candidate service component of a service corresponding to the triggering operation in the component display area; receiving configuration operation through the service configuration area, and adding a service component corresponding to the configuration operation to the service configuration area; receiving an association path adding operation through the service configuration area, wherein the association path adding operation comprises adding an association path between corresponding service components, determining a direction for the association path, and displaying association options between a source service component and a downstream service component corresponding to the association path in the service association area according to the association path adding operation; and receiving the setting operation of the association option through the service association area, and adding the service association relationship generated according to the setting operation to the source service component and the downstream service component corresponding to the association path to generate the service corresponding to the triggering operation.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed description, and are not described herein again.

It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.

To this end, an embodiment of the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to implement the following functions:

The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.

Wherein the computer-readable storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.

Since the instructions stored in the computer-readable storage medium can execute the steps in any method provided in the embodiments of the present application, the beneficial effects that can be achieved by any method provided in the embodiments of the present application can be achieved, for details, see the foregoing embodiments, and are not described herein again.

The service management method and device provided by the embodiment of the present application are introduced in detail, and a specific example is applied in the description to explain the principle and the implementation of the present application, and the description of the embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A method for service management, comprising:

2. The service management method according to claim 1, wherein the step of displaying, in the service association area, association options between a source service component and a downstream service component corresponding to the association path according to the association path adding operation includes:

determining a service component corresponding to the initial point of the associated path as a source service component and determining a service component corresponding to the point pointed by the associated path as a downstream service component according to the associated path adding operation;

and displaying association options between the source service component and the downstream service component in the service association area, wherein the association options comprise an option of whether to establish a service association relationship, an option of triggering types of the downstream service component and an option of filling positions of the downstream service component.

3. The traffic management method according to claim 1, wherein after the step of receiving an associated path add operation through the traffic configuration area, further comprising:

and receiving association identifier adding operation through the service configuration area, wherein the association identifier adding operation comprises adding an association identifier corresponding to a downstream service component on the association path based on the downstream service component pointed by the association path.

4. The traffic management method of claim 1, wherein the step of creating a data source based on the traffic demand comprises:

acquiring the storage type of the service data based on the service requirement;

receiving a connection identifier selection operation through a service data selection interface, determining a connection identifier corresponding to the storage type according to the connection identifier selection operation, and acquiring the service data from a storage address corresponding to the connection identifier;

and determining a display field according to the field selection operation of the service data, and creating a data source according to the display field.

5. The business management method of claim 1, wherein the step of receiving a selection operation through the business composition selection interface, generating business composition data according to the data source and a business composition template corresponding to the selection operation, and generating a corresponding business component for the business composition data comprises:

receiving front-end page selection operation through a front-end page selection interface, generating front-end page data according to a front-end page template corresponding to the front-end page selection operation and the data source, and generating a corresponding front-end service component for the front-end page data;

receiving background process selection operation through a background process selection interface, generating background process data according to a background process template corresponding to the background process selection operation and the data source, and generating a corresponding background service component for the background process data.

6. The service management method according to claim 5, wherein the step of receiving a front-end page selection operation through a front-end page selection interface, and generating front-end page data according to a front-end page template corresponding to the front-end page selection operation and the data source comprises:

receiving a first preset template selection operation through a front-end page selection interface;

displaying a preset front-end page template selection interface corresponding to the first preset template selection operation, receiving the first template selection operation through the preset front-end page template selection interface, and determining a target preset front-end page template according to the first template selection operation;

and associating the data source with the target preset front-end page template to generate front-end page data.

7. The service management method according to claim 5, wherein the step of receiving a front-end page selection operation through a front-end page selection interface, and generating front-end page data according to a front-end page template corresponding to the front-end page selection operation and the data source comprises:

receiving a first self-defined template selection operation through a front-end page selection interface;

displaying a custom front-end page template generation interface corresponding to the first custom template selection operation, receiving layout selection operation and control selection operation through the custom front-end page template generation interface, determining a required layout according to the layout selection operation, determining a required control according to the control selection operation, and generating a custom front-end page template according to the layout and the control;

and associating the data source with the self-defined front-end page template to generate front-end page data.

8. The service management method of claim 5, wherein the step of receiving a background process selection operation through a background process selection interface and generating background process data according to a background process template corresponding to the background process selection operation and the data source comprises:

receiving a second preset template selection operation through a background process selection interface;

displaying a preset background process template selection interface corresponding to the second preset template selection operation, receiving the second template selection operation through the preset background process template selection interface, and determining a target preset background process template according to the second template selection operation;

and associating the data source with the target preset background process template to generate background process data.

9. The service management method of claim 5, wherein the step of receiving a background process selection operation through a background process selection interface and generating background process data according to a background process template corresponding to the background process selection operation and the data source comprises:

receiving a second custom template selection operation through a background process selection interface;

displaying a user-defined background flow template generating interface corresponding to the second user-defined template selecting operation, receiving a processor configuration operation and a processor connecting operation through the user-defined background flow template generating interface, determining a configuration parameter of a processor according to the processor configuration operation, and generating a user-defined background flow template according to the processor connecting operation;

and associating the data source with the user-defined background flow template to generate background flow data.

10. A traffic management apparatus, comprising: