Context-based user authentication, workflow processing, and data management in a centralized application in communication with a plurality of third-party applications

1. A computerized method for context-based user authentication, workflow processing and data management in a centralized application in communication with a plurality of third-party applications, the method comprising:

receiving, by a centralized application executing on a first application server, a user request from a first third-party application executing on a second application server, the request including an identification of a second third-may application executing on a third application server and context data of the first third-party application, the second third-party application providing different functionality than the first third-party application;

determining, by the centralized application, user credentials associated with the second third-party application without any additional user input, and sending the credentials to the second third-party application for allowing user access to the second third-party application;

displaying, by the centralized application, a user interface associated with the identified second third-party application on a client device the user interface configured to include information related to the context data without any user input;

receiving, by the centralized application, changed data from the first third-party application; and

determining, by the centralized application, an urgency type of the changed data,

determining, by the centralized application, that at least a portion of the changed data is applicable to the second third-party application,

mapping, by the centralized application, the at least a portion of the changed data to a data structure associated with the second third-party application,

generating, by the centralized application, a request based on the urgency type and the second third-party application, the request including the data structure for updating a database associated with the second third-party application and coupled to the third computing device,

sending, by the centralized application, the request to the second third-party application based on the urgency type, and

updating, by the centralized application, data in a database associated with the centralized application, the updating being based on the changed data.

2. The method of claim 1 , further comprising determining, by the centralized application, user access to data structures and/or functionality associated with the second third-party application.

3. The method of claim 1 , wherein the context data comprises account data, person data, group data, household data, or any combination thereof.

4. The method of claim 3 , wherein the urgency type is a real-time type, the

sending step comprising sending the data to the second third-party application substantially instantaneously.

5. The method of claim 1 , wherein the database associated with the centralized application comprises a subset of data common to the centralized application, the first third-party application, and the second third-party application.

6. The method of claim 1 , wherein the first third-party application includes a customer relationship management application, a financial planning application, a portfolio management application, a modeling and/or rebalancing application, or any combination thereof.

7. The method of claim 1 , wherein the urgency type comprises a batch type, an on-demand type, a real-time type, or any combination thereof.

8. The method of claim 1 , wherein determining the urgency type comprises determining the urgency type based on at least one business rule.

9. The method of claim 1 , wherein the urgency type is a batch type, the

sending step comprising sending the data to the second third-party application at a later time.

10. The method of claim 1 , wherein the urgency type is an on-demand type, the

sending step comprising sending the data to the second third-party application upon a request for the data from the second third-party application.

11. The method of claim 1 , wherein updating data in a database associated with the centralized application comprises mapping at least a portion of the changed data to a data structure associated with the centralized application.

12. The method of claim 1 , wherein the centralized application, the first third-party application, and the second third-party application are owned and/or hosted by separate unrelated entities.

13. The method of claim 1 , wherein the centralized application, the first third-party application, and the second third-party application communicate across a communications network.

14. The method of claim 1 , wherein the first third-party application stores data in a corresponding database coupled to the second computing device.

15. The method of claim 1 , further comprising:

receiving requests from a plurality of third-party applications; and

sending data to a plurality of third-party applications using a Web Services paradigm.

16. The method of claim 1 , further comprising:

determining, by the centralized application, a conflict between the changed data and data associated with the centralized application; and

reconciling, by the centralized application, the conflict according to at least one business rule.

17. The method of claim 1 , further comprising enabling separate user access to databases associated with the first third-party application and the second third-party application without first requiring user access to the centralized application.

18. The method of claim 1 , further comprising:

receiving, by the centralized application, data from the first and/or second third-party application; and

filling, by the centralized application, a pre-defined form in the centralized application with said data and without any user input.

19. A computer program product, tangibly embodied in non-transitory computer readable storage device, for context-based user authentication, workflow processing and data management in a centralized application in communication with a plurality of third-party applications, the computer program product including instructions being operable to cause a first application server to:

receive by a centralized application executing on the first application server a user request from a first third-party application executing on a second application server, the request including an identification of a second third-party application executing on a third application server and context data of the first third-party application, the second third-party application providing different functionality than the first third-party application;

determine, by the centralized application, user credentials associated with the second third-party application without any additional user input, and sending the credentials to the second third-party application for allowing user access to the second third-party application;

display, by the centralized application, a user interface associated with the second third-party application on a client device, the user interface configured to include information related to the context data without any user input;

receive, by the centralized application, changed data from the first third-party application;

determine, by the centralized application, an urgency type of the changed data,

determine, by the centralized application, that at least a portion of the changed data is applicable to the second third-party application,

map, by the centralized application, the at least a portion of the changed data to a data structure associated with the second third-party application,

generate, by the centralized application, a request based on the urgency type and the second third-party application, the request including the data structure for updating a database associated with the second third-party application and coupled to the third application server,

send, by the centralized application, the request to the second third-party application based on the urgency type, and

update, by the centralized application, data in a database associated with the centralized application, the updating being based on the changed data.

20. A system for context-based user authentication, workflow processing and data management in a centralized application in communication with a plurality of third-party applications, the system comprising:

a first application server executing the centralized application, the first application server configured to:

receive a user request from a first third-party application executing on a second application server, the request including an identification of a second third-party application excuting on a third application and context data of the first third-party application, the second third-party application providing different functionality than the first third-party application;

determine user credentials associated with the second third-party application without any additional user input, and sending the credentials to the second third-party application for allowing user access to the second third-party application;

display a user interface associated with the identified second third-party application on a client device, the user interface configured to include information related to the context data without any user input;

determine an urgency type of the changed data,

determine that a second third-party application executing on a second server to which at least a portion of the changed data is applicable, the second third-party application providing different operations than the first third-party application, and owned or hosted by a different business entity then the first third-party application,

map at least a portion of the changed data to a data structure associated with the second third-party application,

generate a request based on the urgency type and the second third-party application, said request including the data structure for updating a database associated with the second third-party application and coupled to the second server and coupled to the third application server,

send the request to the second third-party application, and

update data in a database associated with the centralized application, said updating based on the changed data.