Screens with Group Context

All the table views and many of the form views in the PT application display information about a specific group (that is, they have group context). When a user action causes display of such a screen, the application uses the GroupID of the related group to query for data from the Eval database. If a user navigates to a screen with group context from a screen without group context, the application must first determine the group about which to query. In general, a screen does not have group context if it is applicable on an organization-wide basis. For example, when an administrator adds an individual using the User Information form, the individual is added to the Eval database for the organization, but not to a specific group within that organization.

Note  Groups are not the only entities for which the PT application maintains context. The user's role and identity are also known as the user moves from screen to screen, and are used to determine correct display elements and to permit appropriate navigation choices.

When using the Group form, an administrator acquires a group context by creating a group. After the administrator leaves this form, the PT application attempts to display information about that group in subsequent screens.

To change the group context, a user must return to the home page and choose a different group.

Group Context Examples

The User Information form does not have group context. Using this form, an administrator adds data about a person to the PT application's Eval database. The person need not be associated with a group, so the screen does not have group context.

The Activity form has group context. With this form, an evaluator creates an activity and associates it with a group.

The following table lists which screens have group context and which do not. Because of the Group form's special function, it appears as a screen of both types.