USER BASED - WORKFLOW AND BUSINESS PROCESS MANAGEMENT

• US 20060259603A1
• Filed: 05/15/2006
• Published: 11/16/2006
• Est. Priority Date: 05/16/2005
• Status: Abandoned Application

• Current Assignee: ECC Development Services Incorporated
• Original Assignee: ECC Development Services Incorporated
• Inventors: Fox, Anthony P., Shrader, Anthony G.
• Application Number:
  US11/383,357
• Publication Number:
  US 20060259603A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

Disclosed is a business rules workflow system that provides a single communication interface for communications between end user applications, such as an agent user interface, and back office applications. The business rules workflow system also provides a single interface to apply business rules to the end user application to back office application communications. The communications and business rules interfaces reduce the need for multiple user interfaces using multiple technology, thus reducing the complexity, maintenance, and upgrade costs for a typical business environment. The business rules workflow system sends and receives data form pre-existing data systems, converts the pre-existing data system data into a common format, and sends the data to the data consumer. Any business rules based on the pre-existing system data will be applied by the business rules workflow system.

Claims

1. A method of optimizing back office enterprise computer systems to end user computer systems workflow comprising:

concentrating workflow communication messages that are transmitted to and from at least one back office application into a single common communication format that is accessible by at least one end user computer application;

communicating said workflow communication messages directly to and from said at least one end user computer application in said single common communication format such that said workflow communication messages are not converted into an end user application format prior to being communicated to said at least one end user computer application; and

applying user configured business rules to said workflow communication messages formatted with said single common communication format such that said at least one end user computer application behaves in accordance with said user configured business rules.

2. The method of claim 1 further comprising translating said workflow communication messages that are transmitted to and from said at least one back office application into and out of said common communication format using a BOA Server in order to facilitate communication with said at least one end user computer application.

3. The method of claim 2 further comprising using a client toolkit to assist said at least one end user computer application in sending and receiving said workflow communication messages formatted in said common communication format and to assist said at least one end user computer application in applying said configured business rules to said workflow communication messages.

4. The method of claim 3 further comprising supplying client connection classes in said client toolkit in order to provide the structure for said workflow communication messages formatted in said common communication format to said at least one end user computer application to assist in sending and receiving said workflow communication messages formatted in said common communication format.

5. The method of claim 4 wherein said client connection classes are implemented with Plain Old Java Objects (POJO) and said common communication format is implemented with extensible Markup Language (XML).

6. The method of claim 3 further comprising applying said user configured business rules to said workflow communication messages via a client script evaluator by sending script events to request that actions be performed by said at least one end user computer application and reading and evaluating responses of said at least one end user computer application to said script events.

7. The method of claim 1 wherein said step of applying user configured business rules to said workflow communication messages further comprises using a business rules graphical user interface application to obtain business rule information from said workflow communication messages and to permit an end user to configure business rules that govern operation of said at least one end user computer application in regards to said workflow communication messages such that said step of applying user configured business rules to said workflow communication messages is controlled by said business rules graphical user interface application.

8. The method of claim 1 wherein said method for optimizing back office enterprise computer systems to end user computer systems workflow is implemented as platform independent, distributed, server deployed software applications.

9. The method of claim 1 wherein said method for optimizing back office enterprise computer systems to end user computer systems workflow performs Computer Telephony Integration (CTI).

10. A business rules workflow system for optimizing back office enterprise computer systems to end user computer systems workflow comprising:

a common language message subsystem that concentrates workflow communication messages that are transmitted to and from at least one back office application into a single common communication format that is accessible by at least one end user computer application; and

a communication subsystem that communicates said workflow communication messages directly to and from said at least one end user computer application in said single common communication format such that said workflow communication messages are not converted into an end user application format prior to being communicated to said at least one end user computer application; and

a business rules interface subsystem that applies user configured business rules to said workflow communication messages that are formatted with said single common communication format such that said at least one end user computer application behaves in accordance with said user configured business rules.

11. The business rules workflow system of claim 10 further comprising a BOA Server capable of translating said workflow communication messages that are transmitted to and from said at least one back office application into and out of said common communication format in order to facilitate communication with said at least one end user computer application.

12. The business rules workflow system of claim 11 further comprising a client toolkit subsystem that interacts with said at least one end user computer application, said client toolkit subsystem assisting said at least one end user computer application in sending and receiving said workflow communication messages formatted in said common communication format and assisting said at least one end user computer application in applying said configured business rules to said workflow communication messages.

13. The business rules workflow system of claim 12 wherein said client toolkit subsystem further comprises client connection classes that provide the structure for said workflow communication messages formatted in said common communication format to said at least one end user computer application in order to assist in sending and receiving said workflow communication messages formatted in said common communication format.

14. The business rules workflow system of claim 13 wherein said client connection classes are implemented with Plain Old Java Objects (POJO).

15. The business rules workflow system of claim 13 wherein said common communication format is implemented with extensible Markup Language (XML).

16. The business rules workflow system of claim 12 wherein said client toolkit subsystem further comprises a client script evaluator subsystem that applies said user configured business rules to said workflow communication messages by sending script events to request that actions be performed by said at least one end 5 user computer application and reading and evaluating responses of said at least one end user computer application to said script events.

17. The business rules workflow system of claim 10 wherein said business rules interface subsystem further comprises a business rules graphical user interface application that obtains business rule information from said workflow communication messages and permits an end user to configure business rules that govern operation of said at least one end user computer application in regards to said workflow communication messages such that said business rules interface subsystem is configured by said business rules graphical user interface application.

18. The business rules workflow system of claim 10 wherein said common language message subsystem, said communication subsystem, and said business rules interface subsystem are implemented as platform independent, distributed, server deployed software applications.

19. The business rules workflow system of claim 10 wherein said business rules workflow system is incorporated in a Computer Telephony Integration (CTI) system.

20. A business rules workflow system for optimizing back office enterprise computer systems to end user computer systems workflow comprising:

means for concentrating workflow communication messages that are transmitted to and from at least one back office application into a single common communication format that is accessible by at least one end user computer application;

means for communicating said workflow communication messages directly to and from said at least one end user computer application in said single common communication format such that said workflow communication messages are not converted into an end user application format prior to being communicated to said at least one end user computer application; and

means for applying user configured business rules to said workflow communication messages formatted with said single common communication format such that said at least one end user computer application behaves in accordance with said user configured business rules.