1 COINS Development Seminar Efficiency of Design Tim Armitage

Design Number of key presses/clicks/page refreshes to enter data Appropriate info on a top level WB to avoid drilling into the detail Better use of concurrent update for faster input (or other technology) Better use of page sets for visibility of different information Use of better logic when creating drill downs i.e if only one record no need to open a second page which caters for many records. i.e s/c liabilities where most the time the order went to one costcode so no need to open a page for multi distribution (potentially) When designing screens consider the order that data is laid out and therefore will be input When designing screens consider what information can be default entered from previous data or parameter type logic Consider the number of tabs, and the order of the tabs is appropriate to the input order i.e PL invoice input you get the hold code tab before you have finished costing which means you click back 2

Examples Financial Batch Actions Default filters Focus on filter Keyboard shortcuts Actions within summary PL Invoices - Shared Services No Batch Field layout / order / single page Single VAT code Post Button VAP Valuation Entry Hover over Keyboard Info Messages 3

Examples Section Maintenance Fields Layout Page Sets Service – Cost Head/Type Sets Concurrent update Column Sets Bulk maintenance Bulk group maintenance User Defined Fields Service Orders Layout Buttons Header Navigation Breadcrumbs 4

Examples RIA Service and Dispatch Workflow Query Editor Ajax buttons Cash Book Number of screens Links 5