Abstract: A data protector is described. In an implementation, the data protector promotes and enforces a data retention policy of a data consumer. In an implementation, the data protector limits access to sensitive data to the data consumers. A key manager provides a time-limited encryption key to the data protector. Responsive to collection of the time-limited encryption key from the key manager and sensitive data from a data provider, the data protector encrypts the sensitive data with the time-limited encryption key effective to produce encrypted sensitive data. In some embodiments, the data protector provides a data consumer with access to the encrypted sensitive data and the key manager provides the data consumer with access to the time-limited encryption key to decrypt the encrypted sensitive data. The key manager deletes the time-limited encryption key in compliance with the data retention policy of the data consumer.

Abstract: A data protector is described. In an implementation, the data protector promotes and enforces a data retention policy of a data consumer. In an implementation, the data protector limits access to sensitive data to the data consumers. A key manager provides a time-limited encryption key to the data protector. Responsive to collection of the time-limited encryption key from the key manager and sensitive data from a data provider, the data protector encrypts the sensitive data with the time-limited encryption key effective to produce encrypted sensitive data. In some embodiments, the data protector' provides a data consumer with access to the encrypted sensitive data and the key manager provides the data consumer with access to the time-limited encryption key to decrypt the encrypted sensitive data. The key manager deletes the time-limited encryption key in compliance with the data retention policy of the data consumer.

Abstract: A system for supporting version management is provided. The system includes a first application having a plurality of versions. Each of the plurality of versions is associated with a separate a version-specific assembly. A loader is configured to load one of the version-specific assemblies, the assembly then being utilized as a basis for deriving an object from a database associated with the first application. The object is provided to a second application, typically in response to a corresponding request.

Abstract: A system is disclosed for processing billable activities. The system includes a scheduling component configured to support creation of a plurality of activity records. A sub-set of the activity records are designated as being associated with billable activity. The system also includes an accounting component for receiving information based on the sub-set of the activity records. The information is transmitted from the scheduling component to the accounting component.

Abstract: The present invention relates to a subscription modeling system and methodology. A query processor receives subscription query and subscriber information and transforms the query and subscriber information into data. An index component propagates at least one database with the transformed data; and a matching component that associates the transformed data with event data to generate a database of notification data that can be delivered to subscribers. The invention provides for abstracting subscription and subscriber information (as well as event information if desired) to high-level classes (e.g., data fields)—thus the invention provides for modeling such notification related information as data. Subscription applications can thus be developed at high levels wherein complex subscription queries and subscriber information can be defined as data fields for example. Databases in accordance with the data fields can be propagated with subscription/subscriber specific information.

Abstract: An application or method of populating a transaction from a document using procedures associated with document type. In the embodiments described, the application or method posts a financial transaction from a financial document, such as a sales invoice or vendor bill to a financial account, such as A/R or COGS. In embodiments described, the application or method employs posting procedures for posting types associated with the document type and document line type of the document. The posting procedures are invoked for the posting class or type attributed to the document type or the document line type to post the transaction.

Abstract: A system is disclosed for processing billable activities. The system includes a scheduling component configured to support creation of a plurality of activity records. A sub-set of the activity records are designated as being associated with billable activity. The system also includes an accounting component for receiving information based on the sub-set of the activity records. The information is transmitted from the scheduling component to the accounting component.

Abstract: A method of modifying an original transaction document of a computerized accounting system that includes a general ledger having original transaction postings corresponding to transactions contained in the original transaction document, a new transaction document is generated in response to a command to edit the original transaction document. Next, the new transaction document is modified and saved as a modified new transaction document. The original transaction postings in the general ledger are then nullified. Finally, transactions of the modified new transaction document are posted in the general ledger.