6.1 supports new user experiences that you can include in your applications. These can contribute to ease of learning, productivity, and accuracy.

• Browser support — Application users can access Process Commander applications using Internet Explorer 7/8, Firefox, or Safari.
• Action section — The action section for Perform harnesses is refactored to use AJAX server interactions, deliver improved performance, support multiple browsers, and provide multiple display and interaction options. A single, configurable section replaces multiple sections needed in V5.X. See How to present actions on a work object form (6.1)
• Tree, Grid, and TreeGrid layouts — Three new layouts are available providing sophisticated, highly interactive user experiences. These layouts provide improved performance, work with all supported browsers, and offer many features that can be configured through direct interaction. Fields in cells may be presented by a wide variety of HTML property rules. At runtime, users can edit row details in place, or through a pop-up modal dialog. Runtime options can become visible only when a row is selected. See How to add a Grid layout to a section
• Modal dialog — You can cause a flow action to appear in a pop-up modal dialog at runtime. This is useful for local flow actions, row editing on Grid layouts, and other user interactions. You can customize the heading, buttons, and styling elements, application-wide or at the class (work type) level. As with normal flow actions, the modal dialog can provide pre-processing validation, post-processing, and multiple buttons. The dialog window can be localized, support all browsers, and reflects application skin styles. See When and how to use a modal dialog
• Flow action form — Each flow action created in 6.1 references a section rule, promoting reusability. To identify an existing section as the section referenced in a flow action, you can drag the section from the Application Explorer onto the Layout tab.
• Navigation rules — A new rule type eliminates the need to hand-craft XML code to configure a menu for a composite portal. This rule type also supports actions available from a Grid, Tree, and TreeGrid layouts. See How to configure a context menu using Navigation rules and How to configure a menubar in a user portal using Navigation rules
• Branding wizard — The Branding wizard (formerly the Application Skin wizard) is enhanced to allow control over many additional user interface elements, including row and column repeat controls, SmartInfo displays, wizard harnesses, and the background color for images. Circumstanced skins can be individually branded.
• Row Repeat and Column Repeat controls — Users can re-order rows of a Row Repeat display, and can re-order columns of a Column Repeat display, at runtime. Cells in a Row Repeat or Column Repeat control can contain Value List properties.
• Flow actions — Configuration of buttons and other presentation elements of flow actions is simpler.
• Bulk processing — Using the WorkManager traditional portal or the Manager composite portal, managers can request that an assignment be processed against all assignments in a folder or cover, or all assignments of a specific work type. See How to perform bulk processing for a large number of assignments
• Accessibility — Applications based on the Work or Manager standard composite portals now can use the Accessibility Framework 6.1, to deliver a user experience that reflects the latest accessibility enhancements. See Satisfying accessibility requirements in composite portals
• Search — The standard Manager and User portals include a search facility that allows searching through work objects and also through text attachments to work objects.
• Login and Logout forms — The login/logout screen is redesigned and remains customizable. See How to customize the login screen and How to display a custom favicon for your application.
• Section rules — To facilitate development and encourage use of sections as the primary building block for user experience, you can save any layout in a harness or flow action as a new section. See How to convert flow actions to the 6.1 section reference format