The concept of resources has been expanded through the introduction of new entity called Business
Units. You will find this under the Resource node of the POMS navigation tree.
It allows you to divide your organization into a number of business units (eg, departments)
such that projects managed by each business unit are kept separate from those run by other business units.
Each user may be allocated to a specific business unit, in which case, they will only have access to
projects managed by that business unit. Furthermore, test cases, issues, and risks created for a project,
inherit their business unit from the project, and hence are subdivided accordingly. Under this scheme, you
can still have projects and users that are shared across business units by not allocating them to a business
unit.

You'll notice that most search screens have a Business Unit drop-down list as an extra search parameter.
For normal users, this is disabled and permanently set to the business unit to which they belong.
For users in the SysAdmin security group, this is enabled so that such users can search across
business units. Furthermore, only SysAdmin users can change the business unit of projects, test cases, issues, and risks.

A user in a specific business unit has access to data created for that business unit, plus shared data (ie, data with
no business unit). If you want to view only data relevant to your business unit, you should tick the
Strict Business Units option in the Settings/User Options screen.

Note 1: If your organization does not require this additional level of flexibility, then simply ignore the business
unit facility, and POMS will behave as before.

Note 2: Any data created using version 2.x of POMS, has its business unit set to
blank. If you want to change this, you should login as a SysAdmin user and make the changes.

The user Utilities/User Activity screen has been extended to allow you to search for activities of various users
instead of just the currently logged-in user. The admin user can search for activities of any user. Other users
can search for activities of users in the same BU as themselves.

A new tab has been added to the project search screen, which allows you to search for requirements across projects.
After a search, you can drill-down the search result and view a requirement within its parent project.

A new module has been added to support the creation of project test plans. This module allows
you to create test cases for a project and, for each test case, to record the details of each
test run. Test Management is linked to Issue Management, so that when you record a failed test run,
you can at the same time raise issues. Conversely, you can navigate from an issue to the test case
that caused it to be raised.

A new tab (called User Access) has been added to the General tab of the project screen. It allows you to define
rules for controlling who should have view/update access to a project. Access rules can be specified using
user groups as well as usernames. The admin user is exempted from these rules. For all other users, access
to each project is determined by the intersection of their security groups permissions and the access rules
specified by the project. To allow universal access to a project, leave its rule table blank.

A new option has been added to the User Options screen (under Utilities) so that you can control whether
the application should timeout after being idle for a user-specified period (defaulting to 60 minutes).

Two new fields have been added to projects to record Estimated Effort and Estimated % Complete. Unlike, the
Effort and % Complete fields (which are read-only and automatically calculated by POMS from tasks), these fields
allow the user to enter their own estimates. The latter fields have been renamed Plan Effort and Plan % Complete for clarity.
The news fields have also been added to reports and printed version of project plans.

The screens for Publications and My Documents nodes (under the POMS node in the navigation tree) have been
totally revised to allow users to access and/or update public/private documents. Access to these nodes is
controlled via new entries in the Permissions tab of the Security Group screen. The View permission allows
group members to view documents and to download documents/folders. The Create/Edit permission allows group members to
upload/delete documents/folders, and to create new folders.

Search screens have been enhanced to allow use of wildcards and to search by keywords in an object's description.
Fields that support these features are clearly marked by corresponding red icons. Also, the field tooltip indicates
what type of search is supported.

A new check box, called Archived, has been added to projects, test cases, issues, and risks. By ticking it, you can
indicate that the object should be set aside. Also, a new drop-down, called Stage, has been added to search screens,
which allows you to search for non-archived items (default), archived items, or both.

A new node, called Project Dashboard has been added under the POMS node. It allows you to view summary information
about projects for a given period. Global summary information (across all projects) is displayed graphically.
Specific summary information for a project is displayed as traffic lights across a range of measures, the rules for
which are user-customizable.

The Project Dashboard Details report is available when viewing the Project Dashboard screen. It produces a
report containing the information in the Global Summary and Specific Summary tabs.

The Users Project Allocation report is available when viewing the Users search screen. It produces a report
which contains the users in the search result and, for each user, a pie chart showing how the user is allocated to various projects.

The Requirements List report is available when viewing the Project Management search screen. It produces a
report which contains all requirements for all projects in the search results.

For SysAdmin users, BU and Project drop-down lists in (test case, issue, and risk) search screens act independent of each other.
Selecting a project from the drop-down list should automatically set the BU according to the project definition
(fixed in Build 323).

For SysAdmin users, the Project drop-down list in (test case, issue, and risk) details screens should show all
projects, and set the BU field according to the selected project (fixed in Build 325).

In the Project Resource tab, data in the Tasks and Graph sub-tabs remain even when you switch to another project
(fixed in Build 327).

Requirements List report is tied to project search result, not the requirements search result (fixed in Build 330).

After submitting timesheets and doing project review, automatic resource cost calculations are incorrect in the
Income/Expense tab, and do not immediately appear in the budget spreadsheet (fixed in Build 332).