Abstract: An adaptable user interface is formed based on a role assumed by a user and the identification of tasks in a process that need to be performed. For each role assumed by the user, a set of tasks assigned to the role is identified. Each task is evaluated to determine if it is an active task that needs to be performed in one or more processes. For each active task, an element is added to the user interface.

Abstract: An application bar is displayed along with a form. The application bar includes a set of controls for performing actions. At least one of the controls has an associated flyout menu. When the user actuates the control, the flyout menu displays groups of flyout controls, without obscuring the display of the controls on the application bar.

Abstract: Date entries may be made using aliases in place of a specific dates. Instead of a user having to locate or determine a specific date for a date entry field, the alias that represents the date may be entered in the date entry field. The date for the alias is determined from a context of the date entry. For example, the context may include a determination as to what application is requesting the date, what entity is associated with the date entry, and the like. In a payroll date example, a next pay date “NPD” alias may change based on the employee. The data used to determine the date that is represented by the alias may be one or more data sets. The aliases may be associated with more than one application.

Abstract: An adaptable user interface is formed based on a role assumed by a user and the identification of tasks in a process that need to be performed. For each role assumed by the user, a set of tasks assigned to the role is identified. Each task is evaluated to determine if it is an active task that needs to be performed in one or more processes. For each active task, an element is added to the user interface.

Abstract: An adaptable user interface is formed based on a role assumed by a user and the identification of tasks in a process that need to be performed. For each role assumed by the user, a set of tasks assigned to the role is identified. Each task is evaluated to determine if it is an active task that needs to be performed in one or more processes. For each active task, an element is added to the user interface.

Abstract: An adaptable user interface is formed based on a role assumed by a user and the identification of tasks in a process that need to be performed. For each role assumed by the user, a set of tasks assigned to the role is identified. Each task is evaluated to determine if it is an active task that needs to be performed in one or more processes. For each active task, an element is added to the user interface.