search cancel

XOG allows resource ID with more than 32 characters

book

Article ID: 257880

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

It is possible to XOG in a user with a Resource ID with more than 32 characters, even though this is limited in Clarity to 32 or less.
When this user is read in other areas of the product (e.g.: a Project 'Project Manager', Resource...), then the XOG write operation will fail with an error like:

[Error] :1:1: attribute "managerResourceID" has a bad value: the length of the value is XX, but the required maximum is 32.
    Invalid attribute in input document. Please remove all instances of attribute from document elements and try again.
    [Element : Project, Attribute : managerResourceID ].

[Error] :1:1: attribute "resourceId" has a bad value: the length of the value is XX, but the required maximum is 32.
    Invalid attribute in input document. Please remove all instances of attribute from document elements and try again.
    [Element : Resource, Attribute : resourceId ].

 

Steps to Reproduce:

  1. Create a new user from Administration > Organization and Access > Resources.
  2. In the User Name section, use one with >32 chars (e.g.: [email protected])
  3. In the Resource ID section, *try* to use one with >32 chars. For the previous example, the maximum accepted is '[email protected]', only the first 32 characters are accepted.
  4. Use XOG and the cmn_users_read.xml to read the newly created user.
  5. Edit the received XML to:
    resourceId="[email protected]"
    and XOG it back in.

Expected Results: XOG request fails.

Actual Results: XOG request succeeds. The resource is now showing a Resource ID of more than 32 characters.

 

  1. Use the resource in a Project as a Project Manager.
  2. XOG out the project.
  3. XOG in the project without any changes.

Expected Results: XOG request succeeds.

Actual Results: XOG request fails.
(Steps 6-7-8 would be the same when using rsm_resources_read.xml to read the resource).

 

If after the Resource ID has been set with >32 chars the resource is financially enabled, the Resource ID cannot be changed back to a shorter one.

Environment

Release : 16.1.0

Cause

DE68092

Resolution

This issue is under review.