Dynamic adaptation of identity related user interface
An embodiment computes an Account Booking Location (ABL) from a login request to access an account of a first user, wherein the ABL corresponds to an asset of a partner entity that initiated the account. The embodiment pushes from a repository to a cache for a UI rendering, a UI element corresponding to the ABL. The embodiment causes a rendering service to compose a rendering instruction using the cached data such that the rendering instruction causes a first brand-specific UI to be rendered on a device associated with the first user. When a second login request from a second user also corresponds to the ABL, the embodiment reuses the cached data to compose a second rendering instruction such that the second rendering instruction causes the first brand-specific UI to be rendered on a second device associated with the second user.
1 . A computer-implemented method comprising:
computing an Account Booking Location (ABL) from a login request to access an account of a first user, wherein the ABL comprises an identifier assigned to an asset of a partner entity, the identifier corresponding to a location of a site where the partner entity first created the account, and where the account is considered to be located;
pushing from a repository to a cache to form cached data, on demand for a User Interface (UI) rendering responsive to the request, a UI element corresponding to the ABL;
causing, responsive to the pushing, a rendering service to compose a rendering instruction using the cached data such that the rendering instruction causes a first brand-specific UI to be rendered on a device associated with the first user; and
reusing, responsive to a second login request from a second user wherein the second login request also corresponds to the ABL, the cached data to compose a second rendering instruction such that the second rendering instruction causes the first brand-specific UI to be rendered on a second device associated with the second user.
2 . The computer-implemented method of claim 1 , wherein the first user and the second user are physically located in different locations.
3 . The computer-implemented method of claim 1 , wherein the reusing further comprises: determining that the cached data is within a cache expiry period.
4 . The computer-implemented method of claim 1 , wherein the login request and the second login request originate from different types of computing platforms.
5 . The computer-implemented method of claim 1 , wherein the first brand-specific UI is consistent with (i) a first brand of the partner with which a user interaction of the first user has to occur, and (ii) an account information of the user relative to the first brand of the partner.
6 . The computer-implemented method of claim 1 , further comprising:
further pushing from the repository to the cache, a UI content corresponding to the ABL.
7 . The computer-implemented method of claim 1 , wherein the ABL comprises a code corresponding to the location.
8 . The computer-implemented method of claim 1 , wherein the ABL comprises a portion of a name of the location.
9 . The computer-implemented method of claim 1 , further comprising:
extracting, as a part of the computing, the ABL data from the login request data structure.
10 . The computer-implemented method of claim 1 , further comprising:
retrieving the ABL, from a server-side application, by validating a login credential in the login request, using the login credential in the server-side application to find a corresponding ABL data, and using the corresponding ABL data as the ABL.
11 . The computer-implemented method of claim 1 , further comprising:
configuring the repository with a hierarchy of a set of UI elements.
12 . The computer-implemented method of claim 11 , wherein a first subset of UI elements is global and applies to a set of branded UI renderings, wherein a second subset of elements is unique to a subset of the set of branded UI renderings, and wherein a third subset of elements is unique to a singular branded UI rendering in the set of branded UI renderings.
13 . The computer-implemented method of claim 12 , wherein the pushing further comprises:
pushing a combination of UI elements, wherein the combination comprises at least one UI elements from the first subset, and at least one UI element from one of the second subset and the third subset.
14 . The computer-implemented method of claim 12 , wherein the pushing further comprises:
pushing a combination of UI elements, wherein the combination comprises at least one UI elements from the first subset, and at least one UI element from the second subset, and at least one UI element from the third subset.
15 . The computer-implemented method of claim 11 , wherein the set of UI elements in the hierarchy further comprises a UI content from the third subset.
16 . The computer-implemented method of claim 11 , further comprising:
changing a node in the hierarchy while a UI element from the node is deployed to the one or more user screens.
17 . A computer program product comprising one or more non-transitory computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions executable by a set of one or more processors to cause the set of one or more processors to perform operations comprising:
computing an Account Booking Location (ABL) from a login request to access an account of a first user, wherein the ABL comprises an identifier assigned to an asset of a partner entity, the identifier corresponding to a location of a site where the partner entity first created the account, and where the account is considered to be located;
pushing from a repository to a cache to form cached data, on demand for a User Interface (UI) rendering responsive to the request, a UI element corresponding to the ABL;
causing, responsive to the pushing, a rendering service to compose a rendering instruction using the cached data such that the rendering instruction causes a first brand-specific UI to be rendered on a device associated with the first user; and
reusing, responsive to a second login request from a second user wherein the second login request also corresponds to the ABL, the cached data to compose a second rendering instruction such that the second rendering instruction causes the first brand-specific UI to be rendered on a second device associated with the second user.
18 . The computer program product of claim 17 , wherein the stored program instructions are stored in a computer readable storage device in a data processing system, and wherein the stored program instructions are transferred over a network from a remote data processing system.
19 . The computer program product of claim 17 , wherein the stored program instructions are stored in a computer readable storage device in a server data processing system, and wherein the stored program instructions are downloaded in response to a request over a network to a remote data processing system for use in a computer readable storage device associated with the remote data processing system, further comprising:
program instructions to meter use of the program instructions associated with the request; and
program instructions to generate an invoice based on the metered use.
20 . A computer system comprising a set of one or more processors and one or more computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions executable by the set of one or more processors to cause the processor to perform operations comprising:
computing an Account Booking Location (ABL) from a login request to access an account of a first user, wherein the ABL comprises an identifier assigned to an asset of a partner entity, the identifier corresponding to a location of a site where the partner entity first created the account, and where the account is considered to be located;
pushing from a repository to a cache to form cached data, on demand for a User Interface (UI) rendering responsive to the request, a UI element corresponding to the ABL;
causing, responsive to the pushing, a rendering service to compose a rendering instruction using the cached data such that the rendering instruction causes a first brand-specific UI to be rendered on a device associated with the first user; and
reusing, responsive to a second login request from a second user wherein the second login request also corresponds to the ABL, the cached data to compose a second rendering instruction such that the second rendering instruction causes the first brand-specific UI to be rendered on a second device associated with the second user.