[SalesForce] Visualforce dynamic/conditional page rendering using user Permission Set

Use Case
Creating visualforce page to conditionally render elements from various custom objects based on the user's permission set assignment. Currently, the visualforce page in use uses the rendered condition based on the user profile. The issue is that all users have the same base profile and that we differentiation application access using permission sets.

Here is a screenshot of the page
enter image description here

Here is an example of what I am trying to do via the rendered condition (which would change the grid based on user permission set assignment):

apex:panelGrid columns="2" style="width:100%;" rendered="{!$User.Id == ObjectType.PermissionSetAssignment.Fields.AssigneeId && $ObjectType.PermissionSetAssignment.Fields.PermissionSetId == $ObjectType.PermissionSet.Fields.Id && $ObjectType.PermissionSet.Fields.Name == 'SOX Control Owner Permission Set' }"

c:GenericDataListComponent filter_p="Process_Owner__c='{!$User.Id}'" title="My Processes" objectName_p="SOX_Process__c" fieldSet_p="Dashboard_Regular_Process_FieldSet" pageSize_p="3" sortDirection_p="desc" orderByFieldName_p="LastModifiedDate" urlForNewRecord="{!URLFOR($Action.SOX_Process__c.New,null)}" hideButtons="true" />

c:GenericDataListComponent filter_p="Sub_Process_Owner__c='{!$User.Id}'" title="My Sub Processes" objectName_p="SOX_Sub_Process__c" fieldSet_p="Dashboard_Regular_SubProcess_FieldSet" pageSize_p="3" sortDirection_p="desc" orderByFieldName_p="LastModifiedDate" urlForNewRecord="{!URLFOR($Action.SOX_Sub_Process__c.New,null)}" hideButtons="true" />

/apex:panelGrid>"

Issue

When i access the screen above, it is blank.
The conditions set forth in the Rendered statement do not carry through relationally across objects.

How should this be restructured?
Is there a better way to do this without having to build a control class?

Best Answer

We cannot use the global variable '$ObjectType' to get object's record data. It can be used to get objects and its fields metadata (schema details) only.

Please see http://www.salesforce.com/docs/developer/pages/Content/pages_variables_global_objecttype.htm

We can use global variable '$Setup' to access hierarchical custom settings which can be evaluated in 'rendered' attribute.

Create a hierarchical custom settings (say Permissions__c)
Create a custom field of type Checkbox in this custom setting (say SOX_Control_Owner_Permission_Set__c)
Add the user to this custom setting

Update the rendered attribute as rendered="{!$Setup.Permissions__c.SOX_Control_Owner_Permission_Set__c}"

Please see http://www.salesforce.com/docs/developer/pages/Content/pages_variables_global_setup.htm

Related Solutions

[SalesForce] Conditional Rendering inside Visualforce pages

Update (2017)

The trick below is good for 90% of cases, especially if you need a placeholder to which rerender might eventually have to inject something. But it can cause problems if you render VF as PDF and you're using this conditional rendering to hide table rows; inside <apex:repeat> for example. (Of course best would be to filter the data in a controller but sometimes you need to make-do without involving Apex)

Recently outputPanel started to inject <span> tags, even with layout="none"; and they break the table into separate rows with renderAs="pdf" Knowledge Base link.

So... what's another VF tag that contains rendered attribute but for sure doesn't generate any HTML so tables don't break...

<table>
<thead>
    <tr><th>{!$ObjectType.Opportunity.fields.Name.label}</th></tr>
</thead>
<tbody>
    <apex:repeat value="{!acc.Opportunities}" var="opp">
        <apex:variable var="renderingHack" value="whatever" rendered="{!opp.Probability > 0}">
            <tr><td><apex:outputField value="{!opp.Name}" /></td></tr>
        </apex:variable>
    </apex:repeat>
</tbody>
</table>

Original answer (2014)

<apex:outputPanel layout="block" rendered="{!recordTypeName = 'foobar'}">
    plain html here
</apex:outputPanel>

Will render into a <div>. Experiment with different values for layout param. apex:outputText can be used in similar way but somehow I prefer the panel, feels, cleaner that way.

[SalesForce] Conditional disabled fields in visualforce

It appears that you're trying to get VF to render disabled="true" when the current user doesn't have a profile name of 'Account Manager'...

A little background: {! } is merge syntax, where the VF engine will evaluate the statements within the brackets during it's render of the data.

What you're probably seeing in your rendered markup is something along the lines of disabled="System Administrator != 'Account Manager'" and that's because the only part being evaluated by the VF renderer is the profile name, not whether it's equal to 'Account Manager'.

If you change your markup and move the closing bracket to the end of the statement, you'll be in business.

disabled="{!$profile.Name != 'Account Manager'}"

Best Answer

Related Solutions

[SalesForce] Conditional Rendering inside Visualforce pages

[SalesForce] Conditional disabled fields in visualforce

Related Topic