6

Use the empty string value '':


6

use <aura:if> to render the component based on the input of the text area. Pseudo code. <aura:component> <aura:attribute name="strTest" type="String"/> <aura:if isTrue="{!not(empty(v.strTest))}"> //TRUE - show your component here <aura:set attribute="else"> False </aura:set> </aura:if> </aura:...


6

Take a look at An Introduction to Packaging: Implications of Managed Packages on Source Code If someone installs a managed package, they don't get access to all the source code of that package. For example, if the package installs an Apex class, they will not be able to view the source code of that Apex class. Here is a list of factors that should be ...


5

If the class you're interested in looking for is global, you can save a query by using Type.forName(namespacePrefix, className). In all other cases, you should be able to at least query for the given ApexClass to confirm its presence, but you won't be able to interact with it in any way.


4

It would seem that Custom Report Types drilled down to the Users Role DO NOT respect the sharing rules ADDING records that the role would not normally see with the Hierarchy alone... Idea: https://success.salesforce.com/ideaView?id=08730000000kzURAAY Knowledge Article: https://help.salesforce.com/HTViewSolution?id=000004564 It seems counter intuitive but ...


4

You can conditionally show/hide components on the page by setting the component visibility. Select your component and in the properties panel you have the flexibility to show/hide based on a field in the record or user level attributes. See below for clarity:


3

Case Comments are affected by several settings. For internal users, only the case's sharing is considered. If the user can see the case, they can see all of the case comments, published or not. For portal users, they can only see the case comments if Published is true, and they are either contact on the case or a super-user for the account the case is ...


3

You need a Trigger on ContentDocumentLink: To customize file sharing behavior, define an Apex trigger for the ContentDistribution or ContentDocumentLink objects. The ContentDistribution object represents a file shared externally. A ContentDocumentLink represents a file shared with an internal object, such as a user, group, or record.


3

This is a very broad question you're asking and probably too complex for any of us to give you a single answer. I think you're going to need to go back to the basics as taught in the Force.com Platform Fundamentals to sort out your OWD, FLS, base profiles, Roles, permission sets and Groups along with deciding whether or not Conditional Permissions and/or ...


3

Try to check if Massoni and Mancini have roles and if Massoni is the manager of Mancini in the Role Hierarchy. In that case you cannot avoid that he sees the Mancini's calendar, unless you remove the Role Hierarchy itself.


2

This information is stored in the profile metadata. It will show up in the profile like: <objectPermissions> <allowCreate>true</allowCreate> <allowDelete>true</allowDelete> <allowEdit>true</allowEdit> <allowRead>true</allowRead> <modifyAllRecords>true</...


2

for the fields you are unable to see, go to that field in full copy sandbox/ where it is deployed > check "Set field level security" and make sure to check this for your profile/ profile who is not having access in work bench


2

I see two ways Create a separate page layout for those 3 users and assign it to their profile. => take into account that any user that gets that profile as well will see the visualforce page as well in your VF page, only show stuff for users that are allowed to see it: eg those 3 users. You can define weater or not it is allowed using a hierarchical custom ...


2

Looks like I have found some partial answer under similar posts. First of all, as was mentioned here: https://salesforce.stackexchange.com/a/7552/3716 Users (including users with the “View All Data” permission) can only query files they have access to, including: All Salesforce CRM Content files in libraries they're a member of and in their personal ...


2

This is only possible upon creation. After you create a new tab, the second screen opens. Here you can choose for which profiles the tab is hidden, default off or default on. I don't think there is another way to configure a tab for multiple profiles. Here, there is an idea that is asking what you want: https://success.salesforce.com/ideaview?id=...


2

First problem: this return statement is outside of the if scope braces and this code will always return null. Based on your other code, you intended the return to be inside the braces. if (sizeOfFaultyProduct == 0){ ApexPages.Message noFaultyProduct = new ApexPages.message(ApexPages.Severity.FATAL, 'You have not marked any case products as faulty units! ...


2

@Michele-Kleinhomer - If you are trying to hide the field on the form so that you can use the value of that field in your logic, you can specifying the class attribute and set it to slds-hide. Let me know if this works.


2

From what you referenced: Use this object to create custom report types and view the results of duplicate jobs. I think the above explains why the ParentId isn't available to you in Process Builder. The purpose of the object is for reporting of results, not for manipulating records during processes. Update: I learned the object is "owned" by Data.com ...


2

If you don't mind add to the User object, just create a custom checkbox field on the User called Beta Tester and then you could conditionally show components on the page based on this true/false checkbox.


1

You cannot give access to Lightning Bundle from profile. But you can do is rerender based on the logged in user profile.


1

Thanks to Rajesh who pointed out that it could be due to other permission sets. I checked and indeed there was a permission set assigned to the sales user, that also granted access to that members field. Since I wanted all other permissions associated with that set, what I did was to clone that permission set, and then remove the members field from the ...


1

Case Comments are part of the case so the visibility will be based on the Case permissions. The IsPublished field (label as Public) on screen means that community and portal users are not able to view it if the IsPublished is not set. You can remove the Related List from the Case Page layout so if you wanted a specific user profile not to view them then you ...


1

Here is what I understood: You want to restrict FLS on a per-country basis. Not just layout visibility. The problem here is that the platform just flat out does not work like that. If you have read access to a field, then you have the access to that field in all the records you can see. This means that if you give access to the Field x to a guy from ...


1

Only recordtype and FLS will not serve the use case. You have to work with page layout. (Currently I think you have same page layout for different users profiles). Displaying and hiding related list can only be done through page layouts. You need to create separate profile for German User and separate profile for Danish user. Create separate German User ...


1

Use a trigger on attachment to populate a junction object linking the Contact's account and the attachment. Put this related list on the page layout. You'll have two related list: Attachments and "Child Attachments". You could link the account's attachment with the junction object as well and keep only one related list, but then you would have to create a ...


1

To help you remember which controls what, remember: Roles control Records. This depends on Ownership and Role Hierarchy. Setup > Administer > Manage Users > Roles This is just an organisation tree. With respect to record access, you can start with Org Wide Defaults. Setup > Administer > Security Controls > Sharing Settings If you only want John to ...


1

You can use record types for this purpose. Here's what you'll need: Two record types Two page layouts For simplicity, we'll call them the Locked and Unlocked record types and page layouts. In the Unlocked page layout, remove the button, and in the Locked layout, add the button. Also remove the Record Type field from all layouts, or make it read-only so ...


1

I would suggest to go for Role Hierarchy setup rather than thinking around any other dynamic approach. the main reason is if you donot setup parallel hierarchies, then you might end up setting same role for Managers. The real impact here is - Manager A will be able to see all the accounts for Manager B's Sales Men. The reason is the small checkbox that ...


1

I have to be honest I've never done this and can't comment on any unintended side effects (check in a sandbox!) but you can set the sharing setting of the user object to private in the normal manner: Setup > Security Controls > Sharing Settings


1

I'm assuming that you're using the ConnectApiHelper class. It's not officially supported by Salesforce, although it was initially written by me (I'm a Salesforce employee). Currently there isn't an option to control the visibility, but since the source code is available, it's easy to add. Look for the code that creates the ConnectApi.FeedItemInput: ...


Only top voted, non community-wiki answers of a minimum length are eligible