Task scene interface jumping method and device, computer equipment and storage medium

Abstract

The invention provides a task scene interface jumping method and device, computer equipment and a storage medium. The method comprises the steps that a task scene identifier of a to-be-jumped task scene interface is acquired; obtaining a plurality of interface element identifiers pre-associated with the task scene identifier; in a preset interface element set, obtaining target interface elements respectively associated with the plurality of interface element identifiers; generating a to-be-jumped task scene interface based on the plurality of target interface elements; and displaying the task scene interface to be skipped. According to the embodiment of the invention, by setting the association relationship between the task scene identifier and the interface element identifier, the corresponding target interface element is directly obtained from the interface element set according to the corresponding interface element identifier in the task scene interface needing to jump; the same interface elements in different task scene interfaces can be combined into one interface element in the interface element set, so that repeated development of the same interface element is avoided, development resources are saved, and the efficiency of a development team is improved.

Description

Technical Field

[0001] The present application relates to the technical field of interface jump, and in particular to a method, device, computer equipment and storage medium for jumping a task scene interface. Background Art

[0002] In an application, there are generally multiple different task scenarios, and different task scenarios have different interfaces for users to perform corresponding task processing in the interface.

[0003] When developing these task scenario interfaces, the development team often develops each task scenario interface separately. However, this will cause the same interface elements in different task scenario interfaces to be redeveloped, resulting in a waste of development resources and reducing the efficiency of the development team. Summary of the invention

[0004] The present application provides a method, device, computer equipment and storage medium for jumping to a task scenario interface, aiming to solve the technical problem of how to save development resources and improve the efficiency of the development team.

[0005] On the one hand, the present application provides a method for jumping to a task scene interface, the method comprising:

[0006] Get the task scene identifier of the task scene interface to be jumped to;

[0007] Acquire multiple interface element identifiers pre-associated with the task scenario identifier;

[0008] In a preset interface element set, obtaining target interface elements respectively associated with a plurality of the interface element identifiers, and obtaining a plurality of the target interface elements;

[0009] Based on the plurality of target interface elements, generating the task scene interface to be jumped to;

[0010] The task scene interface to be jumped is displayed.

[0011] On the other hand, the present application provides a task scene interface jump device, the device comprising:

[0012] A first acquisition unit is used to acquire a task scene identifier of a task scene interface to be jumped;

[0013] A second acquisition unit is used to acquire a plurality of interface element identifiers pre-associated with the task scenario identifier;

[0014] A third acquisition unit is used to acquire target interface elements respectively associated with the plurality of interface element identifiers in a preset interface element set, so as to obtain the plurality of target interface elements;

[0015] An interface generation unit, used to generate the task scene interface to be jumped based on the plurality of target interface elements;

[0016] The interface display unit is used to display the task scene interface to be jumped.

[0017] On the other hand, the present application also provides a computer device, the computer device comprising:

[0018] one or more processors;

[0019] Memory; and

[0020] One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the processor to implement the steps in the above-mentioned task scenario interface jump method.

[0021] On the other hand, the present application also provides a computer-readable storage medium on which a computer program is stored, and the computer program is loaded by a processor to execute the steps in the above-mentioned task scene interface jump method.

[0022] The jump method, device, computer equipment and storage medium of the task scene interface provided by the embodiment of the present application, the jump method of the task scene interface includes: obtaining the task scene identifier of the task scene interface to be jumped; obtaining multiple interface element identifiers pre-associated with the task scene identifier; obtaining the target interface elements respectively associated with the multiple interface element identifiers in the preset interface element set; generating the task scene interface to be jumped based on the multiple target interface elements; displaying the task scene interface to be jumped. The embodiment of the present application sets the association relationship between the task scene identifier and the interface element identifier, and when it is necessary to jump to the task scene interface, according to the corresponding interface element identifier, directly obtains the corresponding target interface element from the interface element set, so that the same interface elements in different task scene interfaces can be merged into one interface element in the interface element set, thereby avoiding repeated development of the same interface elements, saving development resources, and improving the efficiency of the development team. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 It is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0025] Figure 2This is a flowchart of an embodiment of a method for jumping to a task scene interface provided in an embodiment of the present application;

[0026] Figure 3 It is a flowchart of another embodiment of a method for jumping to a task scene interface provided in an embodiment of the present application;

[0027] Figure 4 It is a schematic diagram of the structure of an embodiment of a jump device for a task scene interface provided in an embodiment of the present application;

[0028] Figure 5 It is a schematic diagram of the structure of an embodiment of a computer device provided in the embodiments of the present application. DETAILED DESCRIPTION

[0029] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0030] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, "plurality" means two or more, unless otherwise clearly and specifically defined.

[0031] In this application, the word "exemplary" is used to mean "used as an example, illustration, or description." Any embodiment described in this application as "exemplary" is not necessarily to be construed as being preferred or advantageous over other embodiments. The following description is given to enable any technician in the field to implement and use the present application. In the following description, details are listed for the purpose of explanation. It should be understood that a person of ordinary skill in the art can recognize that the present application can be implemented without using these specific details. In other instances, well-known structures and processes will not be elaborated in detail to avoid obscuring the description of the present application with unnecessary details. Therefore, the present application is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in the present application.

[0032] The embodiments of the present application provide a method, device, computer equipment and storage medium for jumping to a task scenario interface, which are described in detail below.

[0033] like Figure 1 As shown, Figure 1is a schematic diagram of an application scenario provided by an embodiment of the present application. The application scenario may include a computer device 100, in which a jump device of a task scenario interface is integrated, such as Figure 1 A computer device 100 in FIG.

[0034] In the embodiment of the present application, the computer device 100 may be a terminal. When the computer device 100 is a terminal, the terminal used may be a device including both receiving and transmitting hardware, that is, a device having receiving and transmitting hardware capable of performing two-way communication on a two-way communication link. Such a device may include: a cellular or other communication device having a single-line display or a multi-line display or a cellular or other communication device without a multi-line display. The specific computer device 100 may be a desktop terminal or a mobile terminal, and the computer device 100 may also be one of a mobile phone, a tablet computer, a laptop computer, a medical auxiliary instrument, and the like.

[0035] Those skilled in the art will understand that Figure 1 The application environment shown in the figure is only an example of the application scenario of the present application and does not constitute a limitation on the application scenario of the present application. Other application environments may also include Figure 1 More or less computer equipment as shown in Figure 1 Only one computer device is shown in the figure. It can be understood that the application scenario may also include one or more other computer devices, which are not specifically limited here.

[0036] In addition, if Figure 1 As shown, the application scenario may also include a server 200 for interacting with the computer device 100 to determine whether the first update time is the same as the second update time, and to transmit the second interface jump configuration information between the server 200 and the computer device 100.

[0037] It should be noted that Figure 1 The application scenario diagram shown is merely an example and does not constitute a limitation on the technical solution provided in the embodiments of the present application. A person skilled in the art may appreciate that, with the evolution of application scenarios and the emergence of new business scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

[0038] Next, a method for jumping to a task scenario interface provided in an embodiment of the present application is introduced.

[0039] In the embodiment of the method for jumping to the task scene interface of the embodiment of the present application, the jumping device of the task scene interface is used as the execution subject. For the sake of simplicity and ease of description, the execution subject will be omitted in the subsequent method embodiments. The jumping device of the task scene interface is applied to a computer device.

[0040] See also Figures 2 to 4 , Figure 2 The following is a flow chart of an embodiment of a method for jumping to a task scene interface provided in an embodiment of the present application. The method for jumping to a task scene interface includes:

[0041] 201. Obtain a task scene identifier of the task scene interface to be redirected;

[0042] In the embodiment of the present application, the task scene interface can be a scene interface where any task function in the preset application is located, wherein a variety of different task functions are provided in the preset application, and different task functions are provided with different scene interfaces. Take the application with the preset application as CRM (Customer Relationship Management) as an example for explanation, the CRM application is provided with a task function module, and the task function module provides a variety of different task functions (such as the customer follow-up function and the contract follow-up function in CRM, etc.), and the corresponding scene interface is pre-set for different task functions, so that the user can perform corresponding task processing in the corresponding scene interface, for example, in the scene interface of the customer follow-up function, the user can view and manage the customer information, and for example, in the scene interface of the contract follow-up function, the user can view and manage the contract information. The CRM application includes a computer program for executing the jump method of the task scene interface of the present application. For the convenience of description, the following embodiments are all illustrated by taking the application with the preset application as CRM as an example.

[0043] The task scenario interface to be jumped to can be the scenario interface of any task function selected by the user in the CRM application. The task scenario identifier of the task scenario interface to be jumped to can be the name, number, etc. of the task scenario interface to be jumped to. Corresponding task scenario identifiers are pre-set for different task scenario interfaces and stored in the application file of the CRM. Therefore, when determining the task scenario interface to be jumped to, the task scenario identifier of the task scenario interface to be jumped to can be directly obtained from the application file of the CRM.

[0044] 202. Acquire multiple interface element identifiers pre-associated with the task scenario identifier;

[0045] In the embodiment of the present application, the interface element identifier is the identification information of the interface element, and the interface element is for example a menu, a scroll bar, a dialog box, etc. in the interface.

[0046] In the embodiment of the present application, a preset association relationship between a task scenario identifier and an interface element model group is pre-set, and the interface element model group includes multiple model group interface element identifiers. Therefore, obtaining multiple interface element identifiers pre-associated with the task scenario identifier may include: obtaining the interface element model group pre-associated with the task scenario identifier, and using the multiple model group interface element identifiers included in the interface element model group as multiple interface element identifiers pre-associated with the task scenario identifier. Among them, the preset association relationship between the task scenario identifier and the interface element model group is pre-set by the developer based on the actual interface development and design requirements, and stored in the server connected to the backend of the CRM application, so that the CRM application can obtain the preset association relationship between the task scenario identifier and the interface element model group from the server. In addition, the interface element model group also includes interface element display rules of multiple model group interface element identifiers, and the interface element display rules include the display position, display size, etc. of the interface elements of each model group interface element identifier, so as to facilitate subsequent screen rendering based on the interface element display rules to generate the corresponding task scenario interface.

[0047] 203. In a preset interface element set, obtain target interface elements respectively associated with a plurality of interface element identifiers to obtain a plurality of target interface elements;

[0048] In an embodiment of the present application, the preset interface element set includes a plurality of preset interface elements and preset interface element identifiers of each preset interface element, and the plurality of preset interface elements may be interface elements in a plurality of different preset task scenario interfaces, that is, the interface elements in a plurality of different preset task scenario interfaces are summarized and deduplicated in advance to obtain a preset interface element set, and a plurality of different preset task scenario interfaces include a task scenario interface to be jumped to. Since the interface elements in a plurality of different preset task scenario interfaces are summarized, the developer does not need to repeatedly develop the same interface elements in different preset task scenario interfaces. The preset interface element set is pre-set by the developer and stored in a server connected to the backend of the CRM application, so that the CRM application can obtain the preset interface element set from the server.

[0049] In a preset interface element set, target interface elements respectively associated with multiple interface element identifiers are obtained, which may specifically include: for each interface element identifier, comparing the interface element identifier with each preset interface element identifier in the preset interface element set to determine a preset interface element identifier that is identical to the interface element identifier, and using the preset interface element of the preset interface element identifier as the target interface element, thereby obtaining multiple target interface elements.

[0050] In some embodiments of the present application, in certain abnormal situations (for example, some preset interface elements in the preset interface element set may be lost), the target interface element associated with the interface element identifier may not be obtained in the preset interface element set, so it is necessary to set a corresponding protection mechanism for these abnormal situations to avoid errors in the operation of the CRM application. Specifically, in the preset interface element set, after obtaining the target interface elements associated with multiple interface element identifiers respectively, it can also include: if at least one target interface element associated with the interface element identifier fails to be obtained from the interface element set, the preset task scenario abnormal interface is displayed. The preset task scenario abnormal interface may include preset abnormal situation prompt information so that the user knows that an abnormal situation has occurred. The preset task scenario abnormal interface may also include a jump entry to the functional interface of the above-mentioned task function module, so that the user can jump to the functional interface of the task function module based on the jump entry. The functional interface of the task function module may include a list of the names of multiple preset task scenario interfaces, so that the user can select the task scenario interface to be jumped from the list.

[0051] 204. Generate a task scene interface to be redirected based on multiple target interface elements;

[0052] In an embodiment of the present application, the generation of the task scene interface to be jumped to can be implemented by using a renderer. Specifically, based on multiple target interface elements, the generation of the task scene interface to be jumped to can include: based on multiple target interface elements and the interface element display rules in the above-mentioned interface element model group, the generation of the task scene interface to be jumped to. For example, multiple target interface elements and the interface element display rules in the above-mentioned interface element model group can be input into the renderer, so that the renderer uses multiple target interface elements and performs screen rendering according to the interface element display rules; the screen output by the renderer is obtained and used as the task scene interface to be jumped to.

[0053] 205. Display the task scene interface to be jumped.

[0054] In an embodiment of the present application, the task scenario interface to be jumped to is displayed on the display screen of the terminal device where the CRM application is located (i.e., the jumping device of the task scenario interface), thereby jumping the screen displayed on the display screen to the task scenario interface to be jumped to.

[0055] The method for jumping to the task scenario interface provided in the embodiment of the present application sets the association relationship between the task scenario identifier and the interface element identifier. When it is necessary to jump to the task scenario interface, the corresponding target interface element is directly obtained from the interface element set according to the corresponding interface element identifier, so that the same interface elements in different task scenario interfaces can be merged into one interface element in the interface element set, thereby avoiding repeated development of the same interface elements, saving development resources, improving the efficiency of the development team, and the total data volume of the interface elements will be smaller, thereby improving the performance of the CRM application.

[0056] In some embodiments of the present application, Figure 3 As shown, before obtaining the task scene identifier of the task scene interface to be jumped, it also includes:

[0057] 301. Obtain preset first interface jump configuration information from a local disk, where the first interface jump configuration information includes an interface element set and a list including names of multiple preset task scenario interfaces;

[0058] In the embodiment of the present application, the jump device of the task scene interface includes a local disk and a local running memory, and is also connected to the server through the CRM application backend. The local disk is generally a hard disk, and the data will not be lost after a power outage. The local running memory is generally a volatile memory, and the data will be lost after a power outage, and is used for temporary data storage.

[0059] The preset first interface jump configuration information includes the above-mentioned interface element set, the above-mentioned list of names of multiple preset task scenario interfaces, and the preset first interface jump configuration information may also include the above-mentioned preset association relationship between the task scenario identifier and the interface element model group.

[0060] Before obtaining the task scenario identifier of the task scenario interface to be jumped, that is, when the CRM application is started, the preset first interface jump configuration information is obtained from the local disk. Since the preset first interface jump configuration information is not stored in the local disk when the CRM application is started for the first time, two situations may occur when obtaining the preset first interface jump configuration information from the local disk. One situation is that the preset first interface jump configuration information is successfully obtained from the local disk, and the other situation is that the preset first interface jump configuration information fails to be obtained from the local disk. Therefore, after obtaining the preset first interface jump configuration information from the local disk, it can also include: if the preset first interface jump configuration information fails to be obtained from the local disk, the preset second interface jump configuration information stored in the server is obtained from the server connected to the backend of the CRM application (it should be noted that the second interface jump configuration information contains the same object as the first interface jump configuration information, the difference is that the second interface jump configuration information is pre-set by the developer and stored in the server, and the first interface jump configuration information is derived from the second interface jump configuration information and stored locally in the jump device of the task scenario interface), and is stored in the local disk as the first interface jump configuration information, and then returns to execute the step of obtaining the preset first interface jump configuration information from the local disk. If the preset first interface jump configuration information is successfully obtained from the local disk, the following step 302 is executed.

[0061] 302. Store the first interface jump configuration information in the local running memory;

[0062] In an embodiment of the present application, since the read and write speed of the local running memory is greater than that of the local disk, the first interface jump configuration information obtained from the local disk is stored in the local running memory so that the first interface jump configuration information can be quickly used later.

[0063] In some embodiments of the present application, after the CRM application is started, it is necessary to detect whether the first interface jump configuration information has been updated. Specifically, after the first interface jump configuration information is stored in the local running memory, it can also include: obtaining the first update time of the first interface jump configuration information, the first update time is the time when the first interface jump configuration information was last updated; judging whether the first update time is the same as the second update time of the second interface jump configuration information preset by the server, the second update time is the time when the second interface jump configuration information was last updated, wherein the server connected to the backend of the CRM application will store the time when the developer last modified the second interface jump configuration information as the second update time of the second interface jump configuration information; if the first update time is the same as the second update time, it indicates that the first interface jump configuration information is consistent with the second interface jump configuration information, so the following step 303 can be executed.

[0064] If the first update time is different from the second update time, it indicates that the first interface jump configuration information is inconsistent with the second interface jump configuration information. Therefore, the second interface jump configuration information is obtained from the server, and the second interface jump configuration information is stored as the first interface jump configuration information in the local running memory and the local disk. The second update time of the second interface jump configuration information is stored as the first update time of the first interface jump configuration information in the local running memory and the local disk, thereby realizing the update of the first interface jump configuration information in the local running memory and the local disk.

[0065] It can be seen that the embodiment of the present application determines whether the local first-interface jump configuration information is updated by comparing the first update time with the second update time, without having to obtain the second-interface jump configuration information from the server every time, thereby reducing unnecessary interaction workload with the server.

[0066] In a further embodiment, determining whether the first update time is the same as the second update time of the second interface jump configuration information preset on the server side may include: sending the first update time to the server so that the server determines whether the first update time is the same as the second update time, and feeds back a determination result of whether the first update time is the same as the second update time.

[0067] In a further embodiment, in certain abnormal situations (for example, after updating the first interface jump configuration information, the first interface jump configuration information in the local running memory may be lost), the CRM application may fail to run properly, so the interactive processing logic of the CRM application needs to be improved. Specifically, after the second update time of the second interface jump configuration information is stored as the first update time of the first interface jump configuration information in the local running memory and the local disk, it also includes: detecting whether the first interface jump configuration information exists in the local running memory; if the first interface jump configuration information exists in the local running memory, executing the following step 303; if the first interface jump configuration information does not exist in the local running memory, obtaining the first interface jump configuration information from the local disk again.

[0068] In a further embodiment, in certain abnormal situations (for example, after updating the first interface jump configuration information, the first interface jump configuration information in the local disk may be lost), the CRM application may fail to run properly, so the interaction processing logic of the CRM application needs to be improved. Specifically, after obtaining the first interface jump configuration information from the local disk again, it also includes: if the first interface jump configuration information fails to be obtained from the local disk, the above-mentioned task scenario abnormal interface is displayed; if the first interface jump configuration information is successfully obtained from the local disk, return to step 302.

[0069] 303. Obtain and display a list including the names of multiple preset task scenario interfaces from the first interface jump configuration information in the local running memory, so as to determine the task scenario interface to be jumped from the multiple preset task scenario interfaces.

[0070] In the embodiment of the present application, when the user enters the function interface of the task function module, the function interface needs to be displayed, so a list including the names of multiple preset task scene interfaces is obtained from the first interface jump configuration information of the local running memory, so as to generate and display the function interface based on the list. The user can select the name of any preset task scene interface in the list of the function interface, and the preset task scene interface selected by the user is the task scene interface to be jumped.

[0071] In order to better implement the task scene interface jump method in the embodiment of the present application, based on the task scene interface jump method, the embodiment of the present application also provides a task scene interface jump device, such as Figure 4 As shown, the task scene interface jump device 400 includes:

[0072] The first acquisition unit 401 is used to acquire a task scene identifier of a task scene interface to be jumped;

[0073] The second acquisition unit 402 is used to acquire multiple interface element identifiers pre-associated with the task scenario identifier;

[0074] The third acquisition unit 403 is used to acquire target interface elements respectively associated with multiple interface element identifiers in a preset interface element set, so as to obtain multiple target interface elements;

[0075] The interface generation unit 404 is used to generate a task scene interface to be jumped based on multiple target interface elements;

[0076] The interface display unit 405 is used to display the task scene interface to be jumped.

[0077] The jumping device for the task scene interface provided in the embodiment of the present application sets the association relationship between the task scene identifier and the interface element identifier. When it is necessary to jump to the task scene interface, the corresponding target interface element is directly obtained from the interface element set according to the corresponding interface element identifier, so that the same interface elements in different task scene interfaces can be merged into one interface element in the interface element set, thereby avoiding repeated development of the same interface elements, saving development resources, and improving the efficiency of the development team.

[0078] In some embodiments of the present application, the task scene interface jump device 400 is further used to:

[0079] Acquire an interface element model group pre-associated with a task scenario identifier, wherein the interface element model group includes a plurality of model group interface element identifiers and interface element display rules of the plurality of model group interface element identifiers;

[0080] The multiple model group interface element identifiers are used as the multiple interface element identifiers pre-associated with the task scenario identifier.

[0081] In some embodiments of the present application, the task scene interface jump device 400 is further used to:

[0082] Based on multiple target interface elements and interface element display rules, a task scene interface to be jumped to is generated.

[0083] In some embodiments of the present application, the task scene interface jump device 400 is further used to:

[0084] Obtaining preset first interface jump configuration information from a local disk, where the first interface jump configuration information includes an interface element set and a list including names of multiple preset task scenario interfaces;

[0085] Storing the first interface jump configuration information in the local running memory;

[0086] A list is obtained from the first interface jump configuration information in the local running memory and displayed so as to determine the task scene interface to be jumped from multiple preset task scene interfaces.

[0087] In some embodiments of the present application, the task scene interface jump device 400 is further used to:

[0088] An interface element set is obtained from the first interface jump configuration information of the local running memory, where the interface element set is obtained by aggregating and removing duplicate interface elements in multiple preset task scene interfaces, where the multiple preset task scene interfaces include the task scene interface to be jumped.

[0089] In some embodiments of the present application, the task scene interface jump device 400 is further used to:

[0090] Obtaining a first update time of the first interface jump configuration information;

[0091] Determine whether the first update time is the same as the second update time of the second interface jump configuration information preset by the server;

[0092] If the first update time is the same as the second update time, execute the step of jumping to the configuration information from the first interface of the local running memory, obtaining the list and displaying it.

[0093] In some embodiments of the present application, the task scene interface jump device 400 is further used to:

[0094] If the first update time is different from the second update time, obtaining the second interface jump configuration information from the server;

[0095] The second interface jump configuration information is stored as the first interface jump configuration information in the local running memory and the local disk;

[0096] The second update time of the second interface jump configuration information is stored as the first update time of the first interface jump configuration information in the local running memory and the local disk.

[0097] In some embodiments of the present application, the task scene interface jump device 400 is further used to:

[0098] Detect whether there is first interface jump configuration information in the local running memory;

[0099] If the local running memory has the first interface jump configuration information, executing the step of obtaining and displaying the list from the first interface jump configuration information of the local running memory;

[0100] If the first interface jump configuration information does not exist in the local running memory, the first interface jump configuration information is obtained from the local disk again. If the first interface jump configuration information fails to be obtained from the local disk, the preset task scenario exception interface is displayed.

[0101] In addition to the above-described jump method and device for the task scene interface, the embodiment of the present application further provides a computer device, which integrates any one of the task scene interface jump devices provided in the embodiment of the present application, and the computer device includes:

[0102] one or more processors;

[0103] Memory; and

[0104] One or more applications, wherein the one or more applications are stored in a memory and configured to execute, by a processor, the steps of any one of the above-mentioned task scenario interface jump method embodiments.

[0105] The present application also provides a computer device that integrates a jump device for any task scene interface provided by the present application. Figure 5 As shown, it shows a schematic diagram of the structure of the computer device involved in the embodiment of the present application, specifically:

[0106] The computer device may include one or more processing core processors 501, one or more computer readable storage medium storage units 502, a power supply 503, an input unit 504 and other components. Those skilled in the art will understand that Figure 5 The computer device structure shown in the figure does not constitute a limitation on the computer device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:

[0107] The processor 501 is the control center of the computer device. It uses various interfaces and lines to connect various parts of the entire computer device. By running or executing software programs and / or modules stored in the storage unit 502 and calling data stored in the storage unit 502, it executes various functions of the computer device and processes data, thereby monitoring the computer device as a whole. Optionally, the processor 501 may include one or more processing cores; preferably, the processor 501 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 501.

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

[0109] The computer device also includes a power supply 503 for supplying power to various components. Preferably, the power supply 503 can be logically connected to the processor 501 through a power management system, so as to manage charging, discharging, power consumption and other functions through the power management system. The power supply 503 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components.

[0110] The computer device may further include an input unit 504, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0111] Although not shown, the computer device may also include a display unit, etc., which will not be described in detail here. Specifically, in the embodiment of the present application, the processor 501 in the computer device will load the executable file corresponding to the process of one or more application programs into the storage unit 502 according to the following instructions, and the processor 501 will run the application program stored in the storage unit 502, thereby realizing various functions, as follows:

[0112] Obtain a task scene identifier of the task scene interface to be jumped to; obtain multiple interface element identifiers pre-associated with the task scene identifier; in a preset interface element set, obtain target interface elements respectively associated with the multiple interface element identifiers to obtain multiple target interface elements; based on the multiple target interface elements, generate the task scene interface to be jumped to; and display the task scene interface to be jumped to.

[0113] The method for jumping to a task scene interface provided in an embodiment of the present application sets an association between a task scene identifier and an interface element identifier. When it is necessary to jump to the task scene interface, the corresponding target interface element is directly obtained from the interface element set according to the corresponding interface element identifier, so that the same interface elements in different task scene interfaces can be merged into one interface element in the interface element set, thereby avoiding repeated development of the same interface elements, saving development resources, and improving the efficiency of the development team.

[0114] To this end, an embodiment of the present application provides a computer-readable storage medium, which may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc. The computer-readable storage medium stores a plurality of instructions, which can be loaded by a processor to execute the steps in any of the task scene interface jump methods provided in the embodiment of the present application. For example, the instruction can execute the following steps:

[0115] Obtain a task scene identifier of the task scene interface to be jumped to; obtain multiple interface element identifiers pre-associated with the task scene identifier; in a preset interface element set, obtain target interface elements respectively associated with the multiple interface element identifiers to obtain multiple target interface elements; based on the multiple target interface elements, generate the task scene interface to be jumped to; and display the task scene interface to be jumped to.

[0116] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0117] The above is a detailed introduction to the method, device, computer equipment and storage medium for jumping to a task scene interface provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope, and the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for jumping to a task scene interface, characterized in that: The method comprises: Get the task scene identifier of the task scene interface to be jumped to; Acquire multiple interface element identifiers pre-associated with the task scenario identifier; In a preset interface element set, obtaining target interface elements respectively associated with a plurality of the interface element identifiers, and obtaining a plurality of the target interface elements; Based on the plurality of target interface elements, generating the task scene interface to be jumped to; The task scene interface to be jumped is displayed.

2. The method for jumping to a task scene interface according to claim 1, characterized in that: The step of obtaining a plurality of interface element identifiers pre-associated with the task scenario identifier includes: Acquire an interface element model group pre-associated with the task scenario identifier, wherein the interface element model group includes a plurality of model group interface element identifiers and interface element display rules of the plurality of model group interface element identifiers; Using the multiple model group interface element identifiers as the multiple interface element identifiers pre-associated with the task scenario identifier; The step of generating the task scene interface to be redirected based on the plurality of target interface elements includes: Based on the multiple target interface elements and the interface element display rules, the task scene interface to be jumped to is generated.

3. The method for jumping to a task scene interface according to claim 1, characterized in that: Before obtaining the task scene identifier of the task scene interface to be jumped, the method further includes: Obtaining preset first interface jump configuration information from a local disk, wherein the first interface jump configuration information includes the interface element set and a list including names of a plurality of preset task scenario interfaces; Storing the first interface jump configuration information in the local running memory; The list is obtained and displayed from the first interface jump configuration information of the local running memory, so as to determine the task scene interface to be jumped from the multiple preset task scene interfaces.

4. The method for jumping to a task scene interface as claimed in claim 3, characterized in that: The step of obtaining target interface elements respectively associated with the plurality of interface element identifiers in the preset interface element set, before obtaining the plurality of target interface elements, further comprises: The interface element set is obtained from the first interface jump configuration information of the local running memory, and the interface element set is obtained by aggregating and removing duplicate interface elements in multiple preset task scene interfaces, and the multiple preset task scene interfaces include the task scene interface to be jumped.

5. The method for jumping to a task scene interface as claimed in claim 3, characterized in that: After storing the first interface jump configuration information in the local running memory, the method further includes: Obtaining a first update time of the first interface jump configuration information; Determine whether the first update time is the same as the second update time of the second interface jump configuration information preset by the server; If the first update time is the same as the second update time, execute the step of jumping configuration information from the first interface of the local running memory to obtain and display the list.

6. The method for jumping to a task scene interface as claimed in claim 5, characterized in that: After determining whether the first update time is the same as the second update time of the second interface jump configuration information preset by the server, the method further includes: If the first update time is different from the second update time, obtaining the second interface jump configuration information from the server; The second interface jump configuration information is stored as the first interface jump configuration information in the local running memory and the local disk; The second update time of the second interface jump configuration information is stored as the first update time of the first interface jump configuration information in the local running memory and the local disk.

7. The method for jumping to a task scene interface according to claim 6, characterized in that: After storing the second update time of the second interface jump configuration information as the first update time of the first interface jump configuration information in the local running memory and the local disk, the method further includes: Detecting whether the first interface jump configuration information exists in the local running memory; If the first interface jump configuration information exists in the local running memory, executing the step of obtaining the list from the first interface jump configuration information of the local running memory and displaying it; If the first interface jump configuration information does not exist in the local running memory, the first interface jump configuration information is obtained from the local disk again. If the first interface jump configuration information fails to be obtained from the local disk, the preset task scenario exception interface is displayed.

8. A task scene interface jump device, characterized in that: The device comprises: A first acquisition unit is used to acquire a task scene identifier of a task scene interface to be jumped; A second acquisition unit is used to acquire a plurality of interface element identifiers pre-associated with the task scenario identifier; A third acquisition unit is used to acquire target interface elements respectively associated with the plurality of interface element identifiers in a preset interface element set, so as to obtain the plurality of target interface elements; An interface generation unit, used to generate the task scene interface to be jumped based on the plurality of target interface elements; The interface display unit is used to display the task scene interface to be jumped.

9. A computer device, characterized in that: The computer device comprises: one or more processors; Memory; and One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the processor to implement the steps in the method for jumping to the task scenario interface described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in the method for jumping to a task scene interface as described in any one of claims 1 to 8.

Images