Problem with lookup: RIM_BROWSE_USER

[Legacy User]

Many versions ago (before 12.1), we identified a problem with this lookup:

 

               SELECT @SELECT:USERS.ID:ID@,

                @SELECT:USERS.USER_NAME:UNIQUE_CODE@,

                @SELECT:RESOURCES.LAST_NAME:LAST_NAME@,

                @SELECT:RESOURCES.FIRST_NAME:FIRST_NAME@,

                @SELECT:RESOURCES.FULL_NAME:FULL_NAME@,

                @SELECT:RESOURCES.UNIQUE_NAME:UNIQUE_NAME@

                FROM SRM_RESOURCES RESOURCES, CMN_SEC_USERS USERS WHERE USERS.ID = RESOURCES.USER_ID AND

                @WHERE:SECURITY:RESOURCE:RESOURCES.ID@               AND

                @FILTER@             

                 AND RESOURCES.PERSON_TYPE != 0

                AND (@WHERE:PARAM:USER_DEF:INTEGER:IS_ACTIVE@ IS NULL or @WHERE:PARAM:USER_DEF:INTEGER:IS_ACTIVE@ = RESOURCES.IS_ACTIVE)

 

The problem:  This query requires users to have Resource-View All rights.  When assigning a resource to a risk or issue, a typical user does not need Resource-View All rights.

 

We opened a case on this so long ago, that it no longer shows up in the support case list for our company.  We developed a workaround - custom field, with a custom lookup (below) and a process to copy the picked value from our custom field to the out of the box (OTB) field.  This has been working well for years, but we had to turn off the issue/risk notifications - users get notified by the copy process, instead (back then, the risk/issue notifications could not be modified, did not contain much helpful info, and users did not want it along with the more informative Action Item email we were able to send to them).  Works fine, but the Notifications portlet doesn't show Issues and Risks correctly.

 

SELECT

@SELECT:SRM.USER_ID:USER_ID@,

@SELECT:SRM.UNIQUE_NAME:RESOURCE_ID@,

@SELECT:SRM.LAST_NAME:LAST_NAME@,

@SELECT:SRM.FIRST_NAME:FIRST_NAME@,

@SELECT:SRM.FULL_NAME:FULL_NAME@,

@SELECT:CMN.USER_NAME:USER_NAME@         

FROM

SRM_RESOURCES SRM,

CMN_SEC_USERS CMN

WHERE

SRM.PERSON_TYPE != 0                            

AND srm.last_name not like 'Admin%'

AND SRM.USER_ID=CMN.ID

@BROWSE-ONLY:

AND SRM.IS_ACTIVE = 1

:BROWSE-ONLY@

AND @FILTER@

 

We are on v.13.1.

 

Question:  Has this issue been addressed in newer versions of Clarity, sorry, CA PPM?

 

Addressed could mean that the OTB query has been fixed or that customers now have access to modify and save the query via the UI.  Already understand that risk/issue notifications can now be easily edited via the UI, allowing them to be packed with much more useful info than in years past.

 

Goal:  We want to get back to OTB configuration for 'assigned to' fields, removing our workaround, with a solution that does not require Resource - View All rights give to all users.

 

Thanks,

 

Dale

[Jeanne Gaskill]

Hi Dale,

 

I searched cases and bugs and could not find any issues for your company that mentioned this look-up.

 

Can you give me an STR that would demonstrate whether the problem is still occurring or not?

 

Sincerely yours,

 

Jeanne Gaskill

Senior Support Engineer - Clarity

CA Technologies

[Legacy User]

Hi Jeanne,

 

This was a very old case, so not surprised.

 

What is an 'STR'?  Sorry, I don't know that abbreviation.  However, the query in the original email still shows the security clause, so yes, the problem is still present in 13.1.

 

I've had some other ideas in, related to letting customers modify the queries for lookups, as we have problems elsewhere, such as users being able to assign inactive departments to current projects and resources.

 

Good to hear from you,

 

Dale

[Jeanne Gaskill]

Hi Dale,

 

It is good to hear from you too.

 

STR = Steps To Replicate

 

Since the problem is still occurring in a current version of Clarity, we can open a new potential bug with development as long as I can replicate the problem here on a vanilla system.

 

Please open a new case for this.

 

Jeanne

[Legacy User]

Case created:  21990434-1: ASSIGNED OWNER LOOKUP

 

STR:

- make sure resource does not have Global right to Resource-View All

- have resource create/edit issue, opening Owner (assigned to) browse to select a resource (or, try typing name in using look ahead)

- expect to see name(s)

- actually see nothing

- give user Global Resource-View All right

- repeat steps

- expect to see names and does see names

 

The security feature isn't necessarily bad - might be nice to have list limited by one's OBS or Global Rights.  However, most users don't need to see resource data or screens - they just need to pick a name.  And, there are other ways into a resource's records than by just the Resources navigation link (e.g. the 'Allocations' image/link on Team/Staff page).

 

Makes sense?

 

Dale

[Jeanne Gaskill]

Hi Dale,

 

After doing some more research, I was able to determine that this lookup is performing as designed.  The security is built into the lookup by design.

 

So, this is an enhancement request.  Please create an idea for this.

 

Thanks,

 

Jeanne

[Legacy User]

Thanks Jeanne - as this is not changed in later versions, will create an idea.