Posted: 12 May 2016 17:36 EDT Last activity: 24 May 2016 17:28 EDT
Is there a defect for applying a disable privilege to a link control in PRPC 7.1.9?
After applying a privilege to a link control to disable it for certain users, the link is disabled at all times, regardless of whether the user holds the privilege or not. After looking in the product help, there is no mention of this field. Is this a product defect? There is a workaround to use the function to check for a privilege in a when rule, in the disable field, however.
We are using PRPC 7.1.9.
This is all there is for General Properties in Help:
3. Complete the Cell Properties panel— General tab
Complete the General tab.
Optional. Select to determine when the link appears.
Choose Always to have the link appear or be hidden based on the visibility of the enclosing section or flow action when the form is first presented or is refreshed. This condition is checked only once.
Choose Other Condition to make the visibility depend on a when condition rule or a Java expression..
If you selected Other Condition for the Visible field, complete this field.
The When Name key part of a when condition rule. Click() to review or create the rule.
Simple expression based on the comparison of a pair of constants, properties, or both, combined by Boolean operators, such as .Color="Red". You can combine the expression with a when condition rule or another expression using the && and || operators.
An link that is not visible is also disabled and cannot be clicked.
Run on Client?
Appears when you enter a simple expression in the Condition field. Select to cause evaluation and execution of the condition each time the value of a property stated in the condition changes. If unselected, the expression is evaluated and the condition executed when the form is initially presented and whenever the form is refreshed.
Thanks for sharing the SR with us here Andrew Pruss! I have updated the thread. I've also removed the Correct Answer from Susan's reply. When you have your resolution please share in a new reply and mark that as the Correct Answer.
The issue with this was the class of the privilege. Once the privilege was savedto the same class as the primary page, instead of baseclass, the section behaved as expected. I believe my coworker said this is because class inheritance does not occur in this instance.