Clarity

Hi,

I just upgraded to 15.3. I was checking the project details page in new UX and i see that many of existing static dependent lookup and parameter lookup are not giving any value in the project field.

Please let me know is there anything needs to be done to enable them? 

Thanks,

Shiva

You need to have additional right. see the change impact guide 

Release 15.3 Updates (On Premise) - CA PPM - 15.3 - CA Technologies Documentation 

Regards

Suman Pramanik 

Hi Suman,

Checked change impact guide and added the Project Management - Navigate rights but no help. Still the lookup fields not showing any data.

Thanks,

Shiva

Quick one - Are you able to see the values in the classic UI?

NJ

Hi NJ,

Yes, values are showing in Classic UI.

Thanks,

Shiva

Can you please prove the access rights for this user who you are facing this issue.

Regards

Suman Pramanik 

Hi Suman,

I am having admin access. Also provided right externally. Project Management - Navigate is the right mentioned in the impact guide.

Thanks,

Shiva

Can you please share the screen shot of NEW UX where the values are not populated and if those are custom attributes or stock attributes. 

Hi Suman,

These are custom attributes. please see below screenshot of attribute from both new UX and Classic UI.

Thanks,

Shiva

Let me test this and come back to you. 

The attribute is based on static dependent lookup.

We tested the same and we could reproduce. I am checking further and will come back to you 

Hi Shiva,

I looked into the response code and it looks to be a bug. Please raise a case and we can take it via assisted case.

Regards
Suman Pramanik 

Hi Shiva,

We looked further and at this point its a limitation. I missed to check the documentation too

New User Experience: Compare with Classic CA PPM - CA PPM - 15.3 - CA Technologies Documentation 

Regards
Suman Pramanik 

Hi Suman,

Thanks for the clarification. But in our application, couple of custom attributes with static lookup showing the values in new UX. I have attached the screenshot of one the attribute.

Thanks,

Shiva

Hi Shiva,

Yes static lists are coming for us also and I do see a response code correctly, I guess we need to correct on the documentation. 

Thank you for letting us know.

Regards

Suman Pramanik 

Hi Suman,

Not all static lookups are showing values in our new UX. In future does parameter lookup will include in to new UX?

Regards

Shiva

Hi Siva,

There are gradual improvements made in the UX, stay tuned we will continue adding more.

Regards

Suman Pramanik 

Hi Shiva,

I cross checked and static look ups are supported. If you have static lookups and its not showing the value. Please update us on the case which you have and we should be able to figure out. 

Regards

Suman Pramanik 

Hi Shiva,

I verified the same and Static dependent lookups are NOT supported. Static lookups ARE supported.

Regards
Suman Pramanik 

Hi Suman,

Yes, Static lookups are working when the values are created under system partition as partition is not there in new UX. 

Thanks,

Shiva

Will the unsupported lookups be addressed in a patch, soon?  We use these today on most of our projects and we are excited to push for 15.3 before end of year - this could be a showstopper.  Also, the 'view level settings' - may not be a show stopper for these, but lacking 'required' capability will impact our data quality - something that some fight dearly for, preferring data quality over all the other benefits of the new UX (and, they have a valid point).

For anyone facing this as a "show-stopper" get in touch and I'll show you how to build a dirty workaround till it's added

Thanks, Andrew.  Will get 15.3 running on our data, have discussion.  Hope patch will be available before we need it, will contact you if it’s not.

Dale

The limitation mentioned in my earlier comments are designed to work that way at this moment and its not a bug

do these attributes have a valid api key?

Hi Andrew,

yes, it has the api key. please see below image.

Thanks,

Shiva

I am late to the thread, but agree, this can be  showstopper. It may be functioning as designed for this release, but the question was not answered; is this targeted for a patch or is this not until March 2018 release? This will impact people's decisions when to adopt the new UX. 

Design changes doesn't happen in patch and goes into new releases. 

Regards

Suman Pramanik 

Thank you. That, then , becomes a show stopper to implement the new UX, along with the inability to make a field required.  I will provide that feedback to product management.