System, method, and computer program product for improved embedded application data management
Embodiments of the present disclosure provide for improved interoperable data management between a user-accessed software application and an embedded software application. In some contexts, a user-accessed application provides both its own functionality as well as enabling access to functionality of an embedded application. The embedded application is accessed via a data-driven connection that provides several technical advantages and addresses various data interoperability and persistence problems. In some embodiments, a user-accessed application may be configured to provide functionality of multiple embedded applications consistent with the innovations herein described.
1. An apparatus comprising at least one processor and at least one non-transitory memory including computer-coded instructions thereon, the computer coded instructions, with the at least one processor, configure the apparatus to:
identify, by a user-accessed application via a data-driven connection, an embedded app data object maintained by an embedded application, wherein the data-driven connection authorizes an embedded app user account to enable access to functionality for updating the embedded app data object via the user-accessed application;
cause rendering of a user interface comprising an embedded app engagement element and a second sub-interface associated with user-accessed application functionality;
receive, by the user-accessed application, user interaction with the embedded app engagement element, the user interaction indicating update of the embedded app data object; and
cause updating, by the user-accessed application via interaction with the embedded application utilizing the data-driven connection, of the embedded app data object.
2. The apparatus according to claim 1 , the apparatus further configured to:
cause provisioning of a temporary embedded app user account associated with the embedded application, wherein the temporary embedded app user account enables access to first limited embedded application functionality for causing the updating of the embedded app data object.
3. The apparatus according to claim 1 , the apparatus further configured to:
cause provisioning of a fully provisioned embedded app user account associated with the embedded application, wherein the fully provisioned embedded app user account enables access to advanced embedded application functionality for causing the updating of the embedded app data object.
4. The apparatus according to claim 1 , the apparatus further configured to:
initiate the data-driven connection based at least in part on an application identifier associated with the user-accessed application.
5. The apparatus according to claim 1 , the apparatus further configured to:
initiate the data-driven connection based at least in part on a device identifier associated with execution of the user-accessed application.
6. The apparatus according to claim 1 , wherein to identify the embedded app data object the apparatus is configured to:
retrieve the embedded app data object based on an organization associated with a user account authorized via the data-driven connection.
7. A computer-executed method comprising:
identifying, by a user-accessed application via a data-driven connection, an embedded app data object maintained by an embedded application, wherein the data-driven connection authorizes an embedded app user account to enable access to functionality for updating the embedded app data object via the user-accessed application;
causing rendering of a user interface comprising an embedded app engagement element and a second sub-interface associated with user-accessed application functionality;
receiving, by the user-accessed application, user interaction with the embedded app engagement element, the user interaction indicating update of the embedded app data object; and
causing updating, by the user-accessed application via interaction with the embedded application utilizing the data-driven connection, of the embedded app data object.
8. The computer-executed method according to claim 7 , the computer-implemented method further comprising:
causing provisioning of a temporary embedded app user account associated with the embedded application, wherein the temporary embedded app user account enables access to first limited embedded application functionality for causing the updating of the embedded app data object.
9. The computer-executed method according to claim 7 , the computer-implemented method further comprising:
causing provisioning of a fully provisioned embedded app user account associated with the embedded application, wherein the fully provisioned embedded app user account enables access to advanced embedded application functionality for causing the updating of the embedded app data object.
10. The computer-executed method according to claim 7 , the computer-implemented method further comprising:
initiating the data-driven connection based at least in part on an application identifier associated with the user-accessed application.
11. The computer-executed method according to claim 7 , the computer-implemented method further comprising:
initiating the data-driven connection based at least in part on a device identifier associated with execution of the user-accessed application.
12. The computer-executed method according to claim 7 , wherein identifying the embedded app data object comprises:
retrieving the embedded app data object based on an organization associated with a user account authorized via the data-driven connection.
13. A computer program product comprising at least one non-transitory computer-readable storage medium storing computer program code that, in execution with at least one processor, configures the at least one processor for:
identifying, by a user-accessed application via a data-driven connection, an embedded app data object maintained by an embedded application, wherein the data-driven connection authorizes an embedded app user account to enable access to functionality for updating the embedded app data object via the user-accessed application;
causing rendering of a user interface comprising an embedded app engagement element and a second sub-interface associated with user-accessed application functionality;
receiving, by the user-accessed application, user interaction with the embedded app engagement element, the user interaction indicating update of the embedded app data object; and
causing updating, by the user-accessed application via interaction with the embedded application utilizing the data-driven connection, of the embedded app data object.
14. The computer program product according to claim 13 , the computer program product further configured for:
causing provisioning of a temporary embedded app user account associated with the embedded application, wherein the temporary embedded app user account enables access to first limited embedded application functionality for causing the updating of the embedded app data object.
15. The computer program product according to claim 13 , the computer program product further configured for:
causing provisioning of a fully provisioned embedded app user account associated with the embedded application, wherein the fully provisioned embedded app user account enables access to advanced embedded application functionality for causing the updating of the embedded app data object.
16. The computer program product according to claim 13 , the computer program product further configured for:
initiating the data-driven connection based at least in part on an application identifier associated with the user-accessed application.
17. The computer program product according to claim 13 , the computer program product further configured for:
initiating the data-driven connection based at least in part on a device identifier associated with execution of the user-accessed application.
18. The computer program product according to claim 13 , wherein identifying the embedded app data object comprises:
retrieving the embedded app data object based on an organization associated with a user account authorized via the data-driven connection.