Case View in Production Instance
- Go to Cases -> Create New View
- Name the View “My Community Cases” the Unique name will be My_Community_Cases
- Under Specialty Filter Criteria select the radio button “All Cases”
- If you only want your customers to see cases that are “Open” or Cases that are of a certain status, you can use the “Filter By Additional Fields” to narrow down what the view will output.
- You do have the ability to have multiple case lists in Communities. This would allow you to have “Open Cases” on the Home page, and Closed cases somewhere else. If this is what you want to offer, repeat creating views using the instructions in this section. You can use the “Save As” function to speed up the creation of the views.
- Decide what fields you want your customers to have the ability to view, and the order you want them to see them in. If you are using Napili, the recommended Template for those setting up a service type of community using SFDC templates, the Case list is not very wide. There might be coding you can do to make more columns visible. We will not get into that with this documentation. So choose the columns visible to your customers sparingly.
- Under Step.4 in the view set up screen, select the radio button “Visible to certain groups of users”
- Search “Public Groups”
- From the drop down pull over (Add) “All Customer Portal Users”
- “All Customer Portal Users is added as soon as you become Community Users by SFDC / purchase Community Licenses
- Save the View and take note of the Unique Name, (Item 2 in this section)
Case View in Community Builder
- Go to Community Builder: Setup ->Type “Communities” into the Quick Find box -> Select All Communities
- Select the “Builder” link from the Community you are setting up case visibility
- The Community will open up in Builder mode
- From the left had menu select the page editor (second option)
- If you have not already, drop the Case List Lightning Component into the page you are editing
- When you click on the Case List –or when you first drag and drop it into your page a small “Case List” box appears. The only * (mandatory field) is the Case Filter Name or ID. This will default to “AllOpenCases”, this is where you need to drop in your unique case view name from “Case View Production Instance” section 2.
- Make sure you select “Publish” so that the changes will take affect. The community should also be active.
- Go to Setup-> Type Sharing Settings into the quick find box -> Select the Sharing Settings under “Security Controls”
- You will see the Organization-Wide Defaults.
- If it is not already, change the Default External Access on Accounts to “Private”
- Double check to make sure that the Contact standard object, the Opportunity standard object and the Case standard object are also set to Private (typically this is automatic because they are controlled by the account).
- If you are going to allow your customer users to view any other objects (e.g., work orders, assets, etc) also move those to private in the Default External Access.
- Scroll down to the related list section of this page to Account Sharing Rules.
- Select New
- Use the Account Name to create a name for the Label. E.g., Customer Name Community Visibility
- Select “Based on Criteria”
- Use the Account Name field, equals, and then enter the account name for the criteria
- In Step 4 decide who will get to see these records.
- From the drop down select “Portal Roles and Subordinates”
- The second drop down will show you a role name that coincides with the name of the account where you ‘ve just granted access to a contact.
- In Step 5 decide what visibility / control they will have over Account / Contracts/ Opportunities / Cases. If anything is labeled private, the customer contacts will still not have the ability to see those records. A best practice for most orgs is “Read Only” access to Accounts and Contracts and “Read Only” or “Read/Write” access to Cases.
- Select Save
- Go to the contact that you have set up in your production instance
- Use the Manage External User to log in as the contact you gave access to
- Confirm that the user can only see records from their assigned Account
I am planning to give the Marketing Cloud Email Specialist Certification in a month.Any tips on where to start also Is there a way I can get like a Trial Marketing Cloud Org so that I could practice all the stuff.I also coudnt find a Trail for this.Am I looking in the wrong place??
I blogged about this exam's primary content and my experience a while ago:
I found the email specialist exam to be the easiest among other marketing certs (social and cloud consultant) so it shouldn't take too much time to prepare for it ( ymmv). If you focus on the topics that I listed in my post, you should be able to handle 80-90% of the exam content.
As far as a Trial org goes, you could always log a case with support asking them if it is possible to get one. My company already had one so I never had to arrange for it. To be honest, I never practiced anything hands-on and only went through the exact target documentation in theory. There isn't a trail for Marketing emails specialist content as far as I know.
Do google for other resources and make sure you skim through them before taking the exam. Good luck!
I am planing to give ADM201 Exam within this week.
As preparation alone not sufficient for the exam I need MOCK exam papers for ADM201 which will help me to clear this exam.
If you have MOCK Exam papers for ADM201, please provide me.
Based on your wish You can Create Permission set or profile for Managers to achieve this
If you had Existing Profile for Managers
1.)Remove Delete and Modify all Permission for Opportunity
2.)Create Permission set For Users with Existing Profile.
If you dont have Existing Profile,
Create New Profile for Managers and Give Permission for Opportunity such as Read, Create,Edit,View all.
No need of Permission set.
If you would like to give permission for the Records they own Then create "Roles"
How do I recreate this in Lightning?
Currently, we do not leverage the role hierarchy structure. We use only a few objects and set the OWD for those objects to private. We then use profiles, sharing rules, and public groups to control object and record access. I am trying to determine whether permission sets would allow us to:
a. reduce the number of profiles we use
b. reduce the number of public groups we use
My questions are:
1. Can we use permission sets to restrict access compared to the profile settings, or only open up access from the profile baseline?
2. In this location: Permission sets > Apps > Object Settings > select the object > field permissions, does the edit permission give the permission set assignee permission to edit field values on records she has access to, but does not own? What does this edit permission do, exactly?
3. What is the relationship between public group membership and permission set assignment? It seems to me that both grant individual users (or groups of users) access to data that they could not access based on profile alone. The way they work differently, however, is still vague to me-- even after reading the help materials on SF. What are the benefits of using each?
4. Is it possible to provide access to report and dashboard folders through permission sets? Currently, if a user building a report folder selects "this folder is accessible only by the following users" the options to select from are role, role and subordinates, and public groups. We only use public groups from this drop down list. We would like to use permission sets instead of public groups (or roles) to grant access to report and dashboard folders. Is it possible to add permission sets to that drop down list?
Related to the above question, I tested a work around for granting access to a report folder: Permission sets > System > System Permissions > enabling create and customize reports, run reports, report builder, and manage dashboard permissions. Then, in Permission sets > Apps > Object Settings > (example custom object), I enabled access to the XYZ record type.
I assigned the permission set to a user. I then checked to see if my user with the permission set had access to the XYZ report folder. The user did not have access. I then added my user to the XYZ public group and confirmed that the XYZ public group had access to the XYZ report folder. I tested my user's access to the XYZ report folder, and my user did have access. It seems, therefore, that the only way to grant report/dashboard folder access using permission sets would be to add permission sets to the options in the "this folder is accessible only by the following users" drop down list.
Clarification on any/all of this is much appreciated!
2. The edit permission in this location allows users to edit field values on records they have access to. Record access is determined through sharing settings.
3. The short answer is they give access to different things. As I alluded to in my answer to #2, permissions and sharing settings are two separate areas of security. Permissions determine the kinds of records users can create, read, edit or delete. Sharing settings determine which individual records users can view and edit in each object. So the difference in permission sets and public groups is that permission sets allow you to grant additional permissions to specific users, whereas public groups are used in sharing rules to grant access to specific records.
4. To my knowledge, it is not possible to provide access to report and dashboard folders through permission sets.
I have a custom object on the Account page layout called "Promotions". There is a custom numeric field in that section called "Current # Cases or Coupons" that I want populated or updated to reflect the data when a custom field within the Account object called Monthly Cases is updated IF the Promo Start Date is >= TODAY() and the Promo End Date is <= TODAY().
My Starting object is Customer/Office and it is set to start the process when a record is created or edited. I have not selected the Recursion option.
My Criteria is set to execute when conditions are met. My set conditions are a field [Account].Monthly_Cases__c (which is a custom numeric field). The operator is "Is Changed", Boolean with a True value. Conditions are set to "All of the conditions are met". I have not set the option to execute the actions only when specified changes are made to the record.
The "True" arm of my flow: Record: [Account].Promotions__r (which is a custom object placed on the Account page layout. The field I want updated is in this Promotions section.) The criteria for updating records is that updated records meet all conditions.
I want to filter on two fields in the Promo section: Promo Start Date >= (Formula) TODAY() and Promo End Date <= (Formula) TODAY(). The field to update is a numeric field under Promotions called "Current # Cases or Coupons" with a type of Reference and a value of [Account].Monthly_Cases__c.
No errors, no nothing. It just isn't updating. Any suggestions would be greatly appreciated!!
LEFT( Name , 1)
For variables like "The", you could build in those exceptions: IF(LEFT(Name,3)='The',Left(Name,5),Left(Name,1))
When a product is shipped, we add a date stamp to a standard field.
Now, I need to know how long has been outstanding so I'm creating a formula field and it's not working.
Standard field: Shipped
API Name: Shipped
Field Type: Date
I am creating a new AGE formula field. Here's how my formula is but get an error message>
Shipped - Now()
Error message: Error: Incorrect parameter type for operator '-'. Expected Number, Date, received DateTime