TASK LIST module: using FLS on some task fields - known issues

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

 

Field-Level Security is enabled on the Task Object in Release 16.0.1. This article provides a list of issues on the TASK LIST Module when securing Stock Task Object fields.

These known issues apply to the 2-level 'TASK LIST' Module. (This module is highlighted in red below)

This does not apply to the 'TASKS' Module with the generic grid

NOTE: If the Administrator makes any Label Changes through the Modern UX, Administration, Attributes grid for the Task Object, there will be NO impact to the labels on the 'TASK LIST' Module. 

Environment

Release: 16.0.1 and higher

Module: Task List

Cause

DE63148

Resolution

Note: Sustaining Engineering has determined that we will not fix these issues. You should instead use the Task module. 

If you still use this module and secure some of the Task Fields you will encounter the issues described below. 

This TASK LIST Module uses the following fields:

• The following fields are blacklisted and therefore, you won't have the ability to 'secure' these fields:
  • (task) Name 
  • (task) ID 
  • Start 
  • Finish 
  • Milestone 
  • Duration 
  • Is Task  
  • WBS Sort 
• The following 8 fields are used on this page and can be secured through the FLS Attributes grid: 
  • % Complete  
  • Task Owner  
  • Status 
  • ETC 
  • Actuals 
  • Total Effort 
  • Investment ID  
  • Phase Task ID 

Table of Contents

• Issues with securing Task Object fields on the TASK LIST Module:
  • Task Owner
  • Status
  • Estimate to Complete
  • Percent Complete
  • Effort Gauge 
  • TASK LIST Module Filter Section
  • Could not load tasks' Toast message
• Securing 'To Do' Object Fields

 

Issues with securing Task Object fields on the TASK LIST Module:

As referenced above, these issues were reviewed as DE63148 and it was determined these issues would not be fixed. You can instead use the Task Module. 

Task Owner

When a field is secured, below is what happens on the TASK LIST Module even if the field is secured without view or edit access (checkbox for 'Secure' is checked).

• Although the field may be secured, the Owner field is visible in the Details fly-out 
• You can try to select a value, but will get the following toast message:
  API-1007 : You are not authorized to process request. Contact your system administrator for necessary security rights. 

Status

• Although the field may be secured, the 'Status' field is visible in the list as a circle - with a checkmark if status = completed 
• The Status field is visible in the Details fly-out  
• You can try to select a value to mark the status 'Open' or 'Completed', either from the circle in the list or from the Details fly-out, but will get the following toast message:  
  API-1007 : You are not authorized to process request. Contact your system administrator for necessary security rights. 

Estimate to Complete

• Although the field may be secured, the 'ETC' field is visible in the Details fly-out 
• The field is always read-only regardless of the secured setting 
• The field always shows in the Details fly-out even if it is marked secured 

Percent Complete

• Although the field may be secured, the '% Complete' field is visible in the Details fly-out 
• The field is always read-only regardless of the secured setting 
• The field always shows in the Details fly-out even if it is marked secured  

Effort Gauge 

• When securing the read-only 'Total Effort' or 'Actuals' fields, the Effort gauge is still visible in the Details fly-out and on the list row for phases with the data for the total effort 
• The field always shows in the Details fly-out even if it is marked secured 

TASK LIST Module Filter Section

• Although the 'Task Owner' or 'Status' or 'Phase Name' fields may be secured, you can still select these fields for filtering 
• Task 'Type' is a private filter that combines the 'Is Task' and 'Milestone' fields. The filtering will still operate on this page for 'Type'. You cannot secure these fields  
• 'Team Member' is a private filter that represents 'Assigned Resources'. This is a private filter and cannot be secured.  The filtering for this field will still operate on this page 
• 'Finish' date cannot be secured.  This filter will still operate 

Could not load tasks' Toast message

The following issues occur when reloading a Task record

Editing non-secured fields

• • If you have a combination of the 8 fields secured or not secured, after making an edit on a non-secured field, if there are any other of the 8 fields secured, you will get the 'Could not load tasks' message when the record is retrieved after the save 
  • The edit is saved for the one field updated 
  • Workaround: Reload the page 

More than 1 level Hierarchy

The Task List Module only supports 1 level hierarchy.  If you have more than 2 levels, the remaining levels are flattened in the list.  With this use case, after collapsing the top-level Phase, the user won't be able to 'expand' the list of sub-tasks if at least 1 of the 8 fields listed above are secured  

• • Click 'collapse' on a Phase that has more than 1 level below 
  • Click 'expand' on the same Phase (when the 'expand' call is made, it explicitly looks for these 8 fields) 
  • You will experience the toast message: 'Could not load tasks'  
  • Workaround: Reload the page and all top-level phases will load in the default 'expanded' mode 

NEW TASK

• • If any of the 8 fields are secured, after creating a new Task on this page, the user will see the toast message: 'Could not load tasks' 
  • The new task is successfully created, but the user will see this message 
  • Workaround: Reload the page 

Securing 'To Do' Object Fields

• Securing fields on the To Dos object are not supported for the Task List Module. 
• The user may encounter a Toast message from the Details fly-out, To Dos subtab if any fields are secured on the To Dos object. 
• For example, if the 'owner' field is secured, the user will see a Toast message:
  API-1005 : Attribute(s) 'owner' specified in query parameters are not supported or secured.