Techniques for dynamic data processing

• US 10,467,200 B1
• Filed: 08/26/2014
• Issued: 11/05/2019
• Est. Priority Date: 03/12/2009
• Status: Active Grant

• Current Assignee: Pegasystems Incorporated
• Original Assignee: Pegasystems Incorporated
• Inventors: Trefler, Alan, Replogle, Mark, Clinton, John
• Primary Examiner(s): Badawi, Sherief
• Assistant Examiner(s): Hoffler, Raheem
• Application Number:
  US14/469,208
• Time in Patent Office: 1,897 Days
• Field of Search: 707600
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: H04L 67/01 Protocols

Abstract

Described are techniques for processing an instance of a data structure. A request to process an instance of a data structure at a first point in time is received. At least one of the data elements in the data structure is a dynamic data element that uses an association specifying how to access data for the dynamic data element in accordance with criteria evaluated using a current context determined at a point in time. In response to receiving the request, first processing is performed including determining whether the dynamic data element is referenced at the first point in time, and, if so, evaluating the criteria using a current context determined at the first point in time, and retrieving data for the dynamic data element in accordance with a current context determined at the first point in time.

Claims

1. A server for processing an instance of a data structure, the server comprising:

a volatile data store; and

a processing unit in communication with the volatile data store,

wherein, at a first point in time, the processing unit;

receives a request to create an instance of a data structure according to a definition of an object-oriented class defining data elements associated with the instance, those data elements including a dynamic data element the definition of which uses an association specifying how to retrieve data for the dynamic data element in accordance with criteria evaluated using a context that is current subsequent to the first point in time,

in response to receiving the request, allocates storage in the volatile data store for data elements in the data structure which are not dynamic data elements but does not allocate storage in the volatile data store for the dynamic data element;

wherein, at a second point in time that is subsequent to the first point in time, the processing unit;

detects a reference to the dynamic data element in connection with a triggering event; and

in response to detecting the reference, the processing unit;

allocates storage in the volatile data store for the dynamic data element,

evaluates the criteria using a current context determined at the second point in time, and

retrieves data for the dynamic data element in accordance with the association used in the definition of that data element and in accordance with the criteria evaluated using the current context at the second point in time.

2. The server of claim 1, wherein the use one or more parameters which are evaluated in accordance with a current context at each point in time when the dynamic data element is referenced.

3. The server of claim 2, wherein at least one of the parameters is a value of another data element in the instance of the data structure.

4. The server of claim 2, wherein at least one of the parameters is based on a date associated with a time at which the dynamic data element is referenced.

5. The server of claim 1, wherein the instance of the data structure is saved to a persistent data store.

6. The server of claim 1, wherein the server further comprises

a cache that stores the one or more data elements associated with the instance of a data structure, wherein the cache is any of a session cache for at least one client and a global cache used by a plurality of clients;

and

wherein the data is retrieved from a persistent data store to create the instance of the data structure in the session cache.

7. The server of claim 6, wherein a different session cache is used for each client.

8. The server of claim 7, wherein a copy of the instance is stored in the global cache.

9. The server of claim 8, wherein each of the plurality of client sessions corresponds to a different client connected to the server and the global cache is used as a server cache by the plurality of client sessions.

10. The server of claim 1, wherein the data structure is an object in an object-oriented environment.

11. The server of claim 10, wherein each data element associated with the object represents any of an attribute and a property of the class.

12. The server of claim 10, wherein a definition for the data structure is included in a definition of the class, the class being included in a class structure.

13. The server of claim 12, wherein the dynamic data element is included in a second class definition that is defined at a same level in the class structure as the class.

14. The server of claim 1, wherein the evaluating the criteria at the second point in time results in identifying an existing instance of a data entity which is retrieved from a data store by the retrieving.

15. The server of claim 1, wherein the association is an explicit association specifying a single data access description identifying how to retrieve the data for the dynamic data element in accordance with the current context at the second point in time.

16. The server of claim 1, wherein the association is a conditional association including a plurality of conditions and corresponding data access descriptions, wherein if one of the conditions evaluates to true, a selected one of the corresponding data access descriptions is used to retrieve data for the dynamic data element.

17. The server of claim 1, wherein the association is a derived association including a single data access description identifying how to retrieve data for the dynamic data element in accordance with the current context at the second point in time, the derived association including one or more values which are further processed at the second point in time in order to retrieve data for the dynamic data element.

18. The server of claim 17, wherein the derived association includes a plurality of data values which are further processed in accordance with an operation identified in the derived association.

19. The server of claim 18, wherein the operation includes performing any of a mathematical operation and a string operation on at least a portion of the plurality of data values.

20. The server of claim 18, wherein the operation uses any of forward chaining and backward chaining inference methods.

21. The server of claim 1, wherein the association includes a data access description that identifies how to retrieve the data for the dynamic data element, wherein the data access description includes an item that depends upon at least one of the criteria.

22. The server of claim 21, wherein the item is a key included in a database query and the key has a value determined in accordance with a parameter included in the criteria, the parameter having a value determined in accordance with a current context at a point in time when the dynamic data element is referenced.

23. The server of claim 21, wherein the data access description identifies at least one of a database to be accessed in connection with the retrieving, a location of a database, and a protocol.

24. The server of claim 1, wherein the association is included in metadata for the dynamic data element.

25. The server of claim 24, wherein in response to detecting the reference, a portion of the metadata is updated.

26. The server of claim 1, wherein the data structure represents a work item in a business process.

27. The server of claim 26, wherein the business process is managed by any of a public and private entity.

28. The server of claim 27, wherein the business process is a process in one of a plurality of areas, the plurality of areas including telecommunications, government, insurance, insurance claims processing, insurance application renewal, insurance underwriting, finance, loan processing, healthcare, automotive, retail product sales, clothing, marketing, computer services, food and restaurant industry, consumer sales and services, purchasing a product or service, returning a previously purchased item, submitting a complaint or problem report requiring resolution, ensuring compliance with government rules and regulations, and inventory update and purchasing.

29. The server of claim 1, wherein in connection with detecting the reference, the data for the dynamic data element corresponds to a first data instance, and, if the first data instance is already loaded into the volatile data store, the first data instance already loaded into the volatile data store is used in connection with the retrieving, and otherwise additional processing is performed to load the first data instance into the volatile data store.

30. The server of claim 1,

wherein the dynamic data element is referenced at the first point in time and the criteria is evaluated in accordance with the current context at the first point in time to access data for the dynamic data element, and

in response to receiving the request, determining that data for the dynamic data element corresponds to a first data instance of a first class or type.

31. The server of claim 30, wherein the processing unit, in response to detecting the reference, determines that data for the dynamic data element corresponds to a second data instance of the first class or type.

32. The server of claim 1, wherein the triggering event includes any of displaying a user interface with the dynamic data element contained therein, performing rule processing, determining that data for the dynamic data element is not already loaded into the volatile data store, determining that data for the dynamic data element is not already loaded into a session cache or a server cache, and determining that a cached copy of data for the dynamic data element is no longer valid in accordance with an expiration time.

33. The server of claim 1, wherein the association is included in a declarative page, and the declarative page is used in connection with the referencing to retrieve the data for the dynamic data element.

34. The server of claim 33, wherein the declarative page is referenced during processing of the dynamic data element in connection with a workflow process.

35. The server of claim 33, wherein the declarative page is updated to change how data for the dynamic data element is accessed, wherein the change includes using at least one of:

a different criterion, a different condition, a different parameter, and a different data access description.

36. The server of claim 34, wherein the declarative page is defined in a declarative page definition, and the workflow process is defined in a workflow process definition that is separate from the declarative page definition.

37. The server of claim 1, wherein at least one of the data structure and the dynamic data element is a database table.

38. The server of claim 37, wherein the database table is in a normalized form.

39. The server of claim 1, wherein one of the data structure and the dynamic data element is an object and another of the data structure and the dynamic data element is a database table.

40. A computer-implemented method for processing an instance of a data structure, the method comprising:

receiving, at a first point in time, a request to create an instance of a data structure according to a definition of an object-oriented class defining data elements associated with the instance, those data elements including a dynamic data element the definition of which uses an association specifying how to retrieve data for the dynamic data element in accordance with criteria evaluated using a context that is current subsequent to the first point in time;

allocating at the first point in time in response to receiving the request storage in a volatile data store for data elements in the data structure which are not dynamic data elements but does not allocate storage in the volatile data store for the dynamic data element;

detecting, at a second point in time that is subsequent to the first point in time, a reference to the dynamic data element in connection with a triggering event; and

in response to detecting the reference, performing steps of;

allocating storage in the volatile data store for the dynamic data element,

evaluating the criteria using a current context determined at the second point in time, and

retrieving data for the dynamic data element in accordance with the association used in the definition of that data element and in accordance with the criteria evaluated using the current context at the second point in time.

41. The method of claim 40, wherein the criteria is evaluated to determine a location from which data for the dynamic data element is retrieved, the criteria including a first condition which, when having a first value as a result of the evaluating, specifies that the data for the dynamic data element is retrieved from a first location, and which, when having a second value as a result of the evaluating, specifies that the data for the dynamic data element is retrieved from a second location different from the first location.

42. The method of claim 40, wherein the request is made in connection with performing a business process.

43. The method of claim 42, wherein the business process is performed in connection with at least one of insurance, finance, healthcare, automotive, food and restaurant industry, sales and services for consumer goods and services, purchasing a product, purchasing a service, returning a previously purchased item, submitting a complaint requiring resolution, inventory update, insurance claim processing, insurance application renewal, insurance underwriting, and loan processing.

44. A non-transitory computer-readable medium for processing an instance of a data structure, the computer-readable medium comprising executable code for:

receiving, at a first point in time, a request to create an instance of a data structure according to a definition of an object-oriented class defining data elements associated with the instance, those data elements including a dynamic data element the definition of which uses an association specifying how to retrieve data for the dynamic data element in accordance with criteria evaluated using a context that is current subsequent to the first point in time;

allocating at the first point in time in response to receiving the request storage in a volatile data store for data elements in the data structure which are not dynamic data elements but does not allocate storage in the volatile data store for the dynamic data element;

detecting, at a second point in time that is subsequent to the first point in time, a reference to the dynamic data element in connection with a triggering event; and

in response to detecting the reference, performing steps of;

allocating storage in the volatile data store for the dynamic data element,

evaluating the criteria using a current context determined at the second point in time, and

retrieving data for the dynamic data element in accordance with the association used in the definition of that data element and in accordance with the criteria evaluated using the current context at the second point in time.