Incorrect Staffing Module is being referred to when Staffing Workspace is being accessed and the module has been removed from Staffing Blueprint
search cancel

Incorrect Staffing Module is being referred to when Staffing Workspace is being accessed and the module has been removed from Staffing Blueprint

book

Article ID: 382317

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

When Staffing Workspace is being accessed for a particular module, following which if this module is removed from the Staffing Blueprint, when the Staffing Workspace is navigated back to, it still refers to the previously accessed Staffing module, which has been removed from the Blueprint.

 

STEPS TO REPRODUCE:

1 log into the Modern UX and navigate to the Staffing Workspace

2 Navigate to any Staffing Module, for example: Allocation by Investment tab and log out of the application

3 Make changes to the Staffing blueprint and remove all modules with the exception of Staff. Publish and make this Blueprint as default

4 Log back onto the Modern UX and navigate to the Staffing Workspace

 

Expected Results :-

When the Staffing Workspace is accessed it should navigate to the module which is presently available as per the Staffing Blueprint

Actual Results :-

The application still navigates to the initial Staffing module, that was accessed earlier and which has been removed from the Blueprint

 

Workaround :-

Post navigating back to the Staffing Workspace, click once on the available Module as per the Blueprint

Environment

Clarity version 16.2.1, 16.2.2 and 16.2.3

Resolution

This behaviour is no longer being observed and is not occurring on Clarity version 16.3.0