Automated dynamic routing of documents based on database storage of user relationships

• US 20060101031A1
• Filed: 10/21/2004
• Published: 05/11/2006
• Est. Priority Date: 10/21/2004
• Status: Abandoned Application

• Current Assignee: Brian E. Knight, Jacob Joel Faul
• Original Assignee: Brian E. Knight, Jacob Joel Faul
• Inventors: Faul, Jacob Joel, Knight, Brian E.
• Application Number:
  US10/972,075
• Publication Number:
  US 20060101031A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method and system for automated dynamic routing of information based on database storage of user relationships are disclosed. In one embodiment of the invention, user relationships within an organization are centrally managed. These relationships are used as virtual destinations for the routing of business processes. When information is to be routed to a destination, the current user with the given relationship to the source user is determined, and the information is routed to the user whose identity was so determined. Processes, such as the automated routing of documents, can be defined in terms of user relationships and then left unmodified, despite changes to the user relationships within an organization, so long as the centrally managed user relationship information is kept current.

Claims

1. A method of automated dynamic routing of information based on database storage of user relationships, comprising:

uniquely defining a plurality of relationships;

maintaining the defined relationships by mapping a plurality of sources to a plurality of targets for particular relationships;

designating one relationship selected from the defined relationships as a routing destination for information;

resolving the designated relationship by determining a current target mapped to a corresponding source for the designated relationship; and

routing the information from the source of the designated relationship to the resolved target.

2. The method of claim 1, wherein relationship mapping is maintained via an external system.

3. The method of claim 2, wherein the external system is a database..

4. The method of claim 3, wherein the designated relationship is resolved based on information in the external database via a relationship plug-in.

5. The method of claim 1, additionally comprising determining whether the given relationship is resolved via an internal relationship resolver or via a relationship plug-in in communication with an external system.

6. The method of claim 1, wherein either the target or the source is a group of entities.

7. The method of claim 1, wherein either the target or the source is a work queue.

8. The method of claim 1, wherein either the target or the source is an entity and the relationship is defined based on the prior actions of a user.

9. The method of claim 8, wherein the target or the source is a task or a form such that the relationship is defined based on a user previously associated with that task or form.

10. The method of claim 1, such that the user relationships are maintained by a subset of the users, wherein the subset has permission to modify information indicative of the mapping for the plurality of defined relationships.

11. The method of claim 1, wherein the maintaining of the defined relationships comprises changing an entity associated with a given relationship.

12. A method of automation of a business process, comprising:

defining a relationship between two entities;

mapping a source entity to a target entity for the relationship;

storing the information indicative of the mapping in a database;

designating the relationship as a routing destination for a business process;

resolving the relationship for the source entity; and

routing the business process to the target entity.

13. The method of claim 12, wherein the database is an external database.

14. The method of claim 12, wherein a portion of the information indicative of the mapping is stored in an internal database, and another portion of the information indicative of the mapping is stored in an external database.

15. The method of claim 14, additionally comprising determining whether the relationship is to be resolved based on information indicative of the mapping stored in an internal database or in an external database.

16. The method of claim 15, wherein a relationship to be resolved based on information indicative of the mapping stored in an external database is resolved via a relationship plug-in.

17. The method of claim 12, wherein a business process comprises the routing of information.

18. The method of claim 13, wherein a business process comprises the routing of a document.

19. A method of automation of business processes, comprising:

mapping a source entity to a target entity for a given relationship;

designating the relationship as a virtual destination for the routing of a business process;

resolving the relationship for the particular source entity; and

routing the business process to the target entity.

20. The method of claim 19, additionally comprising storing the information indicative of the mapping in a database.

21. The method of claim 20, wherein either the source entity or the target entity is based on the relationship being defined in response to prior assigned tasks or actions of a user.

22. The method of claim 19, wherein either the source entity or the target entity is a task or form, wherein the relationship is defined based on a user'"'"'s previous association with that task or form.

23. The method of claim 20, wherein the relationship information indicative of the mapping is dynamically maintained in response to events.

24. The method of claim 23, wherein the events comprise the routing of the form or the assignment of the task to another user.

25. A method of automation of business processes, comprising:

defining a relationship between at least two entities;

mapping a source user to a target user for the relationship;

designating the relationship as a routing destination for a business process; and

resolving the relationship for the source user.

26. A method of automation of business processes, comprising:

designating a relationship as a virtual destination for a business process;

resolving the relationship for a given source user; and

routing the business process to a target user for which the relationship with the source user was resolved.

27. A method of contextual routing of information, comprising:

defining a relationship between a source and a target;

designating the relationship as a routing destination for the information;

resolving the relationship for the source; and

routing the information from the source to the target.

28. A system for automation of business processes, comprising:

a centrally managed database containing relationship information, wherein target users are mapped to source users for a plurality of given relationships;

a resolver in data communication with the database, configured to identify a target user based on a particular source user and the mapped information;

a process engine in data communication with the resolver, configured to route processes based on designated relationships; and

a network computer, in communication with the process engine via a network, configured to designate relationships as destinations for routing processes.

29. The system of claim 28, wherein the process engine maintains a list of previously routed business processes.

30. The system of claim 29, wherein the process engine dynamically maintains mappings for relationships defined in terms of previously routed business processes.

31. The system of claim 28, wherein the resolver comprises an internal resolver configured to determine a target user based on information indicative of the mapping in an internal database.

32. The system of claim 31, wherein the information in the internal database is managed by the system.

33. The system of claim 32, wherein the resolver further comprises one or more relationship plug-ins configured to determine a target user based on information indicative of the mapping in an external system.

34. The system of claim 33, wherein the information in the external system is managed by the external system.

35. The system of claim 34, wherein the process engine is further configured to determine whether a given designated relationship is to be resolved via the internal resolver or via a particular relationship plug-in.

36. A system for automation of business processes, comprising:

a database containing relationship information, including a mapping of a source user to a target user for a given relationship;

a resolver in data communication with the database, configured to determine the target user mapped to the source user for the given relationship; and

a process engine, configured to route a business process to the target user based on the given relationship used as a virtual destination.

37. A system for automation of business processes, comprising:

a database containing user relationship information;

a process engine, configured to route business processes to targets based on designated relationships; and

a resolver in data communication with the database and the process engine, configured to determine a given target user based on a source user and a particular relationship.

38. A method of automation of business processes, comprising:

defining a first relationship;

for a plurality of source entities, mapping each source entity to a target entity for the relationship;

designating the relationship as a virtual destination for a business process; and

resolving the relationship for a given source entity.

39. The method of claim 38, wherein the mapping of source entities to target entities comprises associating the first relationship with at least a second relationship maintained via an external system in which source entities are mapped to target entities for the second relationship

40. The method of claim 38, wherein the mapping of source entities to target entities comprises associating the first relationship with a plurality of additional relationships maintained via an external system in which source entities are mapped to target entities for the plurality of additional relationships.

41. The method of claim 40, wherein at least two of the plurality of additional relationships are maintained via separate external systems.

42. The method of claim 38, wherein maintaining the information indicative of the mapping for the second relationship is done by the external system.