Clarity: OBS Resource Aggregation Portlet always includes inactive resources in the totals even though the active resource field is unavailable for filtering

Document ID : KB000049175
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Because the 'Resource Active' attribute is not available for configuration, the data presented on this portlet is overstated. It is displaying allocations for both active and inactive resources.

Resource Planning > Capacity Tab
Name = OBS Resource Aggregation
ID = projmgr.OBSResourceAggregation
Description = Resource demand aggregated by OBS
System Provider OBS Resource Aggregation

Behavior:
Filter for a Resource OBS Unit.
This portlet will display active investments with allocations for both active and inactive resources.
This portlet does not provide the 'Resource Active' attribute for configuration and filtering.
If you drill into the 'OBS Resources' or 'OBS Roles' portlets, the 'Resource Active' attribute is available for configuration and used in filtering to display both active and inactive resources.

Steps to Reproduce:

  1. Create a project (myProject1).

  2. Allocate staff members to the project.
    'myResource1' and 'myResource2' are both active and belong to the same Resource OBS Unit.

  3. Go to Resource Planning > Workloads tab > Portlet: Resource Workloads.
    Note the amount of allocations. This portlet only displays active resources allocated to active investments.

  4. Go to Resource Planning > Capacity tab > Portlet: OBS Resource Aggregation. Filter for Resource OBS Unit.
    Note the amount of allocations. It should match the Resource Workloads data for now because both resources are active.

  5. Go to Home > Resources. Select one of the resources and set to 'inactive' (myResource2).

  6. Go to Resource Planning > Workloads tab > Portlet: Resource Workloads.
    Note the amount of allocations. This portlet defaults to display active resources allocated to active investments.
    (The 'Resource Active' attribute is available for configuration.) Therefore, only allocations for the active resource (myResource1) appear.

  7. Go to Resource Planning > Capacity tab > Portlet: OBS Resource Aggregation > Filter for Resource OBS Unit.
    Note the amount of allocations; it still includes the allocations for the inactive resource.

  8. Go to [--Actions--] Configure > Filter Layout. Look for 'Active' or 'Resource Active' attribute.

Expected Result: The 'Resource Active' attribute is available for configuration.

Actual Result: The 'Resource Active' attribute is not available for configuration in the OBS Resource Aggregation portlet.

Solution:

This issue is resolved in Clarity 13.1.0

This issue has been fixed by adding a "Active Resources" field to the filter section of 'OBS Resource Aggregation' portlet which is hidden by default (and hence takes a default value of 'Yes'). End users/admins can 'unhide' it if they would like to. The value of it is also passed to the linked "OBS Resources" and '"OBS Roles" portlets to filter on the same status of Resources (i.e. Active or Inactive), and also gives the ability to end users/admins to configure that filter field to view and change its value, if required, to filter on different status of Resources.

Keywords: CLARITYKB, CLRT-67470, clarity13resolved, clarity1310resolved, studio.