Home > Uncategorized > daily 06/18/2016

daily 06/18/2016

    • Define Sharing Rules
    • Use sharing rules to extend access beyond the role hierarchy structure.
    • You can create sharing  rules based on record owner or field values in the record.
    • Each sharing rule has three components:
    • Share which records?
    • Criteria-based sharing rules determine what records to share based on  field values other than ownership.
      • Cool formulas
    • With which users?
    • A public group is an administrator-defined grouping of users that can be used to  simplify the creation of sharing rules. Each
    • roles
    • What kind of access?
    • Sharing rules work best when they’re defined for a particular group of users that you can  determine or predict in advance,
    • Define a Public Group
    • For example, users with the Recruiter profile as well as users in the SW  Dev Manager role both review job applications.
    • You’ll need to create a public group if you ever want to define a sharing rule  that encompasses more than one or two groups or roles, or any individual.
    • The good news is that we can cover these objects in  a single group because the Review object is on the detail side of a master-detail  relationship, so it inherits the sharing settings we apply to the Job Application object.  Sin
    • Define a Sharing Rule
    • Share Records Manually
    • In some  cases, granting access to one record includes access to all its associated  records.
    • For example, if you grant another user access to an account, the  user will automatically have access to all the opportunities and cases  associated with that account.
    • To grant access to a record, you must be one of the following users.
    • It makes more sense for the  person who owns a record to grant access to specific users, when  required.
    • He’ll never coach again at Baylor
       2. There wasn’t cause for termination
       3. Without cause, other universities willing to flirt with Briles
       4. Another university in the state will get Briles soon enough
       5. Kendall is gone at season end if not sooner
    • “The thing about [Tesla’s] Ludicrous mode is that it’s a façade. Two launches saps the whole battery. That won’t be the case with the Mission E. You’ll be able to run it hard, over and over; the battery will not overheat, the power control module will not overheat, and the seats will not suck.”
    • It got lost it the pace of this thread but the rumor is yesterday’s off campus Pepper-Hamilton presentation was to Briles and his attorney and why a settlement was reached last night.
    • Someone on Baylor’s team making tapes of the PH report would be the single stupidest thing anyone has done in this scandal thusfar. I expect them to be leaked by Monday.
    • So, Baylor is going to settle their way to the finish line? And hope it all blows over in 5 years?
    • Glad that Hernandez didn’t settle. She has a case against Baylor, and it needs to see sunlight.
       Being the 6th rape victim of a known serial rapist who is still on the football team should never $#@!ing happen…ever.
       $#@! Baylor.
    • Now that it’s confirmed his daddy won’t be reinstated – would finger-tape give up that fat paycheck Baylor is going to pay him this year?
    • So not only did Briles not fight Baylor in an attempt to clear his name – but now he has agreed to work towards a settlement (as Baylor is attempting to do) in the Title IX lawsuit against him.
       Where is the man who cared so deeply about his reputation and his family name?
    • With the way they have handled this, they have effectively saddled themselves with school is limits and possibly post season bans since they won’t have enough wins to make a bowl.
    • Create a Role Hierarchy
      • This is important and I never figured it out for sugar
    • Explain how a role hierarchy is different from an org chart.
    • Users at any given role level  can view, edit, and report on all data owned by or shared with users below  them in the role hierarchy, unless your organization’s sharing model for an  object specifies otherwise.
    • By default, the  Grant Access Using Hierarchies option is  enabled for all objects, and it can only be changed for custom objects.
    • Deselect Grant Access Using  Hierarchies if you want to prevent users from gaining  automatic access to data owned by or shared with their subordinates in the  hierarchies.
    • Create a Role Hierarchy for a new Team Alignment
    • Control Access to Records
    • List the four different ways to control access to records
      • Describe a use case for each of the four record-level security controls.

      • Explain how the different record
    • The next step is to set permissions for the actual records  themselves.
    • you can allow particular  users to view an object, but then restrict the individual records they’re  allowed to see.
      • Should your users have open access to every record, or just a  subset?

      • If it’s a subset, what rules should determine whether the user  can access them?
    • The permissions on a record are always evaluated according to a  combination of object-, field-, and record-level  permissions.
    • When object- versus record-level permissions conflict, the most  restrictive settings win.
    • Organization-wide defaults
    • Role hierarchies
    • Sharing rules—enable you
    • You use organization-wide sharing settings to lock down your  data to the most restrictive level, and then use the other record-level  security tools to grant access to selected users, as required.
    • we’ll cover  details of the various record-level security controls
    • Who is the most restricted user of this object?
    • Based on your answers to these questions, you can set the sharing model for that object to  one of these settings.
    • Controlled by Parent



      A user can perform an action (such as view, edit, or delete) on a contact based on  whether he or she can perform that same action on the record associated

    • However, sharing rules can  only be used to grant additional access—they cannot be used to restrict access
    • By repeating  the same exercise with the other recruiting objects, you can easily figure out the appropriate  organization-wide default settings for them. Th
    • Consequently, the sharing  model for the Candidate, Job Application, and Review objects should all be set to  Private .
    • By default, Salesforce uses hierarchies, like a role hierarchy, to automatically grant  access of records to users above the record owner in the hierarchy.
    • those  above them in the role hierarchy. Use the Grant Access Using  Hierarchies checkbox to disable access to records to users above the record  owner in the hierarchy for custom objects. If y
    • You’ve been asked to create a custom object for tracking projects
    • Create the Project custom object and then create an organization-wide default for the Project object to accommodate for this use case.
    • Apex managed sharing allows developers to programmatically share records associated with  custom objects.
    • Control Access to Fields 

    • Describe a typical use case for limiting access to specific fields.
    • View and edit field-level security settings.
    • page layouts, which only control the visibility of fields on detail and  edit pages, field-level security controls the visibility of fields in any  part of the app,
    • related lists, list views, reports, and search  results.
      • You can define field-level permissions in one  of two ways:


        • For multiple fields on a single permission set or profile

        • For a single field on all profiles
    • For the final piece of the puzzle, specify the  individual records to which each user needs access. By combining security  controls at all three levels
    • Modify access to objects using profiles.
    • Create new permission sets.
    • Tip


      The key difference between the two is that users can have  only one profile but they can have many permission sets.

    • Profiles determine the objects a user can access and the  permissions a user has on any object record (Create, Read,  Edit, and Delete).
      • Crud profiles
    • Permission sets grant additional permissions and access  settings to users.
    • Position—Ben should be able to  post new positions, as well as update and view all  fields for positions for which he’s the hiring  manager, but he should only be able to view other  managers’ positions.
    • this field should be  restricted from his view.
    • so we’ll have to find a way of preventing Ben from  updating the lookup fields on job  applications.
    • Ben
      • RW on the review object
    • In addition, we need to make sure a recruiter will never  accidentally delete a record with information about  a candidate. That’s because state and federal laws  require recruitment-related records be saved for a  number of years so that if a hiring decision is  questioned, it can be defended in court.
    • Also, she  shouldn’t be able to view the minimum and maximum  salary values for any of the positions or the social  security number of any candidate, as that’s  sensitive information that has nothing to do with  her job
    • In the rest of this module, you’ll learn how you can use the platform to  implement these rules in the Recruiting app. As you’ll see, this  will require configuring security controls at all three levels:  objects, fields and records.
    • You can never edit the object permissions on a standard profile.
    • n the  Recruiting app, you might create three new profiles, one each for  recruiters, interviewers, and hiring managers. Each profile can then be  configured to provide the specific type of data access required for a  particular role.
    • enable the enhanced profile user interface, from Setup, enter  User Interface in the Quick  Find box, then select User  Interface, then select Enable  Enhanced Profile User Interface and click  Save. Your org can only use one  profile user interface at a time.
    • The easiest way to create a profile is to clone an existing profile  that’s similar to the one you want to create, and then modify it.
    • If it’s not assigned to any users, remove the permission  set by clicking Delete
    • Create an Account Reviewer profile
    • review existing accounts and report on them, b
    • Account object.
    • Any user assigned to the ‘Account Reviewer’ profile should only have read access to the Account object (and no access to any other object in the Org).
      • OrgObjectFieldRecord
    • The Force.com platform provides a flexible, layered sharing model that  makes it easy to assign different data sets to different sets of users. This  ensures you can balance security and convenience, minimizing the risk of  stolen or misused data while making sure all users can easily access the  data they need.
    • Although you can configure the security and sharing model entirely using the  user interface, it is implemented at the API level. That means any  permissions you specify for objects, records, and fields apply even if you  query or update the data via API calls. This ensures the security of your  data is protected, regardless of how it is accessed.
    • Record Modification Fields


      All objects include fields to store the name of the user who  created the record and who last modified the record. This  provides some basic auditing information.
    • Schema Builder provides a dynamic environment for viewing and modifying all the objects and  relationships in your app. This greatly simplifies the task of designing, implementing, and  modifying your data model, or schema.
      • Schema Builder is enabled by default and lets you add the following to your schema:


        • Custom objects

        • Lookup relationships

        • Master-detail relationships

        • All custom fields except: Geolocation
    • Objects created outside of Schema Builder, such as through an app or  the API, don’t automatically  display on the canvas. Select the checkbox for the object created outside Schema Builder to  display it on the canvas.
    • The Force.com database differs from relational databases in the way that record  relationships are implemented. Instead of defining relationships through  primary keys and foreign keys, the database uses relationship fields. A  relationship field is a custom field on an object record that contains a  link to another record.
    • in  terms of relational data, a relationship is a two-way association between  two objects. Without relationships, you could build out as many custom  objects as you can think of, but they’d have no way of linking to one  another.
    • With relationships, you can display data about other related object records on a  particular record’s detail page.
    • A relationship field stores the ID of the  parent record in a relationship, as well as optionally providing user  interface representations in both the parent and child records.
    • If you define a relationship  between the Position and Job Application objects,
    • ach position record can  have a related list of all the job applications for candidates who have  applied for the position. Then a job application record can have a link to  each position for which that candidate is applying.
    • Types of Object Relationships 



      There are two main types of relationship fields.

    • Lookup
    • The relationship  field allows you to navigate from records in one object to the related records in another  object (both visually and programmatically). L
    • create  one-to-one and one-to-many relationships
    • You can also put multiple lookup relationship fields on a single object,  which means that the Job Application object can also point to a Candidate object.
    • This type of relationship closely links  objects together such that the master record controls certain behaviors of the detail and  subdetail record
    • when you delete the master record, all of  its detail records are automatically deleted along with it. Master-detail relationship  fields are always required on detail records.
    • If you delete a job application record, you  will probably want all of its review records deleted as well. In this case, you would  create a master-detail relationship on the Review custom object with the Job Application  object as the master object.
    • The master object in a master-detail relationship can also contain rollup summary  fields.
    • Master-detail relationships are automatically included in report record types.
    • Lookup relationships are appropriate when a relationship between two objects is required in  some cases, but not always. Typical scenarios for lookup relationships are:
    • To relate multiple parent records to the child record.
    • To link two objects together when you don’t want the behavior of the master-detail  relationship, such as sharing rules, profile permissions and cascade delete.
    • If the detail object has its own tab, then you probably want to use a lookup, and not  a master-detail, relationship.
    • You can convert a master-detail relationship to a lookup relationship as long as no roll-up  summary fields exist on the master object. You can convert a lookup relationship to a  master-detail relationship, but only if the lookup field in all records contains a  value.
    • Enter a label, plural label, object name, and description.
    • User is a standard object that comes with all  organizations on the platform. It contains information about everyone who uses the app in  your organization.
    • You can also create a hierarchical relationship between  objects. A hierarchical lookup relationship is available only for the user object. It lets you  use a lookup field to associate one user with another who’s not automatically linked to the  first user. For example, create a custom hierarchical relationship field to store each user’s  direct manager.
    • To enable our users to do these tasks, we’ll create a custom Review  object and relate it to the Job Application object.
    • context
    • This sharing setting prevents people from creating, editing, or deleting a review unless they can also create, edit, or delete the associated job application. We’ll learn about sharing and security in the next chapter.
    • Create a Many-to-Many Relationship
    • You can use master-detail relationships to model many-to-many  relationships between any two objects
      • One position could be posted on many employment websites.

      • One employment website could list many positions.
    • Instead of creating a relationship  field on the Position object that directly links to the Website object, we can link them using  a junction object.
    • A junction object is a custom object with two master-detail relationships,  and is the key to making a many-to-many relationship
    • o create a many-to-many relationship,  you first create the junction object, then create the two master-detail relationships for  it.
    • Every time a position is posted, a job posting record tracks the post.
      • I need a record for each application i send in
    • As you can see in the following diagram, one position can be posted many times, and both  positions can be posted to the same employment website.
    • So, to define a many-to-many relationship between the Position and Employment Website  objects, you’d create a Job Posting object with the following fields:
    • Position
    • Website
    • A Job Posting  record represents a posting about a single position on a single employment website
    • This will require a many-to-many relationship between the campsite, the users and the reservations.
    • Create an object with ‘Campsite’ as the Label and Object Name.
    • he Name field for Campsite must be a Text type (not Auto Number).
    • custom field to Campsite with the type ‘Text Area (Long)’ with the field name and label of ‘Description’.
    • Create an object with the Label ‘Campsite Reservation’ and Object Name of ‘Campsite_Reservation’.
    • Name field
    • custom field
    • custom field
    • For the Related List Label that displays on the page  layout of the master object, don’t accept the default. Change the label to the  name of the other master object in your many-to-many relationship. For  example, change it to Websites so users see a Websites  related list on the Position detail page.
    • custom field
    • custom field
    • A lookup relationship field is optional but you have the option to make it required. When a  lookup field is optional, you can specify one of three actions to take place on dependent  lookup fields when someone deletes a referenced lookup record.
    • dentify the departments using Salesforce (either now or in  the future). These are your primary stakeholders for AppExchange app  installations.
    • Research AppExchange apps for the  business cases provided by your stakeholders
      • What business problem are you trying to solve?

      • What are your main pain points at present?

      • How many users?

      • What is your budget?

      • What is your timeline?
    • Evaluate your choices. Consider budget, app functionality, and any feature  gaps. Consider inviting your stakeholders into the sandbox or Developer Edition org  to preview the app functionality, or invite your stakeholders to a demo of the app.
    • Execute and document. Prepare your users for the change in user experience  (if any), including providing training or documentation as needed.
    • View Collections, including app collections for Salesforce1, Gamification, Small  Business, and Getting Started (for customers new to Salesforce).
    • 5] View Categories, including Sales, Service, Marketing, Finance, and  Analytics.
    • In general, an AppExchange best  practice is to install first in a sandbox or Developer Edition org. A few  considerations:
      • Some of the packages come bundled with custom fields, objects, Apex  classes, and more.

      • All of these customizations have names, which may conflict with  existing names in your org.
    • rom Setup, enter Installed Packages in the  Quick Find box, then select Installed  Packages.
    • Salesforce Labs apps can be a  great resource as you’re learning how to configure and customize the platform.
    • Apps can either be managed or unmanaged, and your  overall limits are affected in different ways depending on which one you choose. When  you’re installing any app, keep your limits in mind. You can learn more about this topic  by viewing the AppExchange Installation Guide.
    • As a Salesforce admin or  developer, you spend a lot of time using the Setup area in Salesforce. It’s where you  customize and configure your org, support users, build functionality, and more.
    • We won’t dive into the details here. Check out our Trailhead modules with  detailed instructions for how to use specific features in Customize, Create, and  Develop.
      • Company Information




        •   At-a-glance view of your org overall 

        •   Find your org ID
    • View all future jobs, including Apex jobs, dashboard refreshes, and reporting snapshots
    • Trusted Multitenant Cloud: At Salesforce, trust is our #1  priority, which is why our trusted, multitenant cloud is our foundation for  everything we build.
    • The secret sauce of our platform is its  metadata-driven architecture. All customizations in the Salesforce schema, including  code, configuration, apps, and more, are specified as metadata.
    • In our architecture,  we keep your metadata layer separate from our services layer, which allows us to  give you seamless, easy upgrades.
    • API: Finally, we wrap it  all up with a powerful suite of APIs, which allow you to  develop and customize, and also give us the power to create things like the Salesforce1 Mobile App (more on  this later).
    • data access and sharing model.
    • So what’s  the advantage of a multitenant cloud? It means all of our customers, from small  businesses to enterprise companies, are on the same code-base and all get the  benefits of the same features, functionality, and automatic upgrades 3 times a  year.
    • Traditionally, if you wanted to build an app, you’d need hardware and software.  You’d have to define access and security, set up reports and analytics, and then  actually build the app. If you wanted the app to be mobile and social, you’d  have to do some work to set that up, too.
    • Since we’re talking about the API, let’s take a moment to talk about API names and make sure you  understand what those are. The API name is a unique  identifier that the platform uses to determine what data or metadata you are trying to  access. In the example we’re working with right now, we’re going to use your full name,  and the unique API name for  your full name is Name. Simple enough, right?
    • And if you’re not a programmer, hopefully the examples we’ve shared will show you that APIs are for everyone,  including you!
    • Speed up the  onboarding process with a custom onboarding app. Using the platform, create a  series of objects and automated processes to manage all of the steps needed to  onboard a new employee. This could include
    • Simplify the IT help desk ticketing process by building on the same platform as your CRM.  Use custom objects, or customize cases to manage internal service requests from  employees. Assign work to queues and use Chatter to collaborate on  requests, and track everything in Salesforce. This could  include:
    • Getting Started with the Platform
    • but it also includes the platform, where customers and partners can use our  suite of technologies to build amazing, connected apps.
    • Market to your audience


      ExactTarget Marketing Cloud to manage your customer’s  journey
    • With clicks or code, you can customize  anything, and what you customize connects to your standard functionality in Salesforce. The platform is your  secret sauce that can help you make your vision a reality.
    • Manage internal project requests


      Custom objects for managing projects
    • Lightning Components and Lightning App Builder for  creating an employee app
    • Heroku for creating a customer-facing app
    • Force.com


      The suite of configuration tools and programming languages  and APIs  native to Salesforce,  including Apex  and Visualforce

      A set of fields, objects, permissions, and  functionality to support a business process
    • The first rule of the platform is don’t be intimidated by the term “platform,” especially  if you’re coming from a non-programmatic background. Think about it like this: any time  you’re customizing in Salesforce, with clicks or code, you’re using the platform.
    • They’re  having trouble finding the phone number fields at a glance, and they want a  place to mark which phone number is preferred.
    • With point-and-click tools, you can  create a custom field for preferred phone number, and add a new section on the page  layout [1] just for phone numbers and your new custom field.
    • The platform makes database and user interface customizations simple, like in this Lead example,  and also makes complex backend logic and completely customized pages possible with  programmatic tools like Apex, Visualforce, Lightning Components, and  more.
    • Declarative refers to point-and-click functionality in Salesforce. It means that you  can configure and customize Salesforce without writing code.
    • Programmatic refers to code-driven functionality in Salesforce. It means that you  can customize Salesforce using  programmatic tools like Apex, Visualforce, and Lightning, and standard web  technologies like JavaScript, CSS, and more.
    • Schema Builder


      Customize objects and create relationships between  them using drag-and-drop tools in Schema Builder.
    • Apex


      Develop with an object-oriented, Java-like programming  language that’s optimized and tuned for accessing Salesforce  database objects.
    • Visualforce


      Define user interface components and construct visual  elements using a markup language similar to HTML, thus allowing the  user to interact with and modify data from the database.
    • Lightning Components


      Develop dynamic web apps for mobile and desktop devices,  using a modern, component-based UI framework.
      • visual force is dying, this ‘component-based’ framework is the future
    • the golden rule  is to always try to build with clicks before going to code, as it is more  sustainable and maintainable moving forward. Code is meant to give you more  granular control of customization when clicks aren’t enough.
    • ust means  that the best admins and developers have a good understanding of both worlds, even if  they only choose to live in one.
    • In Salesforce, an app  refers to a set of objects, permissions, and functionality to support a business  process. For example, if you’re having an event and you want people to sign in, you  could have a paper sheet with columns for Attendee Name, Title, Company, and Email, and  you could have attendees sign in with a pen. Or you could create an Event app in Salesforce. The sheet becomes an  object (‘Event’), and those columns become fields (‘Attendee Name’, ‘Title’, ‘Company’,  ‘Email’) on the object.
      • simple app to show where items are in the process
      • If the data is in Salesforce, you can:




        • Get real-time access to data as it’s entered, via mobile or desktop.
    • Relate attendees to marketing campaigns and sales information, including  order and purchase information.
      • pipeline and ROI
    • Create automated processes to engage with the attendees over time.
      • content marketing, marketing automation
    • Let’s create a fundraising app that can be used to track events for a charitable  organization.
    • Wait a second, did someone just say “mobile-ready experience”? That’s right! What you  just built is ready to go for mobile.

Posted from Diigo. The rest of my favorite links are here.

Categories: Uncategorized
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: