Patent application number | Description | Published |
20090313684 | USING WINDOWS AUTHENTICATION IN A WORKGROUP TO MANAGE APPLICATION USERS - An system for authenticating users of an application program executing at a front-end computer using the security features built into the operating system of a logon computer is provided. Initially, an administrator establishes user accounts for each user with an operating system executing at the logon computer with access to application resources. When the application program starts executing at the front-end computer, the application program prompts the user for credentials. The application program attempts to access resources managed by the logon computer using the received credentials. When access to a resource is successful, the application program knows that the logon computer has authenticated the user and the user is authorized to access the resource. In this manner, the application program can take advantage of the security features built into the operating system executing at the logon computer to authenticate users of the application program and authorize access to application resources. | 12-17-2009 |
20090319382 | EXTENSIBLE FRAMEWORK FOR SUPPORTING DIFFERENT MODES OF PAYMENTS - A method and system for providing an extensible framework for a POS application is provided. A POS application may be extended using a payment format add-in, a workflow add-in, a financial services provider add-in, or a combination of add-ins. A payment format add-in provides support for a payment format not included in the payment formats built into the POS application. A workflow add-in provides a configurable workflow that can be used to extend a built-in payment format or a payment format add-in. A financial services provider add-in provides support for interacting with a financial services provider for which the POS application does not provide built-in support. Each add-in can implement, for example, logic for processing a payment transaction, a portion of a payment transaction, and configuring steps for processing a payment transaction. | 12-24-2009 |
20100274813 | EXTENSIBLE FRAMEWORK FOR DATA IMPORT AND EXPORT - A modular framework for data import/export in an application that allows modules/components to be independently developed for importing and exporting data related to specific entities, including the handling of dependencies between entities. The framework is metadata driven which allows new entities to be introduced in the application with new modules for importing/exporting data related to those entities, without updating modules for exporting existing entities. Each type of entity is defined with a schema that represents the logical entity such that the entity is agnostic as to how the entity data is stored in database tables. A master configuration file is created for the application that lists each entity that can be imported or exported by the application, and defines how the framework imports or exports the business entity. Additionally, dynamic batching is provided to divide large datasets into multiple batches for suitable consumption by consumers of the exported data. | 10-28-2010 |
20110161186 | EXTENSIBLE FRAMEWORK FOR SUPPORTING DIFFERENT MODES OF PAYMENTS - A method and system for providing an extensible framework for a POS application is provided. A POS application may be extended using a payment format add-in, a workflow add-in, a financial services provider add-in, or a combination of add-ins. A payment format add-in provides support for a payment format not included in the payment formats built into the POS application. A workflow add-in provides a configurable workflow that can be used to extend a built-in payment format or a payment format add-in. A financial services provider add-in provides support for interacting with a financial services provider for which the POS application does not provide built-in support. Each add-in can implement, for example, logic for processing a payment transaction, a portion of a payment transaction, and configuring steps for processing a payment transaction. | 06-30-2011 |
20110320433 | Automated Joining of Disparate Data for Database Queries - Described is associating metadata with different sources of data (e.g., database tables) that allows a single view of data from the sources to be created. An administrator creates baseviews corresponding to database tables and associates metadata with the baseviews, including primary key metadata for the baseviews and meta-tags for one or more of the columns of each baseview. A user selects fields (corresponding to table columns) from a starting baseview, along with fields from any other baseview that has metadata that matches the starting baseview's metadata. A join mechanism automatically creates the view if a metadata match is detected. | 12-29-2011 |
20130006664 | Data Change Tracking and Event Notification - The described implementations relate to updating views in a database system. One implementation can identify an active view that retrieves records from a database and determine one or more physical tables in the database that are referenced by the active view. The implementation can track one or more columns in the physical tables that are used by the active view and identify a change to the physical tables in a transaction log of the database. If the change does not affect the one or more columns, the change can be treated as an ignorable change for the active view. | 01-03-2013 |
20130006963 | DATA CHANGE TRACKING AND EVENT NOTIFICATION - The described implementations relate to updating views in a database system. One implementation can identify an active view that retrieves records from a database and determine one or more physical tables in the database that are referenced by the active view. The implementation can track one or more columns in the physical tables that are used by the active view and identify a change to the physical tables in a transaction log of the database. If the change does not affect the one or more columns, the change can be treated as an ignorable change for the active view. | 01-03-2013 |
20130007069 | Data Change Tracking and Event Notification - The described implementations relate to updating views in a database system. One implementation can identify an active view that retrieves records from a database and determine one or more physical tables in the database that are referenced by the active view. The implementation can track one or more columns in the physical tables that are used by the active view and identify a change to the physical tables in a transaction log of the database. If the change does not affect the one or more columns, the change can be treated as an ignorable change for the active view. | 01-03-2013 |
20130110542 | PATIENT DATA MANAGEMENT | 05-02-2013 |
20130298212 | USING WINDOWS AUTHENTICATION IN A WORKGROUP TO MANAGE APPLICATION USERS - An system for authenticating users of an application program executing at a front-end computer using the security features built into the operating system of a logon computer is provided. Initially, an administrator establishes user accounts for each user with an operating system executing at the logon computer with access to application resources. When the application program starts executing at the front-end computer, the application program prompts the user for credentials. The application program attempts to access resources managed by the logon computer using the received credentials. When access to a resource is successful, the application program knows that the logon computer has authenticated the user and the user is authorized to access the resource. In this manner, the application program can take advantage of the security features built into the operating system executing at the logon computer to authenticate users of the application program and authorize access to application resources. | 11-07-2013 |