Modeling the life cycle of individual data objects
3 Assignments
0 Petitions
Accused Products
Abstract
Techniques are provided for individual data objects in an enterprise computing system, where the individual data objects represent unique assets of a family of assets. The individual data objects are used in addition to business partner master data, and also in some cases in addition to generic product master data. The individual data objects are configurable such that attributes for an individual data object change over the lifetime of the unique asset to which the individual data object pertains. Techniques for modeling the lifecycle of an individual object family are described. Techniques also are provided for an integration framework that integrates a software application with an individual object that is used or altered by the software application.
-
Citations
62 Claims
-
1-38. -38. (Cancelled)
-
39. A method for user modeling, within a computer system, of a lifecycle of uniquely identified computer data objects that are members of a computer data object family, the method comprising:
-
receiving a user-defined triggering event occurring in a software application system;
receiving user-defined
1) permissible states for one or more object attributes that may be present for a uniquely identified computer data object that is a member of the data object family, and
2) permissible transitions between the defined permissible states; and
receiving a user-defined action to be performed on a uniquely identified computer data object that is a member of the computer data object family, when the user-defined triggering event occurs and causes a permissible state transition to occur. - View Dependent Claims (40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50)
-
-
51. A computer program product comprising program instructions that when executed enable a computer system to perform a method for user modeling of a lifecycle of uniquely identified computer data objects that are members of a computer data object family, the method comprising:
-
receiving a user-defined triggering event occurring in a software application system;
receiving user-defined
1) permissible states for one or more object attributes that may be present for a uniquely identified computer data object that is a member of the data object family, and
2) permissible transitions between the defined permissible states; and
receiving a user-defined action to be performed on a uniquely identified computer data object that is a member of the computer data object family, when the user-defined triggering event occurs and causes a permissible state transition to occur. - View Dependent Claims (52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62)
-
Specification