IBM Support

Different users see different percentage of resource allocation in the plan view

Troubleshooting


Problem

In IBM Engineering Workflow Management's Formal Project Management process project area, different users can see different percentage of resource allocation in the plan view.

Symptom

You can set up an example to demonstrate the symptom.

UserOf2Projects(userof2/userof2) is a member of 2 project areas (CSM-FORMAL1-702, CSM-FORMAL1-TAP702-1). There is no change to the default allocations, so the resource is 50% allocated to each project.

UserOf1Project(UserOf1/UserOf1 is a member of 1 project area (CSM-FORMAL1-702). There is no change to the default allocations, so the resource is 100% allocated to the project.

The default Access Control for formal project areas is "Grant read access to Members of the project area hierarchy". This means that UserOf1Project does not know about the existence of CSM-FORMAL1-TAP702-1, which means that they think that userof2 is only allocated to a single project. And since the allocation has not been manually set, UserOf1 thinks that userof2's allocation is 100%. As is seen here:

Image1

Note: the 'Yellow Triangle Warning Symbol' next to Allocation indicates the allocation is system-calculated, and can change.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSUC3U","label":"IBM Engineering Workflow Management"},"ARM Category":[{"code":"a8m50000000CjivAAC","label":"Workflow Management-\u003EPlanning-\u003EFormal-\u003EResource Management"}],"ARM Case Number":"TS010117901","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
27 November 2022

UID

ibm16674229