Field length mismatch between OWB and Clarity

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Field length mismatch detected between Workbench and Clarity during save event from Workbench

This is being observed for the fields Project Name, Task / Phase / Milestone Name. On Clarity, the field lengths are as follows:

Attribute	Clarity
Project Name	256 characters
Task / Phase / Milestone Name	256 characters

 

 

If a project having the above field lengths of 80 + characters, is launched into Workbench. Workbench launches the project with field lengths similar and matching with Clarity. If these fields are further edited in Workbench, then Workbench does not allow for changes and displays field length errors. However, acknowledging the errors, reverts the text on the field to the same position, as it was when the project was launched from Clarity.

STEPS TO REPRODUCE:

1. Access Clarity and create a project with a project name, having more than 80+ characters. Also having a Task, with a Task name having 150 + characters
2. Launch this project onto the Workbench. The project gets launched into Workbench with the fields: Project Name and Task Name matching with that of the fields on Clarity
3. Edit the Project Name and the Task Name, by reducing a few characters from it, respectively

Expected Results :The Project Name and Task Name should be saved

Actual Results : Error: xxxx exceeds the maximum allowable length of 80 characters / xxxx exceeds the maximum allowable length of 150 characters

Workbench does not allow editing and displays field length errors, 80 characters for Project Name and 150 characters for Task Name respectively. The field level mismatch check does not get triggered during the launch of projects in Workbench, however only during the Save event, that too, if the Project Name / Task Name is altered, by reducing the field length. 

 

Cause

This is caused by DE78977

Resolution

This is fixed in 16.2.1