The Online Application Interface replaces traditional application dialog boxes with dynamic intelligent user interfaces. The goal of this type of user interface is to improve the efficiency, effectiveness and naturalness of human to screen interactions. The AUI can include instructions and an ability to view supporting documents and add new supporting documents to the transaction (of any file format) either at the transaction level or within specific sections in the AUI. Users can enter data and enrich data from multiple data sources (ODBC views into data sources and API calls). Conditional controls expose other required data without the need to place the user into another dialog box. Error messages are presented to the user within the AUI, eliminating the need for modal or system dialog boxes that restrict user access to the active application interfaces. The user’s entire application experience is in a single, dynamic, morphing AUI in which they can complete all related work without leaving the environment.
- Shows how many documents support this transaction, if any.
- Easy way to browse and upload any primary supporting document or other related documents or files (if any). In this example supporting documents are added to the transaction, but supporting documents can also be consnected directly to a section of the AUI. Some applications don’t involve supporting documents.
- Retrieves all related documents for viewing with a single click. If more than one document is related to the application a list is presented and the user can select one or more documents to view. If documents are associated with a section or a field, the view capability is often deployed with the section or field.
- An example of the user performing a lookup for data validations and auto-filling selected fields with data from external sources.
- An example of the user performing lookups for data to select correct values in a “Repeater Container” that allows the user to dynamically add sections for the number of rows needed to complete their work. In this example, the user is applying account coding with links to the ERP Chart of Accounts. The buttons for adding (inserting) or deleting rows. In this example, adding rows offers an easy way to split the amount of the invoice into multiple account codes.
- Buttons for adding (inserting) or deleting rows. In this example, adding rows offers an easy way to split the amount of the invoice into multiple account codes.
- This user interface includes other variables in a calculation.
- Signature Blocks provide for signing using Windows Credentials (Active Directory) or Named Users or capture signatures using a signature pad or on mobile devices.
As the user enters data, new fields may be automatically created depending on the values entered (conditional panel controls). Look-ups to data sources are completed for the presentation of information or validation of information.
Topaz signature pads are used for AUIs requiring a legally valid signature by a third party.
Windows Authentication (Active Directory integration) or ScerIS User Authentication digital signatures can bind to selected data fields on the AUI for AUIs requiring one or more employee signatures.
The AUI may be joined to a Workflow which will automatically route the AUI into individual or group work queues, or alternatively the user might complete their work and route to (select an individual or group to route to) another party in the system.
The presentation of the AUI is a matter of the design considerations used by the AUI designer. Logos, colors, labeling, links to other files (such as videos for training), panels that expand based on data provided by the user and so much more is simply a matter of setting design parameters for your organization.