Infragistics Scenario Solutions - Answers to Common Problems http://community.infragistics.com/scenarios/default.aspx http://www.infragistics.com/scenarios/visualization/conditionally-format-grid-cells.aspx Wed, 07 Mar 2007 05:00:00 GMT <![CDATA[ Users must be alerted to cell values in tables of information that have meet some condition, such as exceeding an extreme value (an example would be when temperatures taken during quality control testing indicate a problem at some stage of a manufacturing process because their value has exceeded a safety threshold).  Your application would format these values, for instance in a red color, to attract the user's attention to them. ]]> http://www.infragistics.com/scenarios/visualization/conditionally-format-grid-cells.aspx http://www.infragistics.com/scenarios/visualization/tracking-long-processes.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must be kept informed about the progress of any long-running process that your application must perform.  For example, if your application needs to download market price data on a daily basis before your users can interact with the whole set of data, then you can manage user expectations and minimize their frustration by keeping them updated about how much of the download has been completed, and how much is still to go. ]]> http://www.infragistics.com/scenarios/visualization/tracking-long-processes.aspx http://www.infragistics.com/scenarios/visualization/menu-icons.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must find your application easy to learn.  Your application presents graphical icons beside menu commands the reinforce in the user's mind what purpose particular menu commands have.  If users cannot presently use a particular menu command but it must remain visible, your application depicts its graphical icon in a grayed out appearance that users are familiar with as representing a command's unavailability. ]]> http://www.infragistics.com/scenarios/visualization/menu-icons.aspx http://www.infragistics.com/scenarios/visualization/export-grid-to-excel.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must have the ability to download a copy of the information in your application's table(s) in an Excel workbook to work with outside of your application.  For example, prospective buyers of a life insurance policy may download a workbook in the popular desktop spreadsheet application, Microsoft Excel 97 (or a later version).  The workbook could be a spreadsheet containing "What If?" scenarios illustrating for their age, gender, and class rating what their expected returns would be based on ... ]]> http://www.infragistics.com/scenarios/visualization/export-grid-to-excel.aspx http://www.infragistics.com/scenarios/visualization/context-sensitive-tooltips.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must find your application easy to learn.  Your application presents users with tool tips when they mouse over select regions of the user interface, pertinent to the functions performed by those user interface elements.  Consequently, users do not need to continuously refer to documentation or memorize the function and location of every user interface element, which makes them more productive with your application at a faster pace than without tool tips. ]]> http://www.infragistics.com/scenarios/visualization/context-sensitive-tooltips.aspx http://www.infragistics.com/scenarios/data-entry/scheduling-activities-monthly-calendar.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must schedule activities (tasks, appointments, meetings) taking place on specific dates and times on a calendar visually.  You would like the user to double-click on a date and be able to enter an activity on that date through a form.  When the user looks at the calendar UI they must be clear on what dates have activities scheduled so they do not overschedule themselves. ]]> http://www.infragistics.com/scenarios/data-entry/scheduling-activities-monthly-calendar.aspx http://www.infragistics.com/scenarios/data-entry/free-form-text-content.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users working in content-intensive applications (i.e., content management systems) need the ability to enter or edit richly formatted text which includes control over coloring, text formatting such as italicization or underlining, bullet lists, and other features users expect to find in word processing applications.  Users require visual feedback on the impact of their changes through a What You See Is What You Get (WYSIWYG) user interface. You are storing this content in a form appropriate to ... ]]> http://www.infragistics.com/scenarios/data-entry/free-form-text-content.aspx http://www.infragistics.com/scenarios/data-entry/enter-monetary-values.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must enter monetary amounts (i.e., as part of a point-of-sale application) to two decimal places (dollars and cents, pounds and pence, etc.).  Only the numeric digits 0 to 9 are allowed to be entered.  When no value is entered to the right-side of the decimal point, zeroes are to be assumed. ]]> http://www.infragistics.com/scenarios/data-entry/enter-monetary-values.aspx http://www.infragistics.com/scenarios/data-binding/bind-tree-to-xml.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users navigate through application features or information categorized from broad categories to more specific tasks or reports.  When each categorization is a proper subset of the category above it, the subcategories appear in only one unique place within the tree.  Alternatively, when a subcategory may belong to multiple categorizations, a copy of that subcategory must appear in multiple places. An example would be a sales reporting application where business analysts may examine a company's w ... ]]> http://www.infragistics.com/scenarios/data-binding/bind-tree-to-xml.aspx http://www.infragistics.com/scenarios/data-binding/bind-tree-to-hierarchical-dataset.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must be allowed to navigate through application features or information categorized from broad categories down to more finely-grained tasks or reports.  The categorizations can be managed through a relational database, which permits superusers the ability to modify the navigation experience available to users without having to redeploy your application. Your application loads information about these categories using an ADO.NET DataSet, having DataRelations between one or more DataTables w ... ]]> http://www.infragistics.com/scenarios/data-binding/bind-tree-to-hierarchical-dataset.aspx http://www.infragistics.com/scenarios/data-binding/binding-tree-to-object-collection.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users navigate through application features or information categorized from broad categories to more specific tasks or reports.  For instance, financial representatives may be responsible for a wealth management portfolio having separate categories for high net worth clients, qualified investor clients, and foreign investor clients.  Within each category the representative sees the names of their assigned clients and can select a name to see more information. Your application already treats the ... ]]> http://www.infragistics.com/scenarios/data-binding/binding-tree-to-object-collection.aspx http://www.infragistics.com/scenarios/data-binding/binding-menu-to-xml.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users navigate through application features using a command menu structure that organizes their tasks under common headings.  Submenus cascade down and to the right or left.  An example would be a policy claims administrative application where customer service representatives have a set of canned transactions they're authorized to perform to service various clients: policyholders, beneficiaries, and insureds. In addition to menu commands familiar to most users, each of these client types can be ... ]]> http://www.infragistics.com/scenarios/data-binding/binding-menu-to-xml.aspx http://www.infragistics.com/scenarios/comcon/action-on-toolbar-button.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must have the capability to execute an activity of arbitrary complexity by clicking on a button in a tool bar.  These tool bar buttons must support both an image and/or label text, and the button's appearance should be consistent with the rest of the application.  Your application may carry out these activities by posting to a message queue, making a request to a Web service, or dispatching an e-mail. ]]> http://www.infragistics.com/scenarios/comcon/action-on-toolbar-button.aspx http://www.infragistics.com/scenarios/comcon/action-on-menu-command.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Users must have the capability to select an action of arbitrary complexity to be executed by selecting a command from a menu.  The commands on the menu must support both an image and/or label text, and have the ability to cascade to nested menus containing subcommands and options related to the parent menu command.  Your application may already perform these actions by posting to a message queue, making a request to a Web service, or dispatching an e-mail. ]]> http://www.infragistics.com/scenarios/comcon/action-on-menu-command.aspx http://www.infragistics.com/scenario/data-binding/binding-grid-to-hierarchical-dataset.aspx Mon, 05 Mar 2007 05:00:00 GMT <![CDATA[ Present your users with a master-detail table, which they can explore to their desired level-of-detail by expanding or collapsing sub-tables.  Business records have regular fields (i.e., an order date, shipping date, and shipping address) and relationships across one- or more levels of depth (i.e., line item SKU, quantity, unit price, line total), perhaps summarized by sub-table (i.e., per-order total). Your application retrieves these hierarchically related business records from a relational d ... ]]> http://www.infragistics.com/scenario/data-binding/binding-grid-to-hierarchical-dataset.aspx