PRS

"The Registry User Organization ID of the data source. If the logged on user is of type Primary Source, this will default to the Registry User ID of the logged on user. If the logged on user is a Registry Administrator, there will be no defaulted Registry User ID. The user can leave this field empty or enter the Registry User ID of any Primary Source. When the Search button is pressed, PRS will return only those DPS's created by the entered Primary Source, or will return all DPS's if no Registry User ID has been entered."

AND

"The Registry User ID field will default to the organization ID of the logged in user. Unless the user is a Registry Administrator (RA), this default ID cannot be changed. If the user is an RA, the default will be a blank field and the field can be typed in. No wild cards are allowed."

The descriptions implied to me that the functionality was based on Registry User Type (its not). After some tests, Kathy and I cannot determine what controls this behaviour, but do know that FN_IS_REGADMIN does not control it, and that both RA and SRA are treated the same. Note that the tests determined that the Functional Role (or attached permissions of the role) determines the behaviour as a RU Org with both an Registry Administrator and Prime Source acts differently depending on the logged in user.

So, the question is, what specifically controls the behaviour as to whether or not the Registry User ID field on the DPS Search screen is editable?

ANSWER: It's controlled by the functional permission MANAGE_PRIMARY_SOURCES