Abstract: An audit trail system allows a user to configure and view an audit trail of changes that have been made to various types of information that can be accessed by one or more users in a network of computer systems. The various types of information are grouped in business components. A user can select particular business components, and fields within a business component, to be audited. The audit trail shows who has accessed the business component, the operation performed, when the operation was performed, and how the value of at least a portion of the business component was changed. Users can track when operations such as update, create, delete, and copy are performed on the selected business components, as well as track which employee modified a certain field and the data that has been changed. Users can also reconstruct records that existed at a certain point of time. Options to restrict access to audit trails by selected areas of responsibility, positions, and/or employee identifiers, can also be included.

Abstract: A dynamic pricing system and method that enables prices for sellable objects to be dynamically adjusted using pricing factors corresponding to attributes of the sellable objects. Product administrators are enabled to define sellable products and extended attributes for the products, while pricing administrators are enabled to define price lists for the sellable products and extended attributes. Sales representatives build sellable objects, such as quotes, orders, shopping carts, etc, by adding products that customers would like to purchase to the sellable object. Additionally, extended attributes may be selected for all or a portion of the products. Using Static Pricing, an initial or static price is determined for the sellable objects. The static price may then be dynamically adjusted prior to or at the point of a sales transaction or offer using pricing factors corresponding to combinations of various attributes of the sellable object and/or products from which it is built.

Abstract: A dynamic pricing system and method that enables prices for sellable objects to be dynamically adjusted using pricing factors corresponding to attributes of the sellable objects. Product administrators are enabled to define sellable products and extended attributes for the products, while pricing administrators are enabled to define price lists for the sellable products and extended attributes. Sales representatives build sellable objects, such as quotes, orders, shopping carts, etc, by adding products that customers would like to purchase to the sellable object. Additionally, extended attributes may be selected for all or a portion of the products. Using Static Pricing, an initial or static price is determined for the sellable objects. The static price may then be dynamically adjusted prior to or at the point of a sales transaction or offer using pricing factors corresponding to combinations of various attributes of the sellable object and/or products from which it is built.

Abstract: An extended attribute-based pricing system and method that enables users to build sellable objects based on selected products and extended attributes for those products. Product administrators are enabled to define sellable products and extended attributes for the products, while pricing administrators are enabled to define price lists for the sellable products and extended attributes. Sales representatives build sellable objects, such as quotes, orders, shopping carts, etc, by adding products that customers would like to purchase to the sellable object. Additionally, extended attributes may be selected for all or a portion of the products. The extended attributes may be stored in attribute classes, and may be loaded into memory structures to reduce database accesses.

Abstract: An audit trail system allows a user to configure and view an audit trail of changes that have been made to various types of information that can be accessed by one or more users in a network of computer systems. The various types of information are grouped in business components. A user can select particular business components, and fields within a business component, to be audited. The audit trail shows who has accessed the business component, the operation performed, when the operation was performed, and how the value of at least a portion of the business component was changed. Users can track when operations such as update, create, delete, and copy are performed on the selected business components, as well as track which employee modified a certain field and the data that has been changed. Users can also reconstruct records that existed at a certain point of time. Options to restrict access to audit trails by selected areas of responsibility, positions, and/or employee identifiers, can also be included.

Abstract: System and method for preparing, using, and displaying a state model of a process, as an industrial or business process, as a sequence of discrete steps. The state model defines the behavior of the logical objects making up a process model of the process as (1) a set of permitted states and (2) a set of permitted transitions between the permitted states. The state model is created by selecting a template for the state model, and selecting industrial or business object components for the state model (for example, by using “OOP” methods or other programming paradigms). The user then selects or defines state transitions for the state model, for example, by defining permitted state transitions from a “from state” to a “to state”. The defined or selected state transition rules are identified to State Transition Rule names.

Abstract: System and method for preparing, using, and displaying a state model of a process, as an industrial or business process, as a sequence of discrete steps. The state model defines the behavior of the logical objects making up a process model of the process as (1) a set of permitted states and (2) a set of permitted transitions between the permitted states. The state model is created by selecting a template for the state model, and selecting industrial or business object components for the state model (for example, by using “OOP” methods or other programming paradigms). The user then selects or defines state transitions for the state model, for example, by defining permitted state transitions from a “from state” to a “to state”. The defined or selected state transition rules are identified to State Transition Rule names.