When xogging in Role with Role name that exceeds 32 characters it is throwing an error but UI allows it.

book

Article ID: 38316

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL Clarity PPM On Premise

Issue/Introduction

Issue:

When Xogging in Role with the name exceeding 32 characters you get an error.

Steps to Reproduce:

  1. Login to CA PPM as Admin 
  2. Create Role-Labor and provide role name that exceeds 32 characters in length  
  3. XOG out the role by using roles_read.xml  
  4. Try to XOG that same Role with different ID and observe an error message in the output file  

 <ErrorInformation> 

        <Severity>FATAL</Severity> 

        <Description>This record has not been inserted</Description> 

        <Exception><![CDATA['Last Name' is too large. Maximum size is 32.]]></Exception> 

 </ErrorInformation>

Expected Result: XOG should allow you to enter a Role name that exceeds 32 characters, as the UI allows it.
Actual Result: XOG does not allow you to enter a role with role name that exceeds 32 characters.


Cause

Caused by CLRT-79787

Environment

Release: ESPCLA99000-14.3-Clarity-Extended Support Plus
Component:

Resolution

This is fixed in 15.2

Additional Information

As per the defect resolution, the following was implemented:


Truncate the last_name/first_name value at 32 characters when adding a role or non-labor resource via XOG or UI. The ui displays the full_name which can accept up to 100 characters and the code was taking this same value and attempting to put it in the last_name/first_name fields. The UI didn't validate so this worked, generally, since the database allows 96 characters (32 * 3 to account for multi-byte charsets). XOG did validate so it failed. Change will allow a long name to be used but truncate the values stored in the (unused) last_name\first_name