Adaptable application variants

• US 10,380,191 B2
• Filed: 01/26/2017
• Issued: 08/13/2019
• Est. Priority Date: 01/26/2017
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Viol, Markus, Rauh, Alexander, Brandt, Carsten, Erbe, Lars, Haffner, Stefan, Riegger, Felix, Warner, Axel, Voshage, Christian
• Primary Examiner(s): Aponte, Francisco J
• Application Number:
  US15/416,814
• Publication Number:
  US 20180210869A1
• Time in Patent Office: 929 Days
• Field of Search: 717121
• CPC Class Codes: G06F 16/90335 Query processing

Abstract

Disclosed herein are system, method, and computer program product embodiments for managing and accessing variants of applications. In an embodiment, a request for an application including one or more contextual parameters may be received. A base user interface configuration corresponding to the application may first be retrieved. One or more interface configuration files corresponding to the one or more contextual parameters may then be retrieved from a layered repository. The layered repository may be partitioned into organizational layers that store a plurality of interface configuration files associated with the application. The retrieved interface configuration files may be merged with the base user interface configuration to generate a composite interface configuration, and the composite interface configuration may be applied to the application at runtime.

Claims

1. A computer implemented method, comprising:

receiving a request for an application, the request including contextual parameter data;

retrieving a base user interface configuration corresponding to the application;

automatically retrieving a first interface configuration file corresponding to the contextual parameter data from a first organizational layer of a layered repository, the layered repository partitioned into one or more organizational layers that store a plurality of interface configuration files associated with the application;

retrieving a second interface configuration file corresponding to the contextual parameter data from a second organizational layer of the layered repository, wherein the second organizational layer is a memory partition different from the first organizational layer and the second organizational layer utilizes write permissions that differ from the first organizational layer;

merging the first and second interface configuration files with the base user interface configuration by applying changes in the first and second interface configuration files to the base user interface configuration to generate a composite user interface configuration by;

merging the first interface configuration file with the base user interface configuration to generate a temporary composite interface configuration; and

merging the second interface configuration file with the temporary composite interface configuration to generate the composite interface configuration,

wherein the composite interface configuration includes user interface components from the first interface configuration file, the second interface configuration file, and the base user interface configuration; and

applying the composite user interface configuration to the application at runtime.

2. The method of claim 1, wherein the retrieving the first interface configuration file further comprises:

matching the contextual parameter data to a context-specific application descriptor, wherein the context-specific application descriptor includes a reference to a base application descriptor corresponding to the application, and wherein the context-specific application descriptor includes a unique identifier; and

retrieving the first interface configuration file corresponding to the context-specific application descriptor.

3. The method of claim 1, wherein the merging further comprises:

merging the first and second interface configuration files in order of a predetermined priority corresponding to the first and second organizational layer.

4. The method of claim 1, further comprising:

merging a third interface configuration file with a third interface configuration within the first organizational layer in order of a determined priority to generate the first interface configuration file.

5. The method of claim 1, wherein the contextual parameter data includes at least one of a user identification parameter associated with the user, a user location parameter, an industry parameter, a line of business parameter, a company parameter, a usage type parameter, a device type parameter, a network connection parameter, an application partner parameter, a user role parameter, and a security or permissions group parameter.

6. The method of claim 1, wherein the one or more organizational layers of the layered repository include at least one of a vendor layer, a partner layer, a customer layer, a test layer, and a user layer.

7. The method of claim 1, wherein the merging is performed at runtime of the application.

8. A system, comprising:

a memory; and

at least one processor coupled to the memory and configured to;

receive a request for an application, the request including contextual parameter data;

retrieve a base user interface configuration corresponding to the application;

automatically retrieve a first interface configuration file corresponding to the contextual parameter data from a first organizational layer of a layered repository, the layered repository partitioned into one or more organizational layers that store a plurality of interface configuration files associated with the application;

retrieve a second interface configuration file corresponding to the contextual parameter data from a second organizational layer of the layered repository, wherein the second organizational layer is a memory partition different from the first organizational layer and the second organizational layer utilizes write permissions that differ from the first organizational layer;

merge the first and second interface configuration files with the base user interface configuration by applying changes in the first and second interface configuration files to the base user interface configuration to generate a composite user interface configuration by;

merging the first interface configuration file with the base user interface configuration to generate a temporary composite interface configuration; and

merging the second interface configuration file with the temporary composite interface configuration to generate the composite interface configuration,

wherein the composite interface configuration includes user interface components from the first interface configuration file, the second interface configuration file, and the base user interface configuration; and

apply the composite user interface configuration to the application at runtime.

9. The system of claim 8, wherein the at least one processor is further configured to:

match the contextual parameter data to a context-specific application descriptor, wherein the context-specific application descriptor includes a reference to a base application descriptor corresponding to the application, and wherein the context-specific application descriptor includes a unique identifier; and

retrieve the first interface configuration file corresponding to the context-specific application descriptor.

10. The system of claim 8, wherein the at least one processor is further configured to:

merge the first and second interface configuration files in order of a predetermined priority corresponding to the first and second organizational layer.

11. The system of claim 8, wherein the at least one processor is further configured to:

merge a third interface configuration file with a third interface configuration within the first organizational layer in order of a determined priority to generate the first interface configuration file.

12. The system of claim 8, wherein the contextual parameter data includes at least one of a user identification parameter associated with the user, a user location parameter, an industry parameter, a line of business parameter, a company parameter, a usage type parameter, a device type parameter, a network connection parameter, an application partner parameter, a user role parameter, and a security or permissions group parameter.

13. The system of claim 8, wherein the one or more organizational layers of the layered repository include at least one of a vendor layer, a partner layer, a customer layer, a test layer, and a user layer.

14. The system of claim 8, wherein the at least one processor is further configured to merge the one or interface configuration files with the base user interface configuration at runtime of the application.

15. A non-transitory computer-readable storage device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:

receiving a request for an application, the request including contextual parameter data;

retrieving a base user interface configuration corresponding to the application;

automatically retrieving a first interface configuration file corresponding to the contextual parameter data from a first organizational layer of a layered repository, the layered repository partitioned into one or more organizational layers that store a plurality of interface configuration files associated with the application;

retrieving a second interface configuration file corresponding to the contextual parameter data from a second organizational layer of the layered repository, wherein the second organizational layer is a memory partition different from the first organizational layer and the second organizational layer utilizes write permissions that differ from the first organizational layer;

merging the first and second interface configuration files with the base user interface configuration by applying changes in the first and second interface configuration files to the base user interface configuration to generate a composite user interface configuration by;

merging the first interface configuration file with the base user interface configuration to generate a temporary composite interface configuration; and

merging the second interface configuration file with the temporary composite interface configuration to generate the composite interface configuration,

wherein the composite interface configuration includes user interface components from the first interface configuration file, the second interface configuration file, and the base user interface configuration; and

applying the composite user interface configuration to the application at runtime.

16. The non-transitory computer-readable storage device of claim 15, wherein to retrieve the first interface configuration file the operations further comprise:

matching the contextual parameter data to a context-specific application descriptor, wherein the context-specific application descriptor includes a reference to a base application descriptor corresponding to the application, and wherein the context-specific application descriptor includes a unique identifier; and

retrieving the first interface configuration file corresponding to the context-specific application descriptor.

17. The non-transitory computer-readable storage device of claim 15, the operations further comprising:

merging the first and second interface configuration files in order of a predetermined priority corresponding to the first and second organizational layer.

18. The non-transitory computer-readable storage device of claim 15, the operations further comprising:

merging a third interface configuration file with a third interface configuration within the first organizational layer in order of a determined priority to generate the first interface configuration file.

19. The non-transitory computer-readable storage device of claim 15, wherein the contextual parameter data includes at least one of a user identification parameter associated with the user, a user location parameter, an industry parameter, a line of business parameter, a company parameter, a usage type parameter, a device type parameter, a network connection parameter, an application partner parameter, a user role parameter, and a security or permissions group parameter.

20. The non-transitory computer-readable storage device of claim 15, wherein the one or more organizational layers of the layered repository include at least one of a vendor layer, a partner layer, a customer layer, a test layer, and a user layer.